OTOY Forums

Try to save it to .ma file from 1.5 version, and open it in 2.0.
It will not fix all of the differences between stored data, but at least some of them may be better in your case...

JimStar wrote:Try to save it to .ma file from 1.5 version, and open it in 2.0.
It will not fix all of the differences between stored data, but at least some of them may be better in your case...

Sorry just making sure I'm doing this right. Re-download, and install the 1.5 plug in; save my file as a .MA and then re-install the 2.04 plug in open the 1.5 saved file and I should be able to work on creating the rest of the materials with no issues?

You can try to do it this way. I don't have the scene so I can't say if there will be no issues after that...

JimStar wrote:You can try to do it this way. I don't have the scene so I can't say if there will be no issues after that...

Yeah just tried it and sadly it did not work. I'm still running into the same issue where it doesn't render after I create more materials*. But if I replace the object with a Diff material it renders fine.

Another question too. Is there a texture data limit in the plug in? every asset in the scene has about 4k to 2k maps on them. Maybe this might have something to do with it. We are really trying to push octane to the limits to see how far we can go within the Maya plug in.

Would it be easier to just export all the Geo without materials and import the geo into a new scene and recreate the materials from scratch? Just using the the latest plug in. I just don't this to happen again after remaking all of the materials.


*Just wanted to clarify that's what I mean every time I say material.*

jnuno_ wrote:Would it be easier to just export all the Geo without materials and import the geo into a new scene and recreate the materials from scratch? Just using the the latest plug in.

Yes, is the most robust way to do it. As the geometry is not affected by the data formats change due to these Win-Linux format inconsistency fixes. So, if you do this way - it will be most robust and it definitely fixes your issues.

jnuno_ wrote:I just don't this to happen again after remaking all of the materials.

I'm working to improve this situation by additional workaround in next version... But anyway for some not-existing data it may only set some default values... So as it affects only few last 2.0 versions if they are opening old scenes - the most robust way is to do this trick with reexporting geometry. This will ensure that there are no wrong data loaded somewhere into Octane Nodes from old version format.

EDIT: Could you give me some 1.X scene where you have these issues opening it in 2.04?..

JimStar wrote:Yes, is the most robust way to do it. As the geometry is not affected by the data formats change due to these Win-Linux format inconsistency fixes. So, if you do this way - it will be most robust and it definitely fixes your issues.

Alright I'm doing it now hopefully it works.
Do you recommend any certain file type? OBJ, FBX, .MA Etc?

JimStar wrote:EDIT: Could you give me some 1.X scene where you have these issues opening it in 2.04?..

Sorry I actually can not just because this scene belongs to the studio and I think it would brake NDA. I can ask my producer who is in contact with Banafsheh Fathieh to see if I can give you the scene that has the issues.

jnuno_ wrote:Do you recommend any certain file type? OBJ, FBX, .MA Etc?

Any of formats where you can export geometry without old Octane nodes. E.g. disable "Include texture info" if you export selected geometry as .ma.

Did it earlier today. No Hypershade data or node data came through, I'm currently working on Ver 2.03. Lets say I get all the materials done in 2.03 . If we want to upgrade again to higher version when available is it just better to have all your materials set and done before upgrading? Or is there still a risk of running into these material issues.

jnuno_ wrote:Did it earlier today. No Hypershade data or node data came through, I'm currently working on Ver 2.03. Lets say I get all the materials done in 2.03 . If we want to upgrade again to higher version when available is it just better to have all your materials set and done before upgrading? Or is there still a risk of running into these material issues.

I thought you are working in 2.04 as stated in this thread (the last plugin version is 2.04-4.5). There where still the changes between 4.4 and 4.5 (e.g. "Gradient Texture" was added...).
You better first upgrade to 2.04-4.5, and then start working with it...

JimStar wrote:

jnuno_ wrote:Did it earlier today. No Hypershade data or node data came through, I'm currently working on Ver 2.03. Lets say I get all the materials done in 2.03 . If we want to upgrade again to higher version when available is it just better to have all your materials set and done before upgrading? Or is there still a risk of running into these material issues.

I thought you are working in 2.04 as stated in this thread (the last plugin version is 2.04-4.5). There where still the changes between 4.4 and 4.5 (e.g. "Gradient Texture" was added...).
You better first upgrade to 2.04-4.5, and then start working with it...

Yes sorry for whatever reason I can only download the 2.03 Ver on my Live Account. But I have an old download of 2.04. So yes I will now start on the Materials. So DO NOT upgrade the Octane plug in until all materials are done correct?