Quote: "(edit) I made it use planes and cull any planes that wouldn't be visible and you know what happened? The framerate dropped even though the polycount went WAY down. What's up with that? however, I'm not culling the planes that are up against other planes yet."
This is probably because DBPro runs slower the more objects you have, a solution would be to create the plains as limbs to one or a few main objects, leaving you with a low object count and a low poly count, which should give you an increase in speed.
Here is an example program I made to demonstrate:
sync on : autocam off : hide mouse
randomize perftimer()
for o=1 to 1000
cls
make object plain o,1,1
position object o,rnd(500)-250,rnd(500)-250,rnd(500)-250
set object radius o,-1
print "creating object "+str$(o)
sync
next o
do
text 0,0,str$(screen fps())
rotate camera camera angle x()+mousemovey(),camera angle y()+mousemovex(),0
if spacekey()=1
if pressed=0 then exit : pressed=1
else
pressed=0
endif
sync
loop
for o=1 to 1000
cls
delete object o
print "deleting object "+str$(o)
sync
next o
for t=1 to 4
make emitter t,1
set object cull t,0
next t
make object plain 5,1,1
make mesh from object 1,5
delete object 5
for t=1 to 4
for o=1 to 250
cls
add limb t,o,1
offset limb t,o,rnd(500)-250,rnd(500)-250,rnd(500)-250
print "adding limb "+str$(o)
sync
next o
next t
do
text 0,0,str$(screen fps())
rotate camera camera angle x()+mousemovey(),camera angle y()+mousemovex(),0
if spacekey()=1
if pressed=0 then exit : pressed=1
else
pressed=0
endif
sync
loop
end
Notice the command "set object radius o,-1" used when creating the objects, this is because without using this command it would go faster with 1000 object because of the automatic culling system.
I don't have Wolfenstein so I can't check it out but it looks cool so far.
DBPro, limited by the programmer.
