When working with V-Ray latest nightlies build in Cinema 4D S24 also on R23 I have big problems working with Materials in the viewport. I have to turn of material preview in the Viewport so I can actually work, because taskmanager shows one CPU thread continously at 100% and networkusage at about 1 Mbit the second.
My textures are in a network saved. So preview is often never be updated, Cinema is horrendous slow because of continously CPU Usage for nothing and I cant Work anymore.
When using the same textures in a Standard Cinema 4D Material Cinema viewport works fine. It loads the Texture at 100 Mbit over network and its loaded fast and fine.
In my opinion two things have to be fixed as soon as possible to get even work with Vray 5 that is:
- Renderinstances makes Vray unusable because the more you have the longer (and I mean LONGER) vray needs to even start the render. This is horrible
- Materialpreview, what I mentioned above
I mean this in my opinion are ESSENTIAL parts of Vray to work. If These two things get fixed, I can finally Work with Vray 5. Currently I also do but its a pain in the a**
@shaio: I know theres a problem with C4D prioritizing material preview over anything else and all the rest of it but this must be fixed soon. Especially the renderinstance problem. I cant render animations like this or make testrenderings. Because i have to wait minutes before Vray decides to start. Is there any kind of coding progress?
Does this happen with a specific scene or texture or it also happens on a fresh new scene? Could you please try to copy your textures locally and see if you will experience any slowdowns? Can you also install the latest official build and see if the issue will be reproducible?
Edit: I post a scene and a video later
That would be very helpful, thank you.
Could you please go to Edit> Preferences and in the Materials tab of the V-Ray preferences, make sure that the Editor Map Size is set to “Default”? Also, please open the material in question, and in the Preview make sure that the Editor Map Size is also set to “Default”. Please let me know if that resolves the issue.
It was both set to default. And its the same at home, too (currently in Homeoffice). Its not working and CPU is at 100% with one thread. C4D Mat is working. Maybe S24 related? Dont know. At home also using local materials. Did you test my scene with R24 @aleksandar.kasabov ?
AT Home I have a RTX 3090 and at Work a Geforce 1070 TI.
Alson 64 Gb Ram and SSDs as NVMEs. At home I have a AMD Ryzen 9 3900X 12-Core Processor 3.80 GHz. At work I have: AMD Ryzen 9 3900X 12-Core Processor 3.79 GHz.
All newest drivers for Graphic and System. Using S24. Windows 10 64 Bit.
Its both the same stuck materialpreview on both systems. WHich by the way are fresh formated. They have the newest Windows Updates.
EDIT: OK something VERY WEIRD is going on. When creating a complete new V-Ray Material with the SAME TEXTURE: Material Preview in viewport works. BUT with the “old” V-Ray Material not.
I try to figure out whats the difference between those two. Also very weird: Materialpreview of both materials looks different in mapping. Wtf! What is going on?
Material Preview Size was Set to 4096 BUT Override was set to off. Which is weird. Why is V-Ray then rendering the material? There must be an oversight. SO if I turn off “override preferences” in the material preview Tab it seems to still use 4096x4096 even its turned off.
But that fixed the problem! Thank you @aleksandar.kasabov . Could you pls check out what is going on there?
I am glad to hear that this fixed the issue. It seems like the Editor Map Size is considered even if the “Override preferences” option is disabled. I have already logged this in our system (bug ID: VC4D-1033) and will let you know once we have any updates.
