Archived Old Bugs

[Gijs]

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

yes, it seems not working. Initially I thought it had to do with your noise threshold being fairly high, but even at 0.001 the result is the same. Using higher QMC AA settings 'fixes' the problem.

[Micha_cg]

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

... only for a complete bug thread: sometimes the fresnel reflections break. Here a simple example in a white environment. Joe got the scene some days befor.

http://i8.photobucket.com/albums/a46/MichaX/ReflBug.jpg

PS: I can not mark an image url as image at the new forum here.

[Gijs]

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

decreasing the reflection/refraction cutoff should fix that (in material options)

[joe_b]

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

The subdiv option of the refraction layer is broken. I can set any value and get the same noise. Only Vlados universal method works, than the subdivs are determinated by the global adaptive QMC subdivs. So, with manual subdivs it's inpossible to render a smooth frozen glass.

Yes, there must be something I'm doing incorrectly. I just dumped out a scene file and it appears the subdivs option isn't being used for refraction. Whups :-[

[Micha_cg]

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

decreasing the reflection/refraction cutoff should fix that (in material options)

Thank you Gijs, it works now. So, it's seems to be a UI "bug", the default cutoff of the material is to strong - 10 times higher as the global cutoff.

[joe_b]

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

Whups - yeah our two cutoffs should be the same.

[everydayobjects]

Crash bug

What a painful evening it has been! The crash occurs when I switch the order of two reflective layers (Both fresnel.) and then do a renderinwindow comand. It happens every time...

Gavin

[everydayobjects]

Maping problems

I am sure this has been mentioned already, but here I go.

The mapping in VFR is rubbish. I constantly have problems doing the most simple things. For example, when I map a basic texture to a rectangular prism with rounded corners the map does not work properly. I have been told to turn the prism into a mesh and then box map it. That worked OK. (Depending on the mesh quality!) However, when I then move/rotate the object the mappinbg corrupts and I have to remap after every move. This even happens on the most simple planes! I have spent the last 48 hours trying to get it solved, but it seems that it is inherent in the software. I really hope these fundamental problems are solved quickly.

Thanks, Gavin

[joe_b]

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

The mapping is not actually a feature of ours. It is done via the RDK (formally known as RCM). The version we use in VfR 3.0 is probably outdated a bit at this point as it pre-dates the official RDK release. In Rhino 4 I've been told the mapping controls are quite a bit better, so I'd imagine when we make use of the newer RDK stuff for VfR4 and VfR3 SR1 some of your problems should be alleviated.

[edit]
Perhaps if you try on the Rhino forums they can help you more than I was able to with your rotation/scaling issues. Or maybe someone else here has had such problems and gotten around them.

[dalomar_cg]

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

First of all if you download the Brazil beta then you will get an RDK(RCM) update which may help. You won't have to go through all of the other Brazil liscencing stuff just install it and it will have the update. That being said there probably won't be too much more help with the whole mapping thing. With Rhino 4 all of the mapping functions are built in and work 100 times better than RDK+Rhino3 at the moment. And since there are very few users who are sticking with Rhino 3, I don't think McNeel is losing any sleep over the subpar mappings in V3 when V4 is just fine. I'm not saying that I agree with that move, but once we release the public beta of vfr4 there really won't be too much of a reason not to use the better mapping capabilities of v4. If there was really something about it that was within our control that would be another story, but we are at the mercy of it just as you are.

[craiggorton]

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

After a quick test with the new RDK (I installed Brazil but didn't activate), it doesn't appear to help. I still can't seem to get the mapping widget grips to show up, and then when I hide it it doesn't go away.
I noticed a displacement tab, but that doesn't seem to do anything- can you confirm?
I will probably not upgrade to Rhino 4 until the VfR4 beta is out, if I can convince the boss. But don't you plan on the VfR3 service release first?

Thanks,
Craig

[Micha_cg]

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

I suppose, if you get the VfR4, than you will not stick at Rhino3. Rhino 4 can much better handle high polycounts. Also, I hope, if Rhino 4 is official released, the McNeel team will improve the mapping functions per SR.

[dalomar_cg]

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

I did say that it "may" help, and unfortuantely it didn't. As far as v4, even if its just 1 seat that may be all you need to be able to have access to the better visualization capabilities of both mapping and polys. I hope you'd be able to swing the relatively minimal cost of one upgrade (only $295 I think, which you could save with the added productivity). The vfr4 beta and the vfr3 sr are for the most part one in the same, so I believe that they will be released within relatively the same time frame. There are a few things that I would personally like from the McNeel team other than improved/advanced mapping but the most important in my book would be a 64 bit version for my new workstation (that way I can justify buying more memory).

I'll look into the rdk displacement, but my guess is no. We have displacement in the v4 beta/v3 sr though

[everydayobjects]

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

I just received my official copy of Rhino4! Does this mean Vray for Rhino 4 will be available too? Only then will I visit mapping heaven...

Gavin

[dalomar_cg]

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

We currently have an internal build for v4 that is progressing nicely. Once it is at a certain level we will have a limited beta, then a public beta. Again there is no explicit timeframe on this, but Joe is working very hard and around the clock on it. There will be much more functionality and greater possibilities with both our new build and V4 as a whole, and we will see where this progresses to in the future. It is good to hear that you already recieved V4 (from Paul I guess). Personally I still have to order mine, as its been hard to find a educational upgrade. I think I have found one that should be shipping today, so I need to put in my order.