OctaneRender® for Poser (Windows/OSX) 3.03.3 [OBSOLETE]

[ch0pper]

holy mother of hell
4091 x 1952 resolution
you will probably have to click on this picture a few times to actually see the bottom left-hand side if you're using the new feature
Added Out-of-Core Textures (yes keep clicking on the zoom function)

Please note that this is just a quick test scene I threw together (so some characters are not posed in the right angles etc blah blah blah blah blah blah

This possibly 15 characters in here

Paul let me ask you this question with my first initial tests of new feature
is any real point in buying a six meg graphics card now? Is this new feature is now being implemented

[Xipomus]

Sweet option on the new update with using the pc memory for rendering too.

Unfortunately i'm having an issue with the new version:
Install was successfull on Poser 2014 v 10.0.5.28445
Installing OctaneRender_for_Poser_2_21_0_40_Win64.exe

Nvidia driver version 335.23 (vidcards Titan Black 6gb and 780ti 3 gb)

Issues:
Octane Render option not visible in Render Menu

Opening an Octane scene gives this error
Exception in OctaneRender for Poser sceneDeleting
Traceback (most recent call last):
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\__init__.py", line 278, in loadData
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\UiManager.py", line 4148, in CheckSceneVersion
AttributeError: 'module' object has no attribute 'GetOctaneVersion'

On closing Poser I get this error
In a windows called Scene Texture Counter or Main Wmarcos
Exception in OctaneRender for Poser sceneDeleting

Thing I tried to fix it.
Removing the Octane completely before installing again.
Removed Poser temp cache and default settings.

Do you have any idea where it goes wrong and how I can fix it?

Included the poser and octaneplugin.log. Cuda.log was empty coz Octane isn't starting.

Thanks in advance.

Xipomus

[KleanZlate]

Thanks for the latest update. I've discovered a nasty bug though. When I use SubD on V4 it flips the UV so all textures are upside down Anyone else got this problem?

[face_off]

When I use SubD on V4 it flips the UV so all textures are upside down Anyone else got this problem?

Yes - using the Octane subd feature seems to be broken on Octane 2.21. I'm sure Otoy will rectify this in the next release.

Nvidia driver version 335.23 (vidcards Titan Black 6gb and 780ti 3 gb)

Issues:
Octane Render option not visible in Render Menu

Hi Xipomus. You need Nvidia driver version 344.x or later (as per the info in the first post of this thread). I will try to have the plugin provide a more meaningful error in this situation.

is any real point in buying a six meg graphics card now? Is this new feature is now being implemented

Out-of-Core textures will render a little slower than textures stored on your graphics card - so there is still an advantage to having a lot of VRAM.

Paul

[KleanZlate]

Yes - using the Octane subd feature seems to be broken on Octane 2.21. I'm sure Otoy will rectify this in the next release.

Ok. thanks.

[Xipomus]

Nvidia driver version 335.23 (vidcards Titan Black 6gb and 780ti 3 gb)

Issues:
Octane Render option not visible in Render Menu

Hi Xipomus. You need Nvidia driver version 344.x or later (as per the info in the first post of this thread). I will try to have the plugin provide a more meaningful error in this situation.

Thanks Paul.
Thought I had the lastest version because the auto update from Nvidia should auto update.
Apparently that was broken... so reinstalled the lastest and it works now.

Let the testing commence.

[face_off]

I have refreshed the installers at the top of the thread with:

2.21.1.41
- Compiled with Octane 2.21.1
- Disabled Focal Length and Sensor Width pins (since the plugin auto-calculates these from the Poser camera)
- Added "RAM Usage Limit" in the Configuration to limit the to RAM used by Out of Core Textures. Set this as per the Octane Standalone guidelines (ie. < your total RAM). Suggested starting value is 4GB.
- Fixed issue where Out of Core Textures could not be disabled
- Fixed camera field of view calculations for Dolly cameras - so the Viewport should now better match the Poser preview window
- Octane 2.21.1 fixes issue with incorrect UV's when using subd

A big thanks to the Otoy devs for pushing out the UV fix quickly.

Paul

[ch0pper]

think sumthing to do with
Out-of-Core Textures -
as if disable it its fine.



keep getting this error
-> failed to deallocate device memory
CUDA error 700 on device 1: Error code unknown.
-> could not get memory info
CUDA error 700 on device 1: Error code unknown.
-> failed to deallocate device memory
CUDA error 700 on device 1: Error code unknown.
-> could not get memory info
CUDA error 700 on device 1: Error code unknown.
-> failed to deallocate device memory
CUDA error 700 on device 1: Error code unknown.
-> could not get memory info
CUDA error 700 on device 1: Error code unknown.
-> failed to deallocate device memory
CUDA error 700 on device 1: Error code unknown.
-> could not get memory info
CUDA error 700 on device 1: Error code unknown.
-> failed to deallocate device memory
CUDA error 700 on device 1: Error code unknown.
-> could not get memory info

[face_off]

-> failed to deallocate device memory
CUDA error 700 on device 1: Error code unknown.
-> could not get memory info
CUDA error 700 on device 1: Error code unknown.

Firstly - reboot and try again. Make sure the plugin was installed correctly (the plugin version should show 2.21.1.41, and the Octane Log should show 2.21). Does it happen with all scenes, or just one?

Paul

[Masterstroke]

Love the latest update. I can use bigger scenes now by using system RAM, but there is still a polygon count limit. "Forrest Surperior" used for this scene.