Moderator: face_off
Yes! I did a 32bit OSX build, and tested it, and found an issue with the GUI (the buttons contained no text). I have sent the issue through to Smith Micro for assessment. Everything else was working OK. Sorry for the delay.Any update on getting the demo plugin working with Poser 10?
Yep - sorryface_off wrote:Hi Mike - can you provide the info requested in the first message of this thread pls?
Thanks
Paul
The installers is not including the scripts - which I will fix in the next version. I have attached them separately below. Unzip them into [Poser folder]\Runtime\Python\poserScripts\ScriptsMenu\OctaneRender for Poser.The plugin is working fine so far apart from the script not being available for me to use the lights to emitters option.
The OSX version of the plugin is identical to the Windows version (and uses the same compiled python files). I checked the above, and they were not occurring on the Windows version, so I suspect it is either an installer issue (most likely), or a subtle difference between python on Windows and OSX (less likely, but you never know...). I am currently finalising large update to the plugin, so will address the above when doing the OSX build (probably in above 1 weeks time). Sorry for the wait.Exporting the Rendertarget doesn't save anything. The finder window pops up and you can enter a file name but nothing is created.
Import Material does not open the finder window to select a file.
Opening the Live DB and selecting Organic/Liquid crashes every time.
When reopening a scene with that has an environment texture it does not pick up the correct path for the image file (for some reason its looking in content/runtime/reality/textures), the dialog pops up asking for the directory to be selected with the file in, you select the correct folder and it still fails to load the file as it is looking in the content/runtime/reality/textures folder (which doesn't exist).
Thanks for then prompt response Paul, much appreciated.face_off wrote:Hi Mike
The installers is not including the scripts - which I will fix in the next version. I have attached them separately below. Unzip them into [Poser folder]\Runtime\Python\poserScripts\ScriptsMenu\OctaneRender for Poser.The plugin is working fine so far apart from the script not being available for me to use the lights to emitters option.
The OSX version of the plugin is identical to the Windows version (and uses the same compiled python files). I checked the above, and they were not occurring on the Windows version, so I suspect it is either an installer issue (most likely), or a subtle difference between python on Windows and OSX (less likely, but you never know...). I am currently finalising large update to the plugin, so will address the above when doing the OSX build (probably in above 1 weeks time). Sorry for the wait.Exporting the Rendertarget doesn't save anything. The finder window pops up and you can enter a file name but nothing is created.
Import Material does not open the finder window to select a file.
Opening the Live DB and selecting Organic/Liquid crashes every time.
When reopening a scene with that has an environment texture it does not pick up the correct path for the image file (for some reason its looking in content/runtime/reality/textures), the dialog pops up asking for the directory to be selected with the file in, you select the correct folder and it still fails to load the file as it is looking in the content/runtime/reality/textures folder (which doesn't exist).
Paul
Hi Mike - I've been able to reproduce all these errors. So it is not an installer issue. I will need to investigate over the next few days. My apologies for the delay.Exporting the Rendertarget doesn't save anything. The finder window pops up and you can enter a file name but nothing is created.
Import Material does not open the finder window to select a file.
Opening the Live DB and selecting Organic/Liquid crashes every time.
When reopening a scene with that has an environment texture it does not pick up the correct path for the image file (for some reason its looking in content/runtime/reality/textures), the dialog pops up asking for the directory to be selected with the file in, you select the correct folder and it still fails to load the file as it is looking in the content/runtime/reality/textures folder (which doesn't exist).
