|
Post by Medusa on Aug 22, 2011 16:18:22 GMT
This error:
Too many vertex format changes in frame, whole world not rendered
Is it true that this is caused by having the bottom brush that seals my map from the void being textured with the Skybox texture (which was in turn being covered up by another brush that acted as the ground for the map) ?
|
|
|
Post by Zeph on Aug 22, 2011 16:36:52 GMT
Probably not to the second bit. But the fact you have a skybox on the floor suggests a badly made skybox in the first place. Let me guess, is it a huge box around your map?
Is it possible to have the full compile log (set all three options to "normal").
If you are running "fast Vvis = true", then it's not doing a good job at splitting up the inside of your map into volumes (called VisLeafs). This would mean that a lot of the map is inside a few VisLeafs, meaning a lot of vertex info in one frame. If running Vvis = normal, and it takes AGES (especially on PortalFlow) then it's because your map is not optimised fully, and further help can be given (even if the help is the dreaded "start again").
|
|
|
Post by Medusa on Aug 22, 2011 17:25:47 GMT
Thanks, Zeph. No, there is not skybox around my map. I think you've inadvertantly answered my question; I am compiling it on fast because because I want to do quick run throughs and make sure there aren't any MASSIVE issues. hehehe.
Anyways, so do you think if I compile on Normal, these might go away?
I really do appreciate your input.
-M
|
|
|
Post by Medusa on Aug 22, 2011 17:27:14 GMT
Also, BTW, This error is just spammed in console. My map actually loads and runs beautifully (I've finally harnessed those the darn use of hints ha!)
|
|
|
Post by Zeph on Aug 22, 2011 18:55:28 GMT
I don't think it'll disappear on Normal, but the compile log may help to finding the cause.
Hints are not the main optimisation feature. They should be used rarely when visleafs are auto-generated in a non-optimised way, to force them to be generated in a way you wish.
Do you know how to Func_Detail? This is by far the number one optimisation feature you can perform.
The reason i drone on about it is it's highly likely the cause of the error.
|
|