Corrupt save games?

[NomadicStorm]

Hi there, I've got a bit of a problem here.

Game Version & Patch (incl. publisher): Doomsday, v1.3 (publisher?)

OS & build/SP: Win XP, SP2

Computer, CPU & speed: Intel Core2 Quad 2.4ghz

RAM: 2gb DDR2

Free HDD space: 3,79 gb

Video (brand, model, driver, memory): Nvidia GeForce 8600GT, driver version 6.14.11.5827, 512 mb

Sound (brand, model, driver): Realtek HD Audio, driver version 5.1.2535.0

DirectX Version: 9

Other: Depends on what you're asking for.

I read the stickies but I still have the following problem:

Right. So, I've been playing HOI2 for quite a while now, but have never really gotten past 1945, always got sick of it prior to that. It's worked perfectly fine for me until now, as well.

I've modified Sweden, giving it a bit of extra IC so it could pose a marginal threat towards the super-powers. So I'm playing as Sweden, and used the German-Soviet conflict to march down to Berlin via Denmark, finally annexing it. Then I turned my attention to the Soviets, after letting them assemble their forces in the east towards nationalist china. I've conquered them as well now, finished yesterday evening, and saved my game, then went to bed. Everything worked fine. And now when I woke up this morning and started it up, I get an error message when I try loading the game. Looks sort of like this:



I've tried three separate savegames, namely Sibirian sun (mine), autosave and oldautosave. I get the same type of error with each one, except with oldautosave I get "motorized" instead of "infantry".

Older savegames work perfectly fine, but I really don't feel like re-doing the last year and my march through the Soviet Union.

Is there anything I can do about this? I tried checking out the line implicated in the error message using notepad, but it lands at a completely different line. Says nothing about infantry. So then I tried searching for "infantry = {" in the document, and then replaced the value after it with a value from a previous savegame, and saved it as a new file. When I loaded it up (Sibirian sun2), it gave me a new error with another model, this time "armor".

So, to sum things up, because I suspect I've been rambling;
My newer savegames stopped working, even though there were no errors while playing yesterday.

Thanks in advance for any assistance you might offer.

 

[coreymas]

This is a modding issue and not a tech support one....

Please post your question there. You will get a faster response.

Corey

 

[NomadicStorm]

Sorry, I wasn't aware of the fact that my initial modification made it a modding issue, seeing as it worked perfectly fine until that point. The modding itself has, from what I can tell, not caused any difficulties, seeing as I was able to play up until 1946 without any problems whatsoever. The modding itself consisted only of adding extra IC in the northern provinces of Sweden via the scenario editor.

If this was caused by the modding, then why do all my savegames up until 1946 function correctly?

 

[blue emu]

That's a very odd error, since model = 6 is not, in fact, illegal... it exists. It's the Modern Infantry Division.

Check the contents of your /db/tech/infantry_tech.txt file to maker sure that the Modern Infantry entry looks like this:

  # Modern Infantry Division
  application =
  { id        = 10000
    name      = TECH_APP_INFANTRY_50_NAME
    desc      = TECH_APP_INFANTRY_50_DESC
    position  = { x = 25 y = 145 }
    year      = 1947
    # ?
    component = { id = 10001 name = TECH_CMP_INFANTRY_50_1_NAME type = general_equipment difficulty = 6 }
    # ?
    component = { id = 10002 name = TECH_CMP_INFANTRY_50_2_NAME type = artillery difficulty = 6 }
    # ?
    component = { id = 10003 name = TECH_CMP_INFANTRY_50_3_NAME type = electronics difficulty = 6 }
    # ?
    component = { id = 10004 name = TECH_CMP_INFANTRY_50_4_NAME type = rocketry difficulty = 6 }
    # ?
    component = { id = 10005 name = TECH_CMP_INFANTRY_50_5_NAME type = training difficulty = 6 }
    required  = { 1060 }
    effects =
    { command = { type = new_model which = infantry value = 6 }
      command = { type = scrap_model which = infantry value = 5 }
      command = { type = new_model which = militia value = 2 }
      command = { type = scrap_model which = militia value = 1 }
      command = { type = new_model which = garrison value = 3 }
      command = { type = scrap_model which = garrison value = 2 }
    }
  }

... and the contents of your /db/units/divisions/infantry.txt file to make sure that the entry for model 6 looks like this:

# Modern Infantry Division (1947) - 7
model = {
	cost 					= 7
	buildtime	 			= 95
	manpower 				= 10
	maxspeed 				= 6
	defaultorganisation 	= 30
	morale					= 30
	defensiveness 			= 40
	toughness				= 35
	softness				= 100
	suppression				= 2
	airdefence				= 7
	softattack				= 22
	hardattack				= 7
	airattack				= 7
	transportweight			= 10
	supplyconsumption 		= 1.1
	fuelconsumption			= 0.1
	speed_cap_art			= 7
	speed_cap_eng			= 7
	speed_cap_at			= 7
	speed_cap_aa			= 7
	upgrade_time_factor = 0.5
	upgrade_cost_factor = 1.0
}

 

[NomadicStorm]

That's a very odd error, since model = 6 is not, in fact, illegal... it exists. It's the Modern Infantry Division.
... and the contents of your /db/units/divisions/infantry.txt file to make sure that the entry for model 6 looks like this:

# Modern Infantry Division (1947) - 7
model = {
	cost 					= 7
	buildtime	 			= 95
	manpower 				= 10
	maxspeed 				= 6
	defaultorganisation 	= 30
	morale					= 30
	defensiveness 			= 40
	toughness				= 35
	softness				= 100
	suppression				= 2
	airdefence				= 7
	softattack				= 22
	hardattack				= 7
	airattack				= 7
	transportweight			= 10
	supplyconsumption 		= 1.1
	fuelconsumption			= 0.1
	speed_cap_art			= 7
	speed_cap_eng			= 7
	speed_cap_at			= 7
	speed_cap_aa			= 7
	upgrade_time_factor = 0.5
	upgrade_cost_factor = 1.0
}

I think that's the problem right there. It stops at semimodern infantry, then the text file ends. Same with all the other unit types. Faulty installation? I'll re-install and see if that fixes it.

Thanks!

 

[blue emu]

If you are playing with a mod, it's entirely possible that the save-game is for a more advanced version, and the mod for a less advanced version of the game. I can't tell from what you've posted... but this would cause exactly the symptoms that you've reported: units in the game with model-numbers not supported by your data-files.