Archived Old Bugs

[joe_b]

***PLEASE POST ALL BETA 13/13.1 BUGS HERE***

Hey guys.... This beta is the worst I ever tried.... First:

I totally can't understand why render from it looks so shitty. The grain near red cube is supposedly shadow. For me it is some noise which should to do nothing there.. Just mess. It is PNG saved directly by vray frame buffer - non edited result of render. GI switched on in Indirect Illu. and in Environment, material of cube is glossy plastic. (from predefined materials which come with vray) and one rectangular light, intensity 10.. I tried to increase number of samples = same result.

We're using a new version of VRay. I'll pass on your constructive criticism to Vlado. My first thoughts would be either our new default for noise threshold is too high (try setting it to 0.005 maybe) or are you using one of the new colormapping modes? I'll see if Corey or Vlado can provide more information on this.

As for your second problem. I'll check it out. Keep in mind that I don't see every problem that other people have on their machines. Otherwise these problems wouldn't exist. If you don't like being a beta tester then don't do it. Beta testing is for finding problems. If this beta is too terrible for you to use, don't use it.

[edit]
After reviewing your video. All of those problems are caused by some path problem looking for the little m buttons. The reason that exception happened was because you hadn't set a bitmap file before you hit update. I will fix this as soon as possible.

[joe_b]

Re: A couple of bugs

For the noise procedural:

The octaves arrows (to change value) are inversed.

The Perlin setting renders black even with no black used.


Thanks,
Glen

Yeah I noticed the perlin noise thing, it does the same with inflected Perlin. I've already informed Vlado about those two issues. I'll look into the octave issue, thanks.

[joe_b]

***PLEASE POST ALL BETA 13/13.1 BUGS HERE***

Crash bug help:
I have here a file from the previous release. If I open it, than Rhino crash. I have send the file per email to Corey.
My experience: It helps to rename the VrayForRhino.rhp and to open the file without Vray. Than, rename back the plugin and load it manual per rhino plugin manager again. A few global settings are set back, but the materials seems to work fine.

Yes please forward that scene on to us.

[flipside]

***PLEASE POST ALL BETA 13/13.1 BUGS HERE***

Ok, I guess my comments came trough a bit harsh, that was not my intent

About fresnell, I know I couldn't do this before either. In max, this is possible because the fresnell is available seperately from the map button. The setup you have know would be the same as kicking out fresnell parameter in max and use a fallof map instead. With that setup in max, you would also need a blend map to blend the falloff and checker map together.

When you can blend maps this will indeed be possible. I'm just wondering if there isn't a way to leave the fresnell option in the main material window and do the underlying apply map math 'behind the scenes'. That way you can access the fresnell parameter much quicker, and you better see what you're doing.

The ability to add a refraction value was a hack that Vlado added a while ago to combat the problem you brought up about needing different refraction / fresnel IORs.

Yes, and thanks for that But now it looks weird. If the fresnell map would only have reflection IOR now, that would be enough, because you can set refraction IOR in the refraction layer = seperate (in what case would you ever set refraction IOR in a fresnell map you put in the reflection color slot?) Maybe it's as simple as hiding the refraction ior controls in the fresnell map.


I'm not at all saying you should take away layering! And I agree you answer all questions very well & fast & you listen to all our complaints/suggestions etc...


One major thing in the material editor that would improve usability, is that you would be able to resize the mat editor window in all directions. Also the internal regions, like for example the layer part which is very small to navigate. If you can resize the mat editor, you can see many more parameters at once. You must agree that this looks a bit overcrowded now:

[joe_b]

***PLEASE POST ALL BETA 13/13.1 BUGS HERE***

Ok, I guess my comments came trough a bit harsh, that was not my intent

Its ok I'm a bit on the defensive this morning

I totally agree with the resizing issue, I will accomdate this for our next major release (I'm sure we'll be putting out a quick bug fix release pretty soon so all of you can test our product easier )

As far as the behind the scenes stuff, I suppose we could do that...it just seems redundant to have the fresnel texture UI and then replicating it in the reflection window, as you say, it is already crowded in there. The reason I am hesitatant to change it is because it seems to me that this is just an initial reaction to a changed UI. I wonder if you play with it a bit more if it will not seem so out of place? However, if this is a common feeling among users I will do whatever I have to do to make this user-friendly

