Ok, so I just had a heart attack when I upgraded from 2.22 to 2.23. All of my materials and rendering settings were wiped clean. Even my huge OCTANE material library was ruined.
SO my question is... what happens in the 6 months etc, when I want to upgrade to version 2.5 for example or even 3.0 ? Does all of my previous year of using OCTANE come out to nothing ? Does all of my final rendering settings and materials get wiped ? That would be crazy. I am used to a little change from version to version but not a total wipe of all settings. VRAY never did that.
This is a very serious development question I need answering. I have a 100k project that is long term setting up right now using version 2.22. If you are telling me I am in a dead end moving forward and should have stuck with 2.04 then I need to know now so I can plan for it.
Question about future versions
Forum rules
Please post only in English in this subforum. For alternate language discussion please go here http://render.otoy.com/forum/viewforum.php?f=18
Please post only in English in this subforum. For alternate language discussion please go here http://render.otoy.com/forum/viewforum.php?f=18
You can always archive your working Max plugin with your project. I'm still using 2.03 for example.
The plugin needed a sort of "re-write" cause it had too many falws. There should be no such compatibility changes in the future, cause things are now coded as they should have been in the 1st place.
Suv
The plugin needed a sort of "re-write" cause it had too many falws. There should be no such compatibility changes in the future, cause things are now coded as they should have been in the 1st place.
Suv
Hi Richard. Yes we have the same problem as many other people also do. We have a year worth of assets and projects that will no longer be accessible due to the refactoring.
We will basically be starting from scratch having to recreate every material as it will be too hard to copy over one parameter at a time. I'm hoping Otoy can still come up with a solution.
We will basically be starting from scratch having to recreate every material as it will be too hard to copy over one parameter at a time. I'm hoping Otoy can still come up with a solution.
-
lunarstudio
- Posts: 71
- Joined: Fri May 16, 2014 12:36 pm
- Location: Boston, MA
- Contact:
You can always revert back to previous versions of Octane or even do a side-by-side install with Max 2015/2016 running their own independent versions.
I know it's a pain (you'll easily lose a day converting mats and another for models) but they did warn you in the beta release thread. It's worth it in the long run assuming they don't mess with it more.
I wish there was a converter for the libraries but that's the price for being cutting edge.
I know it's a pain (you'll easily lose a day converting mats and another for models) but they did warn you in the beta release thread. It's worth it in the long run assuming they don't mess with it more.
I wish there was a converter for the libraries but that's the price for being cutting edge.
"Otoy must..." - No body MUST if situation is out of logicalvfxman83 wrote:otoy must be fix these bugs ;
-Tiles map don't convert
-Vray2sided material don't convert
-Vray proxy to octane proxy
-Huge scenes will crash and it is very important
if they don't fix i will give up and bakc to vray !
"If they don't...I will..back to..." - situation is out of logical
they have to because tiles is very simple 3ds max default map
vray is most popular render engine in the world
why don't convert vray2sided material
we pay for this plugin and standalone so i want this very simple mat conversations and fix the bugs
vray is most popular render engine in the world
why don't convert vray2sided material
we pay for this plugin and standalone so i want this very simple mat conversations and fix the bugs