To keep everyone updated I got 2 replies when i contacted chaos group.
"Hello Peter,
We do have an error log now in our latest release, which is located in the ASGvis folder, maybe it can shed some light on these issues. The ASGvis folder changes location according to the OS you use:
XP:
C:\Documents and Settings\All Users\Application Data\ASGVIS\VfS\vfs_stderr.txt
Vista and Win7:
C:\ProgramData\ASGVIS\VfS\vfs_stderr.txt
OS X:
/Applications/ASGVIS/VfS/vfs_stderr.txt
The error log is wiped every time you open SketchUp, and it won't be fully written out unless SketchUp is completely closed. So as soon as you see a problem of some sort, close SketchUp, and then open the error log file to see what it says. If there's an issue with materials being mismatched or something along those lines, you should see some sort of message about that particular asset in the error log. The most common things we see causing errors are corrupt materials, textures, or components. If you have any Unicode characters in the file paths this will sometimes cause an error too.
We are working on a patch to correct the Unicode issues but for now you can get around it by storing textures, materials, etc in a root folder using only English characters.
The latest version of our software comes along with a few tools to help you if a particular scene (especially older scenes) doesn't render correctly. They can be found in the Plugins->V-Ray for SketchUp->Help->Debugging menu. They are as follows:
Regenerate all V-Ray Materials - This tool will delete any material information that is currently stored in the V-Ray Material Editor. Then it will iterate through the SketchUp scene, treating it as if it never had any V-Ray material data in it before, and it will create a V-Ray material for every SketchUp material. The newly generate material will only have a Diffuse layer. This tool is useful if your scene's materials are preventing you from rendering, and the Force Sync tool doesn't do the job. Keep in mind that while using this tool, any materials you have set up are going to be completely destroyed, so it might be a good idea to back up the scene prior to running this tool. In addition, if this tool allows you to successfully render the scene, then you know that the issue was a material in your scene. So you can just load your old backup scene, save all of your materials, run the tool, and then import that materials back in to your scene. If after importing one of the materials, you notice that the scene fails to render, then you found your problem. If after importing all of the materials back in to the scene, it still renders fine, then there was probably just some data corruption that was floating around from an old version.
Force Sync for All Materials - This tool will iterate over all of the materials in the SketchUp material editor, and then all of the materials in the V-Ray material editor. The two lists of materials are compared, and if either the SketchUp or the V-Ray material editor is missing a material that the other editor has, a new material is created to correspond with the missing material. This tool should not be destructive.
Clear Texture Cache Folder - Every time you open SketchUp, the directory we write textures gets cleaned out. Occasionally, it helps to have that folder wiped during a SketchUp session. This is usually something that isn't going to help unless you're about knee deep in code though, so I don't recommend using it unless directed. If you use this option make sure that you are using a New/Blank scene.
Please send us your error log so that we can look further into your issue.
Thank you,
Chaos Group USA"
AND
"Hello Peter,
A member of our support team has replied to your support request:
Hello Peter,
With Devin and Ted already helping you there is not too much I can add but I do have one trick to share.
SketchUp is always a 32 bit program even on a 64 bit machine. All 32 bit programs have a RAM limitation and as a result can crash when 4 or more GB of memory is required. To get around this limitation we have added a 64 bit V-Ray DR process that you can offload all of the work to.
If you are using a 32 bit machine crashes at large resolutions or with large or complex scene files would be normal and I'm afraid nothing can be done to fix that.
Please try these steps if you are using a 64 bit computer.
Open the V-Ray options.
Click System
Check "On" and "Don't use local machine" under Distributed rendering.
Press the "..." under Hosts.
In the Window that appears press "Add server"
Enter 127.0.0.1. Press OK.
Ok on the Distributed Rendering Settings window to close it as well.
In the options menu under "Output" Check "Save output" and "Render to VRImage"
Under "Output file" beneath this click on the "..." and choose a location to save the file.
Attempt to render.
It's not perfect and sometimes you'll have to trim the scene down where you can or split large structures into multiple files on top of the above but it can be very helpful. Unfortunately we have to work within the framework we have and not every scene that can be built can be rendered.
Thank you,
Chaos Group USA
We hope this has answered your questions. If not, please just reply to this email.
Thank you,
#TICKET THREAD#
Date: Tue, May 13 2014 12:55pm
From: Keith Thompson
To: phm@timep.com.au
Hello Peter,
With Devin and Ted already helping you there is not too much I can add but I do have one trick to share.
SketchUp is always a 32 bit program even on a 64 bit machine. All 32 bit programs have a RAM limitation and as a result can crash when 4 or more GB of memory is required. To get around this limitation we have added a 64 bit V-Ray DR process that you can offload all of the work to.
If you are using a 32 bit machine crashes at large resolutions or with large or complex scene files would be normal and I'm afraid nothing can be done to fix that.
Please try these steps if you are using a 64 bit computer.
Open the V-Ray options.
Click System
Check "On" and "Don't use local machine" under Distributed rendering.
Press the "..." under Hosts.
In the Window that appears press "Add server"
Enter 127.0.0.1. Press OK.
Ok on the Distributed Rendering Settings window to close it as well.
In the options menu under "Output" Check "Save output" and "Render to VRImage"
Under "Output file" beneath this click on the "..." and choose a location to save the file.
Attempt to render.
It's not perfect and sometimes you'll have to trim the scene down where you can or split large structures into multiple files on top of the above but it can be very helpful. Unfortunately we have to work within the framework we have and not every scene that can be built can be rendered.
Thank you,
Chaos Group USA"
