wolfenstein enemy territory pure server check fail

WOLFENSTEIN ENEMY TERRITORY PURE SERVER CHECK FAIL .DLL
WOLFENSTEIN ENEMY TERRITORY PURE SERVER CHECK FAIL PATCH

The maximum number of facets allowed is 65,535. You've got too many spheres and/or cones in your map. Usually means you have a really complicated complex brush in your map, thats not allowed! you need to make it less complex!ĮRROR: MAX_FACETS during vlight (maxfacets >= 65XXX) Your map has a leak somewhere that needs to be fixed. This error is caused by another.ĮRROR: LoadPortals: couldn't read c:progra~1ravenstartr~1baseEF/maps/unnamed.prt The vis stage of your compile was unsuccessful.

WOLFENSTEIN ENEMY TERRITORY PURE SERVER CHECK FAIL .DLL

dll must be put in the plugins directory, and you must be using a version of xxBuild that is compatible with the editor.ĮRROR: Error opening c:progra~1ravenstartr~1baseef/maps/purectf.bsp: No such file or directory Look for long, thin brushes and clip them (Shift-Enter) into multiple brushes to get rid of the error.ĮRROR: DispatchBSPCommand failed with a COM exception This error often occurs when there are just too many vertices on a brush. Make sure that you place the start position on a floor made out of a solid texture and that it isn't too close to a wall.ĮRROR: ClipWindingEpsilon: 90 > MAX_POINTS_ON_WINDING The two most common are start position in the void or start position on a floor with a detail surfaceparm. This error can be caused by several problems. Revert to an older version of your map in the snapshots folder until it goes away. You can usually ignore it.ĮRROR: Allocwinding: failed to allocate winding This just means that one of your brushes has different textures on two or more sides. This means you have a hint brush or area portal set as detail. Do a search for the offending brush and clip it (Shift-Enter) into multiple brushes to get rid of the error.Įntity 0, Brush 0: mixed CONTENTS_DETAIL and CONTENTS_STRUCTURAL In EFRadiant, click Plugins, Rogue Brush Repair, Remove duplicate planes. It is generally best to avoid this, but it is technically okay to leave it as it is. While this error isn't necessarily a vital problem in the compile process, it can cause some weird visual side effects as you basically have a double-sided texture. When you were editing a brushes vertices, at some point you dragged the vertices in such a way that the two planes opposite each other were in the same place. from the Misc menu and search for the brushes with those errors. If you still get this error, increase the value to 4 and it should fix it.Įntity 0, Brush 0: degenerate plane/mirror plane/bad normal The shadows won't look as sharp, but at least the map will run. To do that, go to your worldspawn entity and add in key: '_lightmapscale' value: '2'. To fix it, you just have to lower the resolution of the lightmaps in your map.

This error occurs when the lightmaps in your map are just too complex and/or large for the EF engine to handle.

WOLFENSTEIN ENEMY TERRITORY PURE SERVER CHECK FAIL PATCH

Also you might of manually rotated a patch and its went all funny, best not to rotate patch meshes manually (by using rotate and then move the mouse around to move them) You can use Bob Toolz brush cleanup to get rid of these in some situations, in other situations you might have to search your map file (in notepad) and look for decimal points (in the first 3 numbers in the brackets) and round them off (get rid of the decimal point).

Usually means that you can't see it in the editor, but can in the map (in game). You've got a mesh too close to the sky box.Ī brush has a dodgy face. Apparently, there was a version of bspc that caused that problem but was fixed with an update. Very useful information here, great work done by bieria.Įxtremely high walls cause this problem for some reason. Urban Terror uses the Quake III engine and so this list of Gtk Radiant errors will apply to RtCW as well. Credit to user bieria, this list was created by them on the Urban Terror Forum.

Wolfenstein enemy territory pure server check fail