Wall Worm Forums

Thanks for your question.

So, as I understand it, you are wanting to select arbitrary meshes in Max (that are not already models in the game engine) and send that as a new VMF with new MDLs? If that is the case, see this document and video:


More info here:

https://dev.wallworm.com/document/218/convert_scene_to_model.html

This defect is now fixed in Wall Worm 6.1.1.

The Commit Sculpt Mesh function is currently broken in some versions of 3ds Max in WW 6.0.0. I'm looking into the problem.

This is the first public release of Wall Worm with Source 2 support. Support is limited to Counter-Strike 2 version of Source 2 formats. Many features are still missing. To export WWMT and Materials to S2, you need to set your game's global settings to Source 2 engine.

Some info on features included on docs site here and here are instructions on setting up for S2.

Below are release highlights.

Version 6.0.0 released on 3-2-2024

   * Engine: Added Source 2 Engine support into several key areas of Wall Worm. Source 2 formats compatible with Counter-Strike 2.
   
   * WWMT: Added support for WWMT to export to VMDL format when the settings are configured for CS2 format of Source 2. Current features supported: Mesh, Hull, LODS, Materials, Textures, Sequences, Skins, Bodygroups,  Attachments and Breakable Gibs.
   
   * Entities: Added support for Source 2 FGD format in Max 2022+. MAXScript FGD parser does not support Source 2 format.
   
   * Materials: Added support for the PBR Material (PBRMetalRough) in Wall Worm. For Source, native support is for base_color_map and normal_map. For Source 2, all maps are supported.
   
   * VMAT: Added support for creating Source 2 materials. Currently limited to shader "csgo_simple.vfx".
   
   * VMAP: Added limited support to export an ASCII VMAP file. Currently only exports entities. The Mesh export is working except for normals.

   * System: Fixed Source compiler problems in many areas of Wall Worm from recent changes in Windows.
   
   * Settings: Updated the settings to automatically try to create missing folders if the settings define them but the folders do not exist.
   
   * Settings: Added new button to open the Wall Worm settings folder in Windows Explorer.
   
   * Settings: Updated the Create Local GameInfo function to get game paths from mount.cfg when creating a new gameinfo.txt file from Garry's Mod.
   
   * Entities: Updated FGD parser in 3ds Max 2022+ to set float spinners to default value of 0 if the FGD provides an empty default value for floats. Fixes malformed FGD issues.
   
   Entities: Updated the link buttons in entities pointing to WallWorm.com and the Valve Developer community to buttons that call a method to open the browser rather than using the Hyperlink control. This alleviates the security warning that happens when using the ShellLaunch() command in embedded scripts as the entity custom attributes are embedded in scenes.
   
   * Materials: Updated Material Exporter to exclude some common tool materials from the export list so that the exporter UI is less cluttered.

I got stalled out last month with my day job so I didn't make much progress since then. This weekend I troubleshooted some issues with exporting a VMap. Still digging into why some scenes are working and some are not.

• Entity Output Connections in VMap
• Support for PBRMetalRough material in the main Material Exporter
• Started new Custom Attribute for S2 Materials

If you want to know why Wall Worm updates have been sluggish for a while, it's because I've been head down at work for so long overseeing USD features in 3ds Max and Maya. What's all the buzz about USD? See some examples of how it's used in a webinar where I gave a live demo in Max, Maya, Houdini and Unreal.

• WW Pro FGD Parser for S2 in Max 2022+
• Multiple Datas in VMap Export (cameras, entities, basic mesh)

Things to note:

The process of exporting a WWMT Helper to a model is the same as it was for Source. This means that the tutorials/docs are generally the same:

• Assign Meshes to WWMT
• Export the Materials/VTF with the Export VTF button in WWMT
• If using custom gibs, compile them from the Prop Data & Custom Gibs rollout
• Export the WWMT

Key differences:

• WWMT uses the PBRMetalRough() material for Source 2 instead of the Standard Material
• Some advanced settings like $jigglebones, IKs, QC Eyes, etc are not yet exported

In my local build I now can export:

• Prop Data
• Custom Gibs (breakable prop)
• Basic Hitbox info

Now S2 support in WWMT in my local build for:

• Attachments

The next release of WW will have support for the Counter-Strike 2 version of Source 2; HL:Alyx and Dota 2 are not supported. In this release, Wall Worm can export models from WWMT Helpers as well as their materials and textures.

This thread will detail the current capabilities and known issues.

If you want to test these tools before they are officially released, simply contact me directly for an installer.

With this first release of Source 2 support, Wall Worm will only have limited support of the features that work for Source/Goldsource. At this time, the capabilities are limited to models and their materials and textures. Level exporting has been started but does not work yet. There are no importers and the MDL loader is not yet working for Source 2.

Setting Up WW

To properly set up WW for Source 2 you will have to manually configure your global WW Settings for Source 2. There is no GameConfig.txt file that WW can use to configure your settings. You will also need to install the CS2 Workshop tools from the DLC. You can do this in your Steam library by right-clicking CS2, clicking properties, then going to the DLC section.



You need to set the modelsrc, materialsrc and mapsrc paths to the models, materials and maps folder in your CS2 content addons folders.

Set the GameInfo folder. The default is:

C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo
Then set the Bin Dir to the Bin folder for the compile tools. By default that is:

C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\game\bin\win64
For the FGD settings, you need to manually point WW to the FGD file. by default that is:

C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\csgo.fgd
Finally, set the Engine to Source 2.



Exporting Assets

The workflow for assets is very similar to Source but there are a few differences.

#1) Only use the PBR Material (Metal/Rough) (PBRMetalRough()) on your models. You can use them with Multi/Sub-Object Materials. This material maps extremely well to the Source 2 materials.

#2) Not every feature of WWMT yet works in the export.

The features that will work:

• Meshes
• Hulls
• LODS**
• Bodygroups
• Sequences
• Multiple Skins
• Attachments
• PropData
• Custom Gibs
• Materials***

** LOD Material Replacements not yet supported.
*** You should set the texture names to .tga and the Material names to use .vmat.

When you export the models with custom materials, the materials will continue to appear red in the modeldoc tools in Source 2. I don't know why yet, so at this time you have to open the model after compile and select materials in the modeldoc and double-click them--they will open in the material editor and suddenly work. Click the Save All button in the material editor to keep the textures working.

Entities

Wall Worm now supports the CS2 FGD for entities. It will honor the new @exclude command as well as the @OverrideEntity and delete_keys command.

VMap Exporter

The Level Exporter now has limited VMap export. At this time, entities should export as expected. However, displacements and world meshes are not yet exported correctly and will crash Hammer if you try to load a VMAP exported from Wall Worm with anything other than entities.


That is it as of now. Please share feedback as you test it.

Now WW can export:

• Bodygroups

I now have support for exporting:

• WWMT Sequences
• WWMT Skins

Features I have working as of now in my local build:

• WWMT can export LODS
• Level Exporter can export basic scene with entities to VMAP
• MAXScript FGD Parser now supports the CS2 FGD

I have gotten around of updates done internally. At this point here is what is supported:

WWMT:

• Meshes
• Hulls
• Export to VMDL + model assets (dmx, fbx or smd)
• Support for some WWMT settings
  
• Compiling to VMDL_C

Materials:

• Material to VMAT
• Support for Max's PBR Material

I'm hopeful that by the holidays I'll have Sequences, LODs, Skins and breakable props implemented. Once those basic set of features are done, I'll release an update to the public.