OctaneRender® for 3ds max® v3.06 TEST 3 - 4.31 [OBSOLETE]

[justix]

I hate to such a pest BUT this version is really buggy in his Switching and stopping at 1 sample even if I saved all the paramaters..hours to test and tweaks and now this.

no matter which pass I change when back to beauty it goes back to sample 1 and goodbye.. and IF i close the viewport to try reopen it it tells me that the viewport is still open even if I clearly close that last..

disappointed

Sorry, but stability is not the priority in test releases, especially in this case. Users pushed for us to get out a 3.06 test build to try out asap, rather than wait for a stable release, so Q&A was minimal. We're working to address all reported issues here and turn around a new release quickly.

My File now does not work anymore. Beauty just stuck on sample 1, switching on Noise or any other pass make the engine run but not back on Beauty..interesting bug.. so something must have happened..do consider that an export on stand alone is actually working..

Sorry to say BUT there is NO STABLE version anywhere as every single release is subject to reviews and bug tracing..by Stable release what you mean? 3.1? V4? .. Users pushed the team in release a 3.06 Test 3 in a rush? can't see the problem really as usually most of the bugs are found by USERS that report back for a fix..sound like you guys made us all a big favour in let us test the AS on MAX , I say that is good instead..as you know if Test 3 received NO Complains about crashes and issues it would be Finalize into 3.1..instead..is not ; )

[Goldorak]

I hate to such a pest BUT this version is really buggy in his Switching and stopping at 1 sample even if I saved all the paramaters..hours to test and tweaks and now this.

no matter which pass I change when back to beauty it goes back to sample 1 and goodbye.. and IF i close the viewport to try reopen it it tells me that the viewport is still open even if I clearly close that last..

disappointed

Sorry, but stability is not the priority in test releases, especially in this case. Users pushed for us to get out a 3.06 test build to try out asap, rather than wait for a stable release, so Q&A was minimal. We're working to address all reported issues here and turn around a new release quickly.

My File now does not work anymore. Beauty just stuck on sample 1, switching on Noise or any other pass make the engine run but not back on Beauty..interesting bug.. so something must have happened..do consider that an export on stand alone is actually working..

Sorry to say BUT there is NO STABLE version anywhere as every single release is subject to reviews and bug tracing..by Stable release what you mean? 3.1? V4? .. Users pushed the team in release a 3.06 Test 3 in a rush? can't see the problem really as usually most of the bugs are found by USERS that report back for a fix..sound like you guys made us all a big favour in let us test the AS on MAX , I say that is good instead..as you know if Test 3 received NO Complains about crashes and issues it would be Finalize into 3.1..instead..is not ; )

You are right, we are here to serve you guys, and indeed you are helping us make the product better through feedback as a group. Prior to this 3.06 test drop, we were focused on improvements to 3.05 (which still is the only production ready release at this time). In any case, we're going to move faster on the 3.06 updates and get it polished in tandem with the final release of 3.06 core which we are also moving up a bit (so we can get 3.07 going this month).

[kcpr-raffaEl]

Sorry, but stability is not the priority in test releases, especially in this case. Users pushed for us to get out a 3.06 test build to try out asap, rather than wait for a stable release, so Q&A was minimal. We're working to address all reported issues here and turn around a new release quickly.

My File now does not work anymore. Beauty just stuck on sample 1, switching on Noise or any other pass make the engine run but not back on Beauty..interesting bug.. so something must have happened..do consider that an export on stand alone is actually working..

Sorry to say BUT there is NO STABLE version anywhere as every single release is subject to reviews and bug tracing..by Stable release what you mean? 3.1? V4? .. Users pushed the team in release a 3.06 Test 3 in a rush? can't see the problem really as usually most of the bugs are found by USERS that report back for a fix..sound like you guys made us all a big favour in let us test the AS on MAX , I say that is good instead..as you know if Test 3 received NO Complains about crashes and issues it would be Finalize into 3.1..instead..is not ; )

You are right, we are here to serve you guys, and indeed you are helping us make the product better through feedback as a group. Prior to this 3.06 test drop, we were focused on improvements to 3.05 (which still is the only production ready release at this time). In any case, we're going to move faster on the 3.06 updates and get it polished in tandem with the final release of 3.06 core which we are also moving up a bit (so we can get 3.07 going this month).

Thanks Goldorak for your kind and humble response.

I understand we - users sometimes think " we pay and we expect" but sometimes on this forum I notice so much negative emotions which has little to do with constructive issues reporting and giving feedback.

Sorry if I contributed to this because I'm aware that it's hard to work in such "mood" when anything you do is wrong or at least not enough in others opinion.

Don't release 3.06 Test - BAD
Realeased 3.06 Test - BAD



I would kindly like to encourage us - users (including myself) to focus how to resolve problems instead pouring out our frustration. It won't help in any way - I think

That's my two cents.

[justix]

