OctaneRender™ Standalone 2.00

[Timmaigh]

So i finally got it today, after getting a brand new credit card just for the sole purpose of buying this (since my otherwise fully capable Visa Electron would not work with PayPal)...and sadly i have to report i have some major issues.

Not only it crashed on my twice already (once as i tried to change the offset value of displacement), but most importantly the UI is incredibly non-responsive right now. I mean, lot of times i cant literally click the pause button, it just would not work. Nor can i randomly right click into the Node Inspector and get the drop-down menu with all the geometry, materials, etc... options... it just wont pop-up. Nor will menus on the right side on occasion - i wanted to add displacement to the material, but no matter how many times i click on the button saying "No Node", nothing will happen... Finally, sometimes i would move the mouse across all these options in those dropdown menus - the chosen item is highlighted in yellow - too bad this is not true for all the items. For example right now in the node inspector menu last highlighted item is Output, even if go with cursor onto Phase Function and lower - therefore i cant click any of these options, bar Paste for some reason....aaaargh.

I updated my display drivers to latest 340.43 hoping to solve the problem, but its no go.

Please fix this.

Edit: Once again i crashed the display driver by changing the height of opacity from 0.001 to 3 something.
Edit 2: Trying again with a lot simpler scene, so far so good. No UI hiccups and found out 3 is way too much for displacement. More like 0.005.

[dionysiusmarquis]

GPU Point 3:
http://render.otoy.com/forum/viewtopic.php?f=23&t=21372

And for displacement:
http://render.otoy.com/forum/viewtopic. ... 60#p190262

[Timmaigh]

Well, thank you, good to know.
On topic of GPU point 3. though, this is not un-responsivity caused by rendering. I have gtx590 and it happens even when i render with just one GPU. Not to mention, the usual slow-down is just that, you click and it takes some time for the action to happen...now it just wont happen at all, no matter how many times i try. Even if i stop the rendering process.

EDIT:

Just to further illustrate what is wrong:



notice the dropdown menu on the right - i cant choose the item i want, cause this is happening.

[Zay]

On a mesh with multiple material zones the mesh will break up in the seams when adding a displacement map. The stronger the height is set the more visible the crack/tear will be. The color black should keep that area flat in this example. But it doesn't.

TearSeams.JPG

test.orbx

[abstrax]

Well, thank you, good to know.
On topic of GPU point 3. though, this is not un-responsivity caused by rendering. I have gtx590 and it happens even when i render with just one GPU. Not to mention, the usual slow-down is just that, you click and it takes some time for the action to happen...now it just wont happen at all, no matter how many times i try. Even if i stop the rendering process.

EDIT:

Just to further illustrate what is wrong:

...

notice the dropdown menu on the right - i cant choose the item i want, cause this is happening.

Hmm, I don't know what the issue is. Have never experienced anything like this. Does it happen immediately or only after some time or after you started rendering? Does it happen in any scene or all the time even in simple scenes?

Just to be sure: We found a bug in the daemon detection of net rendering, which can screw up the whole application sometimes. It will be fixed in the next release, but since by default net rendering is enabled, could you disable it in the application preferences and check if the issues is still there? Thanks.

[manalokos]

WE also have issues in the network rendering, it works fine for a while but then slave fails, it says an error message about missing heartbeats.

[abstrax]

WE also have issues in the network rendering, it works fine for a while but then slave fails, it says an error message about missing heartbeats.

Which OS?

[manalokos]

Windows 7

[Timmaigh]

Well, thank you, good to know.
On topic of GPU point 3. though, this is not un-responsivity caused by rendering. I have gtx590 and it happens even when i render with just one GPU. Not to mention, the usual slow-down is just that, you click and it takes some time for the action to happen...now it just wont happen at all, no matter how many times i try. Even if i stop the rendering process.

EDIT:

Just to further illustrate what is wrong:

...

notice the dropdown menu on the right - i cant choose the item i want, cause this is happening.

Hmm, I don't know what the issue is. Have never experienced anything like this. Does it happen immediately or only after some time or after you started rendering? Does it happen in any scene or all the time even in simple scenes?


Just to be sure: We found a bug in the daemon detection of net rendering, which can screw up the whole application sometimes. It will be fixed in the next release, but since by default net rendering is enabled, could you disable it in the application preferences and check if the issues is still there? Thanks.

Thanks for your response. TBH i need to test it bit more to find out under what circumstances it happens, it looked sort of random to me so far. It would even fix itself on occasion somehow. I will try to disable the net rendering as well to see if it helps. And i will try at work as well, where i have gtx780ti.

Anyway, the HDRI + sun combo seems to work very nicely and displacement, while maybe somewhat buggy now, is a fine addition as well. So thank you for that.

EDIT: Trying now at work, different, but equally big scene, and so far so good. No weird unresponsivity nor crashes.

EDIT no. 2> I tried at home again, same scene as yesterday, and this time around, no weird shit. Everything responsded nicely. I disabled the net rendering, so perhaps it was the root of the problem, but i suspect it was just matter of something going horribly wrong yesterday and if i rebooted the computer, it would have gone away... i dont know. Anyway i am happy it works now, hopefully the problem wont return again.

[ROUBAL]

Well, I am still playing with the demo, as I have not yet had a full answer to my questions about order problems.

So, here is a mix of two screen shots showing a comparison test without and with Edge rounding : the apparent result seem inverted !

Is it the expected behaviour ?

My goal on this model is to smooth some sharp edges without adding one more subdivision level.