Archived Old Bugs

[Micha_cg]

***PLEASE POST ALL V-Ray for Rhino 1.0 BUGS HERE***

I mean the trees of the scene of this thread. The material is a textured diffuse layer with a transparency map. In the rendering, the branches and leaves of the trees are not visible (transparency mapped), only the big planes without transparency.

[Micha_cg]

***PLEASE POST ALL V-Ray for Rhino 1.0 BUGS HERE***

Hi Corey and Joe,

any news from the black bucket bug? I have got this black buckets in a scene (WIP) without SSS too.



Joe, here an example of the last z-buffer bug (I have disabled all lights for a quick report image).

[joe_b]

***PLEASE POST ALL V-Ray for Rhino 1.0 BUGS HERE***

I played around with it for a half hour last week without reproducing the black buckets. I'll look at it again as soon as I can.

[Micha_cg]

***PLEASE POST ALL V-Ray for Rhino 1.0 BUGS HERE***

I know, the gamma usage will be refined. A bug of the current release is, that the color mapping is not used for the material preview. So, a rendering of a material with gamma 2 looks totaly different from the material preview.

[joe_b]

***PLEASE POST ALL V-Ray for Rhino 1.0 BUGS HERE***

None of the actual scene options are used in the material preview. Its meant for an estimation only.

[Micha_cg]

***PLEASE POST ALL V-Ray for Rhino 1.0 BUGS HERE***

None of the actual scene options are used in the material preview. Its meant for an estimation only.

If an user use gamma 2 and the preview use gamma 1, than we can not speak from an estimation anymore.

[joe_b]

***PLEASE POST ALL V-Ray for Rhino 1.0 BUGS HERE***

Just as a user with completely different environment/lighting/sampling will get different results.

[Micha_cg]

***PLEASE POST ALL V-Ray for Rhino 1.0 BUGS HERE***

Just as a user with completely different environment/lighting/sampling will get different results.

I hope this don't mean, the gamma problem is not so important. The current VfR works with a wrong mix of gamma values. Most user use gamma corrected textures, but the default VfR use a gamma 1 for lighting. But most user need a gamma 2.2 output. The gamma 1 material preview dosn't work on 99% of the user screens. My fresnel reflection thread has shown, that the fresnel reflection looks totaly different and wrong in gamma 1 mode.
I think, if we want, that any user get best quality images, than we must find a way to get a simple gamma correct worflow working. This simple feature is my most wanted feature for the next SR. Sorry, if I'm a pain in your neg. (I hope my online translator give me the right phrase )

[joe_b]

***PLEASE POST ALL V-Ray for Rhino 1.0 BUGS HERE***

I hope this don't mean, the gamma problem is not so important.

The gamma problem is an important issue. I'm simply saying that our material editor is used for an estimation only. There are many things that affect the output of the material preview.

I realize the problem of not having gamma-corrected color pickers and the like. We will be addressing these issues.

[Micha_cg]

***PLEASE POST ALL V-Ray for Rhino 1.0 BUGS HERE***

[Micha_cg]

***PLEASE POST ALL V-Ray for Rhino 1.0 BUGS HERE***

I'm not sure I have post this problem befor: if I explode the objects of the attched file and render the scene, than Vray need a long time to create the geometry table. This effect is for some scenes very bad.
Interesting, if I do the same: open the file - explode - but render with a Rhino renderer, than the render process starts within a second. Could be good, if vray could go the same way.

http://www.simulacrum.de/download/Ge...bleProblem.3dm

[joe_b]

***PLEASE POST ALL V-Ray for Rhino 1.0 BUGS HERE***

Yeah - our geometry parsing isn't optimal in some cases. We just use the default Rhino meshing for the most part - but I need to work some voodoo on Meshes, and especially Blocks, to get mapping from them which can add some serious time. I'll check out that scene and see if I can track down the bottle neck.

[Micha_cg]

***PLEASE POST ALL V-Ray for Rhino 1.0 BUGS HERE***

Since a long time I have the feeling, that we have a memory leak. I know this problem from Rhinoman, there was the same problem: after every new rendering the memory will less and less. And if the memory is full, than Rhino crash. My current scene waste approx. 35 MB per rendering.

535 MB -> start rendering -> 430 MB -> falling under 300MB -> render finish -> 499MB

[joe_b]

***PLEASE POST ALL V-Ray for Rhino 1.0 BUGS HERE***

Interesting - its possible. I'll see if I can track anything down where this memory could be going.

[Micha_cg]

***PLEASE POST ALL V-Ray for Rhino 1.0 BUGS HERE***

Sidenote ... it's very important for animation. I had the problem with Rhinoman some years befor - after less than 100 frames (from 2000) Rhino crashed.