DBEditor 1.96.3

[Jinarik]

Recently I gave the old DBEditor an update to 1.9 with some much needed updates to the CA pack list, an updated Schema from PietroMicca, as well as some cosmetic changes. Since, I've been working to update the tool for both Napoleon and Shogun 2. For Shogun 2 I've decided to basically rewrite the tool nearly from the ground up, however I've also been working on porting PFM 2.2's Napoleon schema into a working XSD, and updating DBE's code to handle the new schema. Today, it is finished.

First, a link to Chamber's DBEditor thread, http://www.twcenter.net/forums/showthread.php?t=280329 for an in-depth description of the program.

This program requires the .NET 3.5 Framework which can be found here http://www.microsoft.com/en-us/downl...ils.aspx?id=21

A word of warning though: with DBEditor 2.0 in the works and slated for compatibility with Empire, Napoleon, and Shogun 2 (and hopefully Rome 2!), any updates to this version will be limited to bug fixes for any bugs you throw my way (until 2.0 comes out).

Happy Modding!

Change Log:

1.96.1
- Removed extraneous code.
- Improved installation checking.

1.96.2
- Fixed Registry detection.
- Fixed Locate .exe dialog.

1.96.3
- Updated ability to save installation locations, added directories, and selected pack file.

[wangrin]

Thank you very much for having updated DBE

[coolgit]

How do i say this but i guess i'll just come out and say it....it won't work

Keeps on asking for my game installation even though i put the correct path upteems times.

Looked into the config file....you sure NET 3.5 or it says 4.0 in the config file

Tried putting the game path in config file (<value>my path</value>) and still wouldn't work.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at DBEditor.PackLoadingDialog.fillModListView()
at DBEditor.PackLoadingDialog.addDirectoryButton_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.269 (RTMGDR.030319-2600)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
DBEditor
Assembly Version: 1.9.0.0
Win32 Version: 1.9
CodeBase: file:///C:/Users//Downloads/DBEditor%201.95/DBEditor.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.278 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.282 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.269 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
Common
Assembly Version: 1.1.0.0
Win32 Version: 1.1.0.0
CodeBase: file:///C:/Users//Downloads/DBEditor%201.95/Common.DLL
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.233 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.237 (RTMGDR.030319-2300)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.233 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Xml.Linq
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.Linq.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

[Jinarik]

Did you select an installation in the new Combo Box here?

Spoiler Alert, click show to read: 

I suppose I should have given that thing a default Index of 0 and grayed out the Directory buttons if an install wasn't selected. As for .NET, I didn't use any 4.0 specific features, so it should work with 3.5, will force the 3.5 framework with a quick update to make sure since Windows XP doesn't support .NET 4.0.

1.96 uploaded to original post.

[Flikitos]

I have some issues with the new DBEditor, I can not launch that release:



