Steam Community :: Discussions

Blade Symphony

All Discussions Screenshots Artwork Broadcasts Videos Workshop News Guides Reviews

Blackmarket Armory

Make your own masks, swords, and other content and upload them to the game, viewable immediately by other players.
Learn More

Home

Discussions

About

Workshop> Blade Symphony> All Discussions

Worms

23 Aug, 2017 @ 7:30pm

StudioMDL will not compile sword collision model [Blender]

So today I tried a test to see if I could get SOMETHING into this game, so I made a very basic "sword" mesh using blender. I mainly used this tutorial (https://gtm.steamproxy.vip/sharedfiles/filedetails/?id=291006800), and I got all the way to the point where I needed to compile my meshes into a .mdl file.

Every time I tried to compile, I got the same error:

Running studiomdl for "test1.qc"... qdir: "d:\steamlibrary\steamapps\common\blade symphony\workshop\models\76561198004460670\test1\" gamedir: "D:\SteamLibrary\steamapps\common\Blade Symphony\workshop\" g_path: "D:\SteamLibrary\steamapps\common\Blade Symphony\workshop\models\76561198004460670\test1\test1.qc" Building binary model files... Working on "test1.qc" SMD MODEL D:\SteamLibrary\steamapps\common\Blade Symphony\workshop\models\76561198004460670\test1_ref.smd ERROR: d:\steamlibrary\steamapps\common\blade symphony\workshop\models\76561198004460670\test1\test1.qc(8): - could not load file 'D:\SteamLibrary\steamapps\common\Blade Symphony\workshop\models\76561198004460670\test1_phy.smd' ERROR: Aborted Processing on 'D:\SteamLibrary\steamapps\common\Blade Symphony\workshop\models\76561198004460670\test1\test1.mdl'

it seems that StudioMDL is having trouble compiling the mesh for the sword's collision box. I tried all sorts of things to fix it for 6 hours straight today (and actually fixed some actual problems) but none of them got the compiler to sucessfully load test1_phy.smd.

I also tried just compiling the template sword from the tutorial I mentioned previously, but even that gave the same error; I'll admit, though, that I may have made some mistakes in pathing that caused that, so im not sure that this really means anything.

Like I said, I think its a problem with the bounding box, so the .blend file is probably the issue.

Last edited by Worms; 23 Aug, 2017 @ 7:31pm

< >

Showing 1-4 of 4 comments

jes

23 Aug, 2017 @ 7:35pm

Is the mesh convex? Have you tried moving all files to C:\ drive? If you set your physics mesh to your reference mesh, it should silently fail and auto-generate one (from casual observations) for you.

post your .qc and .smd here or privately.

ps the link to the tutorial doesn't work for me

pps studiomdl should have nothing to do with blade symphony's bounding box, unless you're talking about source max model limits, in which case...

ppps physics meshes are irrelevant to the tracers / combat. they are just used for world collisions on player death.

Last edited by jes; 23 Aug, 2017 @ 7:39pm

Worms

24 Aug, 2017 @ 7:30am

Here is the .qc file, not sure if theres a way to share the .smd on here though:

$modelname "D:\SteamLibrary\steamapps\common\Blade Symphony\workshop\models\76561198004460670\test1\test1.mdl" $cdmaterials "D:\SteamLibrary\steamapps\common\Blade Symphony\workshop\materials\models\76561198004460670test1" $surfaceprop "metal" $bonemerge sword_grip $scale 1.0 $body "Body" "D:\SteamLibrary\steamapps\common\Blade Symphony\workshop\models\76561198004460670\test1_ref.smd" $sequence idle "D:\SteamLibrary\steamapps\common\Blade Symphony\workshop\models\76561198004460670\test1_ref.smd" loop fps 1.00 $collisionmodel "D:\SteamLibrary\steamapps\common\Blade Symphony\workshop\models\76561198004460670\test1_phy.smd" { $mass 1 }

I'll try out moving the files to the C:\ drive today.

Last edited by Worms; 24 Aug, 2017 @ 7:31am

Worms

24 Aug, 2017 @ 8:06am

I migrated all the Blade Symphony files, and changed all the pathing, and sucess! the collision model succesfully compiled! But now I have a new error message:

Running studiomdl for "test1.qc"... qdir: "c:\program files (x86)\steam\steamapps\common\blade symphony\workshop\models\76561198004460670\test1\" gamedir: "C:\Program Files (x86)\Steam\steamapps\common\Blade Symphony\workshop\" g_path: "C:\Program Files (x86)\Steam\steamapps\common\Blade Symphony\workshop\models\76561198004460670\test1\test1.qc" Building binary model files... Working on "test1.qc" SMD MODEL C:\Program Files (x86)\Steam\steamapps\common\Blade Symphony\workshop\models\76561198004460670\test1\test1_ref.smd SMD MODEL C:\Program Files (x86)\Steam\steamapps\common\Blade Symphony\workshop\models\76561198004460670\test1\test1_phy.smd Processing LOD for material: test1 Model has 1 convex sub-parts Collision model completed. The filename, directory name, or volume label syntax is incorrect. --------------------- writing C:\Program Files (x86)\Steam\steamapps\common\Blade Symphony\workshop\models/C:\Program Files (x86)\Steam\steamapps\common\Blade Symphony\workshop\models\76561198004460670\test1.mdl: Error opening C:\Program Files (x86)\Steam\steamapps\common\Blade Symphony\workshop\models/C:\Program Files (x86)\Steam\steamapps\common\Blade Symphony\workshop\models\76561198004460670\test1.mdl! (Check for write enable)

Trying a few different things to fix it.

EDIT: here's my new .qc:

$modelname "C:\Program Files (x86)\Steam\steamapps\common\Blade Symphony\workshop\models\76561198004460670\test1\test1.mdl" $cdmaterials "C:\Program Files (x86)\Steam\steamapps\common\Blade Symphony\workshop\materials\models\76561198004460670\test1" $surfaceprop "metal" $bonemerge sword_grip $scale 1.0 $body "Body" "C:\Program Files (x86)\Steam\steamapps\common\Blade Symphony\workshop\models\76561198004460670\test1\test1_ref.smd" $sequence idle "C:\Program Files (x86)\Steam\steamapps\common\Blade Symphony\workshop\models\76561198004460670\test1\test1_ref.smd" loop fps 1.00 $collisionmodel "C:\Program Files (x86)\Steam\steamapps\common\Blade Symphony\workshop\models\76561198004460670\test1\test1_phy.smd" { $mass 1 }

Last edited by Worms; 24 Aug, 2017 @ 8:10am

Worms

24 Aug, 2017 @ 5:23pm

Okay, Sucess! I got the sword into the game. After transferring to the C:\ drive there was just some pathing issues I had to fix. Thanks for that suggestion :)

< >

Showing 1-4 of 4 comments

Per page: 1530 50

Date Posted: 23 Aug, 2017 @ 7:30pm

Posts: 4

Start a New Discussion