I’m having some issues regarding the new version of V-Ray for Sketchup (1.48.66), in which I try to render a scene that was made with Sketchup 7.1 and VfSU 1.05.30, and when I press the render button, it shows the message “V-Ray is currently processing your scene, please wait”.. then, despiste the increase in parsing time (which was supposed to be smaller, not bigger) compared to the previous version, after some 5 ou 6 minutes, the message “V-Ray is currently processing your scene, please wait” disappears just like if I didn’t pressed the render button at all, with no frame buffer windows nor anything. Can someone explain to me what I’m doing wrong?
Re: New V-Ray (1.48.66) won’t render
Sounds like some sort of problem with the scene. Sometimes imported images or components don’t let us know that they were imported, so we don’t get to process any materials/textures that come along with that import. In our old version we just shrugged our shoulders and said oh well. In this version, we added some debugging tools. If you go to Plugins->V-Ray for SketchUp->Help->Debugging… You should see an option called “Force Sync for all materials” This will iterate through all of the materials in the SketchUp scene, and all of the materials that V-Ray knows about. If there are any materials that aren’t showing on both sides of the equation, it will create materials where they’re missing.
Re: New V-Ray (1.48.66) won’t render
Now, the frame buffer appears, but soon after that, it crashes with the “TEMP folder” msg =(
Re: New V-Ray (1.48.66) won’t render
Should be better for us if we have the scene. Can you send us the scene? support@asgvis.com or to my email fpedrogo@asgvis.com
best
Re: New V-Ray (1.48.66) won’t render
I have a very similar problem. I installed the new Vray 1.48.66 today, and tried to render a large, detailed (40mb) model. I rendered that same model yesterday with the previous version of Vray without any trouble. Now, however, soon after the frame buffer window appears, SU and Vray simply shut down, without any message or warning. I di get a SU bugsplat window afterwards.
I did notice that both on SU startup as well as on opening the model a number of pop-up message fly by, but so fast that the text hasn’t even time to appear.
I find that smaller, simple models do render, so it seems as if the new Vray is handling memory less well than the old one.
This is very disappointing.
Re: New V-Ray (1.48.66) won’t render
nah, shouldn’t be the memory if it worked in our old product. It’s most likely an issue with mismatched materials. In our old product, if a SketchUp material lost sync with a V-Ray material, it was gone forever and the scene would act strangely sometimes. Other times it would behave just fine, and just have a hidden problem waiting to happen. Try clicking on Plugin->V-Ray for SketchUp->Help->Debugging->Force sync for all materials. If it finds any missing materials, it should be able to see them suddenly appear in our material editor.
Re: New V-Ray (1.48.66) won’t render
Thanks for the quick reply, I really appreciate it!
But no, that didn’t do the trick, unfortunately. Program shutdown just like before. I already tried rendering with material override, that didn’t work either.
For completeness sake: I’m on a P4 dual core 2,133 Ghz with 4 GB RAM and a Nvidia GeForce videocard. I’m running SU 7.1
(PS. Tried regenerate textures too, but again without effect)
Re: New V-Ray (1.48.66) won’t render
I have exactly the same problem. I’m using the demo version. I downloaded a couple of models directly from the google warehouse. The program exits, and the bug report window appears.
With smaller models (ie, a couple of boxes) it works fine. However, with larger models it won’t render, or crash or it appears to take forever. I’ve had the three scenarios, after 4 clean installs. (Uninstall, scan for leftover files, even uninstall/reinstall sketchup). to no avail.
Dissapointing… :-[
Re: New V-Ray (1.48.66) won’t render
1. I have the exact same problem with larger files. It says Vray is processing the scene, but nothing ever happens in the frame buffer.
2. My second bug, when trying to preview a matierial (a vray material) in the editor, Sketchup crashes, every time without fail.
3. And lastly - this may have something to do with my inexperience - some of the vray materials I’ve downloaded come in at an extremely small scale. And I cannot figure out how to change it.
Help! Anyone?
Also, I’m using a MacBook Pro, intel based, only a year old. In fact, my hardware was sufficient enough to use Vray on my Windows partition.
Re: New V-Ray (1.48.66) won’t render
1. There won’t be any activity in the VFB when V-Ray is processing the scene. That is work it does before it starts the actual rendering.
3. You change the scale of textures using the Sketchup Material editor. And you always have the option to size using SU’s texture position tool
Re: New V-Ray (1.48.66) won’t render
Thanks Thomthom.
Ok, sorry, my terminology was off. I realize ‘processing the scene’ is what happens before the rendering, but it never goes into rendering. Basically, I’m having the same exact problem as Shinkakashi in their original post.
And as far as the texture scaling goes, that’s what I’ve always done for the windows version of Vray for sketchup, but that option doesn’t appear when I right click the material. Is there another place to do that? How would I change the scale of the texture in the Material Editor? I couldn’t find it anywhere. My apologies if this is basic knowledge…
Re: New V-Ray (1.48.66) won’t render
Wait a minute guys… we’re getting sidetracked. Let’s stay on task. If you have a simliar issue fine, but don’t hijack the thread too much.
SHINKAKASHI - Try running Plugins->V-Ray for SketchUp->Help->Debugging->Clear Texture Cache Folder, what happens then? The folder we write textures to, should be cleared every time you open a fresh instance of SketchUp, but just in case…
MARTINPH - It sounds like you have a different problem to me, please make a separate thread about this issue, so we don’t end up getting everyone’s stories mixed up. Shinkakashi’s issue is related to the error message that reads “Not enough space in your TEMP folder”. Your issue has no error messages, just a bugsplat.
CARVITE - It’s hard to tell if you have the same issue or not. If you do not get the “Not enough space in your TEMP folder” error message, then please make a separate thread as I told MARTINPH.
IWASACLOUD - In SHINKAKASHI’s first post, he was unable to get the frame buffer to show up. All that happened is the preprocessing message, and then nothing, no VFB or anything. You said that nothing happens in the VFB with your issue, so I’m assuming that the VFB pops up, but then you never actually see a render happen. That sounds different from SHINKAKASHI and MARTINPH’s issue, because SU doesn’t crash at all. Please open a different thread about this issue. Also, did you run the debugging tools mentioned previously in this thread?
Sorry to break it up, but this thread has potential for going crazy.
Re: New V-Ray (1.48.66) won’t render
I apologize for ‘hijacking’ the thread. But no, my problem was exactly how SHINKAKASHI explained it. I shouldn’t have tried to reiterate the scenario. VFB doesn’t pop up. I did try the debugs, nothing works. I have a multitude of other things that cause Sketchup to crash such as loading a vray material, but I should start a new thread for that? I appreciate the replies, I’m pretty disappointed with the new Vray. I thought I was competent with it, but I’m not with this new version..
EDIT: Using all three bug tools seems to have alleviated the problem. At least I got it to work once. Still having the other major crash problems. Should I start a new thread? Or report them as directed in the bug section?
Re: New V-Ray (1.48.66) won’t render
I had exactly the same problem as originally described with scenes made during a previous version.
After some testing I found that the “Regenerate all V-Ray Materials” under debugging seemed to do the trick, but not before giving me a bug splat on the attempt to render first time round after doing it.
However, on the second attempt to use the “regenerate…”, even though it began to render the debugging stayed true to it’s warning and pretty much wrecked the materials on the scene…
yup…
I don’t know how relevant this is, but I’m running on win7
Re: New V-Ray (1.48.66) won’t render
I tried the “clean cache” function as well, but stills the program shuts down after some 30 seconds showing a black frame buffer. Strange that the exactly scene renders correctly in the 1.05.30 version. So, if isn’t a texture allocation problem, what is it then?
By the way, I managed to render deleting all my vegetation. So, it could be either a vegetation texture problem regarding the new version of V-Ray, or something about the quantity of geometry being displayed (strange that the scene rendered just fine with the previous version and all vegetation).
I’ve also give a hit at the preview button at all the materials at the Material Editor (in the previous version, you could check if there were any material’s texture missing clicking on the material preview button and seeing if SketchUp suddenly closed out of nowhere). But, it all went fine, all the materials did the preview just fine.
So, what more could be wrong in my scene so far? It is pointless if I can’t render with the vegetation included on the scene.
Re: New V-Ray (1.48.66) won’t render
IWASACLOUD - If your issues match the original poster’s issues, then you don’t need to open a separate thread for that, but the other issues you say you have, should be in a different thread since they’re not related.
SHINKAKASHI- The error message talking about the TEMP folder being full, isn’t one of our error messages, that’s why nobody’s gotten an answer about that error in this forum. I don’t doubt that it’s being caused by something our plugin does, but it’s not an error that we generate ourselves. We also have been unable to reproduce the error on any of our machines. 
We have had some reports about displacement and transparency causing some issues. Displacement does’t render in a material preview (the preview ends up just black). Displacement also has some new parameters in this version, now you can control displacement on a per material basis. I don’t know if any of your materials use displacement, but if they do, you may want to increase the edge length of the displacement. Transparency has been slowing down renders in some cases. Specifically with any scenes that have very intricate transparency maps (that’s really all I’ve tested so far) such as vegetation. If you take out the transparency maps for the vegetation materials, does that change anything?
Oh wow, here’s a question, what resolution are you trying to render out? I can’t believe I missed this one ::smacks forehead::. Does the scene render if you just lower the output to something tiny like 320x240?
TOURNIQUETMASTER - When you regenerate all of the V-Ray materials, we just delete anything material related on the V-Ray side, and then treat the SketchUp scene like it would be handled if it had no V-Ray data, so all you end up with is some V-Ray materials the correspond with a SketchUp material, but the only layer in the material is a diffuse layer. If you save all of your materials prior to running that tool, and then import all of the materials back in after running the tool, you should be fine. I guess that old scene had something messed up in it. I’m glad we were able to salvage it. By the way, did the Force Sync for all Materials tool not work? If there’s a material problem, generally the sync tool should fix it.
Re: New V-Ray (1.48.66) won’t render
dkendig, I think I’ve found the issue. I’ve tried lowering the rendering resolution, but without success. My scene doesn’t have displacement. So, following your lead about the transpareny issues, I connected the dots and found the problem. I’m using a tree which have transparency maps for it’s foliages. I’ve deleted the trees, and the render went fine. I don’t know if it’s a problem with the maps or the objetcs, but I will try to isolate the problem.
Nevertheless, the issue about the huge parsing time is still present. I though you guys were going to decrease the parsing time, not increase it. Because that’s what happening at my scene. At the previous version, the parsing time for this specific scene was about 3 to 4 minutes. Now, it’s about 5 ou 6. I’m quite disapointed at that.
Re: New V-Ray (1.48.66) won’t render
SHINKAKASHI- YAY IT RENDERS! ::high fives:: Who says working from home all hours of the night means you’re crazy? ::twitches:: I’m really glad you were able to get it to do something at least. I wish I knew why transparency was killing render times so bad, and how not a single one of our beta testers missed it…
The parsing time should be down in this version, but not necessarily for all scenes. It shouldn’t take LONGER though… that’s bizzare. Are you counting the time prior to the VFB popping up, or are you talking about between pressing render and actually seeing something in the VFB? The scene parsing happens prior to the VFB popping up. Now the important thing to know about the parsing time, is that in the old version, if you had materials applied to components or groups, you might as well go read a novel after hitting the render button, because it would take forever. In the latest version this issue is not a problem, and in fact I believe it speeds up parsing time if you use components and groups as you’d normally expect to be able to use them. You’d have to ask Fernando or one of our beta testers for confirmation though. I know one scene that Fernando had took something like 15 minutes to preprocess in our old product, and less than a minute in the new version… and Thomthom had a scene with a bunch of toruses that went pretty quick too.
Re: New V-Ray (1.48.66) won’t render
You’re talking about that entire story regarding the Remove C-G plugin, right? Well, in my case, the plugin was helpfull when I use third-party components, in which I don’t know how was the texturing process that the creator adopted. When I’m texturing stuff, I always paint the face of the geometry inside the group/component (you can see that you’re painting the face when you can actually “touch” it, showing the little blue dots along the selected face), instead of painting the group/component, as some people does. The plugin really kills some parsing time, in the case that I use a lot of third-party components. In some occasions, I’ve been able to get about 200 materials deleted with the plugin :o
About the question that you asked me regarding the VFB pop up, when I’ve meant “parsing time”, I’m talking from the moment when we click the render button until the VFB shows up at the screen. Another thing that would require your attention is that even after the VFB appears, it does take a large amount of time until the first pass (or pre-pass, light cache, whatever) shows up, specially on larger scenes.. that is also strange.
About the render, it went well. One thing to notice, it’s that the tree renders normally in a new scene alone (works using both actual B&W transparency JPEG map as the new “use color for transparency”). But in the scene, it just doesn’t render. I think the new version is lacking some retroactivity regarding the scenes saved in the previous version. Is there any chances that ASGvis will launch a fix to those little things?
Re: New V-Ray (1.48.66) won’t render
You’re talking about that entire story regarding the Remove C-G plugin, right?
Right, try benchmarking your scenes with and without using that tool. Not using the tool should speed up parsing time I believe. I could be wrong, but I’m right about this.
About the render, it went well. One thing to notice, it’s that the tree renders normally in a new scene alone (works using both actual B&W transparency JPEG map as the new “use color for transparency”). But in the scene, it just doesn’t render.
Odd… and you said that this is still the case even after using the Force Sync for All Materials tool in the debug menu? Where did this tree come from? Is it on 3D Warehouse? Would it be possible to send us the offending tree so we can figure out what makes it so special? btw, “use color for transparency” will make your diffuse layer ignore anything you have set for a transparency texture. Instead it will use the alpha of the image that is being used for the diffuse color texture. Just wanted to be clear everyone knew what that option does.
Is there any chances that ASGvis will launch a fix to those little things?
Well of course. We just need to figure out what slipped past the beta process and patch it up. So the more detail we can get about everyone’s issues, the better. Video demonstrating issues makes it so incredibly easy to communicate about this stuff, so that’s something to keep in mind for the future. There are programs out there like Jing that let you record your screen and then upload the video somewhere to share with others.