Author Topic: please optimize your code  (Read 1423 times)

gabrielefx

    Reputation: 6
please optimize your code
« on: February 18, 2011, 03:25:50 pm »
February 18, 2011, 03:25:50 pm
I think that Lumion needs to be reprogrammed from scratch with c++ code because if it works like Quest all calls and functions basically are scripts, that's why its interface is so slow.

I have a good workstation at my studio, dual xeon, Quadro CX (waiting for 580 Phantom 3G), 16Gb, etc.

Now I'm working with a very complex scene and it's really difficult to select objects, I have to click several times before do a simple selection

I have 16 imported big blocks of geometries. The Quadro works perfectly but the Lumion interface is sleeping...

 

Best regards
« Last Edit: January 01, 1970, 01:00:00 am by modifiedName »

please optimize your code
« Reply #1 on: February 18, 2011, 03:53:41 pm »
February 18, 2011, 03:53:41 pm
I am glad you know why it is slow thank you for the tip!

 

Also we made the interface more responsive since rc5.
« Last Edit: January 01, 1970, 01:00:00 am by modifiedName »

please optimize your code
« Reply #2 on: February 18, 2011, 03:56:14 pm »
February 18, 2011, 03:56:14 pm
gabrielefx said:



 Quest all calls and functions basically are scripts, that's why its interface is so slow.




Quest3D generally uses binary components (compiled C++) not script. Most of the heavy processes in Lumion are HLSL shaders.


You can speed up the editor by selecting 2 star modus and a lower resolution using the resolution slider in the setting menu.
« Last Edit: January 01, 1970, 01:00:00 am by modifiedName »

please optimize your code
« Reply #3 on: February 18, 2011, 04:02:39 pm »
February 18, 2011, 04:02:39 pm
Gabriele, I think you have misunderstood something. Channels in Quest3D (which are also used in Lumion) are not scripts. They're actually compiled native C++ code from Visual Studio and are executed very very fast, so it makes no sense to claim that Lumion (and by extension, Quest3D) need to be "reprogrammed from scratch with C++ code".

As I already mentioned in my reply to one of your earliest posts, the Quadro CX card you're using is far from ideal for use with Lumion. If you check out some 3D benchmarks you'll notice that they are comparable to ATI 38xx cards, so you've done the right thing by ordering the 580 Phantom card! Smile

Regarding the responsiveness of the interface, it is indeed affected by low frame rates but as Ferry mentioned the UI responsiveness has in fact been improved recently, although one of the button types (Modify Object -> Menu) had somehow escaped from this treatment. It has been fixed in the next update though. And as Arthur already said, you can adjust the Star modes and the resolution slider in the Home section to improve your frame rate.
« Last Edit: January 01, 1970, 01:00:00 am by modifiedName »

tug

    Reputation: 28
please optimize your code
« Reply #4 on: February 18, 2011, 06:45:01 pm »
February 18, 2011, 06:45:01 pm
HI gabrieleb

 

I'm also using more or less the same configuration, Dell T5400 2xQuadCore, Nvidia 4000 2Gb and 16 Gb Ram, the interface in lumion sometime seems be sleeping as you said and is a little maddening have need picking several times in the model to do anything.

 

Ferry said he developed a new code to solve this issue in next candidate RC7, I hope so.
« Last Edit: January 01, 1970, 01:00:00 am by modifiedName »

please optimize your code
« Reply #5 on: February 18, 2011, 07:28:01 pm »
February 18, 2011, 07:28:01 pm
The Quadro 4000 is based on the same chip as GeForce 4xxx series. It's super fast for CAD applications (SPECview benchmark), CS etc but I don't think it's that great for Lumion (and other real-time 3D engines). At least if this 3DMark Vantage benchmark where they compare it to the ATI 5870 is correct.

For comparison, Gabriele's Quadro CX is about 50% faster than a GeForce 9600 GT 512MB in the 3DMark Vantage benchmark, so an upgrade is not a bad idea.
« Last Edit: January 01, 1970, 01:00:00 am by modifiedName »