Is there an approximate ETA for some of these important features to be supported on GPU?:
1.Full support for V-Ray MTL ( mainly Dispersion and Glossy Fresnel, Translucency, Roughness)
2.VRayOSLMtl
3.VRayToon
4.VRayEnvironmentFog
5.Maya File node with full support of projection node. (I have been requesting this one for over a year now)
Thanks a lot for the feedback! It is very helpful to know what people need.
1. Glossy fresnel is being worked on atm. Use FastSSS2 instead of translusency …
2. I doubt it will happen soon. We have MDL (materials + textures) and GLSL textures instead.
3. Can’t give ATA, will have too look at it.
4. Env fog is implemented in internal builds (although, atm without textures). Some volunteers already beta test it https://www.instagram.com/p/BR8dpphhqCH/?hl=bg&taken-by=dabarti\_cgi. It is comming.
5. Can you give a scene? Projection is support foq quite some time in the engine.
We know about the camera, I hope it is not huge annoynment?
Image filter should alias images as well as in the CPU (keep in mind that subpixel mapping does not work in GPU and we don’t plan to support it).
Dispersion is somewhere in the todo list, but to be honest so far not many people have actually asked for it, so we have planned few things before it … I will at least check how much efforts it will take.
Dispersion seems like a low hanging fruit. People avoided it on CPU i assume since it’s so expensive to render but in GPU I think it makes the most sense. Can you guys bump it in to do list please
If you can upload scenes, some of the QA guys will check what is going on. Are you sure you are not rendering the production with CPU (it looks different)? What is texture size mode?
You’re right, had 512px in IPR tab and 2048 in Vray, so yeah after making both same value results identical, wouldn’t it make sense to link those together for user intuitiveness? (only if you have specific production need you would want to tweak stuff separately)
Almost forgot one thing, will layered texture be supported when plugged into vraytriplanar, (i’m assuming right now it’s not recognized as bitmap and only bitmap is allowed)?
HI,
the difference between the CPU and the GPU is because currently the GPU is ignoring the “Size” parameter when the filter is set to “Gaussian”. I’ve reported the issue for fixing and as a workaround you can use some of the other filter types.
Thanks for the feedback.