OTOY Forums

I updated Octane from Version 1.20 to 1.51 and the Poser Plugin from 1.20a to 1.50 recently and took it for my first whirl today. Sadly, I seem to be getting a very similar message.

Traceback (most recent call last):
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\Node.py", line 1374, in <lambda>
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\SetupForm.py", line 1765, in comboBoxNodeType_SelectedIndexChanged
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\Node.py", line 452, in ChangeNodeType
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\Node.py", line 389, in ReplaceNode
WindowsError: exception: access violation reading 0xFFFFFFFFFFFFFFFF

I am running Windows 7 x64 (german) with Poser Pro 2014 (build 10.0.2.25578) and, as mentioned above, Octane 1.51 and Octane for Poser plugin 1.50 (build from March 25th, 2014).

I loaded a render-ready scene which had no Octane info in it yet (though the same happens with a completely new scene, so just mentioning it for completeness) and then went on to set the plugin up. When I tried switching from "Daylight" to "Texture Environment", I got the above error. Though it also spews exactly the same when I try to switch anything in the plugin that has a drop-down menu.

One thing that struck me as odd is that I have PPro 2014 installed under "L:\Poser Pro 2014", not on the C: drive (and heavens forbid not in the "Program Files" directory) as mentioned in the error.

Searching for defaultrendertarget.por as suggested yielded no results, neither via the Windows search nor the manual search via Speed Commander. It seems that the file does not exist on my machine.

I then de-installed both Octane and the plugin via the Windows Programs and Applications window, rebooted and re-installed both, cleared out all Octane related files from my "AppData" directories as well as from the Poser Temp folders (where it stores the logs, for example) and then tried again.
Sadly, I got the exact same error again.

I have included the log file as an attachment, if that helps in any way.

Oh, and going back to my earlier Octane versions (1.20/1.20a respectively) works for me without any errors, so I suspect the error is somehwere in the new versions. But where, that is the providence of men smarter than me.

Cheers and best regards,

SpiritWolf448

Hi

Which version (X.X.X.X format number) of the plugin are you using pls?

Can you provide your hardware and driver versions as requested in http://render.otoy.com/forum/viewtopic.php?f=45&t=38937.

When you rightclick the tree in the Settings tab of the plugin, as "Load from Default" greyed out, or available?

Finally, when you start Poser - does the Default Andy scene load? Or do you have another startup scene? If you have another, switch back to the default scene, which won't have any old Octane data in it (Edit->General Preferences->Launch to Factory Scene).

Thanks

Paul

face_off wrote:Which version (X.X.X.X format number) of the plugin are you using pls?

1.50.0.22 Win64

face_off wrote:Can you provide your hardware and driver versions as requested in http://render.otoy.com/forum/viewtopic.php?f=45&t=38937.

Intel [email protected](4Ghz Turbo)
64MB DDR3-1600 RAM (G.Skill)
AMD Radeon R9-290x 4GB with Catalyst 13.12 (Primary Display card)
NVidia Titan 6GB with NVidia Driver 334.89 (used exclusively for CUDA, not hooked to a display)
ASUS Xonar Phoebus Soundcard
Windows 7 Ultimate (German)

face_off wrote:When you rightclick the tree in the Settings tab of the plugin, as "Load from Default" greyed out, or available?

Greyed out.

face_off wrote:Finally, when you start Poser - does the Default Andy scene load? Or do you have another startup scene? If you have another, switch back to the default scene, which won't have any old Octane data in it (Edit->General Preferences->Launch to Factory Scene).

The default Andy scene is loaded on startup as per settings.


Cheers,
Sascha

Thanks Sascha.

Everything seems to be in order on your system - although installing Poser SR3 wouldn't hurt.

There has only been one other report of this issue, so it is very odd.

If you open the Viewport before changing the Environment Type (or any other node type) does that then still pop the error?

Paul

face_off wrote:If you open the Viewport before changing the Environment Type (or any other node type) does that then still pop the error?

No, if I first initiate a render (even if I immediately stop and close the viewport again), the error does not occur.

I'll update to SR3.1 on Poser later today when I have some spare time and see if that changes things.

Thank you.

Sascha

EDIT:

Updated to Poser Pro 2014 SR3.1 now and repeated the de-install/clean temp-files and settings/reboot/re-install routine with Octane and the Plugin.
The error still occurs if I don't open the viewport first.

Perhaps Morphious could tell us if he is still having the problem, and if not, how he resolved it?

Yes, I had the exact same problem. Had to open viewport first to by pass errors switching the ENV node to PathTracing.

Sooooooooo. I gave up. Then.......I just upgraded to Windows 8.1 Pro and installed fresh copies of Octane Stand Alone And Poser Plugin. Wa La. Problem solved. I did notice however, a scene I did in Windows 7 could not find the textures I used from Live DB, and textures that were not used in Poser setup. Once I had the Octane window open, I had changed some textures on a couple trees and some sand with my own. But, it did pop up a window to point Octane to the folder with the textures. But I had to go back to Live DB and re-apply the textures I previously used when on Windows 7. Other than that, no errors so far.

*laughs* Thank you for the input, morphius. Though I must say, I'm not going down the Win8 route again. Tried it once for ~7 month, went back to 7... and liked it. (Not raining on W8, it is just a personal preference. It just didn't feel as good as W7 does for me.)


So, what facts do I have now?

- Intel i7, Asus RIVBE, 64GB RAM, AMD R9-290x 4GB, NVidia Titan 6GB, Asus Xonar Phoebus Soundcard
- Running Win7 Ultimate (german) x64, fully updated
- using Poser Pro 2014 SR3.1, installed on a physically separate drive (L:\Poser Pro 2014)
- Octane 1.51 and Octane Poser Plugin 1.50 give the error and require the workaround with the viewport
- Octane 1.20 /Octane Poser Plugin 1.20a do not generate the error


Well, it is not like Octane is unusable now, as the error can be worked around by opening the viewport shortly before doing anything else. So no pressure, face_off. If you ever happen to find out what causes this behaviour,do let us know, though. If you need any more info for such a task, please do not hesitate to ask.

When I get back in a few days - I'll double check my Win7 PC to make sure the issue doesn't happen there. In the meantime, could pls start Poser (default scene), start the plugin, save the scene to a pz3, reload that scene then start the plugin again, and confirm the error pops. Assuming it does, pls send me that scene.

It you have the inclination, you could re-install Poser - that would ensure there is not a corruption in your PoserPython system.

Paul

Hello again, face_off.

My apologies for the long silence, but something called Real Life(tm by god) intervened.

Now I had the time to do as you asked. I have attached the scene as per your request.

Cheers and best regards,

Sascha