[DarkLight]

***PLEASE POST ALL BETA 13/13.1 BUGS HERE***

As for your second problem. I'll check it out. Keep in mind that I don't see every problem that other people have on their machines. Otherwise these problems wouldn't exist. If you don't like being a beta tester then don't do it. Beta testing is for finding problems. If this beta is too terrible for you to use, don't use it.

Oh, no problem, I like being betatester, sorry for strong words. I was just screwed up by situation here (quarrel). I just wanted to point out of some "problems"? Well, grainy shadow is not so big problem, I think better settings will fix it (anyway, in other betas it was great immediately past the installation) anyway, fresh instalation of vray freezing when you try to open bitmap for GI or background, I think it is serious bug, huh? And then it causes path problem

Sorry again, dont be angry with me... I'm glad I'm tester

[joe_b]

***PLEASE POST ALL BETA 13/13.1 BUGS HERE***

Oh, no problem, I like being betatester, sorry for strong words. I was just screwed up by situation here (quarrel). I just wanted to point out of some "problems"? Well, grainy shadow is not so big problem, I think better settings will fix it (anyway, in other betas it was great immediately past the installation) anyway, fresh instalation of vray freezing when you try to open bitmap for GI or background, I think it is serious bug, huh? And then it causes path problem

Sorry again, dont be angry with me... I'm glad I'm tester

Its no problem, there is just no need to describe problems by insulting our hard work.

Anyway, I'm working on fixing all of these issues, and I believe Vlado has updated the Vray Sdk today to fix some of the image sampling problems. I'll try to release a better version for you all to test some time today or tomorrow.

[edit]
I appreciate you editing your post - it wasn't necessary, but thank you.

[DarkLight]

***PLEASE POST ALL BETA 13/13.1 BUGS HERE***

Hey Joeb. Downloaded and installed Beta 13.1.... all is working smoothly, there is no problem with freezing or path Perfect job!!!

[Thomas An._cg]

***PLEASE POST ALL BETA 13/13.1 BUGS HERE***

Hi,

I am gettng a delay on each render attempt. The progress window gets stuck on "Building static raycast accelerator". It proceeds normally after a while, but the render is no longer instanteneous.

Is this new ? (is it by design ?)

Regards,
Thomas

[broozee]

***PLEASE POST ALL BETA 13/13.1 BUGS HERE***

I have the same problem!

Bill

[Thomas An._cg]

***PLEASE POST ALL BETA 13/13.1 BUGS HERE***

I am having trouble controlling the DOF in this latest release (the focal distance parameter is not producing changes).

Anyone have the same problem ?

[joe_b]

***PLEASE POST ALL BETA 13/13.1 BUGS HERE***

Hi,

I am gettng a delay on each render attempt. The progress window gets stuck on "Building static raycast accelerator". It proceeds normally after a while, but the render is no longer instanteneous.

Is this new ? (is it by design ?)

Regards,
Thomas

Yes I've told Vlado about this. It is actually working, I believe he is just failing to update the progress as it works. Perhaps Vlado could shed some light on what these new calculations are up to.

[joe_b]

***PLEASE POST ALL BETA 13/13.1 BUGS HERE***

I am having trouble controlling the DOF in this latest release (the focal distance parameter is not producing changes).

Anyone have the same problem ?

I haven't tested DOF in a while, I'll play around with it a bit

[Thomas An._cg]

***PLEASE POST ALL BETA 13/13.1 BUGS HERE***

I have a scene which was started on beta12.1 ....
... now on 13.1 all lights are reset to default values every time the scene is loaded.

(The lights are Rhino rectangular; they are not surfaces)

[Thomas An._cg]

***PLEASE POST ALL BETA 13/13.1 BUGS HERE***

Hi,

I am gettng a delay on each render attempt. The progress window gets stuck on "Building static raycast accelerator". It proceeds normally after a while, but the render is no longer instanteneous.

Is this new ? (is it by design ?)

Regards,
Thomas

Yes I've told Vlado about this. It is actually working, I believe he is just failing to update the progress as it works. Perhaps Vlado could shed some light on what these new calculations are up to.

If we choose "renderWindow" the render never starts (it is stuck on raycast indefinately)