Archived Old Bugs

[craiggorton]

Re: **** PLEASE POST ALL VFR4 BETA 1 PROBLEMS HERE *****

I was mousing over the global gamma correction and the two check boxes underneath it (RGB..) Also the boxes above that were doing it, too. You have to move up and down to get it to do it.

[Gijs]

Re: **** PLEASE POST ALL VFR4 BETA 1 PROBLEMS HERE *****

- I can't install the beta either without uninstalling VrayForRhino3 first.

- Displacement seems quite unstable, I was testing it on a sphere and with different settings it can crash Rhino after hitting the render button.

- I can't change the way Rhino maps the displacement, also there are seam artifacts: First image shows the displacement mapping, second shows bump mapping. As you can see in both cases there are problems at the seams between the 'edges' of the box map. This has been noted in Rhino3 as well IIRC.




- custom mesh setting per object is ignored by displacement.

- will there be controls how Vray handles the subdivision?

[dalomar_cg]

Re: **** PLEASE POST ALL VFR4 BETA 1 PROBLEMS HERE *****

Gjis,

We've been having a discussion about displacement here http://www.asgvis.com/index.php?opti...0&topic=1885.0 I definitely think that there needs to be more control of displacement. Your insights would be good, since you've got quite a bit of max experience as well.

[everydayobjects]

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

When I do a renderinwindow command, then adjust any Vray settings, the render stops. (Unlike being able to adjust settings while using normal render.)

Thanks,
Gavin

[merlik585]

Re: **** PLEASE POST ALL VFR4 BETA 1 PROBLEMS HERE *****

I sended Joe some bugs befor, but befor new beta user spend time to discover it, I post it here again:

- "_renderwindow" in GI mode based on LC (use for glossy rays) cause that the reflected objects are shown dark in reflections

I don't know if it is related to the same thing,but when I do a render window vray skip building the light cache and goes right to the prepass when I have IM as my first engine,if I set both primary and secondary engine to light cache it goes straight to rendering.

Renee

[everydayobjects]

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

I have been using blocks alot recently. I notice that it is only posible to use one colour for any block instance within a file. I tried exporting the same block to a different block files and giving each file a different colour. I then placed each block into the same file and it would only render in one colour. (I hope this is not too confusing...)

Thanks,
Gavin

[Micha_cg]

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

Hmm, last I tested blocks: http://www.asgvis.com/index.php?opti...0&topic=1917.0

But maybe I used R4 beta.

[skysurfer]

Re: **** PLEASE POST ALL VFR4 BETA 1 PROBLEMS HERE *****

Hy all,
the new beta is very promising... the new gamma control helps a lot...

The current beta it's really unstable... but yes it's ok, it's just the first beta..

First bug:
The main problem I have are about texture mapping. I can't use the tiling in mapping option because I get strange result. At the first rendering works, then I change the tiling (for example from 1 to 30) and the texture becomes like a small noise (but the window preview is good). Then If I try to change back to 5 or 1 the texture reamin like a small noise.

Second bug:
I tryed to use the cloth maps (really good) but If I try to set the tiling (inside the cloth option) I get strange surface apparing on the rendering.

Thanks to all...
If canhelp I can send an example but I have a lot of copyright problem with this... Maybe this night I try with an different object.

[skysurfer]

Re: **** PLEASE POST ALL VFR4 BETA 1 PROBLEMS HERE *****

Sorry I forget this:

I'm using/installed

Rhino V4 RC1, Brazil last Wip and Penguin 2 vers. 11 and the Techinical Drawing plugin.

Bye

[joe_b]

Re: **** PLEASE POST ALL VFR4 BETA 1 PROBLEMS HERE *****

- I can't install the beta either without uninstalling VrayForRhino3 first.

Yes - I have found the problem with the installer, sorry for the inconvenience guys.

- Displacement seems quite unstable, I was testing it on a sphere and with different settings it can crash Rhino after hitting the render button.

If you could provide me with a test scene or go into more detail about what your using for the displacement map I'd appreciate it.

- I can't change the way Rhino maps the displacement, also there are seam artifacts: First image shows the displacement mapping, second shows bump mapping. As you can see in both cases there are problems at the seams between the 'edges' of the box map. This has been noted in Rhino3 as well IIRC.

Ok - i'll check that out

- custom mesh setting per object is ignored by displacement.
- will there be controls how Vray handles the subdivision?

Yes - this is an oversight of mine. I forgot to put the UI in. Sorry about that :-[

[joe_b]

Re: **** PLEASE POST ALL VFR4 BETA 1 PROBLEMS HERE *****

I don't know if it is related to the same thing,but when I do a render window vray skip building the light cache and goes right to the prepass when I have IM as my first engine,if I set both primary and secondary engine to light cache it goes straight to rendering.

Did that happen in Rhino 3.0 too? Or is this unique to the VfR 4.0 beta?

[joe_b]

Re: **** PLEASE POST ALL VFR4 BETA 1 PROBLEMS HERE *****

First bug:
The main problem I have are about texture mapping. I can't use the tiling in mapping option because I get strange result. At the first rendering works, then I change the tiling (for example from 1 to 30) and the texture becomes like a small noise (but the window preview is good). Then If I try to change back to 5 or 1 the texture reamin like a small noise.

What are you using for a uvw generator? An explicit map channel? If you are using explicit map channel and are using the default surface uvs then the problem is that the default surface uvs are on channel 0 - as explained above.

Second bug:
I tryed to use the cloth maps (really good) but If I try to set the tiling (inside the cloth option) I get strange surface apparing on the rendering.

Maybe this is the same problem? Maybe you could post an image of this effect or email a test scene to me so I can see what your seeing. Your scene will be kept in confidence unless you explicitly say otherwise. Thanks

[joe_b]

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

When I do a renderinwindow command, then adjust any Vray settings, the render stops. (Unlike being able to adjust settings while using normal render.)

hmm thats odd...do you have "Batch Render" un-checked?

I have been using blocks alot recently. I notice that it is only posible to use one colour for any block instance within a file. I tried exporting the same block to a different block files and giving each file a different colour. I then placed each block into the same file and it would only render in one colour. (I hope this is not too confusing...)

By color you mean just a basic material diffuse color - or V-Ray material diffuse color? Sorry - I don't use blocks much so I'm not sure if you mean something else by color.

[merlik585]

Re: **** PLEASE POST ALL VFR4 BETA 1 PROBLEMS HERE *****

I don't know if it is related to the same thing,but when I do a render window vray skip building the light cache and goes right to the prepass when I have IM as my first engine,if I set both primary and secondary engine to light cache it goes straight to rendering.

Did that happen in Rhino 3.0 too? Or is this unique to the VfR 4.0 beta?

VfR 4.0 beta only never had that problem with Rhino 3

one other thing,each time I use vray in Rhino 4,and close rhino,I have a new rhino4 in the task manager.At one time I had 3,I have to kill them manually.
If I use Rhino without doing a rendering it closes correctly.

[dalomar_cg]

Re: **** PLEASE POST ALL VFR4 BETA 1 PROBLEMS HERE *****

The closing thing isn't a vfr4 problem, but more of a Rhino 4 problem in general. Many users on the news group have been saying they've been having the same issue. I remember someone saying it was possibly because of logitech drivers, but I don't think its been pinned down to one thing in particular at the moment.