I have a huge problem.
Yesterday i updated my Vray nest to newest Vray next ( update 2 ). Since then - on every scene i’m having irradiance map splotching problem in shadows, especially on detailed geometry. Each scene i decided to render. I’ve been trying to solve the problem for 10 hours. I tried everything with no success. Is something wrong with Vray update or what? The only solution to get clear image is to use bruteforce or very high preset on irradiance map. Both solutions are unacceptable to me.
Anyone can help? 3ds max 2016 and Vray next update 2.
I put image as a reference. Rendered on medium preset in irradiance map, very high settings. Still - splotches as hell, also noisy image.
I would say try defaults. I haven’t used presents in a loooooong time.
i tried everything. Nothing worked. I think it may be problem caused by not enough lighting, because it happens always in shadows. But…it never happened in previous vray versions.
Can i see what a render with default settings looks like?
If that splotched like a low-quality irmap, then you may have geometry issues.
Geometry was correct, also renderer settings were okay. Splotches dissapeared after putting huge planar light directed downwards. It’s like new Vray couldnt get enough rays for area. But it never happened before in previous installations. Now it is regular in every scene, all my projects. It’s not vray settings. Something else, inside vray itself.
Could i see the renders with default settings? Or be given a scene?
If truly there was such an issue, we’d surely want to know what it is that generates that, so to fix it.
Sure, let me get back home, within 2-3 hours i will send you my scene.
I figured it out what was causing this problem! Somehow my scenes got virus nested inside max ! I’ve never heard about max viruses, i’ve never met with this kind of issues. I found that by accident, thanks to sini forensic plugin. After scanning and repairing files - they work perfectly, so is vray! What is curious - in my work lately we have been having the same problems ( for 2-3 days ). I shouldn’t have doubted to Vray. My apologies!
All the more so, support would love an infected scene!
Very glad it’s sorted for you!
Oh that. Glad it’s resolved now. This is one of the reasons I moved to 3ds Max 2020 now.
Best regards,
Vlado
I need to consider this as well…I feel uncomfortable, because i’ve never used illegal software or assets. I’m maybe stupid enough to buy models, textures and soft. And this is sad, that i bought with some assets bonus, which could have spread .
We had this problem a couple of weeks ago, the virus nests himself in scenes and gets distributed, almost our entire farm was infected. If you work with 2018 or older you need to install the 3Ds max security tools manually, this will prevent the virus from infecting your computer and other scenes.
https://apps.autodesk.com/3DSMAX/en/Detail/Index?id=7342616782204846316&appLang=en&os=Win64
Thank you for this tip.
In all the years I read about the 3dsmax `virus` I`d never seen any sign of it, and then 2 scenes come in infected from 2 different clients just this month. The only thing it seemed to do was have a few garbled named objects that you couldn`t unhide or delete although it then spread that rubbish to every other file. Luckily the Security tools zapped it before it got too far. Some people have too much time on their hands to program this stuff.
in my case virus caused lighting errors, exposure control issues, long rendering time, in animation - camera flickering and much much more.
Yeah the “virus” does all sorts of things. In our case it deleted lights right at render time. Kind of hard to identify what’s wrong with your render if it happens haha.
I warned the office where I work about this almost a year ago about this but it fell on deaf ears. Took us a day and a half to find the culprit and clean everything once we were infected.
It’s not a Virus, as such.
It’s a set of borked scripts (the licensing thereof) which have a tendency to nest into odd places.
Calling it a “virus” is fearmongering from the part of AD, imho (and i have told them so in no uncertain terms too.).
Likewise, their approach (of parsing every possible controller in nodes and xrefed stuff, on file open, merge. for big scenes, that’s potentially *hours* of single-core action.) is like trying to shoot down a fly with a bazooka.
I’d suggest running the cleaning scripts only on a need-to-clean basis.
And as with viruses, the very best practice against them is preemptive control over the data.
The likes of us, having to open a gazzillion scenes from anywhere, unfortunately, are likely to save more time leaving the cleaning scripts active.
But if i was a firm, i’d be happier to take the cue and clean up my assets, and tightening the process to add new assets to the library.
Yeah try explaining that to my colleagues 
I hope (for you!) that the technical direction there isn’t a democratic process. ^^