i was just answering the guys post to what you had already wrote, he had missed it so i quoted you… hey give us a hug you guys . :lol:
kiss and make up guys.
It seems to have been an innocent miss understanding that gone blown out of proportion.
Infact natty’s last post cleared it all up for me.
<edit> me speel bad
Jason, you have HOW many machines hooking up to this server at any given time? I believe you said 8 earlier with the possible +1 for the main workstation - is that correct? And your file server is running which OS?
Didn’t I read a post somewhere about memory issues related to DR and dropping textures? lemme hunt around…
And Jason, don’t be such a stranger 
ME
“Wow!”, I thought. “22 replies!” What a caring and helpful forum we have here. Imagine my surprise when I opened the thread. :lol:
Anywho, to answer the question in post 2 and #10 (sorry):
I’m mapping my textures using UVW Map modifier. I still don’t get how a color difference can be due to a missing texture when a texture isn’t applied to the area in question - like the ceiling. After some thought, I also dont understand how the root of my problem could be due to maxing out the number of network connections when V-ray is clearly connecting to and using all of the render slaves.
Anyone care to try and elighten me? I love enlightenment. I could actually stand to be about 15 pounds more enlightened. I’d better lay off the morning Krispy Kremes.
…and it’s bedtime!
Howdy Matt! Good to see ya, dood.
I have 8 dedicated render slaves launching at render time. We also have 4 workstations, none of which (except mine) are used during normal buisness hours. So, 9 all in. However, the other 3 workstations are connected to and pulling resources from the server in other ways (texturing, modeling, etc…) The file server is running Windows XP Pro. It’s really just an old 3D workstation turned file server - that’s all it does. It’s not a “true” file server (i.e. running a server OS)
Sorry about being a stranger. Want some candy? Here, get in my car…
well, sounds like a quick test then…shut down the 4+ machines and try with only 9 in the mix
me likes kandy YUM!
oh, and I almost forgot…
DAFORCE FTW!!!
:shock:
…ahhh…ooookkk… :roll:
Are the ceiling and wall materials reflective? If so I would guess that they are reflecting the gray left by the missing maps.
color bleeding might also cause those color variations…
jason: how many render nodes are present during rendertime?
ps. Daforce:
i agree sadly it wasn t some post before, were it should have been in the first place…and …ah well nevermind
Hi Jason,
did any of this help you?
mm
With me, the problem was when DR was registered as SERVICE, not started from the Launche DR Spawner icon. Even if the machine was logged ON, all the path were UNC , the slaves couldn’t load some, if not all textures.
There’s also a problem with the distribution of the Light cache, I prefer to render it first on a network drive, then assign it to read from it, and afterwords start the IRR map.
A very important thing is to actually save the .max file every time you change smth, before starting a DR. Otherwise, the DR won’t save the file for you, and will render from the previously saved version.
Hope that helps
Thanks everyone! I’ll be testing some of your suggestions later today, and possibly this weekend. We’re also looking into getting a true server machine. I’ll post back here if we land on a solution.
Thanks again,
jason , i have a question .
Did you find a way to resolve the textures path problem. We have the same problem here since 2-3 weeks.
thanks
Jason, when the DR machine can’t see the materials it can’t calculate any color bleed that would slightly modify the materials that don’t even have maps, like your wall and ceiling. So there is a slight difference in that bucket.
Hi
Has anybody come up with a solution to this? From what i have found it is something to do with the second bounce, if you switch it off the render is fine. The other thing is it happens what ever second bounce you use, light cache or brute force and it is the main machine that is causing it and not the DR machines.
The one solution i have just found is to take a file that renders fine, delete the contents and merge the problem one in and it renders fine!
Anyone come up with definitive answers for this one? I am having the same problem now with one of only 2 nodes. It was rendering fine and then one just started up with the grey buckets.
Thanks!
b
Just a quick note that turning off the spawner service and running it as an .exe seems to have solved this issue.
b