V-RayMax Converter PRO
V-RayMax Converter PRO is the best tool for convert 3d scene (materials, maps, lights, cameras, proxies, modifiers, helpers, render elements, etc.) from various render engines to V-Ray and from V-Ray to Corona Render, and also for converting V-Ray and Corona materials/maps to Standard materials/maps.
V-RayMax Converter PRO converts the source materials with maximum possible preservation of the basic material properties, such as diffuse, specular, opacity, glossiness, roughness, bump, displacement, selfillumination (emission), translucency, reflection, refraction, although it is necessary to understand that certain materials may need adjustments once the conversion process is complete. Also, all the textures that are used for the above parameters were saved. As for the special procedural maps, they are converted only if there is an analogue. Otherwise, procedural maps are baked into textures or removed if the resulting materials can be used without them.
Current version: 4.0032
Supported for conversion:
- Standard (Default Scanline)
- Corona Render
- FStorm Render
- Octane Render
- finalRender
- Arnold
- Brazil_Advanced (RS v 1.2) material
- NVIDIA iray (unofficial) material.
- Standard (Default Scanline) materials/maps
- Corona Render (v9 or higher)
- Standard (Default Scanline) material/maps
See full list of supported conversions.
Main features:
- Convert materials, maps, lights, cameras, modifiers, helpers and GI environment from supported renderers to V-Ray and from V-Ray to Corona
- Convert clouds from CoronaSky to VRaySun and vice versa.
- Convert Render Elements to V-Ray (currently supported Scanline RE, Corona RE, FStorm RE, Octane RE) and from V-Ray to Corona
- Convert V-Ray and Corona materials|maps to Standard (Default Scanline) materials|maps
- Convert proxies (currently supported from Corona, FStorm, Octane) to V-Ray Proxy (static and animated)
- Convert V-Ray Proxy to Corona Proxy (static and animated)
- Convert standard Bitmaps to VRayBitmap (VRayHDRI) and vice versa
- Convert 3ds Max Physical cameras to V-Ray Physical cameras and vice versa
- Automatic configure ACEScg workflow in V-Ray
- Batch processing for multiple *.max files
- Programmatically interact with most converter functions using built-in maxscript methods (API), which allows you to use the converter without UI and in combination with other 3rd-party scripts.
- ...and more additional tools for fixing and adjusting the scene.
More detailed information about the all features and capabilities of the "V-RayMax Converter PRO" can be found here: https://maxtools.3dzver.ru/vmcpro
Also, on this V-RayMax Converter telegram channel, you can read about all the updates.
IMPORTANT: To convert between different rendering engines, it is necessary that these rendering engines are installed (alpha/beta/dailybuilds/rc versions are not supported).
PS: Please, respect the developers and other users - do not post promotional messages in comments (ie spam).
If you have any suggestions or comments related to the work of the plugin, use the support form at this webpage: https://maxtools.3dzver.ru/supportpro
- Scripts
- ACEScg
- autodesk material to vray material
- brazil
- conversion
- convert render elements
- converter
- converting
- Corona
- corona to standard
- corona to vray
- finalrender
- iRay
- Material
- Material Converter
- material converting
- Physical
- renderer
- revit
- sRGB
- standard to vray
- v-ray
- VRay
- vray material converter
- vray to corona
- vray to standard
- vray to standard material
Comments
This issue has already been fixed in update 4.0032
Thanks for reporting the issue. At the moment, this has already been fixed in update 4.0032, which you can download in your personal account on the website.
New update v4.0032 are available!
v4.0032 release notes:
>>PS: It is possible that the
>>PS: It is possible that the removed Bump map had an empty texture file path.
No, but i use relative path like:
"Maps\xmpp\D_Cloth_Awning_Stripe_Green_NORM_OGL.jpg"
Normal
Re-checked and the problem was repeated.
Maybe I don't understand the principle of operation, but disabling normal map seems strange.
mailed the files to [email protected]
Please write in detail about
Please write in detail about this in the support form on the website: https://maxtools.3dzver.ru/supportpro
Or here: [email protected]
PS: It is possible that the removed Bump map had an empty texture file path.
Bump problem
the script started to disable bump maps with vraynormalmap, already connected to the material
Probably because of the fix bump for Vray-GPU option
New update v4.0031 are available!
v4.0031 release notes:
Sorry, the text in the
Sorry, the text in the description was slightly changed, so it was moved to the top. We will try to monitor this in the future and make only relevant changes.
Double post
Double post
On top with nothing new:(
I have seen it now a few times: VMCP is on top of the news section while there are no new updates or comments. Please do this only if there is some REAL news:(