Edit:Alpha-Map bug or not? And more questions about cloning.

[Humpti]

Do you have this behavior with any kind of scenes, for example a scene with only one cube or sphere? ... Please, open the Layout, enable Octane and load a cube. Do you have problems moving this cube or the camera while the IPR is rendering, with the display GPU priority set to low?

I tested a small scene like you said and also a few scenes provided from Octane. They are fast and fluid. I was so fixed on the tree that I forgot to test that, sorry

But why is a (polygon heavy) tree soooo slowing down the ui? Is it because of the many alpha maps that are used for the leafes?

I'll switch the cards to try it out and report back. Could this be a demo thing like with LW and the 3DConnexion Mouse? (which works fine now with the full version of LW)

Cheers
Philipp

[juanjgon]

I don't think that the demo version could be the problem. How many polygons have your tree? ... if you want to send me the scene by pm I could test it here. I have a laptop with only a GT650 GPUs, something like your GT640 to make some tests.

Perhaps the problem is that Octane needs a lot of time to render the first sample due to the clip maps. Can you please enable the "Half Res" option or the clay rendering in the IPR to see if Layou works faster?

-Juanjo

[Humpti]

Jesus, how long are you working??

Perhaps the problem is that Octane needs a lot of time to render the first sample due to the clip maps. Can you please enable the "Half Res" option or the clay rendering in the IPR to see if Layou works faster?

Tried both, not better.

Tree HalfRes

Tree HalfRes Clay

I packaged the tree, it's 45 MB, is it ok for PM to be sent?

[juanjgon]

I am not sure, try it ... you can also email it to me to [email protected]

-Juanjo

[Humpti]

Seemed to have worked

[juanjgon]

I am testing your scene here and yes, it is true that the Layout becomes really slow while the IPR is rendering in the same GPU that is used for the monitor. I think that the problem is the mix of the complex object model, the opacity maps and the instances. For example: every time you move an object one pixel, the Layout sends a move event to Octane and Octane needs to stop the render, update the scene and init the rendering again. In this scene this process needs a lot of time (specially because in the same GPU the Layout is updating the OpenGL viewports data), and meanwhile the Layout must wait.

Perhaps Rhino sends the move event to the plugin only once, when the user release the mouse button, but in the Layout you get a move event every time you displace the mouse one pixel ... this is why you can see the the transformation events in real time in the IPR, not only at the end.

Anyway believe me, if you plug your monitor to the gt640 GPU while render with the gtx970, the Layout is going to work a lot faster with Octane. One workaround to work with this kind of scenes is to use the Pause command in the IPR (that you can even map to a hotkey): pause the render, update the scene and unpause. But test your gt640 as display GPU, you are going to see that all works a lot better.

-Juanjo

[UnCommonGrafx]

I run a similar setup, yet older 620 for video.

The way you have it setup and the way you want it aren't compatible, so to speak.
The 640 is JUST a slow card and you can't get the speed you want from it. Upgrade the card for the experience you seek.

It sounds like you don't want' to use the 640 for Rhino; why would you want to use it for LW?

Slow(er) ui or render is part of your setup. Pick one and go with it.

xfrog trees look really nice in Octane.
Robert

[Humpti]

Hi Juanjo,

I attached the screen to the gt640 and you are right, much better. But only when I set the original tree to be displayed as bounding boxes the whole experience becomes truly cool (and with the SpaceMouse settings edited!). It seems that LW has problems with it's openGL and high-polygon models, even when displayed as simple wireframes. They should do something about it, but I don't think this will happen anytime soon. Rhino has no problem at all with high-polygons. But these trees are really huge...

The only problem I have now, that I can only change the cable to the dvi-ports when Windows is up. During boot time there is no signal on the gt640 ports. Do you know if I must change the GPU's in the PCI-E Slots? (I know this really not Octane related, but maybe you know by experience )

Cheers
Philipp

[Humpti]

I run a similar setup, yet older 620 for video.

The way you have it setup and the way you want it aren't compatible, so to speak.
The 640 is JUST a slow card and you can't get the speed you want from it. Upgrade the card for the experience you seek.

It sounds like you don't want' to use the 640 for Rhino; why would you want to use it for LW?

Slow(er) ui or render is part of your setup. Pick one and go with it.

xfrog trees look really nice in Octane.
Robert

Oh no, you misunderstood, the gt640 runs fine with Rhino, Blender and even Octane standalone. The UI is fast and responsive and the render is done with the gtx970. No problems at all. It's only with LW and Octane that I have problems and must switch the cards.

Yes the trees are cool, free and HUGE!

[juanjgon]

The only problem I have now, that I can only change the cable to the dvi-ports when Windows is up. During boot time there is no signal on the gt640 ports. Do you know if I must change the GPU's in the PCI-E Slots? (I know this really not Octane related, but maybe you know by experience )

I am not sure, sorry. Perhaps the there is a setting in BIOS to select the GPU used for boot, or perhaps you should change the GPUs in the PCIe slots.

-Juanjo