I wonder if somebody could do a simple test for me
get a cube
select all polygons and subdivide them (ctrl+d) to, say, 20k polys
zoom in to cube so you will see only few polygons covering whole view
activate tweak tool
how many FPS do you have?
because here it drops to even 2 fps and highlighting is very slow, and I'm wondering if its my computer...
tweak tool highlighting performance
- bottleofram
- Posts: 355
- Joined: 17 Aug 2010, 11:21
Re: tweak tool highlighting performance
Same here. Now we know why we dont have pre-selection highlighting on regular selection tools.
Re: tweak tool highlighting performance
hehe ;)
thanks for confirmation
I made small (lame) patch in my extrude tool and now its highlighting up to 60x faster then tweak tool
thanks for confirmation
I made small (lame) patch in my extrude tool and now its highlighting up to 60x faster then tweak tool
Re: tweak tool highlighting performance
Same fps here. No idea why, but the tweak tool doesn't seem to use the component id buffers (the ones you can see by accident when antialiasing is on in the display driver settings, see attachment).
Maybe it's because it would need all 3 buffers (for polygons, edges and points), which would use a lot of video ram. Then again video ram is usually pretty big nowadays.
Maybe it's because it would need all 3 buffers (for polygons, edges and points), which would use a lot of video ram. Then again video ram is usually pretty big nowadays.
- Attachments
-
- pass.gif (62.19 KiB) Viewed 1429 times
softimage resources section updated Jan 5th 2024
Re: tweak tool highlighting performance
dunno..actually picking in custom tool is quite fast (4 picks for object, points, edges and faces takes up to 40ms on 2 million poly mesh)
and since tweak tools gets slower on faces selection, I believe it's picking in similar way as custom tool picking.
btw: http://www.opengl.org/resources/faq/tec ... ection.htm
glreadpixels was raped on geforces cards by nvidia some time ago to milk cash on quadros...
and http://www.opengl.org/wiki/Common_Mista ... dback_Mode
anyway, I managed, with this weird piece of code, get huge performance boost (way faster than tweak tool, for example 0.1 fps(tweak) vs 10fps(my), or 4 fps vs 100fps)
I wonder if there are any drawbacks with this 'method' and WHY is it working. Basically you slow down refreshing and you get...better performance.
and since tweak tools gets slower on faces selection, I believe it's picking in similar way as custom tool picking.
btw: http://www.opengl.org/resources/faq/tec ... ection.htm
glreadpixels was raped on geforces cards by nvidia some time ago to milk cash on quadros...
and http://www.opengl.org/wiki/Common_Mista ... dback_Mode
run tweak tool = 1 core is maxed out.A modern OpenGL program should not use the selection buffer or feedback mode. These are not 3D graphics rendering features yet they have been added to GL since version 1.0. Selection and feedback runs in software (CPU side). On some implementations, when used along with VBOs, it has been reported that performance is lousy.
A modern OpenGL program should do color picking (render each object with some unique color and glReadPixels to find out what object your mouse was on) or do the picking with some 3rd party mathematics library.
anyway, I managed, with this weird piece of code, get huge performance boost (way faster than tweak tool, for example 0.1 fps(tweak) vs 10fps(my), or 4 fps vs 100fps)
I wonder if there are any drawbacks with this 'method' and WHY is it working. Basically you slow down refreshing and you get...better performance.
Code: Select all
#define MOUSE_MOVE_TIME_DELAY = 3; //0-10..or whatever number (miliseconds)
...
CStatus MouseMove( ToolContext& in_ctxt )
{
CStatus l_status;
in_ctxt.GetMousePosition( m_mouseX, m_mouseY);
clock_t now=clock()-m_tooltime;
if (now>MOUSE_MOVE_TIME_DELAY) {
l_status=GetPickData(in_ctxt,m_mouseX,m_mouseY,m_pickedSubcompPos);
in_ctxt.Redraw(false);
m_tooltime=clock();
};
return CStatus::OK;
}
Who is online
Users browsing this forum: No registered users and 16 guests