Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
- If export is supported, when a user exports a file with SFM data and naively tries to compile it with studiomdl.
- If export isn't supported, whet a user imports a SFM animation and tries to export it again.
In both cases the SFM data is lost and the best I can do about it is provide spammy warnings that the user may not understand nor even read.I think the best solution is to implement SFM import/export as a different operator from studiomdl import/export, and perhaps even a different addon. This new operator would invoke the Source Tools and then do its own SFM-specific work afterwards. How does that sound to you?
(I just remembered that there is a third SFM-only feature: bezeier handles on each keyframe. The importer currently ignores them, and the exporter bakes them into extra keyframes. That's another feature that could be implemented.)
If you need help navigating DMX files try my desktop editor, DMXPad[github.com]. It's a bit wonky in places but it does have a massively useful file comparison feature.
In terms of the formats, they are very similar. Here's the spec for the basic studiomdl format; anything SFM does ought to be a layer on top of that.
You can't start Blender from VS due to a limitation in the Python Tools'[pytools.codeplex.com] UI. You'll need to start it up then attach. But I absolutely do develop and debug there.
There is also a test module that demonstrates how to get automated tests working. Unfortunately the tests require a special build of Blender which exists as a Python module instead of an executable. It builds with VS2013 though, so it's not a huge hurdle.
If Blender crashes while debugging, make your own build with "Python Safety" enabled. That build will be slower but will throw exceptions instead of crasting on invalid Python access.