Re: OctaneRender for Modo (Windows) 2.03 [TEST]
Posted: Mon Jul 28, 2014 6:45 pm
Hello everyone!
here are some finds:
Saving material presets is giving me odd colours on the preview generated.see example. Material and how it previews when saved as a preset.
And a second error.this one is driving me NUTS! It seems it comes from some specific mesh layers, when i disable them i can run the render.
Problem is, there's nothing special about them.
Story behind this:
Scene was fine, then at some point modo lost the track of a texture and link was gone.
The octane material lost the connection, i re imported the texture and relinked it in the octane material, all good.
after this this error started to pop.
i tried to relink it, create another matrial from scratch and everything it it would NOT work.
after some time trying i decided to try this specicfic material isolated.then the litle fucker worked!!
ok, so it's NOT related to the material.
then, i try to turn on other mesh layers and the scene stops working again.
my final conclusion is that something related to some meshes, but really ... it's a guess.
i tried deleting all the assemblies... nothing.
feeling a bit hopeless hehehe.
Would you like me to send you the scene Paul? its a bit chunk but should go just fine.Heavy on the GPU, 4 gigs i guess.
Does the error code says anything specific to you?
It's is showing the same error this many times only because i was trying over and over.but it only gives me the error once per try.
it says it couldn't bind the texture(and this makes sense coming from how the error first started) but then i delete all the materials and go with clay and the error still shows up.Weird.
Thank for reading!
Cheers
Raf
here are some finds:
Saving material presets is giving me odd colours on the preview generated.see example. Material and how it previews when saved as a preset.
And a second error.this one is driving me NUTS! It seems it comes from some specific mesh layers, when i disable them i can run the render.
Problem is, there's nothing special about them.
Story behind this:
Scene was fine, then at some point modo lost the track of a texture and link was gone.
The octane material lost the connection, i re imported the texture and relinked it in the octane material, all good.
after this this error started to pop.
i tried to relink it, create another matrial from scratch and everything it it would NOT work.
after some time trying i decided to try this specicfic material isolated.then the litle fucker worked!!
ok, so it's NOT related to the material.
then, i try to turn on other mesh layers and the scene stops working again.
my final conclusion is that something related to some meshes, but really ... it's a guess.
i tried deleting all the assemblies... nothing.
feeling a bit hopeless hehehe.
Would you like me to send you the scene Paul? its a bit chunk but should go just fine.Heavy on the GPU, 4 gigs i guess.
Does the error code says anything specific to you?
It's is showing the same error this many times only because i was trying over and over.but it only gives me the error once per try.
it says it couldn't bind the texture(and this makes sense coming from how the error first started) but then i delete all the materials and go with clay and the error still shows up.Weird.
Thank for reading!
Cheers
Raf