Page 1 of 1

6.16 and 6.17 breaks files from 6.14 or 6.12

Posted: Thu May 02, 2019 6:09 am
by nildoe
Hi

I've been trying to use ver 6.17 to render but shaders are turning up wrong... when I use load a file created with either 6.12 or 6.14 shaders will be wrong.

if i merge an object(s) from 6.14 to a clean max file in 6.17 and render it will initially render OK...but if i save this file and reload it will render badly.

please help...i can provide file if necessary

at some point octane recommends activating conversion but even that will not work.

please fix this I'd love to take advantage of the latest versions

Nildo

Re: 6.16 and 6.17 breaks files from 6.14 or 6.12

Posted: Thu May 02, 2019 6:31 am
by paride4331
Hi nildoe,
could you send me a 3dsmax archive in pm please?
Regards
Paride

Re: 6.16 and 6.17 breaks files from 6.14 or 6.12

Posted: Thu May 02, 2019 7:40 am
by nildoe
Hi Paride

PM Sent

Re: 6.16 and 6.17 breaks files from 6.14 or 6.12

Posted: Thu May 02, 2019 7:42 am
by paride4331
Hi nildoe,
thanks, I'm dowloading it.
I'll let you asap.
Regards
Paride

Re: 6.16 and 6.17 breaks files from 6.14 or 6.12

Posted: Fri May 03, 2019 10:29 am
by paride4331
Hi nildoe,
a work around is to disable (before open the file) >> Global Preferences / Prev. versions: disable 'Move Geometry settings to Octane properties modifier'
it should be fixed in the next version.
Regards
paride

Re: 6.16 and 6.17 breaks files from 6.14 or 6.12

Posted: Fri May 03, 2019 11:45 am
by nildoe
Thanks Paride.. i will try that, i never would have guessed that..

but what will happen when i use this file in future versions? will I have to reconfigure anything for it to be updated?

another thing... regarding the different octane versions (4.04 vs 2018/2019 for max) , we are considering updating our 4 licenses to 2018... in your experience is there any advantage in terms of usability or render speed?

because as i understand it...versions 2018 etc..are good if you need access to other plugins different than max..which is not our case

Nildo

Re: 6.16 and 6.17 breaks files from 6.14 or 6.12

Posted: Fri May 03, 2019 12:38 pm
by paride4331
Hi nildoe,
Next Octane for 3dsMax plugin release should fix this issue.
Said that, abput your question, it depends on your needs.
OctaneRender All-Access Extension provide also a secondary render slave node plus access to the ORC cloud rendering service and gets continuous access to all future updates and new features beyond OctaneRender 4, including NVLink, available in Octane 2018.1, and full Vulkan-RTX hardware acceleration on Turing GPUs coming in Octane 2019.
Octane 2018.x new features: viewtopic.php?f=24&t=70809
Octane 2019.x new features: viewtopic.php?f=33&t=70971
Regards
Paride

Re: 6.16 and 6.17 breaks files from 6.14 or 6.12

Posted: Fri May 03, 2019 12:58 pm
by nildoe
ok thanks for your help Paride! :)

still regarding the upgrade or not.. I'm planning also to invest on rtx 2070... I just ordered a new laptop with it..but also wanna update my 5*gtx1070 on the workstations to 5*rtx2070.

is there an estimation as to when 2019 version will be available for max?

also when I upgrade the 4 licenses (they are not subscription) i have...it will cost 800usd... that means I have to plan my years accordingly to always spend 800 if I want to stay updated correct?

once I upgrade v4 to later versions... will I still be able to use all GPU's in the system or just 2? (i read somewhere there was a limitation..but i may have understood it wrong)

i also read somewhere about "rent-to-own" and this is interesting..any info regarding this?

N

Re: 6.16 and 6.17 breaks files from 6.14 or 6.12

Posted: Fri May 03, 2019 1:12 pm
by paride4331
Hi nildoe,
I have not any ETA about Octane for 3dsMax V2019.
OctaneRender All-Access Extension is $199 (1 Year), you will use all of your GPU's and purchasing a new workstation, you will have an extra slave node included.
Octane RNDR info is available here: https://rendertoken.com/
Regards
Pairde

Re: 6.16 and 6.17 breaks files from 6.14 or 6.12

Posted: Fri May 03, 2019 10:57 pm
by coilbook
I agree also when you try to xref an object that was does in 6.14 or earlier version 3ds max freezes on not responding. Deleting the textures fixes the problem