What do you mean by "it doesn't compile properly"?
[QUOTE=IronPhoenix;35522172]What do you mean by "it doesn't compile properly"?[/QUOTE]
It's a bit hard to explain. It does not compile certain brushes at random, nor does it compile the lighting properly.
[QUOTE=Doom;35523953]It's a bit hard to explain. It does not compile certain brushes at random, nor does it compile the lighting properly.[/QUOTE]
You are still being really vague. Add images, show what you mean.
The issues have changed, I know have the following problems:
1. Props are not spawning
2. Some decals and overlays are not spawning (Certain surfaces has no decals, even though the map still shows no errors)
If the issues have changed, provide an up to date compile log and images. Give us as much info as you can, it is no good being vague about the problem.
maybe it's because you func_detailed a displacement. read your compile log thoroughly.
If you see in your compile log:
[quote]
overlays 440/512 154880/180224 (85.9%) VERY FULL!
[/quote]
Your overlay count is very full, although not at 100%. It's possible that because you have so many/use so much of the allotted space, some overlays do not spawn as you state. Try taking some away so you don't get the VERY FULL! and see how it works.
Good luck!
[QUOTE=Prez;35548852]If you see in your compile log:
Your overlay count is very full, although not at 100%. It's possible that because you have so many/use so much of the allotted space, some overlays do not spawn as you state. Try taking some away so you don't get the VERY FULL! and see how it works.
Good luck![/QUOTE]
Yeah, I noticed that too, but it still has 14.1% to go, so I didn't think that was an issue. I'll try to fix that and see if it changes anything, overlay wise, but I don't see why it should affect my props. I'll try to find the func_detailed displacement and fix that too.
No it isn't
fix the bloody error:
Error: displacement found on a(n) func_BRUSH entity - not supported (entity 725, brush 0)
Yeah, I found that a bit after posting, it is already fixed :)
Reason why I thought it already was fixed is because both me and my partner has fixed it at some point, but we have several versions of the map, so I must've used one that did not include the fix. I've deleted the rest so we have one file to develop, a backup and a serverfile.
Sorry, you need to Log In to post a reply to this thread.