Are every tables compatible with the NTW PFM tables (like the factions_table, the units_table? Cause it is a problem using tools like Symphony.

Anyway thanks for upgrading DBE.

[Jinarik]

Interesting, looks like the 1.96 zip file includes the debug file for common instead of the actual DLL, will fix that quick. As for the tables, they should be, I use a separate schema file for NTW and ETW, if something doesn't work let me know and I'll look into it.

Edit: Fixed download.

[Flikitos]

It works! Thanks!

[PietroMicca]

Le informazioni su come richiamare il debug JIT (Just-In-Time) anziché questa finestra
sono riportate in fondo al messaggio.

************** Testo dell'eccezione **************
System.ArgumentOutOfRangeException: InvalidArgument=Valore di '0' non valido per 'index'.
Nome parametro: index
   in System.Windows.Forms.ComboBox.ObjectCollection.get_Item(Int32 index)
   in DBEditor.PackLoadingDialog.GetDataPath(Int32 Index)
   in DBEditor.PackLoadingDialog.PackLoadingDialog_Shown(Object sender, EventArgs e)
   in System.Windows.Forms.Form.OnShown(EventArgs e)
   in System.Windows.Forms.Form.CallShownEvent()
   in System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
   in System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
   in System.Threading.ExecutionContext.runTryCode(Object userData)
   in System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
   in System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   in System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   in System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
   in System.Windows.Forms.Control.InvokeMarshaledCallbacks()


************** Assembly caricati **************
mscorlib
    Versione assembly: 2.0.0.0
    Versione Win32: 2.0.50727.5456 (Win7SP1GDR.050727-5400)
    Base di codice: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
DBEditor
    Versione assembly: 1.96.0.0
    Versione Win32: 1.96
    Base di codice: file:///D:/Guide%20e%20Manuali/DBEditor%201.96/DBEditor.exe
----------------------------------------
System.Windows.Forms
    Versione assembly: 2.0.0.0
    Versione Win32: 2.0.50727.5460 (Win7SP1GDR.050727-5400)
    Base di codice: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Versione assembly: 2.0.0.0
    Versione Win32: 2.0.50727.5456 (Win7SP1GDR.050727-5400)
    Base di codice: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Versione assembly: 2.0.0.0
    Versione Win32: 2.0.50727.5462 (Win7SP1GDR.050727-5400)
    Base di codice: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Common
    Versione assembly: 1.1.0.0
    Versione Win32: 1.1.0.0
    Base di codice: file:///D:/Guide%20e%20Manuali/DBEditor%201.96/Common.DLL
----------------------------------------
System.Windows.Forms.resources
    Versione assembly: 2.0.0.0
    Versione Win32: 2.0.50727.5420 (Win7SP1.050727-5400)
    Base di codice: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms.resources/2.0.0.0_it_b77a5c561934e089/System.Windows.Forms.resources.dll
----------------------------------------
System.Core
    Versione assembly: 3.5.0.0
    Versione Win32: 3.5.30729.5420 built by: Win7SP1
    Base di codice: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Data
    Versione assembly: 2.0.0.0
    Versione Win32: 2.0.50727.5420 (Win7SP1.050727-5400)
    Base di codice: file:///C:/Windows/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Xml
    Versione assembly: 2.0.0.0
    Versione Win32: 2.0.50727.5420 (Win7SP1.050727-5400)
    Base di codice: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Xml.Linq
    Versione assembly: 3.5.0.0
    Versione Win32: 3.5.30729.5420 built by: Win7SP1
    Base di codice: file:///C:/Windows/assembly/GAC_MSIL/System.Xml.Linq/3.5.0.0__b77a5c561934e089/System.Xml.Linq.dll
----------------------------------------
System.Configuration
    Versione assembly: 2.0.0.0
    Versione Win32: 2.0.50727.5420 (Win7SP1.050727-5400)
    Base di codice: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
mscorlib.resources
    Versione assembly: 2.0.0.0
    Versione Win32: 2.0.50727.5456 (Win7SP1GDR.050727-5400)
    Base di codice: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------

************** Debug JIT **************
Per attivare il debug JIT, è necessario impostare il valore
jitDebugging nella sezione system.windows.forms del file di configurazione
dell'applicazione o del computer (machine.config).
L'applicazione inoltre deve essere compilata con il debug
attivato.

Ad esempio:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

Quando il debug JIT è attivato, tutte le eccezioni non gestite
vengono inviate al debugger JIT registrato nel computer,
anziché essere gestite da questa finestra di dialogo.

my packs are not in C:
I cannot select the correct folder

[Jinarik]

Interesting, you got caught on some extraneous code I left in, which should have a 100% success rate. Alright, I've cleaned up the code a little and looked through the error catching blocks to make sure they are up to shape. Try 1.96.1.

Edit: OK, after a quick update 1.96.1 will actually load now.

[PietroMicca]

Le informazioni su come richiamare il debug JIT (Just-In-Time) anziché questa finestra
sono riportate in fondo al messaggio.

************** Testo dell'eccezione **************
System.NullReferenceException: Riferimento a un oggetto non impostato su un'istanza di oggetto.
   in DBEditor.PackLoadingDialog.DetectedInstallscombBox_SelectedIndexChanged(Object sender, EventArgs e)
   in System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
   in System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
   in System.Windows.Forms.ComboBox.WndProc(Message& m)
   in System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   in System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   in System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Assembly caricati **************
mscorlib
    Versione assembly: 2.0.0.0
    Versione Win32: 2.0.50727.5456 (Win7SP1GDR.050727-5400)
    Base di codice: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
DBEditor
    Versione assembly: 1.96.1.0
    Versione Win32: 1.96.1
    Base di codice: file:///D:/Guide%20e%20Manuali/DBEditor_1.96.1/DBEditor.exe
----------------------------------------
System.Windows.Forms
    Versione assembly: 2.0.0.0
    Versione Win32: 2.0.50727.5460 (Win7SP1GDR.050727-5400)
    Base di codice: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Versione assembly: 2.0.0.0
    Versione Win32: 2.0.50727.5456 (Win7SP1GDR.050727-5400)
    Base di codice: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Versione assembly: 2.0.0.0
    Versione Win32: 2.0.50727.5462 (Win7SP1GDR.050727-5400)
    Base di codice: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Common
    Versione assembly: 1.1.0.0
    Versione Win32: 1.1.0.0
    Base di codice: file:///D:/Guide%20e%20Manuali/DBEditor_1.96.1/Common.DLL
----------------------------------------
System.Windows.Forms.resources
    Versione assembly: 2.0.0.0
    Versione Win32: 2.0.50727.5420 (Win7SP1.050727-5400)
    Base di codice: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms.resources/2.0.0.0_it_b77a5c561934e089/System.Windows.Forms.resources.dll
----------------------------------------
System.Core
    Versione assembly: 3.5.0.0
    Versione Win32: 3.5.30729.5420 built by: Win7SP1
    Base di codice: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Data
    Versione assembly: 2.0.0.0
    Versione Win32: 2.0.50727.5420 (Win7SP1.050727-5400)
    Base di codice: file:///C:/Windows/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Xml
    Versione assembly: 2.0.0.0
    Versione Win32: 2.0.50727.5420 (Win7SP1.050727-5400)
    Base di codice: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Xml.Linq
    Versione assembly: 3.5.0.0
    Versione Win32: 3.5.30729.5420 built by: Win7SP1
    Base di codice: file:///C:/Windows/assembly/GAC_MSIL/System.Xml.Linq/3.5.0.0__b77a5c561934e089/System.Xml.Linq.dll
----------------------------------------
System.Configuration
    Versione assembly: 2.0.0.0
    Versione Win32: 2.0.50727.5420 (Win7SP1.050727-5400)
    Base di codice: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
mscorlib.resources
    Versione assembly: 2.0.0.0
    Versione Win32: 2.0.50727.5456 (Win7SP1GDR.050727-5400)
    Base di codice: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------

************** Debug JIT **************
Per attivare il debug JIT, è necessario impostare il valore
jitDebugging nella sezione system.windows.forms del file di configurazione
dell'applicazione o del computer (machine.config).
L'applicazione inoltre deve essere compilata con il debug
attivato.

Ad esempio:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

Quando il debug JIT è attivato, tutte le eccezioni non gestite
vengono inviate al debugger JIT registrato nel computer,
anziché essere gestite da questa finestra di dialogo.

no path in combo box

[Jinarik]

Okay, I think I've figured out your problem. It looks like you don't have any registry entries for Empire or Napoleon, if you can check, they should be located at "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Steam App #####" 10500/10600 for ETW, and 34030 for NTW. I've patched the issue and will put up an updated version in the original post as always, look for 1.96.2.

[PietroMicca]

now it works

[Flikitos]

Hey Jinarik, I have a question about the DBEditor.

So as to create a new battlefield building we need to modify a db table called "models_building_tables" so as to do it we need to use jruby and the command prompt in order to extract, uncompile and compile that.

It is really an annoying process, so may be it would be possible to add that table in the next release, what do you think?

[daniu]

So as to create a new battlefield building we need to modify a db table called "models_building_tables" so as to do it we need to use jruby and the command prompt in order to extract, uncompile and compile that.

It is really an annoying process, so may be it would be possible to add that table in the next release, what do you think?

battlefield_buildings are special db tables which can contain other entries. The DB editor is currently only capable of displaying a single row for each entry.
I'm currently working on integrating a building model editor in PFM; a specialized version is pretty straightforward, but a general one (allowing for several levels of contained entries and a flexible number of values in each row) very challenging.
The specialized will work fine for the battlefield buildings for now, but the same problem arises for naval models which are way more complex, and if Rome II uses a similar scheme, it would be great if we could easily update it.

If anyone has a good idea on how to display this kind of thing, let me know.

EDIT:
I think a tree view might work, somewhat like the ESF editor. You'd only be able to work on a single "row" at a time, but I'd guess that's what you do anyway when messing with the building models table?

[panzerschreck]

battlefield_buildings are special db tables which can contain other entries. The DB editor is currently only capable of displaying a single row for each entry.
I'm currently working on integrating a building model editor in PFM; a specialized version is pretty straightforward, but a general one (allowing for several levels of contained entries and a flexible number of values in each row) very challenging.
The specialized will work fine for the battlefield buildings for now, but the same problem arises for naval models which are way more complex, and if Rome II uses a similar scheme, it would be great if we could easily update it.

If anyone has a good idea on how to display this kind of thing, let me know.

EDIT:
I think a tree view might work, somewhat like the ESF editor. You'd only be able to work on a single "row" at a time, but I'd guess that's what you do anyway when messing with the building models table?

That's a great news, I hope that you will manage to do it! We have a lot to do too with the cs2.parsed that remains a mystery.
There is a great challenge with these 2 problems: make total conversions more easier to do, especially for the buildings.

[Jinarik]

At the moment, I'm just trying to get DBEditor updated for use with Shogun 2, so still playing catch up, though it is coming along nicely. As for the models_buildings_tables, you guys make it sound like each entry is a collection of collections, as in a List<List<model_entry>>, or at least each entry may or may not contain a collection that can be a different size for each entry, am I understanding correctly?

[daniu]

As for the models_buildings_tables, you guys make it sound like each entry is a collection of collections, as in a List<List<model_entry>>, or at least each entry may or may not contain a collection that can be a different size for each entry, am I understanding correctly?

Yes, that is correct.
Each row contains a List<ModelEntry> which can be empty or have any amount of items.

[gameroach81]

What can i do with this? Can i change turns per year or change diplomacy relationships etc?

if so, can you help me do it please..

[Jinarik]

The DBEditor allows you to edit most of the information contained within the db file tables in the *.pack files. There is a pretty gargantuan amount of information in them, so explaining everything that can be done would be quite the task (even if I knew it all). Most people use it to change or add new units, modify building effect, mess with technology, etc. I wrote a tutorial on the program that can be found HERE.

Turns per year, as well as starting diplomatic states are contained within the startpos.esf, EasyESF would be your best bet to mess with those, though DBEditor will allow you to change the penalties and bonuses of diplomatic actions (breaking alliance, war, etc). There a large amount of information in the mod workshop forums for ETW and NTW, check them out.

The Pack File Manager over in the Shogun 2 forum also is backwards compatible with both ETW and NTW, and is another excellent tool. Happy Modding!

[Jinarik]

Yes, that is correct.
Each row contains a List<ModelEntry> which can be empty or have any amount of items.

Hmm, a Tree view like the PFM would seem to be the optimal solution to displaying that. I suppose I could write a mini user control that could either be opened in a new window or simply stuffed into the appropriate cell in the table (ala the current combo boxes) might work for the DBEditor, but would neither look good, nor be very user friendly. Either way, it's going to be a pain to figure out and code, thankfully taw has that converter so no need to start with a hex editor!