Massive upgrade from v2.23 to v3 . What should I expect?

[pump_studio]

Hello,

We are a cg conpany working with octane since years. Now it's the time for us to go to v3 ( we are still working on 2.23 ).

I know that some of this questions has been discussed on other threads, but I want to be sure before moving. We have 10 licences and we are working on the 3dsmax plugin with lot of backburner rendering.

There are my questions:

When I will move to v3:

- Will we open older scenes without shader/maps/light issues?
- Will the result of an old scene exactly the same as before ( or nearly)
- Will we continue to use our other plugins (forest pack for example)
- Will we be able to render with the 2.23 version without reinstall?
- Will backburner work fine?
- Will I be the happiness man ever?

Thank for your reply,

Yvain

[paride4331]

Hi pump_studio,
You will not have to reinstall v2.23 every time, but disable it when you switch to v3.
Obviously you can not use V2 and V3 in the same version of 3dsMax,
so you should have (eg) V2 in 3dsmax2016 and V3 in 3dsmax2017.
About your other questions, you should not have problems or render different results.
Regards
Paride

[mbetke]

Well I did the switch from 2.23 last week and reget it.

My whole material library doens't work anymore. This is tricky because I still get the proper preview images but when I drop them into the material editor they are just white and without textures applied.
Also, on n first run all scenes converted fine. Also the Xref files I use. After reopening them all Xref files are just white. I have to open every model I have made with octane 2.23 and save it again with Octane 3. Very time consuming and monkey work. The scene conversion within a scene works flawless until now.

Today I noticed that even used Xrefs which refer to a already manually converted model are still white. I was able to fix it with an update in the xref dialog.
I reported this in the release threads but no answer/solutions so far.

[pump_studio]

Thx for your reply,

I think I will keep 2.23 on 2016 and 3 only on max 2017 during a long time, this a pretty good idea.

I have a question about licence desactivation. I have 5 computer only used as backburner render node. So I only have a 3dmax trial version installed on them.

The problem is that I can't open 3dsmax anymore to deactivate/reactivate 2.23 on this computers...

Have you any idea for this problem? I hope I will not have to buy 5 additional licences just to reactivate octane!

Thank you!

Yvain

[paride4331]

Hi pump_studio,
I think I understand your problem.
I recommend you this solution:
You could buy one 3dsmax license and install it on a PC (master) with backburner.
Pc (master) uses four other pc (slaves) via Octane slave daemon (you already bought).
This way you could also use as slave daemon your workstations when no user is working (eg at night).
Regards
Paride

[acc24ex]

I'm keeping 2.21 on max2015 and switched to max2017 with octane 3 - 90% of stuff works good, sometimes I'm getting glitches and maps not loading, not sure what, but loading/reloading library helps, need to make that switch at some time, before I do another 100 projects on old kernel, the converter is turned on all the time, and probably gonna keep it like this for a long time.. around 500 projects on old kernel, but as I said, surprisingly they all load like they should - some glitches might as well be from switching to max 2017 - you like sometimes it does strange things to chamfers and modifiers - maybe even due to different unit setup

[pump_studio]

Thx for your replies.

I made the upgrade last week.

So now I have 16 computers with octane 2.23--max2016 and octane 3 -- max 2017.

All works fine. As you said, I have some minor trouble when using old kernel scenes but it's acceptable.

Now I have a licencing issue.

All my render farm is working with backburner and now some of the computer are loosing randomly the octane 2.23 licence.

I guess this is because of the new " floating " licence system but it's a problem for me.

How can I fix this?

Thank you!

Reban

[paride4331]

Hi pump_studio,
the issue you reported is not the V3 floating license.
The issue is that octane V2 needs on and off every time.
what you report is correct, otherwise you would have 32 workers licenses ..
I advise you to gradually migrate to the V3 permanently, so you will not have to switch licenses every time.
Regards
Paride

[pump_studio]

Ok thank you.

It's hard for us to switch without transition time.

We have some project still running in V2 so we can't just change without finish them. And it will be a problem if our customers come back with old project update...

Thank you anyway

Reban

[paride4331]

Hi pump_studio,
sorry for the hassle, new floating licenses is to prevent the manually activation and deactivation of the licenses every time.
Regards
Paride