BVE WorldWide
Would you like to react to this message? Create an account in a few clicks or log in to continue.

should default option for object optimization mode in object viewer is low or high instead none ?

2 posters

Go down

should default option for object optimization mode in object viewer is low or high instead none ? Empty should default option for object optimization mode in object viewer is low or high instead none ?

Post by ADbve Wed Jul 14, 2021 1:34 am

hello

yesterday i tested my addon with object viewer that contain 100.000 vertex and some 1K texture without using alpha channel, when i test using none and low mode the fps is around 8-13 fps with around 55000 opaque faces detected but when i use high mode the fps jump to 100-120 fps, that a lot performance boost isnt it? so i wonder if should the default option is high or low not none.

see image below for comparison
*none and low mode is make same fps and faces detected result
should default option for object optimization mode in object viewer is low or high instead none ? Annota12
should default option for object optimization mode in object viewer is low or high instead none ? Annota13 

but why on high mode opaque faces detected is so low ? although the total opaque faces not effecting the mesh visually.

ADbve

Posts : 22
Join date : 2020-05-14

Back to top Go down

should default option for object optimization mode in object viewer is low or high instead none ? Empty Re: should default option for object optimization mode in object viewer is low or high instead none ?

Post by leezer3 Thu Jul 15, 2021 6:47 pm

I'd suspect (without seeing the model) that high object optimization has managed to combine most faces & junk a bunch of duplicate vertices.

If opaque & using the same material / properties, faces can be combined into a single contiguous draw call. This however takes time, and in Object Viewer may not be the best idea if the object is being repeatedly reloaded, hence why it's set by default to off.

Other thoughts-
GL3 is likely to be an order of magnitude faster with this many vertices.
I would also strongly suspect you don't require 1k textures. Look at the size your texture ends up when rendered to screen. If you're worried about blurriness when downsizing, just use a decent resample algorithm (after all that's all GL is doing internally)

leezer3

Posts : 1785
Join date : 2011-08-23

http://www.bvecornwall.co.uk

Back to top Go down

Back to top


 
Permissions in this forum:
You cannot reply to topics in this forum