OcDS 1.2.120.34xx - BUG REPORTS

[vortex3d]

Unable to render an empty scene.
Upon opening the viewport, the top orange progress bar just cycles without indication of what's happening.
Is this the default behavior?

yes. you just can't render nothing
(or at least octane can't)

the reason is that raytracing just needs a geometry to shoot view rays at and shadow/color rays from (to trace them to any available light source). so even if rendering would start, it would just render nothing (no visible color, no light either); if you are interested in the principles, wikipedia gives a little more insight as i can give you here: http://en.wikipedia.org/wiki/Ray_tracing_(graphics)

ps: for completeness the viewport should give a slight feedback in this case (where it tells waiting/building, render time, etc) sthg. like "no geometry to render" or so...

I was just trying to get a preview of the sky as I experimented with the daylight system.
The issue was the misleading progress bar as I though it was stuck processing the scene.
Perhaps graying out the viewport button until an object is loaded would be more intuitive?
Some users might not be experts in ray tracing principles or know the plugin can't render just the sun and background?
Just a friendly suggestion.

ps: Thank you for the link, it was very informative.

[t_3]

I was just trying to get a preview of the sky as I experimented with the daylight system.
The issue was the misleading progress bar as I though it was stuck processing the scene.
Perhaps graying out the viewport button until an object is loaded would be more intuitive?
Just a friendly suggestion.

ps: Thank you for the link, it was very informative.

early (pre-release) versions of the plugin had the vp button in fact disabled, but it turned out to be rather counter intuitive if the most important button is not working all the time - it'll then still need to present a reason why it is disabled. so i think i'll add an unmistakable message to the viewport when either there is no geometry in the scene, or all scene nodes are set to invisible in studio ...

[vortex3d]

I was just trying to get a preview of the sky as I experimented with the daylight system.
The issue was the misleading progress bar as I though it was stuck processing the scene.
Perhaps graying out the viewport button until an object is loaded would be more intuitive?
Just a friendly suggestion.

ps: Thank you for the link, it was very informative.

early (pre-release) versions of the plugin had the vp button in fact disabled, but it turned out to be rather counter intuitive if the most important button is not working all the time - it'll then still need to present a reason why it is disabled. so i think i'll add an unmistakable message to the viewport when either there is no geometry in the scene, or all scene nodes are set to invisible in studio ...

That would work by letting us beginners know what's going on.
Thank you for humoring my thoughts and ideas.

[t_3]

That would work by letting us beginners know what's going on.
Thank you for humoring my thoughts and ideas.

seriously: i can make good use of different viewpoints. being into this for a long time already, and unfortunately a bit off from real work, any feedback to make the plugin easier and more intuitive to use is more than welcome. what is possible and makes sense will find its way in sooner or later...

[michael_g]

Has any one got Asian court 3 they can test? it`s crashing studio right after octane creates all the mats. I going to msg the the author Jack tomalin as well.

Just to update this, the crash happens when you select the system tab and only that particular tab.

[t_3]

Has any one got Asian court 3 they can test? it`s crashing studio right after octane creates all the mats. I going to msg the the author Jack tomalin as well.

Just to update this, the crash happens when you select the system tab and only that particular tab.

i expect this to be also a problem when reaching limits of some sort; i noticed just yesterday, when reviewing the problem DrHemulen reported (a 2nd time), that octane reports random numbers for free vram when vram usage is maxed out; could be connected to that. btw, how much vram does your gpu have?

@DrHemulen - this is also the reason why my last fix didn't fix anything; i can still work around this particular problem, so it should be sorted out with the next update.

@all: i'm currently implementing a check and barrier for adding additional maps if this is about to happen. the downside is, that i only know _after_ rendering had started how much vram octane needs for the scene geometry, and then it would be already too late of course. in addition it depends on the render size how much additional vram is needed for the film (20 bytes per pixel). i therefore need to set the map safety limit rather low (at about 80% or around 2-300mb free vram).

in this case the plugin will still create still materials but just not apply new maps (during auto create).

when dealing with large scenes it is probably a good idea to turn auto mats off before loading them. this way you can start rendering, see how much vram the geometry needs, create materials in smaller groups and take appropriate measures like i.e. resize maps before creating new materials; or to set a particular map type explicitly to "floatimg" or "not used" (in the preferences) before let the plugin create new auto materials, or change existing maps sizes/types in the textures tab.

and a final note: the "problem" with daz content and octane is often that there are maps everywhere, when a procedural material would also do. in order to let you choose appropriate live db materials instead of map-loaded converted daz mats, i'm also going to add a hint (probably a badge to the thumbnails) for live db materials that are completely procedural - as it is of course always save (in terms of resources) to apply such materials even when you are already high on vram usage...

[vortex3d]

Has any one got Asian court 3 they can test? it`s crashing studio right after octane creates all the mats. I going to msg the the author Jack tomalin as well.

Just to update this, the crash happens when you select the system tab and only that particular tab.

i expect this to be also a problem when reaching limits of some sort; i noticed just yesterday, when reviewing the problem DrHemulen reported (a 2nd time), that octane reports random numbers for free vram when vram usage is maxed out; could be connected to that. btw, how much vram does your gpu have?

@DrHemulen - this is also the reason why my last fix didn't fix anything; i can still work around this particular problem, so it should be sorted out with the next update.

@all: i'm currently implementing a check and barrier for adding additional maps if this is about to happen. the downside is, that i only know _after_ rendering had started how much vram octane needs for the scene geometry, and then it would be already too late of course. in addition it depends on the render size how much additional vram is needed for the film (20 bytes per pixel). i therefore need to set the map safety limit rather low (at about 80% or around 2-300mb free vram).

in this case the plugin will still create still materials but just not apply new maps (during auto create).

when dealing with large scenes it is probably a good idea to turn auto mats off before loading them. this way you can start rendering, see how much vram the geometry needs, create materials in smaller groups and take appropriate measures like i.e. resize maps before creating new materials; or to set a particular map type explicitly to "floatimg" or "not used" (in the preferences) before let the plugin create new auto materials, or change existing maps sizes/types in the textures tab.

and a final note: the "problem" with daz content and octane is often that there are maps everywhere, when a procedural material would also do. in order to let you choose appropriate live db materials instead of map-loaded converted daz mats, i'm also going to add a hint (probably a badge to the thumbnails) for live db materials that are completely procedural - as it is of course always save (in terms of resources) to apply such materials even when you are already high on vram usage...

Could this also be related to my report on TEXTURE tab crashes? I couldn't replicate it with smaller scenes.

[SimonJM]

Has any one got Asian court 3 they can test? it`s crashing studio right after octane creates all the mats. I going to msg the the author Jack tomalin as well.

Just to update this, the crash happens when you select the system tab and only that particular tab.

Just loaded and tried it - and it works for me, the system tab reports 2478MB VRAM used.

[t_3]

Could this also be related to my report on TEXTURE tab crashes? I couldn't replicate it with smaller scenes.

yes. it's not the only bug in there, even not the only one that can cause a crash, but if it happens it affects both tabs (as both use the stats numbers to calculate other values)...

[michael_g]

Has any one got Asian court 3 they can test? it`s crashing studio right after octane creates all the mats. I going to msg the the author Jack tomalin as well.

Just to update this, the crash happens when you select the system tab and only that particular tab.

Just loaded and tried it - and it works for me, the system tab reports 2478MB VRAM used.

Chears Simon, now I know what the problem is.

@T_3 I have two GFX cards both with 2gb.