by elenacalderas » Sat Apr 27, 2013 11:42 am
elenacalderas
Sat Apr 27, 2013 11:42 am
Possible bug?
I created a new scene, put in a figure (that I had used in the plugin before with no trouble) and posed it. Then I used the delete_lights script from Poser's utility scrips, created two new lights (one diffuse IBL and one infinite), and opened the plugin. It opens, and so does the render window.
The first thing I did was try to switch texture environment floattexture to image, and got an error message that I didn't record. So I left that alone and just tried to move the camera (with the render window open), and got this message in a window titled "delete lights":
Traceback (most recent call last):
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\OctanePlugin.py", line 10465, in poserEvent
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\OctanePlugin.py", line 8912, in setOctaneCameraInfo
WindowsError: exception: access violation reading 0x000000000000001C
The same message now appears when I move the Poser camera with the render window closed, or when I try to re-open the render window. Effectively, the scene is now useless in Octane.
So, I saved the scene and closed the plugin. This took abnormally long. Without changing the scene or closing Poser, I next tried to re-open the plugin. As it began to process geometry items, a Cuda error popped up.
Cuda error: Cuda device 0. Failed to bind device to thread, since it's already bound.
The Cuda error was caused by the figure in the scene, one I had before worked with without trouble.
Next step: Close Poser, re-open, and re-open scene. Next thing that happens is that Poser asks me to find a pmd file with the name of the Poser file I'm trying to open. Such a file doesn't exist on my drive, so I click cancel, and the scene opens.
I open the plugin, which crashes with the following message:
Main wacro: Traceback (most recent call last):
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\OctanePlugin.py", line 10581, in ShowOctaneOptionsWindow
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\OctanePlugin.py", line 7582, in Init
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\OctanePlugin.py", line 8956, in refreshScene
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\OctanePlugin.py", line 9947, in copyMeshToOctane
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\OctanePlugin.py", line 8912, in setOctaneCameraInfo
WindowsError: exception: access violation reading 0x000000000000001C
As a test, I created a new scene, loaded the same figure, and opened the plugin without deleting the lights via the Poser script. It looks for the same pmd file but otherwise opens normally, and I can move the camera normally. So, apparently, the trouble was originally caused by the python script "delete lights".
Sorry for the long post, and I hope it's not too confusing.
Win 10 Home x64 / NVIDIA GeForce GTX 1070 8 GB / (Intel i7 2.8 GHz) x8, 16 GB RAM / PoserPro 11.2