Installation guide - Mesa setup - Project setup - Ressources Structure - Manually install Mesa shelf - Mesa_config help - Environnement variables - Issues and common errors - Uninstall MESAHow to update - update from 2.0.1 to 2.1 - Update from 1.1 to 2.0.1 - Update from 1.0.1 to 1.1Export Guide - Preparing the scene - Shading - Layering - Collision and Ragdoll model - Cleaning the scene - Export the assetsTutorials - Maya Settings for Source Engine - Import SMD mesh and skeleton - MESA install video - MESA export videoSource Engine - HitBoxes and HitGroups - Create a Source Engine Mod - Decompile the Models and animations - Extract Content from VPK files - StudioMDL common ErrorsDota Items Creation Guide - Workspace for Dota 2 01 – StudioMDL.exe do not compile the scene. If studiomdl log don’t appears into the script console of maya. You must start steam if you want to compile your asset ( texture and model), as the binaries require steam library to work with the Vconfig game system. 02 – Wrong Materialsrc Path on Path Tab. The path from the texture file do not start with /Materiasrc/ directory. The project hasn’t being properly set to the /modname_source/. 03 – Materialsrc path Fails When i click on GENERATE PATH of the Path Tab , the path is not ending with the materialsrc directory. It’s possible that the sdk launcher config overwrite the environment path set in the maya.env, so edit your current game to the same one than set for MESA, or exit the sdk launcher. It’s possible the texturemap is out of the modname_source/materialsrc/ directory. so put your texture in /materialsrc/ folder with the TGA format, and the path could become the right one. 04 – Unterminated string This mades both exportVTA and smdOptionsWindow Panel unable to work. 1 2 // Error: $list[$cnt] = substitute “? $item “”; // Error: Unterminated string. Go to control panel -> region and language -> language for non-unicode After changing this to English(United States), everything works well. 05 – VTF Edit buttons on the MESA Shelf do not opens the VTF and VMT files in VTF Edit. Multiple issues when determining the path of the materials files from the smdTarget attribute. Issue 1 If the path of the textures in materials, is different then the path of the smd/QC path, we can’t find the VTF/VMT Example : 1 2 c:/mymod/models/props/ c:/mymod/materials/models/props/ VTF Edit script expected that path : 1 c:/mymod/materials/props/ Issue 2 Another case with two materials on the same models the script will only open the file based on the name of the Scene ( cause the smd /qc path is generated from the path of the scene). Issue 3 But we can rename the QC and reference SMD name. and in that case if the name of the scene is cube.ma, and the SMD /qc path is Cube_reference.smd the script will looking for : c:/mymod/materials/models/props/cube_reference_diffuse.vtf But that file doesn’t exist. the name of the texture is cube_diffuse.vtf 06 – Fix the missing smdInfo.Tips in scene built with 1.X version of MESA. Cannot get attribute smdInfo.Tips To fix this, you simply have to click on “Scene upgrade” icon from the MESA shelf.
01 – StudioMDL.exe do not compile the scene. If studiomdl log don’t appears into the script console of maya. You must start steam if you want to compile your asset ( texture and model), as the binaries require steam library to work with the Vconfig game system. 02 – Wrong Materialsrc Path on Path Tab. The path from the texture file do not start with /Materiasrc/ directory. The project hasn’t being properly set to the /modname_source/. 03 – Materialsrc path Fails When i click on GENERATE PATH of the Path Tab , the path is not ending with the materialsrc directory. It’s possible that the sdk launcher config overwrite the environment path set in the maya.env, so edit your current game to the same one than set for MESA, or exit the sdk launcher. It’s possible the texturemap is out of the modname_source/materialsrc/ directory. so put your texture in /materialsrc/ folder with the TGA format, and the path could become the right one. 04 – Unterminated string This mades both exportVTA and smdOptionsWindow Panel unable to work. 1 2 // Error: $list[$cnt] = substitute “? $item “”; // Error: Unterminated string. Go to control panel -> region and language -> language for non-unicode After changing this to English(United States), everything works well. 05 – VTF Edit buttons on the MESA Shelf do not opens the VTF and VMT files in VTF Edit. Multiple issues when determining the path of the materials files from the smdTarget attribute. Issue 1 If the path of the textures in materials, is different then the path of the smd/QC path, we can’t find the VTF/VMT Example : 1 2 c:/mymod/models/props/ c:/mymod/materials/models/props/ VTF Edit script expected that path : 1 c:/mymod/materials/props/ Issue 2 Another case with two materials on the same models the script will only open the file based on the name of the Scene ( cause the smd /qc path is generated from the path of the scene). Issue 3 But we can rename the QC and reference SMD name. and in that case if the name of the scene is cube.ma, and the SMD /qc path is Cube_reference.smd the script will looking for : c:/mymod/materials/models/props/cube_reference_diffuse.vtf But that file doesn’t exist. the name of the texture is cube_diffuse.vtf 06 – Fix the missing smdInfo.Tips in scene built with 1.X version of MESA. Cannot get attribute smdInfo.Tips To fix this, you simply have to click on “Scene upgrade” icon from the MESA shelf.