OTOY Forums

for me vray material converter don't work with vraylight materials

it does not work indeed!:(

j7th wrote:for me vray material converter don't work with vraylight materials

in fact it doesn't convert vraylightmaterials...

thomasmesser wrote:It's my little wisch list:

1-working with animated textures (avi or image sequences)
2-camera only render without reloading scene to gpu- this can speed up render in simple scenes when only camera is moving.
3- stereo render support in various modes - Side by side , over and under, interlaced- it makes possible to preview render scene on 3D TV in realtime

+1.000.000.000

OK, so i just purchased the 3ds Max plug-in and have found a bug. (I know I know we are beta testing the product. I'm just looking to help)

PC Specs: Windows 7 64Bit, 3ds Max 2012, GTX 580 (using one card for graphic display and rendering)

Bug: Right Clicking the OctaneRender Viewport causes 3ds Max to crash.

Process:
1. Opened 3ds Max
2. Assigned OctaneRender as the render engine
3. Created a plane and 2 teapots
4. Changed Environment color to white
5. Selected Open Octane Render Viewport
6. While OctaneRender Viewport was opened right-click on the screen.
7. Received 3ds Max Application Error. (Max crashes)

KaroBastardKiter wrote:
At startup of 3ds max: Error 126 - the module could not be found.

Any ideas why I am receiving this message?

check your firewall

I shut down the firewall completely but I ge the same message.

I am running a 32bit 3ds max on a 64x Windows 7, could that be the problem?

Has anyone had the same problem?

then i assign image texture to diffuse slot, the 3ds max button "Show standart map in Viewport" dosn't show texture in max viewport

This could be a small bug, if not it might have been overlooked. If you are in a project at the moment you can just load a bitmap and use them as you would while doing any UV unwrapping. Just remember to put the textures into a image/floatimage texture node before final rendering.

obadonke wrote:where would you like bug reports? I can get consistent crashes trying to use an Octane viewport with 3Ds Max 2012x64 on my Win7 machine (2xGTX570) but plugin works fine as a renderer.

I installed 3ds Max 2012 x32 SP2 to investigate stability issue. Turns out there is a method to create an Octane viewport in 2012 x64 that doesn't exist in 2012 x32 namely:

1) left click the POV viewport label menu
2) choose Extended Viewports->Octane
3) you will probably get a crash soon after!

Since I hadn't understood Page 11 of the Octane plug-in manual, I thought this was the correct way to launch an Octane viewport. Therefore I always got crashes.

This Extended Viewport menu item doesn't exist in 3ds Max 2012 x32.

Now that I'm using the "Open Octane Viewport" button from the render settings panel, I can happily say that Octane viewports work for me in both x32 and x64 versions of 3ds Max on Win7x64 2xGTX560 (3 monitor set up, 1 on primary card, 2 on aux card - primarily a gaming rig).

I do get the right-mouse-click-in-viewport crash in 2012x64.
I don't get the right-mouse-click-in-viewport crash in 2012x32.

This is what I have with the same results for both camera and render settings in both octane standalone and octane3dsmax

OctaneStandalone

Octane3dsmax


Anybody have a thought or have tried a comparison. I am wondering whether you need to fiddle with 3dsmax gamma, or something, but does not explain the big noise difference.