Hi
Last week I upgraded to SU8 and Vray 1.49.01
Ive noticed that after a render error pops up.
I save the file, close it down.
When I reopen it. Some of the material layers have disappeared.
This has happened on 2 different models.
Re: Losing material layers
A question.
If I have a component and apply materials with reflections
in Vray. I then save the component.
When I reopen the component in my model, all the layers
have gone. Is this right?
Im sure this didnt happen in the older versions
I’ll continue to test.
Re: Losing material layers
It´s bug >
and its really annoying for every day work … hey ASGVIS, change this chaos in last beta build. How long will we wait ?
Re: Losing material layers
WOW big bug.
Ive spent the last two days on this model
getting no where.
Hmmmmmmmm
Re: Losing material layers
Yeah, it is a big bug that’s for sure! I ended up having to revert to my older installation due to work flow needs. I posted a topic with similar problems here.
Re: Losing material layers
Thanks for the link.
Maybe time to revert back until this is solved.
This problem is costing me money
Re: Losing material layers
I know this problem too >:(it’s generally when you render your scene at first time,before i hit render,i save my SU model,then hit render,then get this error pop up,hit ok,and don’t save again the model,just quit without saving,open again my model and hit render without losing my reflection layers…but it’s very annoying bug and expensive too
Re: Losing material layers
I’m having this same problem. It happens all the time. I can’t really work with Vray anymore.
Any clue?
Re: Losing material layers
I just realized that it seems to happen when I paste new geometry from another document
Re: Losing material layers
Yea - I’ve seen oddities when doing that as well lately. It seems like a regressions, because before one could paste / import components / meshes with no problems and you’d even have the V-Ray materials for the new mesh added to the model.
I’m definitely seeing this same thing with 1.49.01 -- importing geometry from a file and having reflection layers vanish.
That’s been an issue with the latest builds for a while. Devin had indicated in another post recently that it’s getting fixed in a new beta. For me, the best way I’ve found to get all the vray information to stay from one model to another is to work in SU without vray. There seems to be something about the SU and vray interaction currently that messes up how materials are saved in a copy. Still, this doesn’t always work, but seems to have a better success rate.
Does anyone know if there has been any movement towards getting these issues resolved in the current version of V-Ray? I have stuck with my old version of V-Ray (01.05.30) because it’s been stable for the most part. My DR spawner works most of the time (unless the model is extremely large and and has a lot of materials/textures) and I haven’t had problems of losing materials, lights, or layers like I did when I installed the new one. I have a couple of VERY large models that I have worked on over the years with some long term clients and I continue to add to them with new/continuing projects. When I last tried the most current version of V-Ray on a copy of one of the models I lost all sorts of V-Ray material layers, lights, and even entire textures due to some incompatibility between the old and the new versions. Every time I tried a new copy of the model the same things happened. Because of the level of detail and our need to keep working with these models over time I have not been able to justify moving to the new version, even thought I would love to use some of the new features in the current version and feel the overall output is better. Last year, around this same time, I had posted these questions as well as others here (http://www.chaosgroup.com/forums/vbulletin/showthread.php?63474-DR-issues-blocky-renders-here) but since then I have seen very little information and/or updates regarding this.
Also, one side question I have is regarding the current version of the DR. Does the new version allow you to connect to more than 10 machines, which is the current limit I have? And, with some of our new machines having multiple processors that are “hyper threaded” is the DR limited to 10 “machines” or is it limited to the number of “threads”?
Now that Chaosgroup has fully integrated V-Ray into their system are these issues being addressed? If not, is there an expected update/fix for this? I do prefer V-Ray’s results as opposed to other rendering software out there and the fact it integrates into Sketch-up is even better. However, I am about to start some new models and would like to know what to expect in the future so we can make adjustment accordingly.
Thank you!
That 10 DR machines per license is a limit for all versions of vray, not just vfsu. You’d need to have additional licenses for each 10 additional machines (and no penalty for multiple cores/ cpus) I don’t know if it’s possible with vfsu as it is now to have multiple licenses running. With the newer versions, (like the updated vray for Rhino, vray for maya, etc.) there’s a USB dongle system for licensing, so that makes it easier to have a larger DR farm.
That’s the best I currently understand it, if any developers care to chime in and confirm that would be great.
Yes indeed, vray is still the best for quality/speed ratio!
Andy
Okay, thanks for the input on the DR andybot. Every now and then, on my large models, something fails in the connection to the other machines and I get an error message saying “ping not received…” from each node when I try to run a rendering. I have searched the error logs and all I can tell is that maybe there are too many lights? Not sure exactly what it is…but for the most part it has served us well and I just work around it as best as I can.
What about the other issues such as losing materials, lights, or layers that were set up in old models? Have you heard of a fix for this in the new version? Is the new version more stable?
we are working on the new version right now, and trying to address these issues. A beta testing period will be starting once we get the build to a point where it is potentially better than the current release. We use the same code in V-Ray for Rhino as we do in V-Ray for SketchUp for the most part, so many issues have already been addressed, and some features have already been brought over from the latest V-Ray for Rhino update (or at least partially so far). There’s nothing to show right now that will help anyone, but we expect to have something in working order before the end of summer. Not sure if it will necessarily be done by then, but we should at least by starting a beta by then.
Hi dkendig,
Any word yet on a potential update? I’m still working with a very old version of V-Ray due to some VERY large long term projects we have been working on and the problems we were having when we tried upgrading to version 01.49.01 when it first came out (problems outlined in previous posts). And, wondering if the updates from Trimble are going to be a problem and some seem to be having? Anyway, we are coming to a point very soon that would be ideal to change before we start several new long term projects again. Any help is greatly appreciated!!!
Thanks!