After a few months not working with V-ray my bloodpressure reached normal levels again. But unfortunately I had to do some work with V-ray for a client.
So after spending a few hours finetuning the model in Rhino, I tried to make some renders…
What should have taken me an hour or something, has taken me 8+ hours so far and no end in sight!
I keep getting the same problems as I had months ago:
Missing geometries
Faulty vrscenes/proxies with missing surfaces
Decals not working properly or disappearing
V-ray not understanding the difference between mm’s and meters
Displacements all over the place…Probably because mm’s are not the same as meters!
Starting a render with displacements taking ±10 minutes…
Ending a render taking ±10 minutes.
Trying to edit a block while rendering results in crashes.
Updating to the latest V-Ray 7 for Rhino, update 2 had the effect that Rhino already crashed 4 times since I installed it 2 hours ago… And to make matters worse, my model seems to be corrupted, so Rhino crashes the moment I try to make a render… When it did render I had the same exact problems as with version V-Ray 6 for Rhino, update 2.6.
I’m sorry that you experience all those issues.
Have you reported any of them so far ? especially the last one. I don’t see any ticket in describing any of the problems you listed on our ticketing system.
The development team must at least know that there is a problem to get it fixed, right ?
I was very careful with updating to V7 because I had some bad experiences in the past after updating. And working in the field of architectural competition I really need to rely on a sable software. Which I have found with Version 6.20.05. So I waited for about a year to finally update. to Version 7.
Working in the field since 15 years I have developed a very careful observation for crash reasons and how to avoid them. Thus, what happened here was really strange: I had a lot of crashed with V7. And I was not able to track it down. Not even to reproduce them. That’s why I have not been posting about it, because I can’t give you any info on it. Working on the same file, with the same PC with the exact same settings might crash or might not. A file that has always worked flawlessly, crashes instantly.
So, just to put this here. Not very nice to work like that.
I can understand the frustration of rene.
Hope you guys find the reason. Let me know if I can help without having to invest too much time.
Best
Toni
If you see the Rhino crash handler window (the one with the rhino and the flat ball), a .dmp file is automatically created on your desktop. That file contains everything needed to investigate the issue. From there, you have two options:
Click “Send Report” — this automatically sends the .dmp file and some system info to McNeel. Their automated system then shares the report with Chaos as well. You don’t need to do anything else.
Share the .dmp file manually — if you prefer, you can copy the file before closing the crash window (it disappears once the window is closed), upload it to online storage (Google Drive, Dropbox, etc.), and send the link directly to Chaos. Note that these files can be quite large — sometimes close to a gigabyte — so cloud storage is usually necessary.
If the crash window doesn’t appear, then it becomes all about reproducing the issue. I know that can be tricky, but it helps to narrow down the type of crash. Generally, we see two kinds:
Integration crashes – while setting up the scene, editing materials, copying from older files, etc.
Rendering crashes – when everything is already set up and you’re just waiting for the render to complete.
Interactive rendering can involve both, and those tend to be the hardest to debug.
Could you let us know which situation your crashes mostly fall into?
Thanks for the quick reply. Good to hear about how the .dmp file sending works. I will do this more often. Concerning your second question, I think the crashes might be more on the rendering side. But not entirely. So first case (integration) also occurs. Never working with interactive, so this is easy.
Next time something crashes I will send the report.
mind that if you send the report to McNeel, I have no way of knowing which is the machine/user it came from. You are better off sending it directly to me
thanks