OctaneRender® for 3ds max® v4.01.1 - 6.12 [OBSOLETE]

[paride4331]

Noticed a funny one: The memory display. Although I ordered two new Titan RTX cards, its not delivered yet and it should show the amount of a 1080ti card.

Hi mbetke,
It may be a wrong report of the memory usage, as the internal details have changed recently. You could check in the Device tab of the Render setup, with the button 'Octane Device Settings'
Regards
Paride

[coilbook]

Octane won't render superspray particles if rendering begins before Emit Start. So If emit start is set to 100 and octane starts rendering from frame 99 superspray won't render. It has to be 100 or up.
It is similar to phoenix problem you had before where rendering must start when the first phoenix sim file is present.
This doesn't happen all the time but it happens often

[marcjday]

Render elements / passes ?

Used to work really nicely - now they're not - now I can't get them to work at all.

Maybe you've changed how they work? Who knows? Your 'documentation' suggests they haven't changed - set them up with Render Elements tab (are they elements or passes? please decide) - and they should all work.

I'll roll back to a good old version where things work like you expect - in the meantime I hope this gets a legible meaningful response.

-- - - - -

UPDATE

I've rolled back - and all of that 'enable multiple passes' and right click save gubbins have disappeared - and for the better, let's face it. So - you've changed how it works and not explained how anywhere? I'm using this good old version til someone explains how to get it working - because I can't.


------ - -- --

UPDATE 2

Oh - I've found this radical change in how the octane interface works mentioned somewhere. . . .

Changes of the 6.10 version, from 6.09
Added 'Multiple Render Passes' mode for Viewport, to switch render pass without restarting render.

As far as I can tell this has completely broken render passes.
Moving back to 4.00 RC7 - 6.09 (AGAIN) fixes this mess instantly.

[paride4331]

Render elements / passes ?

Used to work really nicely - now they're not - now I can't get them to work at all.

Maybe you've changed how they work? Who knows? Your 'documentation' suggests they haven't changed - set them up with Render Elements tab (are they elements or passes? please decide) - and they should all work.

I'll roll back to a good old version where things work like you expect - in the meantime I hope this gets a legible meaningful response.

-- - - - -

UPDATE

I've rolled back - and all of that 'enable multiple passes' and right click save gubbins have disappeared - and for the better, let's face it. So - you've changed how it works and not explained how anywhere? I'm using this good old version til someone explains how to get it working - because I can't.


------ - -- --

UPDATE 2

Oh - I've found this radical change in how the octane interface works mentioned somewhere. . . .

Changes of the 6.10 version, from 6.09
Added 'Multiple Render Passes' mode for Viewport, to switch render pass without restarting render.

As far as I can tell this has completely broken render passes.
Moving back to 4.00 RC7 - 6.09 (AGAIN) fixes this mess instantly.

Hi marcjday,
viewtopic.php?f=27&t=70290
Regards
Paride

[mbetke]

I get this error. It also kills my whole graphic driver and forces to restart. Driver version: 417.35, specs like my profile signature.

Code: Select all

....
CUDA error 999 on device 0: unknown error
  -> failed to deallocate device memory
CUDA error 999 on device 0: unknown error
  -> could not get memory info
CUDA error 999 on device 0: unknown error
  -> failed to unload module
CUDA error 999 on device 0: unknown error
  -> failed to unload module
CUDA error 999 on device 1: unknown error
  -> failed to destroy CUDA event
CUDA error 999 on device 1: unknown error
  -> failed to destroy CUDA event
CUDA error 999 on device 1: unknown error
  -> failed to deallocate device memory
CUDA error 999 on device 1: unknown error
  -> could not get memory info
CUDA error 999 on device 1: unknown error
  -> failed to deallocate pinned memory
CUDA error 999 on device 1: unknown error
  -> could not get memory info
CUDA error 999 on device 1: unknown error
...

I will pack and sent scene. No idea what happens. This is a deadline job. Thanks again OTOY for this.

[paride4331]

I get this error. It also kills my whole graphic driver and forces to restart. Driver version: 417.35, specs like my profile signature.

Code: Select all

....
CUDA error 999 on device 0: unknown error
  -> failed to deallocate device memory
CUDA error 999 on device 0: unknown error
  -> could not get memory info
CUDA error 999 on device 0: unknown error
  -> failed to unload module
CUDA error 999 on device 0: unknown error
  -> failed to unload module
CUDA error 999 on device 1: unknown error
  -> failed to destroy CUDA event
CUDA error 999 on device 1: unknown error
  -> failed to destroy CUDA event
CUDA error 999 on device 1: unknown error
  -> failed to deallocate device memory
CUDA error 999 on device 1: unknown error
  -> could not get memory info
CUDA error 999 on device 1: unknown error
  -> failed to deallocate pinned memory
CUDA error 999 on device 1: unknown error
  -> could not get memory info
CUDA error 999 on device 1: unknown error
...

I will pack and sent scene. No idea what happens. This is a deadline job. Thanks again OTOY for this.

Hi mbetke,
could you try to install 417.22 WHQL Nvidia drivers?
To get an effective Nvidia drivers installed, please use DDU Nvidia unistaller drivers (safe mode unistall), the best way to get a clean installation.
Let me hear from you.
http://www.guru3d.com/files-details/dis ... nload.html
Regards
Paride

[mbetke]

I guess the 417.22 doesn't support my Titan RTX cards?

[paride4331]

I guess the 417.22 doesn't support my Titan RTX cards?

Hi mbetke,
yes it do.
Regards
Paride

[anifex3D]

I am using 417.35 with 4 Titan RTX and no problems so far.

[Elvissuperstar007]

Why are the verticals not correct?
physical camera