OctaneRender® for 3ds max® v2.25 - 2.17 [OBSOLETE]

[Gestaltdesign]

I rebooted Windows and the problem disappeared - all OK !!!!

I will give that a go, cheers.

[Goldisart]

I rebooted Windows and the problem disappeared - all OK !!!!

I will give that a go, cheers.

again problem - I can *. max scene for Jim ... for analysis ... tomorrow I will be in the office and prepare his archive ...
last 3D max crash when I translated 6000х6000 picture from octane viewport render in 3Dmax viewport

[Goldisart]

scena\

here is picture when you rotate the screen is divided into 3 segments and each segment collects common picture - I have three video cards - maybe it's a coincidence

[JimStar]

So, if I understood correctly - a crash only happens sometimes only when you transfer the image from Octane render-viewport to 3ds Max viewport? If yes - it may be something related to the workaround I was forced make to overcome the 3ds Max bug where it screws up the alpha channel sometimes. I will check it on Monday and make a quick-fix release after I find the reason. The scene where it is reproduceable is welcomed - 'cause I never had such a crashes when I tested this workaround before this release... So may be scene-related somehow...

Goldisart
Image-tearing when you e.g. rotate the view is expected in current version - this is a sacrifice to improve the interactive rendering responsiveness and render speed in this mode (among other improvements in this regard in this version). I could eliminate image-tearing but it will decrease a responsiveness and render speed slightly.
The thing is: if you want to always get a whole image in every frame during each on-the-fly scene change - it needs to be done synchronously, blocking the GPU rendering threads for a while every time a whole image is copied into the Octane viewport (that is - many times per second). In this case the GPU rendering will be interrupted several times a second, the rendering will be stopped for a time the image is copied, and you will see a repeating decreases of a GPU usage on a GPU usage graph (saw-like graph)...
So, just decide what is more important for you. If this image-tearing really drives your nuts - I can eliminate it in next release but it will cost some Octane viewport responsiveness and render speed decrease in Octane viewport mode...

[Gestaltdesign]

Hi Jimstar,

In my case yes, the crash only occurred when transferring from Octane render viewport to 3ds Max viewport (2016), it happened with all scenes I tried and was resolved by reverting back to 2.16.
I will attempt tomorrow to pack a scene and send it to you.

Cheers.

[Goldisart]

I really like version 17 --- just need to fix in 3D Max crash/// need to change anything, Jim... you're always the right thing to do!!!!

.....
16 version no crash with only 17 version started crashing when working obviously because of this ?
....
16 version is very slow for large sizes . . . 17 version is just a fairy tale ... I worked freely with pictures 6000х6000 pixels ... beauty !!! ...

[Gestaltdesign]

Hi Jimstar,

I setup a teapot scene with hdri lighting (included) that is also creating the same 2.17 Octane buffer to Max buffer crash. Link is attached:-

https://www.dropbox.com/s/3svq3dxu1f0mv ... e.zip?dl=0

Cheers

[JimStar]

Next version HERE.