Normally you don't have to set the budget. the budget will be calculated at the start of the career, so if you have created the team with a normal amount of riders and correct contracts, then everything should be fine when starting a career.
The budget can be changed with either editor after the career has started. But you have to edit the save, editing the DB has no effect at all.
Lachi is right. The budget is calculated at the start of each season, depending on your riders and their wages. This means that the budget can only be altered in the save game, not the database.
The problem is that the team does not appear in game.
The edited database does, but the 'added' team isn't in it. Do you need to add a minimum number of riders to the team? Perhaps that's the issue, since I didn't add any at all.
if you make a new team, you need at least 12 riders in it.
Also, if you want to race a stage race, you must:
- click on corse - anagrafica (tabs)
- choose a race you want to play
- on the right side, you have option to edit that race
- you must click on Vai a Inviti (Mod. Singolo) and there add your own team in
- DON'T forget to SAVE your .cdb
Edited by KlemenPipic on 15-08-2008 12:44
How do I fix the problem that whenever I open a DB, is says Unhandled exception:
ee the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.BadImageFormatException: Could not load file or assembly 'CDBParse, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format.
File name: 'CDBParse, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'
at AccessDB.AccessDB.LoadDB(String PathFile)
at ClEditor.frmMain.btnLoad_Click(Object sender, EventArgs e) in C:\Users\marco\Documents\Visual Studio 2005\Projects\ClEditor\ClEditor\frmMain.cs:line 59
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(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)
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
************** 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.
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.
I changed the budget with Hannes converter last year and did it this year too.
But I havent tested it really this year, only buying a few equipment with my new-stolen cash - and that worked ok.
