Wall Worm Forums

So was resident evil on the source engine? The format supported in Wall Worm is entirely for Goldsource, Source and Source 2. The SMD format in these engines do not contain any material information. Instead, the information for opacity and specularity is contained in other formats.

Im making a mod for resident evil 4 2005, and this was the only plug-in for 3dsmax that worked for me. But I still having a issue, when I export my model to SMD format it does not retain the Specular or any other map, it only uses map_kd all the others disappear and the model look opaque in-game. How can i preserve the specular when exporting the model? Thanks if anyone can help me!

Just a quick update as I've had a few inquiries in the last couple of weeks. I'm still stalled on updating WW for S2 and haven't made appreciable progress since the last post. I still fully intend to continue the S2 work but just haven't had the energy after my day-job these days.

In terms of next steps, I still need to get proper brush/displacements exporting followed by more material exports. Blend materials is high on list and I also plan to add support for the OpenPBR material that is now in Max 2025.3.

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.

Quote from: wallworm on December 11, 2024, 11:01:59 AMIf 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

Quote from: wallworm on December 12, 2024, 11:00:23 AMDid 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.

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?

Quote from: wallworm on December 11, 2024, 11:01:59 AMCan you inform me of the file origins?

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

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.

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