OTOY Forums

Poser freezing verses crashing are two very different things.

Poser 2012 scenes should render fine in 2014. I suspect the scene collector is doping something that is not compatible with 2014, or there is a prop in your scene which is causing the issue. You can load the 2012 scene into 2014 and remove items until you can get it to render to determine the exact reason for the problem.

Paul

OK, I'll try that. Just pain in the Ars as I have to reboot everytime it freezes. Thanks.

Still having problems with Poser 2014. Latest Octane standalone 1.2, latest octane plug, latest nvidia driver. No error when octane transfers scene from Posr, but as soon as Octane Viewport opens it freezes. I can move my mouse around, but cannot select anything, not even task manager. Continuously retsrting computer. I am pasting the Octaneplug log. Cuda log was blank.

DEBUG:root:addon:__init__
DEBUG:root:Python Version : 2.7
DEBUG:root:Platform : win32
DEBUG:root:OS Architecture : 64bit
DEBUG:root:Poser Version : 10.0
DEBUG:root:Poser App Version : 10.0.1 .25099
DEBUG:root:Plugin Version : 1.17a6
DEBUG:root:OctanePlugin.py = C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\OctaneWrapper.pyc
DEBUG:root:OctaneDefaults.py = C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\OctaneDefaults.py
DEBUG:root:Loading Octane library C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\64\PoserOctane64.dll
DEBUG:root:Paths
DEBUG:root:C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\64
DEBUG:root:C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\PoserScripts
DEBUG:root:C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\PoserScripts
DEBUG:root:C:\Program Files\Smith Micro\Poser Pro 2014\python27.zip
DEBUG:root:C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\DLLs
DEBUG:root:C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\lib
DEBUG:root:C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\lib\plat-win
DEBUG:root:C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\lib\lib-tk
DEBUG:root:C:\Program Files\Smith Micro\Poser Pro 2014
DEBUG:root:C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python
DEBUG:root:C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\lib\site-packages
DEBUG:root:C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\lib\site-packages\wx-2.9.1-msw
DEBUG:root:C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\PoserScripts
DEBUG:root:C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons
DEBUG:root:octane.dll: date/time = Fri Jun 07 11:39:14 2013, filesize = 12213740
DEBUG:root:PoserOctane.dll: date/time = Mon Jun 10 14:19:00 2013, filesize = 27136
DEBUG:root:octane.dat: date/time = Fri Jun 07 11:39:12 2013, filesize = 38998196
DEBUG:root:Current Directory = C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\64
DEBUG:root:Octane library loaded
DEBUG:root:addon:load
DEBUG:root:init:objectsAdded

It does not look like you have opened the Viewport in this octaneplugin.log. Can you post a full log file after opening the Viewport pls?

What Cuda drivers are you running?

Is this happening with every scene, or just one?

Can you also post your config.xml file pls? (In C:\Users\[username]\AppData\Roaming\Poser Pro\10)

Thanks

Paul

Here is the config file in a zip file. This is the workflow. Add a scene, ad V4, add textures, render, everything good. Add another V4, add textures, render, but second figure does not show textures. Sooo, go to Materials Tab, right click on second V4, re-import figure/materials. Open viewport again, and everything freezes. 320.49 nvidia driver.

but second figure does not show textures.

What does this mean pls? Where does it not show the textures? Does the untextured figure render?

Inbetween the first and second render, are you shutting down the viewport, or leaving it open?

Does this happen if you do the same workflow with Roxie?

Sorry for all the questions. I just followed your workflow with Antonia, and everything was fine. And your card is 5 times more powerful than mine. My workflow was:

1) File->New, delete Andy, Load Antonia
2) Render->OctaneRender, open Viewport, everything renders fine
3) Load a second Antonia (whilst Viewport is open), scene automatically refreshes due to a new figure being added, everything renders fine (both figures are textured)

One suspect is the new Cuda 320 drivers. I'm running 314.07.

Paul

Yes, figure renders, but without textures I applied. I am closing the viewport between tries. Should not matter. This all started after I upgraded from 1.12 to 1.2 standalone. It's happening in Poser 2012 also. I don't have the content installed. Never use it. eVERYTHING IS GOING FINE, TILL UPDATE 1.2!

The Poser plugin doesn't use any part of Octane Standalone, so upgrading to Octane Standalone 1.20 should have any effect. I have just posted a Poser plugin 1.20 build, so worth giving it a try.

Paul

Alright I'll try new plug.

Still the same thing. No matter what I do, it will not render the texture on the 2nd V4. Tried saving it, closing Poser, re=open, still same thing, no textures render on the 2nd V4, unless I go to Re-import figure/prop. Get a message saying it re-imported all materials for the 2nd V4 figure. Open viewport, and everything freezes. Mouse only works. Can't select anything, cant force quit. Have to restart computer. Soooo.... I tried it with V4, textured added, loaded M4 this time, loaded his texture, open viewport, and get the RED error message at top of viewport, low video card memory, renders for 1 or 2 seconds, then freezes up again. WTF is going on. I have used these textures, figures already with no problem. All started with Standalone 1.2.