OctaneRender® for Maya® 3.08 - 12.32-Beta[OBSOLETE]

[BK]

Hi Bikram,

I'm getting this errors due the GPU tab in most all my scenes:

CUDA error 201 on device 0: invalid device context
-> failed to create link
// Error: print("device 0: failed to create OSL compile context: //
// Error: Line 1.55: Unterminated string. //
device 0: failed to compile module 0

I don't know why soon I uncheck "Use all available GPUs at Full power" I have two GPU Quadro and GTX when I activate use the 1 display start this problems I didn't had this before.
and I think is a plug Issue cause the Standalone has no such error.

Best,
JO

Hi Jo,

Would you mind sharing the scene for us to debug here? If it has copyright then please PM me.

Cheers

[BK]

Since some time has passed I thought I'd check this out, and nope, it's still unusable.
The kernel doesn't even refresh automatically when you assign a material....

Hi Rikk,

Thanks for testing the plug. Maybe you launch IPR before applying the Octane material.
Did you try reload button?? Anyways, this will be improved in the next release.

Cheers

[Rikk The Gaijin]

Since some time has passed I thought I'd check this out, and nope, it's still unusable.
The kernel doesn't even refresh automatically when you assign a material....

Hi Rikk,

Thanks for testing the plug. Maybe you launch IPR before applying the Octane material.
Did you try reload button?? Anyways, this will be improved in the next release.

Cheers

The point is, if I assign a new material, the viewport (or the IPR) must update immediately, like it always has. I cannot accept having to click refresh every time, that's ridiculous. Also you can only refresh the IPR, not the Octane Viewport.

Another thing: can you add an option to move the render information of the Octane Viewport on a different position? I use the scene stats and they overlap because they are also on the top left corner.

[Rikk The Gaijin]

I'm trying to render a scene saved with 3.06.4 - 11.10
Every time I click on IPR I get this "Translating transform object" message at the bottom and it takes over 30 minutes before starting render... EVERY SINGLE TIME.

[Jolbertoquini]

Hi Bikram,

I'm getting this errors due the GPU tab in most all my scenes:

CUDA error 201 on device 0: invalid device context
-> failed to create link
// Error: print("device 0: failed to create OSL compile context: //
// Error: Line 1.55: Unterminated string. //
device 0: failed to compile module 0

I don't know why soon I uncheck "Use all available GPUs at Full power" I have two GPU Quadro and GTX when I activate use the 1 display start this problems I didn't had this before.
and I think is a plug Issue cause the Standalone has no such error.

Best,
JO

Hi Bikram,

Is not a scene in particular is any scene really can be a empty default scene with sphere I have the issue. Is looking like is broken the GPU option if you chose to use the power of one and other for display.
After switch on and off some GPU start giving this errors in any scene.

Cheers,
JO


Hi Jo,

Would you mind sharing the scene for us to debug here? If it has copyright then please PM me.

Cheers

[calus]

I'm trying to render a scene saved with 3.06.4 - 11.10
Every time I click on IPR I get this "Translating transform object" message at the bottom and it takes over 30 minutes before starting render... EVERY SINGLE TIME.

Hi Rikk, I have the same issue with all my production scenes (30 mn being a minimum), this is because of this :

Known issues:
- Autodesk developers are working on a new context-driven API for plugins. It started with Maya 2018, and in theory it must dramatically improve the scene translation performance for Octane when this API gets completed and polished. But in current state it is just partially implemented, and even those parts implemented are buggy and do not work correctly (even lead to Maya crashes sometimes when the plugin tries to use this new API).
So, Octane plugin now uses this new API whenever it is possible, but only in aspects where it works correctly. It already allowed to eliminate scrolling the timeline back and forth during scene translation for some particular objects that did not support context-driven data output earlier. But some Maya objects (like nHair for example) still don't support any kind of context-driven data output - neither old approach nor the new Autodesk API. And some objects which now (with Maya 2018) show some signs of starting to be supported by the new API (like e.g. instancer) - still don't work correctly with the new API and even crash in some cases.
Thus for now: for the scenes having such objects in them, expect the timeline is still scrolled back and forth during translation of the scene (this happens only when "Frames to pre-cache" is set to some noticeably-high value and only during the first translation or when such objects got changed during rendering session). This does not affect the rendering quality, it is mostly the matter of visual attraction of how Maya API supplies the plugin by objects' data from different time-contexts...

I know JimStar is trying to improve the situation but this might take a while. In the meantime you can try to set "frames to precache" to 0, this disables the "cache animated objetcs" feature but may solves the pre-compute time issue.

[Rikk The Gaijin]

Hi Rikk, I have the same issue with all my production scenes (30 mn being a minimum)

Jesus, this plugin is a disaster... I'll stick with 3.06... R.I.P.

[BK]

Hi Bikram,

Is not a scene in particular is any scene really can be a empty default scene with sphere I have the issue. Is looking like is broken the GPU option if you chose to use the power of one and other for display.
After switch on and off some GPU start giving this errors in any scene.

Cheers,
JO

Hi Jo,

Thank you, just making sure if you have both the cards checked/enabled or is the GPU display uncheck?
Seems the CUDA error comes up when we use the display and have the "Use all GPU power" enabled.

cheers