MiniB3D

BlitzMax Modules Forums/MiniB3D/MiniB3D

The forum is locked. These are the original blitzbasic.com forums, kept so they can still be read. No new topics, replies or edits can be made here. To join in, head over to the Blitz3D+ forums.

Si - I've not looked at this at all so apologies if you've already done this - you could amend all your functions / methods to use "NoDebug", this would improve matters for debug mode performance.

I wasn't aware you could do that - thanks for the tip!

Thanks for the info. Turning debug off makes a lot of difference, but loading a dwarf warrior (medium complex model) still takes about 35 seconds (on my 1 GHz G4), so any optimization is welcome. ;)

35 seconds sounds like an insanely long time! Even with debug mode on, it takes 1 second at most here and I only have a 1.7Ghz CPU. Did you mean 3-5 seconds perhaps? (I hope!).

Loading the file into memory and parsing it there would give a major speedup

It would? I'll have to try that, thanks.

What do people think would be the best way to handle camera frustum culling

A camera culling system exists in 0.3, using bounding spheres. It works fairly well, although I really need to change it to bounding boxes (which is what B3D does).