Archived Old Bugs

[merlik585]

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

Micha is beta 2 available somewhere ?

[dalomar_cg]

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

Beta 2 is only available to a private test group at the moment. This however is the last stage before it gets released publicly.

[Micha_cg]

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

Some times the sun cause little white spots at reflections. Vlado was talking about to add some extra options to avoid it.

http://www.chaosgroup.com/forum/phpB...ight=sun+spots

Please don't forget to add it.

A workaround can be, to use clamp output and subpixel.

[Travis Serio_cg]

**** PLEASE POST ALL VFR4 BETA 2 PROBLEMS HERE *****

We just started testing the DR stuff and here's what we have found so far.

here is the image as is



Here is the same image with 5 nodes (9 buckets)




The nodes do not seem to have the correct GI multiplier or color information? as they always render at what looks like 2x whatever the current GI multiplier is.


DOF does not seem to be calculated by any of the child nodes.


Also, one small other thing was that ALL of the nodes had to have the HDR maps in the same location as the render server. like C:\Maps\*.hdr otherwise they message that they cannot locate the file... that's a pain.

Another last thing was that we found VFR itself HAS to be installed on the machine or the DR Spawner app will crash. perhaps there are still some missing runtimes?

[andreas]

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

Hello ASGVIS Team, hello Forum

as Micha pointed out there seems to be a problem in DR concerning the transfer of certain parameter values from vray to the slaves. The bucket problem occurs with multipliers of textures, colormapping values, physical sky and so on. Another thing i noticed is that alpha channels like "raw GI" "shadows" and so on, are not rendered by the slaves (the buckets stay solid white).

The displacement map is still a little bit hard to understand. I tried to create nice gras plane but it seems that there is some kind of fixed subdivision which prevents very fine displacement meshes. It seems that this can be compensated somehow by meshing the plane manually with a and very small value e.g. for maximum edge lenght. I guess we will see more detailed options in a later version, so this is probably solved then anyway.


Another thing is that the displacement map still is somehow connected to the used diffuse map. It happens that you can not influence your displacement map by the displacement map repeat values but by the diffuse repeat values. Size in displacement map option is sometimes not updated until you assign a diffuse map at least temporarly.

I keep on hunting

Andy

[Micha_cg]

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

Hello ASGVIS Team, hello Forum

as Micha pointed out there seems to be a problem in DR concerning ...

Not I, I don't have enough hardware to test it, but I hope next week.

... It seems that this can be compensated somehow by meshing the plane manually with a and very small value e.g. for maximum edge lenght. I guess we will see more detailed options in a later version, so this is probably solved then anyway.

Thanks, this suggestion helps a lot at a current project.

[dalomar_cg]

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

Yes the displacement features at not fully developed at this time, so the will change to hopefully have a few more controls.

As far as what you experienced with the displacement is a great find. The reason why this happens is that Rhino typically meshes simple planes as simply as possible, usually with either one quad or two triangles. Because of this mesh has very few faces getting a more detailed displacement requires much more subdivisions (something we can't currently control). So in order to create better displacement (an also have it render faster and be more stable) more faces are needed. I'm not sure if you actually made a mesh for your plane or not, but my suggestion would be to override the global mesh settings in the object properties and set it from there. It would probably be a bit simpler, and less objects to deal with.

There is a thread on the CG forum that explains it in more detail...here it is http://www.chaosgroup.com/forum/phpB...ic.php?t=14300

...btw I think it was Travis who did the dr test, not Micha

[Travis Serio_cg]

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

it was me :P

[dalomar_cg]

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

Gotta give credit where credit is due

[Gijs]

VfR4 beta 2

bug: a bitmap in the reflection or highlight glossiness cancels out the reflection layer

[merlik585]

Re: VfR4 beta 2

first thank you to have made beta2 available to everybody.

May be it is me may be it is a bug,no matter what I try I can't have a reflection when I use the physical camera,and a sun.

Renee

[dalomar_cg]

Re: VfR4 beta 2

with the sketchup 2 sided material, the front material appears in reflections even if the back material should be reflected...the concrete material in the reflections is the front material

[smail]

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

Hi, I was trying to use distributed rendering, but I could't run the program VRayForRhino_DRSpawner.exe on the second computer! It writes "Start to run of this program wasn't do, because the configuration of aplication isn't right. This problems will can be solve by new instalation of the aplication" (translation from Czech). The computer use WinXP Home SP2; CPU CORE 2 Duo 1,6 GH. I normaly unrar the DRSpawner.rar, so do you know where is the problem?
Note> If try to run program on another computer (WinXP Pro SP2, CPU ATHLON 3500+ 64bit), the program runs, but the render is with white square - but this problem can be do by problems between 32bit and 64bit CPUs, Becose Rhino 4 with VRay runs on CPU Centrino 1,5GH 32bit.
I use Rhino 4 and V Ray for Rhino 4 Beta 2
Thanks for your reply. Smail

[corey]

**** PLEASE POST ALL VFR4 BETA 2 PROBLEMS HERE *****

Beta 2
Bug Fixes

• Default surface uvs are now on mapping channel 1 instead of 0
• Installer will not uninstall VfR 3
• Field-of-view issues with Physical camera should be resolved
• VRay2SidedMtl should be working ok
• VRaySkp2SidedMtl should be working ok
• Material Editor / Options / Tex Ed remember their sizes between Rhino sessions

New Features

• Physical sky/sun

- use the RDK command "SunLight" to create a sun-light based on location in the world/time
- you can use the Rhino default light as a sun too, though we suggest you use "SunLight"

• Distributed rendering

- In the root V-Ray for Rhino directory ( Program Files/Rhinoceros 4.0/Plug-Ins/VRayForRhino ) you will see a file called DRSpawner.rar. If you extract(WinRar) that to a directory on another machine and run the DRSpawner.exe command it will start up the render slave
- To shut the slave down hit ctrl-c in the command prompt window
- There is a bug with the current V-Ray Core in which 64bit machines cannot communicate properly with 32bit machines under DR conditions
- To choose which slaves to use and to enable DR you will find the settings in our global options "System" tab

[Gijs]

Re: VfR4 beta 2

Maybe a moderator can move this thread and the gamma issue thread over to the beta 2 bugs thread to keep things tidy. I didn't notice that thread until today.