Trying to import a .TX sequence in vraybitmap crashes max.

[HowardDay]

Using windows 10, 3dsmax 2022.2, and the latest nightly of Vray. I try and import a .tx sequence as a, well, sequence and max crashes. If I import an PNG sequence, then manually change the suffix to .tx in the generated.ifl file, it seems to work fine. Might this be something internal to MAX not recognizing .tx as a filetype?

[hermit.crab]

No issues here, just did a quick test. You are importing the .tx files through a VRayBitmap and then replacing the sequence number with <frameNum>, correct? Does it happen with a particular .tx sequence?

[HowardDay]

I'm importing the .tx sequence as an IFL sequence, using the import dialog. Here's a video. Empty scene, new VRayBitmap, set assigned to a dummy .tx file, then I try and assign a sequence to it.
https://drive.google.com/file/d/1Zet...ew?usp=sharing

[hermit.crab]

I see. This is most likely an Autodesk thing. I tried manually converting the .tx sequence to IFL through the IFL manager, however, .tx files are not recognized and cannot be selected.

[HowardDay]

Please confirm that this is a crash bug - possibly you should disable the "import tx as sequence" from your UI, or find some way to quietly handle this in the background (have the VRayBitmap generate the .IFL itself, for instance). I've tried this on 3 different computers and it is an insta-kill of 3dsMax every single time.

[hermit.crab]

Yes, I've already reproduced the crash and logged it (internal bug-tracker id: VMAX-11694) for developer investigation.