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
So I guess we can deduce whether the XML files are just like a white paper for the actual engineering of the BMD file once we find out how to open them :)
Does anyone who worked with ctyengine have any ideas how to do it?
http://stateofdecaymods.com/mod-home...imits-diy-mod/
and
http://stateofdecaymods.com/mod-home...imits-diy-mod/
So my main concern is how.
The core idea is that the hex editor doesn't have to operate on a level that we can read and therefore it can scour the file and handle the raw numbers we figure out as the ones that are needed.
I've been working on making meshes/skins work in a fully customized way and haven't worked on the BMD files since around the original post we're talking on, haha.
It's fair to say that if any of us find the solution then we should post a how-to for the community :)