@valerostudio said: That makes sense! Thanks Thom! As you found out, setting an aspect ratio in SketchUp and matching the VfSU view usually works. (Though I've had issues at some ratios...) But I find it generally best to set an aspect ratio in SU as the scene can then be rendered on any machine and still be matching. Without the different size of the monitor will mess things up. I also found that rendering Photo Matched scenes doesn't work well. But I recreated the scene as a normal scene with the Ruby API and then it would render. It will be in the update of VfSU Tools 2.0 which I am working on.

@thomthom said: That limit the size of your render to the size of the viewport. If you need highres images, but in the same aspect ratio of the viewport use the "Get view aspect" button and then lock the aspect ratio. Then you can increase the output size and still be relative to SU. So if you save out a 3000px wide image in SU and then render out a 3000px wide image in VfSU they match, no problem. as it indeed, I was wondering if there is a vertical correction for the camera as in 3d max vertical correction at a vray camera or Guess vert, I've tried 2 point perspective but it changes the camera position and if I move it back the perspective changes . so my question is: is it posible to correct verticals (easy way) without moving my view?

No..not loading any GI maps...but vray 2.0 worked for me....i guess older version ddnt support the materials well......anyways tnx evrybody for the responses...

i hope layer change will be supported in the so waited new version..

i'm speechless, great find!

@dkendig said: with the way things currently are set up, we have to basically restart the whole scene parsing process again for each scene if we want to account for visibility changes, which slows down animation renders considerably. i understand, i suspected it.. but maybe would be possible to add it as an option to tick, so that it is not default, but, if you really need it from time to time, you may try to render the animation properly even if slowly.. i don't know, you have to tell, but i think this could be at least an half way solution.. as we say in italy "meglio feriti che morti" ---translation--> "is better to be hurt than to be died" very thank for your answering

did you try to check "keep continuity"?

Hi John, Maybe you need to lower your ambient occlusion value (radius & amount), or increase ambient occlusion subdivs value to 32 or more, if you have fast computer. I'm suspecting it is the ambient occlusion effect behavior. regards, vd

http://help.chaosgroup.com/vray/help/sketchup/150PB/vraydirt_params.htm

Worked like a charm, thanks for the quick response, it was really driving me crazy.

http://www.youtube.com/watch?v=RvOWlhZzq78 <-- Displacement water level tutorial. This will help you punch holes in the geometry.

Thanks chaps, that made the world of difference

Cool Illustration Andybot! So everyone can understand what we are after! Professionnal in architectural photo field always utilize such tool (In french it is called "un objectif à décentrement") It keeps the perspective height (usualy human eye) keep all the subject in the photo and vertical lines stay "vertical". That is exactly what you do in sketchup when you activate "two point perspective". When it is on you can pan the image whitout loosing the perspective point of View. It is a crucial tool in Archviz. Take a look at Thea or Maxwell. the use ot this tool is absolutly obvious...In VFSU it is much less IMO! but andybot approach does work

@stefanq said: Yes, I had this issue in the past. My problem was that the face (surface) was reversed. Use the monochrome style to see if your floor have this problem. Cheers! Hi thanks for the suggestion already tried this. @eidam655 said: [questionable]i would say that the moment when a texture is loaded into the vray material editor, it doesn't make sense to edit the texture size in SU Material editor.[/questionable] the solution, imho, is to change the u/v repeat values in the TexBitmap slot. (so to make the texture bigger, the repeat number needs to be lower.) Hello thanks for the quick response, this solved my problem

The main issue here, in my experience is memory consumption. SketchUp is limited to 4gb of ram, it doesn't matter what hardware you have, what operating system you have, etc. That's why Maxwell has an issue, and it's why V-Ray has an issue. If you are hitting that memory limit, you're going to crash. Sketchup on OSX appears to consume more memory than it does on Windows, as does the V-Ray plugin. Also, if you have multiple Sketchup models open on OSX at the same time, each model contributes to that 4gb memory limit. On windows, this is not the case. Each Sketchup window has it's own 4gb playground to work with. Many other modeling applications have made the jump to become a 64bit application, which allows an application to use far more memory. Currently it's not even possible to have a computer that exceeds the maximum amount of memory that a 64bit application can use (it's something like 18 exobytes). When you load SketchUp, it loads any extensions that are currently installed and active. If you have many plugins, you're going to use more memory. Just loading V-Ray's dependencies can take some time, and eat up quite a bit of memory. V-Ray does indeed scan over the model and look for textures, materials, lights, proxies, etc. During that process, it consumes more memory as it builds various data structures that help us interact with the SketchUp model, and even render it in real time. It's possible to have a model that will crash due to memory consumption on OSX, by simply opening the model, and due to OSX's feature which will allow an application to reopen whatever documents were last open in the application, it's possible to end up in the crashing loop as described above. The workaround of moving a file is very effective in breaking the endless loop of crashes. This prevents V-Ray from scanning the file, and prevents SketchUp from loading the file in to memory in the first place. If you have any example scenes that demonstrate this issue, and are willing to share them for diagnostic purposes, please contact me, because I would like to resolve as many of these issues as possible before we release our next patch. You can reach me at devin.kendig@usa.chaosgroup.com. We now have a dedicated VfS for OSX developer, as well as a developer solely devoted to VfS for Windows. We are hoping we can resolve this issue, but it may require some work on the part of Trimble, to allow plugins such as V-Ray and Maxwell to utilize more memory than we are currently limited to.

Since I created this post I have given up on Vray and moved onto using SUpodium. Sorry for the redundant thread, thanks to anyone who stopped to try and help.

are you using the vray "raw" image option? try rendering normally, you can save as exr and do regions that way. I think the issue may be that with raw format, it breaks up the image into the tiles, so maybe it's trying to render a region of just that tile...

@dkendig said: We typically will handle licensing related issues within 24 hours, but instantaneous is much faster! Actually, you're near-instantenous already. I had license issues today. Solved in no time, thanks to the dynamic duo A & K. I was quite impressed. That said, the Mac version's UI? Needs work.

Menu->Plugins->V-ray->Help->Debbuging->Regenerate all v-ray materials or else Menu->Plugins->V-ray->Help->Debbuging->Force sync for all materials Saludos