Does anyone have an idea what causes this?
[IMG]http://www.1337upload.net/files/FFFF.png[/IMG]
[editline]28th January 2011[/editline]
[IMG]http://www.1337upload.net/files/rp_jorpakko0112.jpg[/IMG]
Was this by any chance, mirror from the other half? And what's your vmt setting.
You have 32 bones for a static object, why? Anyway, I also changed your *.QC file a bit:
[code]
$modelname props_jorpakko/track_512.mdl
$cdmaterials models/props_jorpakko
$body studio "track_512"
$staticprop
$surfaceprop metal
$sequence idle "track_512"
$collisionmodel "track_512_phys.smd"
[/code]
Your collision model was also too complex for the engine, so I built a new one. Here's the source files, all fixed, and ready to compile:
[url]http://s000.tinyupload.com/?file_id=48351754369624554918[/url]
Strange the collision seem to be fine from what i can see to be honest, but, that shouldn't mess up the lighting either. Plus, doesn't the QC for custom collision prop need this at the end.
[code]$modelname "props_jorpakko\track_512.mdl"
$body mybody "track_512.smd"
$staticprop
$surfaceprop "metal"
$cdmaterials "models\props_jorpakko\"
$sequence idle "track_512_idle.smd" fps 30
$collisionmodel "track_512_phys.smd"
{
$concave
$automass
}
[/code]
Anyways, can't really tell if the lighting is still mess up without the proper textures.
[QUOTE=Hybrid 4F;27708532]You have 32 bones for a static object, why? Anyway, I also changed your *.QC file a bit:
[code]
$modelname props_jorpakko/track_512.mdl
$cdmaterials models/props_jorpakko
$body studio "track_512"
$staticprop
$surfaceprop metal
$sequence idle "track_512"
$collisionmodel "track_512_phys.smd"
[/code]
Your collision model was also too complex for the engine, so I built a new one. Here's the source files, all fixed, and ready to compile:
[url]http://s000.tinyupload.com/?file_id=48351754369624554918[/url][/QUOTE]
It worked, thanks!
This thread may be closed now.
[editline]28th January 2011[/editline]
Also i'm still novice with modeling, so next time i'll keep eye on the bones.
Sorry, you need to Log In to post a reply to this thread.