egosoft.com

X2BC latest version 1.0.11 - released 15.1.2007

X2BC page on X-Wiki

Download from www.doubleshadow.wz.cz

Changes:
+ support for normals maps (bump maps) - you must have DBOX 1.8 (or higher)

Description
Program for decompilation of BOB files and compilation of BOD files.

Compatible with X2 The Threat and X3 Reunion files.

The version 0.0.8 can decompile X3 BOBs but the price is that you cannot no longer compile bod files into bobs.

This is just a temporary sollution until I will have time to fix it.

There are bout 4 files which will not decompile - you will receive error.

To decompile them, you must use the option The objects\ships\bodies\Raceship1.bob is one of them.

Example:

Great job as always!

Version 0.0.9 is out.

Can decompile all files without need for the x3bob flag.
Can compile all files.

Please re-read the readme and the extra_bob_data.txt. the second will tell you about data which are stored in BOB format but which are not supported by BOD format and how this can be overcomed.

You are the man DS..

The new version has reduced loadtime of new models to almost the same
as the original ES ones.
Great, great work!!


Note to endusers;
This version comes as a 7z file, you can get the decompressor here:

http://www.7-zip.org/

Moxy wrote:Note to endusers;
This version comes as a 7z file, you can get the decompressor here:

http://www.7-zip.org/

Also of note is that WinRAR will also extract from 7z format, so no need toget 7zip if you already have WinRAR.

Also of note is that WinRAR will also extract from 7z format, so no need toget 7zip if you already have WinRAR.

My Winrar didn't, but then again, I probably use version 1.0a.

Moxy wrote:My Winrar didn't, but then again, I probably use version 1.0a.

It helps to have version 3 or higher =]

When I open the command prompt to run this program (win xp sp2) I can't. Tried "run xb2c.exe" etc. Have tried the RUN command from the start button, but either way I cant get it to launch in the cli prompt.

I am a noob, anyone able to be give me some advice? Please?

Thanks!

okay, I now tried "start x2bc.exe" from the cli and I get this error about how the lib.dll (forget full name) file is missing. Its in the same dir as the x2bc.exe though.

kevonski wrote:okay, I now tried "start x2bc.exe" from the cli and I get this error about how the lib.dll (forget full name) file is missing. Its in the same dir as the x2bc.exe though.

You need the .lib files from the doubleshadow site. Download them and place them in your system directory or your application directory (whichever turns you on).


Step by step method:

1 - Start->Run->type "cmd" (no quotes) in the run box->OK. This opens the command prompt.

2 - In the command prompt, navigate to your X2BC directory (Example: I type "D:", press enter, then type "cd X2BC", press enter. My command prompt then says: "D:\X2BC>"

3 - Run the program.

3a - Decompile example: After having copied xenon_m1.bob to the X2BC directory (use windows and drag drop or whatever turns you on): I type "x2bc -d xenon_m1.bob" at the command prompt. This creates xenon_m1.bod

3b - Compile example: After making sure that the xenon_m1.bod file I want to work with is in the X2BC directory: I type "x2bc -c --bob xenon_m1.bod" at the command prompt. This creates xenon_m1.bob. Note the "--bob" after the "-c". Software needs an operator after "-c" to compile.

4 - Refference: Type x2bc -? and press enter at the command prompt in order to see the flags (the -c or -d type stuff) you can type at the command prompt.



IMPORTANT NOTE: This is command line software. It is NOT windowed software. This means that it talks to you and accepts commands from you through the command prompt ONLY. It does NOT open a GUI on the desktop to interface with it.

kevonski wrote:okay, I now tried "start x2bc.exe" from the cli and I get this error about how the lib.dll (forget full name) file is missing. Its in the same dir as the x2bc.exe though.

Instructions can be found here: http://www.xwiki.chaos.net.nz/index.php/X2BC

If you downlaoded the X2BC_1.0.9.7z (binary only) package, then all the required files are in there. If you downloaded the source package, then you need to move msvcr71.dll next to the x2bc.exe (or to a location listed in your PATH env. variable) as explained in the readme.

wrong one

Version 1.0.11 is out.

It has support for bump maps. You will need to re-export your bodies with DBOX 1.8 (or higher) and then re-compile with x2bc.

I am having problems recompling bod files.

I wanted to change the color of the minbari Sharlin so I decompiled the bob files and changed the color of the dds files it used, changed their names, adjusted the bod files acordingly, inserted the new textures into my mod and then attempted to compile the changed bod files into bob files but got an error saying "Type of input file notspecified"

I typed "x2bc -c minbari_c0.bod" Is this wrong? Have I screwed up somewhere or changed the bod files somehow when I saved them after using a text editor on them?

Try this:

Thanks Observe, worked a treat as usual

Hadhafang wrote:I am having problems recompling bod files...

I typed "x2bc -c minbari_c0.bod" Is this wrong?

Observe wrote:Try this:

Code: Select all

x2bc -c --bob "minbari_c0.bod" "minbari_c0.bob"

@Hadhafang - you have to specify the file type when compiling: body file (bob) or scene file (cut).

Run x2bc /? or x2bc --help to view all the options. (which applies to all other command line based programs as well).

Recompiling asteroid bodies with 1.0.11 is causing the models to lose their collision data.

The models work fine in game if they're used as .bod files, but compiling to .bob causes the in-game autopilot to stop avoiding them.

halo112358 wrote:Recompiling asteroid bodies with 1.0.11 is causing the models to lose their collision data.

The models work fine in game if they're used as .bod files, but compiling to .bob causes the in-game autopilot to stop avoiding them.

Yeah there is still one set of data which is a mystery to me. But as long as I have bumb maps I don't give a ... (you surely got the idea)

Collision data you say? That's a good start to decypher the stuff. I will look at it *sometime*.