Search

[mark2580]

Found a conflict with another script. When I try to import several fbx files, I get spam from messages related to some wallworm helper, I have to hold enter to skip them automatically.

Script - https://www.scriptspot.com/3ds-max/scripts/batch-exportimport
Files - https://drive.google.com/file/d/1qh6Ha2mdq6V7ef8IarNQ7ZJtFIShXIyo

[wallworm]

Thank you for reporting. I will try to investigate this.

[wallworm]

I verified the problem but it's totally baffling me as to why the error is happening. It's straight vanilla MAXScript wrapped in some validation and this code has been running for years across countless environments without issue. So I'm not clear on the issue. I've asked a fellow MAXScripter for some extra eyes on the issue. I'll let you know if I find anything.

[mark2580]

Here's another file. It seems to be directly related to the FBX format, not the bulk import script. 🤨
https://drive.google.com/file/d/1iqsHJH619b4EQmkS9n-NK3Xdnl2eG9Gg

[wallworm]

Thanks. So I looked at the code and literally have no clue how the FBX importer is creating this problem with some specific files. It looks to me that the FBX Importer itself is creating some unexpected nodes from these specific files. Can you inform me of the file origins?

I did find a workaround for you in the meantime.

If you click Wall Worm > Wall Worm Utilities > Toggle Wall Worm Events the functions that scan nodes added to the scene will become disabled and you won't get the error.



Do note that this effectively turns off Wall Worm management system and many things won't work correctly in WW (like VMF Export, etc) until you turn it on and reload a scene or restart Max.

[mark2580]

Can you inform me of the file origins?

This is an export of the entire scene from Unreal Editor (UE4).

[wallworm]

Thanks for sharing. I know the line of code that is choking in WW, but I don't know how the specific files can cause the problem. I'll look into an official solution, but for the moment the work around above is the solution. Did you test it?

[mark2580]

Did you test it?

Yes, specifically with the last file. I don't know how to create an fbx that causes this problem, so I'll check something else.

[mark2580]

If you click Wall Worm > Wall Worm Utilities > Toggle Wall Worm Events the functions that scan nodes added to the scene will become disabled and you won't get the error.

is it possible to disable this permanently somehow? after restarting it turns on again, forgetting about it I import FBX and again get spam from these errors, and they slow down the import a lot

[wallworm]

There isn't a setting for that ATM, but you could write a startup script to do that. Note if you did do that, a vast percentage of the functions in WW will not work correctly. Ideally I can figure out why the particular FBX imports can cause this as these functions have been running on a large number of computers for years without the issue popping up.