V-ray rendering problem
-
Hi.
I just recorded a short clip that you can see part of my problem. The flick i'm talking about and the lack of rendering. I'm uploading it now. When it's ready i'll post here the link from youtube, so you can all see and try the things.
If it's not clear again.. I can make more clips so you can see the problem from different angles.
-
The flickering is coming from V-Ray being done processing the scene and SketchUp window becomes responsive again - where it updates the window. The rendering not starting after it's done processing the scene is probably some bug. I bet if you open the Ruby Console before you hit render you will see error messages appearing.
-
BlackMastah, so far i'm experiencing the same things as you, but the Task Manager is showing 100% CPU activity, so although the window doesn't redraw, the light cache is being built at this stage (and it always takes the more time the more lights you have in the scene), so i wouldn't say something is wrong. it just takes time.
-
@eidam655 said:
BlackMastah, so far i'm experiencing the same things as you, but the Task Manager is showing 100% CPU activity, so although the window doesn't redraw, the light cache is being built at this stage (and it always takes the more time the more lights you have in the scene), so i wouldn't say something is wrong. it just takes time.
The problem appear, from the video, that V-Ray doesn't start rendering after the processing.
-
@thomthom said:
The problem appear, from the video, that V-Ray doesn't start rendering after the processing.
that's yet to be confirmed by looking at the task manager / cpu usage. my framebuffer isn't redrawn either.
-
Okay. I can see there's some bug. That's nice that you confirmed that. Maybe i'm dumm, but... What now?!
-
Are we stuck?
-
did you check the ruby console output? did you check your cpu usage with task manager?
-
@eidam655 said:
did you check the ruby console output? did you check your cpu usage with task manager?
Yes, please check both there. Particularly the Ruby Console.
-
Guys, i don't understand HOW to menage with the problem and are you talking to me? WHERE is the problem? In the file or.. In the program? I can't figure that out. And with the CPU, it's obvious that there is some bug, but that's not enough and that wasn't my question. The quesion is HOW to deal with that so i can finish with the file? To put the IES lights, to finish everything else and to RENDER...
-
to know where the problem is, it would be useful to check the ruby console output, so we could be more helpful and accurate
try creating a new file, with a big box and copy the lights from the original file to the new one and see if this problem persists. or try to purge your original file and do a test render with the room and lights only.
i was curious about the cpu usage because sometimes it happens that the rendering continues, but the window is not redrawn, so i thought maybe this was the case.
other than that we (or at least i) have no idea how to solve this, that's why those pieces of extra info from you could be useful.
-
@blackmastah said:
Guys, i don't understand HOW to menage with the problem
Open the Ruby Console before you start to render and watch for error messages that might appear. They will probably give us a clue to why your render fails.
-
I ma having the same problem. i found out mine it's with the retengular lighting that i have with is small square and arrayed 12 x 15 lights for the whole building. after i delete the light it starts to render.but if i am with the light it dont render..what's the problem..is it grouping layering for retengular lights are making bugs for vray?
-
If you convert the light group to a component, it will prevent the scene from rendering. We see that happen a lot, people want to have instances of the same light so they just convert the group, thinking everything will be fine. In order to have that functionality though, you need to place the light group inside of a component, rather than converting the group to a component.
-
@dkendig said:
If you convert the light group to a component, it will prevent the scene from rendering. We see that happen a lot, people want to have instances of the same light so they just convert the group, thinking everything will be fine. In order to have that functionality though, you need to place the light group inside of a component, rather than converting the group to a component.
Feature request for the nexy Version? It is an intuitive thing to convert to Component.
-
@dkendig said:
If you convert the light group to a component, it will prevent the scene from rendering. We see that happen a lot, people want to have instances of the same light so they just convert the group, thinking everything will be fine. In order to have that functionality though, you need to place the light group inside of a component, rather than converting the group to a component.
wow. i did that mistake no wonder it wont render. making component perhaps alter the data of the light..thx man for waking me up
-
That's odd, I find I've never run into that problem. I usually have some kind of light fixture model and I make my vray light part of that component. I could see this option being useful for an area light (but I usually draw a line with my area light to tell me which direction it's shining...) Hmm, I wonder why changing to a component messes it up.
-
we didn't want our lights to clutter up the component definitions, so we use groups. When we go to look for lights in the scene, we don't check any components, we only check groups. You can put the light group in the component, that's fine. You can not convert it to a component directly though, or we will not know what to do with it.
-
Yes, directly converting vray light to component will cause problem, I often just create a tiny line or a point (often the center point) with the vray light before i make them component. Once an instance then it can be grouped and converted to other components. Often, I experience a crash or not being able to start a render if I use maps larger than 1 MB, be it diffuse, reflection, opacity or most especially displacement maps. Other days, there are just problematic geometry that will cause the problem.Detecting which one is a pain especially for a large model. Most likely its from imported blocks.
-
Hello everyone,,,I'm having a strange problem while rendering in sketchup. I m using Vray 1.48.49 and sketchup pro 8. I used .vismat materials for the scenes and vray used to render well(m not a professional but good enough for me) but it doesnt do so anymore. I searched the forum for help and did some techniques like purging unused materails in the editor and turning off .vri in the options. but it ddnt work....if anyone can help
Advertisement