OTOY Forums

Not sure if you solved the issue in the meantime but I found a pretty simple solution to the problem.
The "energy lights" from 1101 are being translated correclty as diffuse materials with a texture emission set to white and usually a power of 2 or 3 which - in my oppinion - is way to high.

A value of 0.01 is sufficient enough and comes pretty close to what you can see when you render it in Poser. Just change the material Settings once and then just copy them over the other energy materials - worked pretty well for me.

RGUS wrote: Well yeah I do... but with what you guys poke into your models and textures it really is expected. Plus... without 4 terabytes of video RAM... it's difficult to get hings to render as converted by the plug-in. Not complaining, just means I have to change materials and decrease detail.
The light emitters can be turned off in the plug-in under emissions, so not too much of a problem for me.

I see and I agree about the memory issue with our products since all our textures are 4k and the meshes are med-res/hi-res.
I have a gtx690 (2gb) so I know what you mean. We are working to find the best compromise, but right now the only idea we have is to include in the package textures at 2k resolution.
Thanks for the feedback.

TRRazor wrote:Not sure if you solved the issue in the meantime but I found a pretty simple solution to the problem.
The "energy lights" from 1101 are being translated correclty as diffuse materials with a texture emission set to white and usually a power of 2 or 3 which - in my oppinion - is way to high.

A value of 0.01 is sufficient enough and comes pretty close to what you can see when you render it in Poser. Just change the material Settings once and then just copy them over the other energy materials - worked pretty well for me.

Nice information, note taken!

I see and I agree about the memory issue with our products since all our textures are 4k and the meshes are med-res/hi-res.
I have a gtx690 (2gb) so I know what you mean. We are working to find the best compromise, but right now the only idea we have is to include in the package textures at 2k resolution.
Thanks for the feedback.

There are 3 things to consider....

1) Polygon Count : At the moment a 2GB card will hold roughly 15million polygons. So the difference between a 100k polyon count prop and a 200K polygon count will not really matter.

2) Texturemap size : The amount of VRAM used by a texturemap is it's uncompressed size (and the most efficient shape is square). A 2000x4000 map will use the same space as a 4000x4000 map. Sizes are as follows:
2000x2000 image/alphaimage = 15MB
3000x3000 image/alphaimage = 35MB
4000x4000 image/alphaimage = 62MB
2000x2000 floatimage = 4MB
3000x3000 floatimage = 8MB
4000x4000 floatimage = 15MB
So you can see the there is a large difference between 3000x3000 and 4000x4000. Also, if possible, use greyscale (although there are fewer greyscale texturemap slots - so there is a balance).

3) Texturemap count : The limits are in the FAQ in this Poser forum. Most people using Poser need a 600+ series card for the higher limits. If a bump map is the same as the diffuse map, the most efficient way to handle this is to have the diffuse color map plugged into the bump pin (you can add a color correction node to tweak the power etc).

Paul

Ultimately - if all fails - you could always still get a beefy-er graphics card.
When I hit the same limits as you I upgraded from a GTX 570 (1.25 GB RAM) to a GTX 760 (4 GB RAM)
The difference in terms of how many objects you can put in the scene (geometry and textures) is tremendous with a 4 GB card.
I so far never encountered a scene that would overpower the GTX 760.

Of course - it was 300 bucks - so it might be worth considering what face_off said. Always try and compress the texture maps with the Python script inside Poser - that helped me a lot when I was still on a GTX 570.
Also - if you're trying to load huge scenes inside Poser - for example the Stonemason products. Always remember that setting your scene works like you would film it with a movie camera.
Objects you don't SEE in the image you can go ahead and delete - cause they just fill up your VRAM.
So try and focus on the objects you can actually SEE in your rendered image.

Hope this helps

getting this error message after i upgraded to sp3 on poser pro 2014 and running 120.6 version octaine render


Traceback (most recent call last):
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\__init__.py", line 73, in Render
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\UiManager.py", line 4036, in ShowSetupForm
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\MaterialManager.py", line 151, in CreateNodesFromPoserScene
File "C:\Program Files\Smith Micro\Poser Pro 2012\Runtime\Python\addons\OctaneRender for Poser\MaterialManager.py", line 365, in ConvertMaterial
UnboundLocalError: local variable 'bumpNode' referenced before assignment

getting this error message after i upgraded to sp3 on poser pro 2014 and running 120.6 version octaine render

The latest version rectifies this error (1.20.2.7).

Paul

deleted

oh thanks!

Hello

I've tried to render an scene of planet alpine from poser in octane, the scene is a bit large but when I trying render it with low res my machine cripple. I have 2 GTX 690. I know that could be a bit low memory for it. In fact I planing to get 3 GTX Titan that could solve my low memory card problems ?
I ask that because I want to use octane to render scene like this

Thanks

Pablo