Ramikad

The only thing I can think of that could cause this error would be that you just selected part of the mesh and unwrapped only that part. Make sure you select everything in the mesh (press A until everything is selected in Edit Mode) and try again. Other than that, I don't know.

Warhammer 40,000: Rites of War is free on GOG until 19th July 2020, 1 PM UTC.

I'm speechless.

From what I remember you can just have it extended and tick the start_open option - that should illuminate the bridge because it's technically physically there when compiled. Not 100% sure it works though, but I think I did it this way a few times.

I generally make them usable func_door entities - they're simplest func_ entity with an already integrated basic movement, so they're pretty much flexible enough for me to use them as doors, bridges and elevators, anything moving on a straight line really. Otherwise you can have them as func_static (maybe with an origin brush too, not sure if it was needed or not) and move them through script.

Personally I've been experimenting with Blender: It doesn't look very good from up close, but I think it can be improved with shaders. The only real problem is that those terrains, being solidified models, don't render grass sprites. For the record, at least the top screenshot spans 3.5 km from side to side, about 5 km from corner to corner.

I personally prefer to use 1.5 for that very reason: vertex manipulation is painful in 1.4 and 1.6. Also, I remember trying 1.3.12 (I believe) once, and I absolutely despised that you basically couldn't scale groups of models as you easily can in 1.5 - not even sure if they were scaled at all. On the other hand, I rarely use one of the latest Radiant versions because (unlike 1.5 - and that's my only gripe with it really) it allows very large maps - 1.5 cuts them off at about +/- 32000 units from the center. As for invisible brushes, I did fall for them a few times in the past, but it's an easy fix once you get the hang of it.

Yeah, lowering blocksize to 0 isn't necessarily good for every map, but since there's no real need for VIS in this one I figured he may as well take it out entirely. There's only literally the two corridors to the sides that could cull parts of the map, and the geometry overall isn't that complex as to require VIS.

Simply select any worldspawn brush and type in blocksize 0 (setting the blocksize value to 0).

Just tested it - I misinterpreted it. This bug isn't caused by duplicate brushes - it seems to be related to some strange VIS stuff as NAB622 suggested. I tried to compile the map you posted, and it did create that bug. I reduced the blocksize to 0 (in the worldspawn), made everything detail brushes (except for the "outer shell"), compiled it and the bug was gone.

That's puzzling. To my knowledge only a few things can cause the bug you're describing: - An actual leak - but this is not the case, as the compiler doesn't return any sort of error on this matter; - A brush with a mirror shader - if the mirror doesn't have any entity and camera to go with, it will show a similar effect to that; - Two brushes, one overlapping the other: it seems strange though that you couldn't find anything - make sure you didn't hide the brush beneath it (accidentally hitting the H key); make sure that you didn't make it a detail and filtered it out (CTRL + D); and make sure your filter list (View -> Filter) is clean, so that everything that's there is shown. What suggests me that it's actually another brush overlapping it is that you said you tried to recreate it with the same results - that shouldn't happen. Other than that, I don't know. One last thing you could try would be to move all your map by a little in any direction - say 128 units (a random number) - and see if that changes anything.

Easiest way would be to look at this sort of bug / invisible brushes in-game - that's what generally duplicate brushes cause. That at least helps narrowing down the area where to look for them.

Make sure that there aren't any duplicate brushes in that area - if there was a leak it would return a ton of errors, and duplicate brushes aren't really visible in Radiant.

Not sure, but probably Naboo Streets. Stuff like the domes and the details on the bridges seem to match.

Unless we're talking hundreds of edges I'd manually split them, to make sure - the modifier may have missed some. Select the mesh, enter Edit Mode, switch to the UV / Image Editor, tick Keep UV and edit mode mesh selection in sync (right of the Rotation / Scaling Pivot), then manually select all edges of the islands, return to 3D View, then Mesh -> Edges -> Edge Split. That should solve it, splitting any edge that the modifier didn't.

Eye of the Beholder Trilogy is free on GOG until 19th June, 5 PM UTC.

You can try selecting the mesh, entering Edit Mode, then Mesh -> Clean up -> Delete Loose ticking Vertices only. Not sure this will fix it though, but it might.

The solution here would be to go through the UVmap of the mesh which causes the error, then tick the option to "Keep UV and edit mode mesh selection in sync" (left of the selection modes), select all the seams that make up the "islands" (the "perimeters" basically), then go back to 3D View and select Mesh -> Edges -> Edge split. That does exactly what the program asks you to do - splitting meshes at UV seams - and should fix the problem.

Can't be sure - make sure to check mrwonko's site as Lancelot suggested, as well as this section and subcategories - but I don't think anyone has ever made a coop map like the one you're describing.

Snake Pass is free on Humble Bundle while supplies last or until June 14, 2020 at 10:00:00 AM PDT.

Total Annihilation: Commander Pack is free on GOG until 7th June, 1 PM UTC.

I believe he means in multiplayer - it returns an error about "bad or missing bones, or missing animation" and displays as Kyle. Not sure what causes it in this specific case, since it's clearly rigged to the humanoid skeleton.

Most likely, the parented objects don't disappear, but are moved and scaled around the place: one way you could minimize the issue is to apply location, rotation and scale of the object (CTRL + A? that way, when you parent it to another object, for example a part of a base model, it will take on the location, rotation and scale of the parent object - in the aforementioned case of the base model part, it will be scaled to 1/10th of its size. You can then just scale it back (S 10) and apply object scale (CTRL + A). As for the other problem, make sure that the newly added objects all have a name under Ghoul 2 Properties (in the Object menu), that they all have an Armature Modifier (in the Modifiers menu) named skin and with the skeleton_root armature set as Object, and that the object is properly weighted (which you can verify in Vertex Groups under Data). Basically, the gist of weighting is that you want to link each vertex of the added model part to the bone you want it to move with. You can either do it manually, by entering Edit Mode, selecting the vertexes and assigning them to a specific vertex group (which you can do in Vertex Groups under Data), or you can select the object, enter Weight Paint mode, select a specific vertex group and paint over the object. Vertex groups are named after the bones of the model skeleton: if there isn't any in Vertex Groups, you can simply add them, making sure that the names are correct. When exporting you want to make sure that every vertex is weighted - a good test of this would be to select the skeleton_root, enter Pose Mode, then select all the bones (A) and move them around. If everything is weighted there will be no vertexes warped towards the origin. Also make sure that you're in Object Mode, not Edit Mode, I seem to remember it turned up a lot of errors when I tried it once.

I think this picture tries to explain the mysteries of going up and down Cloud City: