Hi, Another member, oli, recently did an extensive/exhaustive test with Twilight on this subject. Some of his final renders are amazing and deserves to be read. I know it's not VRay but his experience and suggestion might help? Click here [image: file.php?id=3071] @oli: Hope you don't mind?

Every length unit in VfSU refer to inches. Displacement multiplier for instance 1.0 = 1 inch. Override focal distance - inches.

You must use the VrImage to .exr tool found on ASGVis website, then open the .exr in an image editor and resave in the format you want.

just a heads up, the OP posted this thread 4 years ago.

@arjunmax09 said: Do you've faced any such situation earlier?? No. @arjunmax09 said: The vray isn't accepting any alpha map.. What do you mean by it isn't "accepting"? Are you getting errors?

@earthmover said: I've tested it with the latest build of Vray and it renders fine. Perhaps you should try upgrading. With the new version you don't need a clipmap for faceme plants. It's a free upgrade and well worth it, IMO. I have full version of Vray version 1.05.30 ... will I be able to upgrade it for free?? @earthmover said: Regarding getting the render output to match the SU camera, you have to use ThomThom's Vray Toys plugin to set the aspect ratio in SU to match that of Vray. Can you upload a screenshot of the above procedure..?? I've tried doin' it but the vray output remains the same... even in the options tab...

Hi Thom & Kalf, I just found something curious about the vray settings (don't know if it's only in my case) I just change the override viewport and get view aspect in the output menu and my renders was lessen to almost twice the render time and with the same settings that took me 6 hours same scene and same output size, here is the screen shot, don't know why[image: 5g0Q_2010-03-27_08-01_V-RayforSketchUp-Render.jpg]

Thanks for the reply. I tried several other models last night and they seem to act as expected so maybe there's something unusual about this one. I work in modo and I like rendering in modo but VRay seems to give everything a very distinctive 'light'. There's a clarity to the light that I haven't been able to achieve with other rendering apps. I'd like to have that as an option so I intend to spend some time exploring VRay. Hard to beat the modo Preview though. Again, thanks for the reply

A few more levels of subdiv would get rid of those nasty black bits around the blobs

this bug is still there? i'm using 1.49.01 there is still a slight difference. [image: SSBP_31.jpg]

ok, I found the "spots" problem - it was connected with bulbs. It works now. Thanks

@chrisglasier said: Google translation: "anyway thanks for the many responses, clowns"! Yeah, I ran it through Google's translator as well. Ozzidora, do you always insult people for not helping you fast enough to your liking? I suggest you either reconsider your attitude or pack up and leave.

http://forum.asgvis.com/index.php?topic=7539.0

thomthom, thank you for your support! Mark

@tomot said: Missing on mine aswell, All previous versions of VfSU had Low Priority.

No worries. The version numbering of VfSU is somewhat unusual - IMO.

Sorry, the above picture, with its blowout lighting, was rendered with version v1.48.66. I have now installed v1.48.67, and giving it a try. I tried to render the same Scene, however after 50 minutes the, Building Photon Map process was only 70% done, hence I abandoned, the Rendering process. Something is clearly wrong! thomthom, you still have my file and png's of my settings. Perhaps if you have time, you might give it a try.

tomot - Our previous version of our plugin was written in C++ and used a binary format. This made our plugin much more difficult to maintain than it needed to be. Now we use Python and XML, which will allow our stuff to be more flexible and forward/backward compatible. I understand it's nice to be able to use the same files you would use in a new version, in an old version... but this isn't something that happens very often in the software world. We are trying to achieve that goal though. I would like to point out that it's free to upgrade to the latest version of our product though, and hopefully after this patch, this will be a very stable and flexible plugin. Anyone that signed up for our beta - We had MANY beta applicants. We didn't really hand pick anyone. We waited too long to get our product out to testing, so we didn't really have time to hand pick anyone. We thought that if we allowed 700 or so eager users to use our plugin and test it out, we would be able to get feedback from a diverse group of people that would hopefully represent a majority of our users... That didn't quite work out. Instead of getting 700 users that were constantly testing and reporting back any bugs they found... we got maybe 10... 15? people to really give us any feedback. There was enough feedback to keep us busy though, and so we put our heads down and got to work. Since the developers were in charge of the WIP testing (corresponding with our users, and providing support/debugging), the developer blog (sorry if anyone was keeping up with that... I hope to update it at some point), and developing our plugin. We were too busy developing to mess around with finding more testers and sorting the bunch we already had. It was sad. We even added a couple people here and there after the WIP tester selection was made, and they would provide some feedback here and there, but quickly faded away as their interest faded (I'm guessing that's what happened... maybe they were eaten by sea monsters?). So that's why some people got left out. It's nothing personal, you just fell through the cracks unfortunately. Next time around, we'll try to be more particular about who we let in... or we'll just do a public beta... haven't figured that one out yet.

I don't see why it would render correct for you. It render fine with the latest version. (I don't have the original to try any more)