OctaneRender® for Poser (Windows) - build 1.20.2 [OBSOLETE]

[Krew]

Hi Paul,

I just updated to 1.20.2.2 and I got an error which I thought I'd report. To set the stage, I have both Poser Pro 2012 and Poser Pro 2014 installed on my computer. I updated to 1.20.2.2 on Poser Pro 2014 and when I ran the program I got an error every time I turned a dial on a model (requiring a refresh of vertices, I guess). The plug-in seemed to be looking at my 2012 folder. The error was:

************
Traceback (most recent call last):
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\UiManager.py", line 3045, in poserEvent
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\UiManager.py", line 2762, in refreshVertices
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\UiManager.py", line 985, in updateMesh
AttributeError: PropMeshNode instance has no attribute 'polyTextureMismatch'
************

I then updated Poser Pro 2012 to 1.20.2.2 and the plugin failed to initialize because it reported that it couldn't find Octaneplugin.log in my users/appdata/local/temp/Poser Pro/9/ folder (which was correct, it wasn't in there). I copied that file over from my Poser Pro/10/ directory and now Poser Pro 2014 works fine.

My problem is solved, and I'm not sure if my explanation was convoluted or not, but I thought I'd just let you know what I ran into. I've updated 2014 several times in the past without updating 2012 and this is the first time this error has occurred.

[Krew]

Oops spoke too soon, it's still throwing the error.

[face_off]

I just updated to 1.20.2.2 and I got an error which I thought I'd report. To set the stage, I have both Poser Pro 2012 and Poser Pro 2014 installed on my computer. I updated to 1.20.2.2 on Poser Pro 2014 and when I ran the program I got an error every time I turned a dial on a model (requiring a refresh of vertices, I guess). The plug-in seemed to be looking at my 2012 folder. The error was:

I wasn't able to reproduce this error - but I suspect there is some non-standard geometry in our scene, which the "material Visibility" change has effected. I have updated the installer at the top of this thread to hopefully rectify this issue. Pls re-download and install.

Paul

[Zay]

Hi Zay - I had a look at this but could not reproduce it. What exactly do you mean by "set a custom render target"?

I can't reproduce it either. I have just seen it twice now and when it happens it also locks the sliders in the material list. I can move the sliders but nothing happens. Custom render target just means I have it saved with different HDRI maps.

I have installed the new plugin version and it seems I have lost some materials in a scene. I think at some point I have saved the scene with the reduced textures function. But now it can't find them and I can't roll back to the original textures as refreshing the scene will of course just look for the reduced textures and not the original ones. I don't have a MAT pose either to replace the textures.
I think some sort of solution should be made to prevent this from happening so you can roll back to the original textures if it can't find the reduced textures or you want to roll back to the original ones.

[face_off]

I have installed the new plugin version and it seems I have lost some materials in a scene. I think at some point I have saved the scene with the reduced textures function. But now it can't find them and I can't roll back to the original textures as refreshing the scene will of course just look for the reduced textures and not the original ones. I don't have a MAT pose either to replace the textures.
I think some sort of solution should be made to prevent this from happening so you can roll back to the original textures if it can't find the reduced textures or you want to roll back to the original ones.

The Compress Texture Maps script stored the compressed texturemaps in the Poser Temp directory - which unfortunately we now know gets wiped out by Windows when you clean up your hard disk. They should actually be stored in the Poser Preferences folder (C:\Users\[username]\AppData\Roaming\Poser Pro\10). I will make this change in the next update.

Paul

[RGUS]

Another wee error message with version 1.20.2.2...
Importing all materials... as shown in the images.

[Zay]

When trying to load "Import all materials for this Figure/Retain existing Imagemaps, I get this error:

Traceback (most recent call last):
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\SetupForm.py", line 1677, in MenuSelectionCb
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\MaterialManager.py", line 1434, in MenuCommand_ImportMaterialCollectionRetainMaps
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\MaterialManager.py", line 1463, in ImportMaterialCollection
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\MaterialManager.py", line 1071, in FindTextureMaps
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\MaterialManager.py", line 1056, in FindTextureMapsIter
AttributeError: Node instance has no attribute 'pinName'

[Zay]

Somewhat similar error when using "Copy Glossy Node".

[face_off]

Somewhat similar error when using "Copy Glossy Node".

I will release a fix for this in the next hour.

[face_off]

I have updated the installers at the top of this thread with

1.20.2.3
- Fixed exception raised when Importing -> Retaining Texturemaps
- Re-write the Compress Texture Maps script to improve it's function, and store the resulting files in the Poser Preferences folder rather than the Poser Temp folder.

Paul