corona 14 converter error unknow proprty fronttexmap

Hi. I got this error (corona 14 hotfix 1 3ds max 2026.3) “converter error unknow proprty fronttexmap in line 5003”… I deleted half the objects and tried running the conversion each time to figure out which object was causing it. At one point, I deleted everything and cleared the material editor—and the error still occurred. Another time, I deleted about 20% of the objects. The error persisted. I personalized the scene and the error disappeared… I’m not sure how to fix this. Maybe someone can suggest what to do?..

Can you send your scene along with some simple steps so we can reproduce the same error on our end?

You can send us a ticket using this link: https://support.chaos.com/hc/en-us/requests/new

Hi,

I can see where the issue comes from and this will be reported straight ahead.

Hi,

Can you please send one of the scenes where this error was hapenning, so we can double check if the error persists?

(Translation by Google.)
Thanks for the replies. I was able to find the object causing the error. More specifically, it’s a material. I have V-Ray 7.0.1 installed and corona 14.
The problem is aggravated by the fact that when an error occurs, the converter stops working, and the rest of the materials in the scene remain unconverted.
Usually, when a converter fails to convert something, it simply warns about the potential problem but doesn’t stop processing the remaining objects. But with this error, as soon as it processes the faulty object, it throws an error and stops processing the remaining objects.
Well, or so it seemed to me…
I’m attaching a scene archive. 3dmax 2025
error 5003.rar (33.3 KB)

Hi. Added the scene archive above. Error 5003.
error 5003.rar (33.3 KB)

Now that I’ve realized it’s a vraytosided MTL file, I’ll search for it. But I’ve already decided to attach the file… In any case, the error interrupts the rendering process, and the remaining materials remain unconverted. The scene was very large. I had to work for a long time and delete objects until I found this object.
(Sorry for English - Google Translate.)

Hi,

I confirm that this is fixed in Corona 15 RC 1.
It is a super edge case for conversion, nevertheless, the converter will not throw an error anymore.

You can give the v15 RC1 a try here:

Thanks for the report!