Bigger the CSG slower it gets?

[Andy Gilbert]

Whilst porting my flight code over, for a terrain ive been using a single CSG box as a ground plane.

 

But ive noticed the bigger i make it, the longer loading and slower it gets why is this?

 

Making a really big single CSG box makes my project lock-up at runtime for a good 20 - 30 seconds before it comes back to life. What is it doing?

 

Make it small and it loads faster, make it smaller again and it loads instantly.

 

Andy

[shadmar]

I have noticed aswell.

[beo6]

noticed that too when i tried to use a big box for a background image because i can't find a way to draw an image behind the world because it always draws black where nothing is.

[Admin]

Navmesh generation may be slowing it down. Navmesh generation is presently completely dynamic, which is fine for small scenes but slow for larger ones. In order to accommodate larger worlds with terrain, navmeshes are going to be generated in the editor and saved, in a new dialog that will appear in the next update. This also provides extra control over a few parameters the routine uses.

[Andy Gilbert]

Ok. Is or will there be an option to not use navmesh at all?

 

Andy

[Admin]

If you don't calculate a navmesh, none will exist.

[Andy Gilbert]

I'm not telling it too? I assume the editor automatically does this? How would I tell it not to when using the editor and lua and running the project from within the editor?

 

Andy

[Admin]

I mean in the next update, it will be something you let build in the editor.

 

You can set the brush's navigation mode to false and then the navmesh won't get built for it.

[Andy Gilbert]

Ahh i see. Sounds good and look forward to it.

 

Andy