OctaneRender® for Poser beta - build 1.02q [OBSOLETE]

[Zay]

Got an error when playing with instances.

I clicked on Refresh scene and got:

Code: Select all

Traceback (most recent call last):
  File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\OctanePlugin.py", line 3914, in EventInstantRefresh
  File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\OctanePlugin.py", line 8259, in refreshScene
  File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\OctanePlugin.py", line 8990, in copyMeshToOctane
  File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\OctanePlugin.py", line 8309, in refreshMaterials
  File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\OctanePlugin.py", line 8617, in createNodeFromSavedTree
TypeError: cannot concatenate 'str' and 'NoneType' objects
Traceback (most recent call last):
  File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\OctanePlugin.py", line 3324, in OnSize
  File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\OctanePlugin.py", line 3287, in AdjustScrollbars
WindowsError: exception: access violation reading 0x00000000000000A0

At the same time I get the "Warning: Low video Card Memory" in the viewport.

No CUDA errors.

Log file:

octaneplugin.zip

(21.83 KiB) Downloaded 264 times

[Zay]

Is there a way to speed up the object scattering workflow?

Let's say I have a scene that takes a minute to transfer to octane and I have 20 objects to scatter. That will take 20 minutes just to set the objects from mesh to scatter as the plugin transfers the scene for every single object. Wouldn't it be possible to wait with the "scene transfer to Octane" until all the meshes are set to scatter?

[face_off]

Hi Zay

I've had a quick look at that error, but I'll need to do a deeper analysis to see what has happened.

Is there a way to speed up the object scattering workflow?

I haven't tested this yet, but from memory activating the "No Updates" button does not yet stop instance updates. If it did, you could click it, then setup all your instances, save, then refresh the scene, resulting in only 1 scene refresh. Would that solve your issue?

Paul

[ch0pper]

hi i having issue with a skin . on Octiane i have closed down resaved and still does not apply the skin
to octaine any ideas i supply the Original files if it helps.

sure its a bug!

http://www.renderosity.com/mod/bcs/mdd-nalia/93445

[face_off]

hi i having issue with a skin . on Octiane i have closed down resaved and still does not apply the skin
to octaine any ideas i supply the Original files if it helps.

Hi. What do you mean by "apply to skin"? Are you loading a previously saved template, or reconverting from Poser, or pasting a material to all skin materials? Could you describe your exact workflow pls, and I will resolve the issue.

[EDIT] Nice character!

Paul

[ch0pper]

Yes sorry please forgive me its 6:39 AM here in the UK and I'm not quite awake yet

I can supply you with the original files if this helps from the vendor.

Basically I have tried to apply the face skin.

But it doesn't seem to apply to the mesh on octane even though you can still see it in Poser
You will see the character has various Tats. It quite happily renders as you can see in poser when I try to take the character into octane it neglects to take the updates from the character stored within poser if this makes sense.

I have rebooted.

I'm using Poser pro 2012 version 9.03.23027
Windows 7 64 bit with 24 gig ram
With a GTX 450s one gig ram


Sorry and very new to this forum are what you mean by a template exactly?

[ch0pper]

I've fixed the problem I believe it's down to user error and me not understanding that you cant stack multiple skins on top of each other it obviously only takes the first skin to render.

Sorry to waste your time but it down to user error

[Zay]

I haven't tested this yet, but from memory activating the "No Updates" button does not yet stop instance updates. If it did, you could click it, then setup all your instances, save, then refresh the scene, resulting in only 1 scene refresh. Would that solve your issue?

Yes, that would fix the issue if you could add that!

[Zay]

A scene that worked fine yesterday will not load into the plugin today.

When I start the plugin it will start to convert to Octane and then Poser will crash. I get cuda errors about not having enough memory but I actually have more than enough. Something very weird here.

Code: Select all

Opening OctaneRender for Poser Setup Dialog
CUDA error 2 on device 1: The API was unable to allocate enough memory to perform the requested operation.
    -> Failed to allocated device memory
CUDA device 1: Failed to allocate film buffers
CUDA error 2 on device 1: The API was unable to allocate enough memory to perform the requested operation.
    -> Failed to allocated device memory
CUDA device 1: Failed to allocate film buffers
CUDA error 2 on device 1: The API was unable to allocate enough memory to perform the requested operation.
    -> Failed to allocated device memory
CUDA device 1: Failed to allocate film buffers

Log file:

octaneplugin.zip

(10.72 KiB) Downloaded 249 times

[Zay]

I loaded the scene into a SR2 version where I could save the file without the addon settings. Then I could load it back into SR3.1 again without a Poser crash, but of course lost the instances - but I saved the scene.

I have a feeling this has something to do with a minimized viewport. I have seen the cuda errors before from a saved pzz file where the viewport will start minimized and float somewhere on the desktop just as a bar and suddenly an error will pop up. Or I try to stretch the minimized viewport bigger and a cuda error will show. Put this is the first time I have seen a saved file will open the viewport minimized. I think that might become a problem. Does the viewport window settings get saved in the pz3 file?

I also noticed if you minimize the viewport window by dragging the window smaller until at can't get any smaller, a cuda error will pop up and the plugin will shut down.