Wall Worm Forums

I haven't had a lot of time to work on WW for several months. I learned this week that WW had been causing pop-up errors for CS2 because the FGD Parser in WW wasn't supporting some new changes in the FGD.

I took time to address that problem today and put out WW 6.2.

The items I want to look at next are proper Brush/Displacement support and Blend Materials. Those are the two items outstanding to get the full level design workflow in S2 on par with S1. As it stands, the brush export only works for single mesh brushes and the UVs are not correct. Displacement support is currently missing in full. I am hopeful I can find some time over the Christmas holidays to do that.

Sorry, I re-read your posts from the beginning. Obviously I only skimmed some of the posts (probably between meetings at work) as I now realize what you are asking.

• Use the Selection as Point Entity button you mentioned in OP
• Once all have the entity, select them all
• Run following snippet in MAXScript Listener:

for obj in selection do obj.model = obj.name

Version 6.2.0 released on 11-3-2024

* FGD: Fixed the FGD Parser for CS2 in Max 2022+. There were changes in the CS2 FGD files that had stopped the WW Parser from working.
   
* FGD: Updated the FGD Parser to no longer use a messagebox to inform of parse errors. Now the errors are only put into the MAXScript listener.
   
* Convert Scene to Model: Updated the tool to clear the undo buffer to avoid potential crashes when using Undo with that tool.

* CSV Report: Fixed script error if running the CSV Report when no displacement functions had been loaded.
   
* Materials: Fixed MAXScript error when loading some older scenes created with Wall Worm.
   
* Security: Updated digital signatures for DLLs and EXE.
   
* Security: Updated build system to stop signing MAXScript files since the AdskSignTools.exe does not support modern certificate requirements.

Those are three lines of code to run in sequence in the MAXScript listener. Or open the MAXScript Editor and paste the entire lines and execute the script in full.

The VMF Exporter is already set up to export the Source Model object type to VMF. Plop one down, set the World Model path in the MDL properties and export. It will include the position and rotations for that entity. The tools above are simply the way you make them.

If you don't have the game configured, the Source Model object will simply appear as a box--which will essentially be what you are looking for if you don't want to load in the MDL in the viewport.

Quote from: wallworm on November 01, 2024, 06:41:41 PMBefore running that script, click F11 and enter this code into the white MAXScript Listener:

Code Select Expand

callbacks.removeScripts id:#WallWormAutoSliceModID

Okay, this works.

Quote from: wallworm on November 01, 2024, 07:02:14 PMAdditional information:

To permanently turn on the Wall Worm Slice modifier options:

Code Select Expand

::wallwormSlicemodOps.AutoSliceMod = true
::wallwormSlicemodOps.saveSettings()
::wallwormSlicemodOps.initiateCallbacks()
or to permanently turn it off:

Code Select Expand

::wallwormSlicemodOps.AutoSliceMod = false
::wallwormSlicemodOps.saveSettings()
::wallwormSlicemodOps.initiateCallbacks()

And this is what I don't understand at all. Should I also send this to MAXScript Lister??? Because it seems it didn't give any result.

Quote from: wallworm on November 01, 2024, 06:52:51 PMYou can place static prop entities directly in Max already. Simple configure WW for your game in the global settings and then you can add entities via the point entity tools.



Here you can see I configured WW for Black Mesa. Now all the entities are available in the Entity button on the Wall Worm Level Design Toolbar. When configured, you can load entities in via that menu, use the Wall Worm > Wall Worm Importers > Mass Model Fetch, or by going to the Create Tab in the Command Panel, changing the category to Wall Worm, and adding entity objects in the scene with the Source Model object type.

Those model nodes include a field called World Model. That will be the model that will load directly in Max, and the VMF Exporter will place those entities in the world when you export.

I don't understand how else to explain what I want to do. I'm not interested in mapping in 3ds max at all, I don't need to create any models from the game like prop_static.

Imagine. I have a 3ds max scene with objects from somewhere. Doesn't matter. I just want to get a vmf with their coordinates and name. I don't need anything else. Is it really that hard to understand?

I don't care at all whether it will be prop_static or prop_physics or prop_dynamic, even npc_alyx, as long as I have xyz coordinates + rotation angle and the name of the original mesh that was in 3ds max. The rest I will edit myself using a text editor.

Additional information:

To permanently turn on the Wall Worm Slice modifier options:

::wallwormSlicemodOps.AutoSliceMod = true
::wallwormSlicemodOps.saveSettings()
::wallwormSlicemodOps.initiateCallbacks()
or to permanently turn it off:

::wallwormSlicemodOps.AutoSliceMod = false
::wallwormSlicemodOps.saveSettings()
::wallwormSlicemodOps.initiateCallbacks()

There is a problem with the CS2 FGD Parser. I suspect that something has changed with the formats in the CS2 FGD formatting. I will try to get a fix for it soon.

UPDATE: Fixed in WW 6.2.

You can place static prop entities directly in Max already. Simple configure WW for your game in the global settings and then you can add entities via the point entity tools.



Here you can see I configured WW for Black Mesa. Now all the entities are available in the Entity button on the Wall Worm Level Design Toolbar. When configured, you can load entities in via that menu, use the Wall Worm > Wall Worm Importers > Mass Model Fetch, or by going to the Create Tab in the Command Panel, changing the category to Wall Worm, and adding entity objects in the scene with the Source Model object type.

Those model nodes include a field called World Model. That will be the model that will load directly in Max, and the VMF Exporter will place those entities in the world when you export.