So i saw the same forum post and i think that its not misleading but not the full story. It appears to me that the new engine is slightly faster in the fps or video portion but the managing of geometry is slower. The video here orbits widely around the model but not through it and its not a heavy model already. FPS goes through the floor when dealing with heavy models (maybe worse than 23) and even just selecting heavy geometry (as in left click, mouse down to the right or in reverse - left click and up to the left) often pauses for me in the new engine to select raw geometry much less manipulating that geometry - which seems to be much slower. The new qt framework is a wrapper and in that way a middleman and when you have to convert into the wrapper, you lose time for the conversion but its much easier for the devs to maintain one codebase then coding natively to the hardware. Hopefully Trimble can speed up the managing of geometry or how the geometry gets managed portion of the code.
I tried Test.time_display on that 5 mil poly cafe scene with everything turned on, including Ambient Occlusion..you're right model level of detail affects the FPS result. For this 'heavy model', I'm still running at 68 fps with new graphics engine....vs 7.4 with the old graphics engine.
@@SketchUp Im probably not be being clear. Yes the viewport itself is more performant than 23, at least slightly but... Anything (the part of the code) that deals with managing the actual geometry is less performant. Your test is fast because you are away from the geometry and it was a small model and the camera was not in and around the model. Did you test in the coffee shop with textures on? What is that fps? nowhere near the first model I'll bet. Being inside the geometry and having the test orbit from inside the building crushed my fps compared to being away from the geometry and having it orbit around. Separately, Selecting geometry and manipulating geometry seems slower than 23. Box selecting is now painfully slow most of the time and well worse than 23 and I don't believe this is related to the viewport but in how the code handles geometry manipulation. In aggregate, the engine seems only slightly faster in viewport but also slightly painful where I need it... Managing and manipulating the geometry. Also, turning off ambient occlusion speeds it up a bit better but again doesn't really help with box selecting and/or managing the geometry itself. To me, it's a bit of a 1 step forward 1 step back to me so far. Hopefully Trimble can get the new qt engine under superior control...
Fun fact, the Test.time_display thing can be done in any of your file. If you want to benchmark your own files, do it like he did, open in 22 or 23, test, open in 24 with similar parameters, test again. got some old big files to go from 7 to 30+ fps. it's a good code bit to have in your head when working, sometimes you feel sketchup is getting slower, like it's running in water. the test can immediately tell you if that's the case.
Hi. I modified the vines that came with this model from the 3DW - 3dwarehouse.sketchup.com/model/3c47c0a5559b1f9440a932c8e4de67d8/Garden-by-The-Bay-Supertrees?hl=en
Thanks Eric! Looks great! Looking forward to upgrading my computer so I can try it out. Best, Steve
So i saw the same forum post and i think that its not misleading but not the full story. It appears to me that the new engine is slightly faster in the fps or video portion but the managing of geometry is slower. The video here orbits widely around the model but not through it and its not a heavy model already. FPS goes through the floor when dealing with heavy models (maybe worse than 23) and even just selecting heavy geometry (as in left click, mouse down to the right or in reverse - left click and up to the left) often pauses for me in the new engine to select raw geometry much less manipulating that geometry - which seems to be much slower. The new qt framework is a wrapper and in that way a middleman and when you have to convert into the wrapper, you lose time for the conversion but its much easier for the devs to maintain one codebase then coding natively to the hardware. Hopefully Trimble can speed up the managing of geometry or how the geometry gets managed portion of the code.
I tried Test.time_display on that 5 mil poly cafe scene with everything turned on, including Ambient Occlusion..you're right model level of detail affects the FPS result. For this 'heavy model', I'm still running at 68 fps with new graphics engine....vs 7.4 with the old graphics engine.
The box/cross selection is slow no matter how big the file is. Maybe my computer is throwing it out
@@SketchUp Im probably not be being clear. Yes the viewport itself is more performant than 23, at least slightly but... Anything (the part of the code) that deals with managing the actual geometry is less performant. Your test is fast because you are away from the geometry and it was a small model and the camera was not in and around the model. Did you test in the coffee shop with textures on? What is that fps? nowhere near the first model I'll bet. Being inside the geometry and having the test orbit from inside the building crushed my fps compared to being away from the geometry and having it orbit around. Separately, Selecting geometry and manipulating geometry seems slower than 23. Box selecting is now painfully slow most of the time and well worse than 23 and I don't believe this is related to the viewport but in how the code handles geometry manipulation. In aggregate, the engine seems only slightly faster in viewport but also slightly painful where I need it... Managing and manipulating the geometry. Also, turning off ambient occlusion speeds it up a bit better but again doesn't really help with box selecting and/or managing the geometry itself. To me, it's a bit of a 1 step forward 1 step back to me so far. Hopefully Trimble can get the new qt engine under superior control...
@@ivc_studio8925 same with me, it's consistently lagging when I do it. I suspect they will get it managed over time...
I still using an older version 21, but...
I think if nothing added to SU2024 other than AO and GPU rendering it would be enough.
Thanks Eric!
Thanks Eric! Looks great. Looking forward to upgrading my computer and adding SU 24 so I can try this. Best, Steve
Fun fact, the Test.time_display thing can be done in any of your file. If you want to benchmark your own files, do it like he did, open in 22 or 23, test, open in 24 with similar parameters, test again. got some old big files to go from 7 to 30+ fps.
it's a good code bit to have in your head when working, sometimes you feel sketchup is getting slower, like it's running in water. the test can immediately tell you if that's the case.
Hi Eric, what did you use to create the creepers at the corners of the cafe? Regards.
Hi. I modified the vines that came with this model from the 3DW - 3dwarehouse.sketchup.com/model/3c47c0a5559b1f9440a932c8e4de67d8/Garden-by-The-Bay-Supertrees?hl=en
@@SketchUp Thanks, Eric! Please keep up your great work. One learns a lot from the videos you guys produce.
Anyone notice the lag on box selection? So annoying. Everything else is smooth
Yeah it is definitely faster
Sweeeeeet!