OTOY Forums

morphious2013, the octaneplugin.log will report a Plugin Version : 1.16a5 if you have the right version installed.

I'm on 1.16a5 and have Reality 3 (build 116). No errors.

But my Render Option List is gone. All is back to default. No option to "Load from default".

EDIT: Does the installer overwrite the config?

All is good

But my Render Option List is gone. All is back to default. No option to "Load from default".

Is "Load from Default" not in the popup menu at all, or just dimmed? You can only load from default if there is a default rendertarget file (which is C:\Users\[username]\AppData\Roaming\Poser Pro\[9 or 10]\defaultrendertarget.por.

So if you have deleted that file, you will no longer have your defaults (and the Load from Defaults option will be dimmed). If you migrate from Poser 9 to Poser 10, you can copy that file from the '9' to the '10' folder.

EDIT: Does the installer overwrite the config?

No. If config.xml goes missing, it is because someone or some process is deleting it. It also lives in C:\Users\[username]\AppData\Roaming\Poser Pro\[9 or 10]. If config.xml is deleted, the plugin will re-create it when it is next run and set all the settings to defaults.

Does that help?

Paul

face_off wrote:Does that help?

Yes! I have a folder with clean preference files for Poser. Whenever Poser crashes I copy those files to Poser's preference folder after deleting the old ones. A great tip from Smith Micro to prevent corrupted files (had a lot of corrupted saved files some years back). So I was just missing the defaultrendertarget.por.

All OK now.

Hi Paul

I just installed an d playing around with this build. Is there a way to set resolution hard coded? I can only seem to set it by adjusting the view port but I cant get the view port to the size I want to render.

Never mind, I found the button, :-O sorry about that was looking in old spot.

But, since I posted here there is one strange thing i am noticing. When I use the Live DB and load a MAT, then go back and want use the same type of MAT the material group (Metal) I was using is blank and I have to choose a different group (Cloth) then go back to Metal. In the previous version I was brought back to the exact same material I had just used, made it easy when using same mat on many parts of the render.

not a huge issue but seems to be acting oddly.
thanks

But, since I posted here there is one strange thing i am noticing. When I use the Live DB and load a MAT, then go back and want use the same type of MAT the material group (Metal) I was using is blank and I have to choose a different group (Cloth) then go back to Metal. In the previous version I was brought back to the exact same material I had just used, made it easy when using same mat on many parts of the render.

Fixed in the next version.

Paul

face_off wrote:So far there appear to be 3 users who cannot get 1.16a4 running - and everyone else can. For the 3 users who cannot get it running - what virus scanner are you running pls? Also, have you tried re-booting?

I have repackaged everything and re-uploaded, just in case there is some odd firewall or file corruption issue. This version also fixes Uwe's problem.

1.16a5
- Fixed issue where clicking the "image" button was not bringing up the current image's default directory.

partially.
It works fine with textures I have stored locally in my runtimes, but I still have problems with images from the LiveDB. I did the following:
- loaded a simple cube
- in Octane-plugin i assigned a material from the LiveDB "metal panes - scratched"
- if I start rendering right afterwards, everything is OK.
- I save the file, close Poser and restart it.
- After reloading the scene and opening the Plugin, I get the cuda errors indicating the texture maps are missing.
It seems to me, images from the LiveDB are stored in memory and only as long as you don't close Poser. I scanned all my hard drives completely, but couldn't find the requested images. no luck with selecting from within the plugin either.


Apart from that - just noticed - dynamic change of rendersize?
How cool is that! Whoot. YAY!

Posted in main thread probably wrong spot,


I am getting a message from the plugin, using 1.16

"Total number of textures exceeds the limits for Octane Plugin set up"

This render has no issues or errors running 1.13, I changed the defualt.py file to accommodate the 4 gig card i have and selected that card , high priority, apply

Is there another place I should be looking to set this up the material count is

----------------------
Total Num Texture Maps (rgb) : 37
Total Num Bump/Trans Maps (grayscale) : 33
Total Memory Required for Textures : 1031.0MB (assumes only LDR textures)
----------------------

Defult.py settings

MAX_NUMBER_OF_RGBA_TEXTURES = 144 # This is the maximum number of LDR "image" and "alphaimage" textures that your video card can store.
MAX_NUMBER_OF_GRAYSCALE_TEXTURES = 68 # This is the maximum number LDR of "floatimage" textures that your video card can store.
MAX_NUMBER_OF_HDR_RGBA_TEXTURES = 10 # This is the maximum number of HDR "image" and "alphaimage" textures that your video card can store.
MAX_NUMBER_OF_HDR_GRAYSCALE_TEXTURES = 10 # This is the maximum number of HDR "floatimage" textures that your video card can store.

I can also report, that the problems I had with vers. 1.16a4 are gone now! 1.16a5 is running nicely.
Thanks for the support, Paul