Vrscene fails to load

[bruce_hart]

Just working on a project today and decided to take it onto Vantage for a quick animation. The file failed to load and referred to the log. Vantage reported the following errors in red:
12:06:41.171 [ERR] Parser error at B:/Project/Castle_Hill/Castle-Hill5.vrscene:9140: Expected "," in AColor definition
12:06:41.171 [inf] Loading scene took 0.02 seconds !
12:06:41.171 [ERR] Error loading scene: -2: Error parsing scene

Back in 3DS Max - this error appeared in the export log:
[12:24:04.179] Warning : Invalid floating point number(s) found while writing .vrscene: -nan(ind)

I had the same problem in a previous project. After about 2 hours of isolating geometry in a process of elimination, I tracked the problem down to a piece of imported Revit geometry - namely an elevator door. Pretty much all of my work involves rendering up imported Revit files, so using this kind of geometry in Vantage seems very unreliable at this point. I have only had the import failure since upgrading to Vantage 2.x versions. Would you like an example scene?

Thanks

[bruce_hart]

Spent some time on my scene to isolate the offending geometry. The 3DS Max 2024 file is attached along with the exported Vrscene file. At the top of the log it generates the following: [15:20:15.383] Warning : Invalid floating point number(s) found while writing .vrscene: -nan(ind)
In the original scene it came from I was able to successfully export complex geometry for cars. plants, trees etc. without any problem (no floating point number error). The geometry attached is simple by comparison, created in Revit, and imported via the *.rvt file import. I tried doing a vertex weld operation on the geometry and a Reset XForm, but that didn't help.

[Alexander.Atanasov]

Hi, bruce_hart,

The problem here lies in the imported geometry materials and how the vrscene exporter exported them, not in Vantage. There is an invalid VRayColor plugged in the self-illumination of material Default Generic and that fails the parsing of the scene. Remove it and the mullions will import correctly.

Best regards,
Alexander

[bruce_hart]

Hi Alexander
thanks so much for solving the problem. I have a script that converts Revit materials to Vray, and occasionally there are some bad translations. Thanks again!

[bruce_hart]

Hello - I have yet another scene that crashes Vantage, due to this error: [ERR] Parser error at B:/Project/V_____/V_____Full_Site_E.vrscene:34485: Expected "," in AColor definition
As before, it would seem there is probably a rouge Revit material that has been converted with some invalid colour value. Every Vrscene export I do contains hundreds of errors, mostly to do with Bitmaps having a blur value of less than 1.0., so it's difficult to see the one error line that may indicate which object or material is causing the issue. Do you have any tips on how I can track down the material(s)?

Would it be possible for the Vrscene export process to automatically clamp invalid/out of range values?

[npg]

There is a syntax error on line 34485. This could mean the file is corrupted (not fully saved; network error; etc.) The syntax error is probably not related to warnings about bitmap filtering. Try inspecting the vrscene file with a text editor. If the file just ends abruptly on this line then it's obviously broken. If the file continues, paste the lines around the error so we can have a better idea of what trips the parser.

BTW You said "crashes Vantage", but isn't it just an error message after which you can load another scene?

[bruce_hart]

Hi Nikola - thanks for the reply. When loading the Vrscene, I get an Error dialog: "Error loading scene - Press OK to return to an empty scene. Details about the error are in the log"
Here is a One Drive link to the Vrscene and the log file if you want to look at it. When the error dialog shows up, the whole application will close a few seconds later, even if you don't press OK. So in that sense, it does indeed crash.

Vantage_Vrscene

Some background info - this file started as imported geometry from Revit (FBX import). I then used a third party script to convert the Revit Autodesk materials to Vray. This scene renders fine in normal Vray.
I'm really looking for an easy method of determining what material or objects are causing the issue. This Max file and Vrscene was saved on a local SSD drive, but all of the texture and proxy assets are called from a mapped network drive location. The scene also includes Forest Pack and RailClone objects

[npg]

The error in the scene is triggered by this broken color, which is attached to the material "Default Generic":

TexAColor VRayColor@tex_219 {
texture=AColor(-nan(ind), -nan(ind), -nan(ind), 1);
}

I see that the file was exported from V-Ray 6.20.02. There is at least one patch released after that - 6.20.06, as well as V-Ray 7. I don't know if the broken color is fixed there. It could be some issue specific to this scene. Try deleting this material. Actually, it seems that the issue was caused by the script you mentioned.

This scene renders fine in normal Vray.

You probably mean the CPU renderer in Max. If you export the scene to a vrscene file from the V-Ray menu and try to render it with V-Ray standalone, it should produce the same syntax error.

This Max file and Vrscene was saved on a local SSD drive, but all of the texture and proxy assets are called from a mapped network drive location.

There is a parser error before we get to reading any assets, so the network doesn't seem relevant.

I was not able to reproduce a crash with this file using Vantage 2.7.0 or 2.7.1. Try using the latest Vantage update and a more recent driver. If you are still getting crashes there are probably .dmp files generated in your %TEMP% folder that you can send (check the timestamp).

[bruce_hart]

Hey Nikola - thanks for your time looking at it. I've recently ditched the conversion script in favor of using the Max Scene & Vray Scene converter combo, so hopefully this won't be an issue in the future. I'll update Vray & Vantage as well. Thanks again