Could someone please explain to me what this is and what it means? I’ve been getting this from time to time and I think is causing some rendering artifacts.
Thanks,
Scott.
are you doing interior scenes ??
basicaly it means the materials that are getting this message are over bright.
try lowering your light settings ?
but if its not affecting your renders, dont worry.
its only a warning not an error.
Natty
Yes, it is an interior scene and I am getting a few small white splotches sprinkled through out the rendering. I will try to lower the light settings…stay tuned.
Thanks
give everything a thickness aswell.
oh …and keep the second bounces below .6
why dont you post your settings.
natty
That doesnt mean a error, only a warning that you are using higher color values than 255. This is normal when a HRDI map is used.
Gonçalo
my thoughts exactly Gonçalo
That seemed to do the trick. I had the second bounces set to .85 and I reduced it to .58. I’m still getting a few of the over bright warnings but the white splotches are not longer there.
Thanks.
happy to help
Natty 
Re: Invalid color
hey scott
i had a similar problem - i got many of these warnings and some neon colored spots all over my scene.
i didn’t use raytrace materials or HDRI, and my secondary bounce is set on 0.5 . the lighting used to be fine too, and i didn’t change it, so i doubt it’s an overbright light.
other files renders fine, but previous backup files of the same scene (which used to render fine) also get the same problem.
any idea from your own experience?
thanx
noam_farhi its possible that your old scenes are using old materials and since the material for vray has been changed over time there might be some incompatibilities. not sure though
Re: Invalid color
I’m very new to Vray but I will give it a shot. On one of my scenes, I found out that it was specific item (geometry) that was causing the problem of the neon spots. After removing it, the problem went away. I do not know if that helps.
Scott.
Re: Invalid color
right, this sounds really weird to me, but maybe one of you guys would see the logic behind that:
i checked my geometry, and it’s probebly not the problem - since we’re talking about a scene that used to render fine, and then didn’t, without me changing anything (surely not geometry). BUT, i noticed that if i open an older version of the file, made many changes ago, render it (it always render ok), and then open the new one - in renders fine. that’s really odd.
i thought maybe it has something to do with the “incremental add”, but i also tried “single”.
does this make sense to someone? please share your thoughts…
thanx for the replies
noam
On the topic of warnings, what does this mean?
warning: HDRI map locked, not loading
i don’t know, but i get that one whenever i use HDRI but i see no problem with the results, so i live in peace with it now…
I think the problem here is the word “warning” seems to have a negative conotation with most people, might be better if it was something like “attention” or “info” or … the hdri thing just means that it is already in memory and does not need to be loaded again.
RErender - yeah, i learnt to know that those warnings are meaningless if you’re happy with the results.
however - when the warnings come hand in hand with some annoying neon spots all over my scene, i tend to take them seriously. any idea about that problem of mine, three or four replies up the stack?
noam_farhi- Hard to pin it down without images/settings but the usual suspects are:
Raytrace materials
uncropped bitmaps
double faces
out of scale model
What changes have you made since it rendered corectly?
Rerender, what’s the uncropped bitmap problem?
Been a while since Vlado explained it, but if I remember it was something like Max returning illegal values for the edges of bitmaps which is fixed by applying cropping. Vlado has since said that he has rewritten the bitmap handler to fix the problem but needs Discreet to authorize it …
I have written a script to apply cropping globaly www.varcht.com/tools.htm
Thanks for the explanation and link.