Page 60 of 63
Re: OctaneRender 3 for Modo [TEST and STABLE]
Posted:
Wed Oct 17, 2018 12:55 pmby MrFurious
I just deleted the .CFG file and it still crashes on launch. Interesting thing is Modo isn't creating a new config file on launch either.
Re: OctaneRender 3 for Modo [TEST and STABLE]
Posted:
Thu Oct 18, 2018 4:20 amby face_off
I just deleted the .CFG file and it still crashes on launch. Interesting thing is Modo isn't creating a new config file on launch either.
Does the previous version (.134) work for you? What Nvidia driver version are you using? Have you tried running Modo from a command line window to see if it throws any errors that might give a clue as to what is going on? If have had no other reports of the issue - so it appears to be something specfic with your system or setup.
Paul
Re: OctaneRender 3 for Modo [TEST and STABLE]
Posted:
Thu Oct 18, 2018 7:10 amby MrFurious
.134 works fine. Have just installed the latest nvidia driver, removed my modo .CFG file and still crashes on launch. Tried the command line thing ( i think) basically used CMD, navigated to the modo install directory and ran it from the console. Not sure if that's what you meant.. Launched modo but crashed on launch and no info in the console. Have also tried moving 3rd party scripts and configs out of the default user directory with no luck
Re: OctaneRender 3 for Modo [TEST and STABLE]
Posted:
Thu Oct 18, 2018 7:13 amby face_off
.134 works fine. Have just installed the latest nvidia driver, removed my modo .CFG file and still crashes on launch. Tried the command line thing ( i think) basically used CMD, navigated to the modo install directory and ran it from the console. Not sure if that's what you meant.. Launched modo but crashed on launch and no info in the console. Have also tried moving 3rd party scripts and configs out of the default user directory with no luck
Which version on Modo please Dino?
Paul
Re: OctaneRender 3 for Modo [TEST and STABLE]
Posted:
Thu Oct 18, 2018 7:13 amby MrFurious
Also I'm using Modo 902, but I notice in the current release this is mentioned:
"Windows : Modo10, Modo11 and Modo12 on Window Vista, 7, 8 or 10 64bit"
Is Modo 902 no longer supported?
Re: OctaneRender 3 for Modo [TEST and STABLE]
Posted:
Thu Oct 18, 2018 7:14 amby MrFurious
face_off wrote:.134 works fine. Have just installed the latest nvidia driver, removed my modo .CFG file and still crashes on launch. Tried the command line thing ( i think) basically used CMD, navigated to the modo install directory and ran it from the console. Not sure if that's what you meant.. Launched modo but crashed on launch and no info in the console. Have also tried moving 3rd party scripts and configs out of the default user directory with no luck
Which version on Modo please Dino?
Paul
yup.. 902
Re: OctaneRender 3 for Modo [TEST and STABLE]
Posted:
Thu Oct 18, 2018 7:24 amby face_off
Modo902 is no longer supported. You need Modo10 onwards. Sorry for this news (it's been at the top of this thread for a few months now). I have updated the Modo SDK version from Modo901 to Modo10 and regretfully that is what is causing your crash. I would have thought the plugin would simply not load.
Paul
Re: OctaneRender 3 for Modo [TEST and STABLE]
Posted:
Thu Oct 18, 2018 7:26 amby MrFurious
Argh missed the obvious one. I'll keep on using .134 until I'm ready to upgrade, thankfully it's pretty solid.
Many thanks,
Dino.
Re: OctaneRender 3 for Modo [TEST and STABLE]
Posted:
Thu Oct 18, 2018 3:37 pmby Fredrikvictorhugo
So the latest build have problem with mesh update in octane render Viewport when adding a mesh and modeling? I have to press reload scene button to see the reslult.
Re: OctaneRender 3 for Modo [TEST and STABLE]
Posted:
Thu Oct 18, 2018 11:31 pmby face_off
So the latest build have problem with mesh update in octane render Viewport when adding a mesh and modeling? I have to press reload scene button to see the reslult.
Which version of Modo are you using pls? What specific steps are you taking which produce this problem? What version of the plugin has this problem, and which version of the plugin were you previously running which did not have the problem?
Thanks
Paul