Well, my rant was legit and be dissappointed about something you expect to run is part of being USER, I'm aware about how hard it is to compile and my answer to Goldorak was about the release of this Test version being a necessity to understand the whole matter here, frustrated? and why not? We have been waiting almost one year since the AS announce and seen many good users just migrate elswhere as this 3.x version still under the hammer, as a matter of facts we were told to wait for the 3.1 but obviously (and gratefully ) Otoy decided to gave us a taste of it..

Now, I'm not and di not plan to use this as production tool BUT AS WAS the reason for me to renew the license and THAT is being loyal to something I still believe BUT as it never happen before , seen the engine sudden stop sampling after that you spend many hours tweaking and adjusting and testing and try to find a reason why is ..disappointing, that is that, if you just like to scroll your shoulder good for you mate, I'm different.

Said that, I did copy the objects and re merged in a new scene loading up the preset saved previously BUT it work UNTIL I check in the KErnel Production Resolution and BANG..samples back to 1..

Now I doing it again re entering all values without loading anything off this file, errors may nest sometime but I understand I'm not alone on this Bug...

Wait for Test 4 to happen or any other release to test

[kcpr-raffaEl]

Well, my rant was legit and be dissappointed about something you expect to run is part of being USER, I'm aware about how hard it is to compile and my answer to Goldorak was about the release of this Test version being a necessity to understand the whole matter here, frustrated? and why not? We have been waiting almost one year since the AS announce and seen many good users just migrate elswhere as this 3.x version still under the hammer, as a matter of facts we were told to wait for the 3.1 but obviously (and gratefully ) Otoy decided to gave us a taste of it..

Now, I'm not and di not plan to use this as production tool BUT AS WAS the reason for me to renew the license and THAT is being loyal to something I still believe BUT as it never happen before , seen the engine sudden stop sampling after that you spend many hours tweaking and adjusting and testing and try to find a reason why is ..disappointing, that is that, if you just like to scroll your shoulder good for you mate, I'm different.

Said that, I did copy the objects and re merged in a new scene loading up the preset saved previously BUT it work UNTIL I check in the KErnel Production Resolution and BANG..samples back to 1..

Now I doing it again re entering all values without loading anything off this file, errors may nest sometime but I understand I'm not alone on this Bug...

Wait for Test 4 to happen or any other release to test

Is this happening only with Live View or during "regular" rendering submission also?

When I stuck with Live View after setting everything up, tried to render not via Octane Live View and everything went OK.

If this occurs only in Live View that may mean that this bug lays somewhere in interactive mode, during translation setting from 3ds max to rendering core.
And I never experienced this while rendering lo-res images.

Plus - in my case, after coming back to Beauty layer rendering doesn't stuck again in Live View.

[justix]

Well, my rant was legit and be dissappointed about something you expect to run is part of being USER, I'm aware about how hard it is to compile and my answer to Goldorak was about the release of this Test version being a necessity to understand the whole matter here, frustrated? and why not? We have been waiting almost one year since the AS announce and seen many good users just migrate elswhere as this 3.x version still under the hammer, as a matter of facts we were told to wait for the 3.1 but obviously (and gratefully ) Otoy decided to gave us a taste of it..

Now, I'm not and di not plan to use this as production tool BUT AS WAS the reason for me to renew the license and THAT is being loyal to something I still believe BUT as it never happen before , seen the engine sudden stop sampling after that you spend many hours tweaking and adjusting and testing and try to find a reason why is ..disappointing, that is that, if you just like to scroll your shoulder good for you mate, I'm different.

Said that, I did copy the objects and re merged in a new scene loading up the preset saved previously BUT it work UNTIL I check in the KErnel Production Resolution and BANG..samples back to 1..

Now I doing it again re entering all values without loading anything off this file, errors may nest sometime but I understand I'm not alone on this Bug...

Wait for Test 4 to happen or any other release to test

Is this happening only with Live View or during "regular" rendering submission also?

When I stuck with Live View after setting everything up, tried to render not via Octane Live View and everything went OK.

If this occurs only in Live View that may mean that this bug lays somewhere in interactive mode, during translation setting from 3ds max to rendering core.
And I never experienced this while rendering lo-res images.

Plus - in my case, after coming back to Beauty layer rendering doesn't stuck again in Live View.

Hard to reproduce as my FIle ( 2 of them now ) just won't start render.. It start and stop at sample 1, we used to tweak while in Live View and in my case switching to Noise layr makes the Engine start but not the way back to Beauty, like I said IF I export the same and open with Standalone it works, so it has to do with Max compile.

+

Imager seems a bit laggy, it takes half a second to react while rendering..

[paride4331]

@Justix
Hi Justix,
I checked and reported to developers your issue last week.
I could not always reproduce the issue, I did not understand this issue and why and when it happens.
Have you a scene that always repeats your issue?
Could you kindly share it, in pm if you want?
Regards
Paride

[mbetke]

I have a scene with this error. last week I already asked here how to submit a scene to the devs so they can work with it.

[paride4331]

Hi mbetke,
send me it in pm, please.
Thanks
Regards
Paride

[paride4331]

@GOLDISART
about PNG corrupt:
it does not look like an Octane issue, could you kindly take a look here:
https://corona-renderer.com/forum/index ... 297.0.html
Regards
Paride