WORKAROUND to CAG-bug (CAG with insane combat stats)

[Long Lance]

The discussion in the thread NO workaround to CAG-max firing range bug finally led to workraound in this point.

Not for the CAG combat range, this was fixed to the Carrier model. But upgrading for CAGs is possible (-> correct Grahpics) without getting insane combat stats like 400 km striking range etc., because alls of their stats were set to zero and are added directly to the specific CV-model.

Also for every new CV techlevel reserached, combat stats for CVs are increased, so that older CV-models also improve over time. These values need perhaps a little fine tuning.

Disadvantage of the workaround are besides the fixed combat range, that the new combat stats after a new CV-Tech is researched only become valid to deployed CVs when one country annexes another. This is due to errors in the coding of DDA, which presumably also causes the naval brigades mess - but that's another story.

Perhaps give it a try, Borsook kindly offered web space do download it here

 

[DrinkingHeavily]

You could integrate the HSR workaround..

The upgrade event utilizes two off-map territories.. one rebels a la partisans and forms a new nation, the other annexes the new rebel nation.

 

[DrinkingHeavily]

Or, combine the off-map annexation with another option resulting from a long thread on this forum.

What if the actual CV hulls are mapped to the battlecruiser tech slots, and only the CAG's are upgraded with the CV tech slots?

That way, you can have a use for your BC tech slots (I've never researched BC for any nation) and CAG's could have separate strength/org combat.

Doesn't it seem a bit of overkill to claim there's 9 different classes of *ships* when for many of those tech slots, only the CAG stats are changing?

Sure, this will create a long list of additional things to debug, but I haven't seen it discussed before.

 

[Long Lance]

You could integrate the HSR workaround..

The upgrade event utilizes two off-map territories.. one rebels a la partisans and forms a new nation, the other annexes the new rebel nation.

That's a good idea. To be found onthe HSR-page methinks. Gonna look for it.

Regardings CAG-upgrades: AFAIK, after every upgrade of CAGs, they get another increase of their combat stats upon annexation. This is why I think the idea of reaerching CAGs seperately is no help to the CAG-bug, although a worthwile idea. This is also why I set their stats to 0.

 

[unmerged(74599)]

Well I think its really cool that you went through all the trouble to try and fix this thing. Looks good on you.

One question, does the workaround work with existing games or do you have to start fresh?

 

[Long Lance]

Well I think its really cool that you went through all the trouble to try and fix this thing. Looks good on you.

One question, does the workaround work with existing games or do you have to start fresh?

Sorry, but you'd need to start a new game.

 

[Long Lance]

@Drinking heavily: Where can this event be found exactly? Didn't find it on the HSR-site and not in the HSR2.08 events

 

[unmerged(74599)]

That is what I thought. I'll let you know any playtesting results, when I get a chance to try it out.

 

[unmerged(11893)]

Does the "official" DDA hotfix not fix the CAG bug? I ask, because I am trying to decide if it is worth it for me to upgrade to DDA or not . . .

 

[Long Lance]

Does the "official" DDA hotfix not fix the CAG bug? I ask, because I am trying to decide if it is worth it for me to upgrade to DDA or not . . .

Nope. But for 5 bucks, IMHO it's worth to upgrade anyway. It has some bugs, but it's playable, and the patch shouldn't be away too long.

 

[Long Lance]

Regarding the annex/release event, I wrote on where Panama does this with Costa Rica. After some playtesting and in case someone is interested, I would 'publish' it.

But perhaps finally DDA 1.1 will be out and hopefully not require new workarounds for new bugs

 

[Myth]

Nope. But for 5 bucks, IMHO it's worth to upgrade anyway. It has some bugs, but it's playable, and the patch shouldn't be away too long.

well, to be precise, its playable with the workaround or if naval warfare is irrelevant to your game...and we hope the patch isn't too far away. we don't know anything for certain yet

 

[unmerged(57311)]

Good job

Congratulations, now I can play DD. Really good job and thank you!
Only thing I found and might be problematic is that in the zip file carrier.txt is in the brigades folder and it should be in the divisions folder. So it might be a bit messy for those who just unzip them to their dd folder.

 

[Borsook]

Congratulations, now I can play DD. Really good job and thank you!
Only thing I found and might be problematic is that in the zip file carrier.txt is in the brigades folder and it should be in the divisions folder. So it might be a bit messy for those who just unzip them to their dd folder.

Ok, the file is now in Divisions folder.

 

[Long Lance]

Thanks for the info and sorry, that was my mistake!

Thanks for fixing it, Borsook!

 

[unmerged(11893)]

Not for the CAG combat range, this was fixed to the Carrier model. But upgrading for CAGs is possible (-> correct Grahpics) without getting insane combat stats like 400 km striking range etc., because alls of their stats were set to zero and are added directly to the specific CV-model.

Now I'm confused . . . A 400 km (215 nm) striking range is about normal for a 1943-1945 carrier air group . . . why is that a bug?

 

[unmerged(74599)]

We aren't talking about 400 km range in 1943, we are talking about 400 km range in 1941.

That's not the problem. The problem is that it doesn't work the way its supposed to work. What happens is that ships built in 1938 end up having higher attack stats and attack range than ship built in 1941. Your brand new 1945 carriers end up being mauled by the 1938 issue Japanese ships, because the upgrades multiply in the wrong way.

 

[Long Lance]

That is what I thought. I'll let you know any playtesting results, when I get a chance to try it out.

Sorry, I somehow read over this. Of course I'd be interested about your experience!

EDIT: Btw, perhaps just try it with an old game, perhaps it works, or works after the stats are updated upon annexation? But I'm not sure...

Please beware that the first 'release' of this workaround had an error in, carrier.txt was to be found mistakenly in db\units\brigades, not in db\units\divisions, as it should have been.

 

[Long Lance]

Workaround to CAG-Bug refined!

To be more precise, I finally managed to write an event where one country is periodically annexed and then liberated. I chose Dom. Repulic and Haiti, because both countries are not very important in terms of HoI, rarely (if at all) attacked and somehow isolated on a common island.

EDIT this sentence (wrote BS):
Starting in 1940, every 90 days HAI is annexed by DOM and released some weeks afterwards.

(Btw it took beer, sweat and tears to realize that an event may kill itself if fired too early ).

To install it, you should copy and paste the bold lines to your Hoi2.txt in the db\events folder. I playtested it handsoff for several years (in game terms ), it sems to work fine and not to provoke dows on HAI.

Enjoy!

#########################################################################
#Persistent Annex events by Long Lance - Fix Annex and Fix liberate
#########################################################################


event = {
id = 9999991
random = no
country = DOM
persistent = yes

#trigger = { random = 99}


name = "Fix Annex"
desc = "Fix Annex"
style = 0

date = { day = 1 month = january year = 1940}
offset = 90
deathdate = { day = 30 month = december year = 1964 }

action_a = {
name = "Fix Annex"


command = { type = inherit which = HAI}
#command = { type = trigger which = 9999992 }

}



}
event = {

id = 9999992
country = DOM
persistent = yes
name = "Fix Liberate"
desc = "Fix Liberate"
style = 0

date = { day = 1 month = january year = 1940 }
offset = 40
deathdate = { day = 30 month = december year = 1964 }

trigger = { not = { exists = HAI }}

action_a = {
name = "Liberate"
command = { type = independence which = HAI }#value = 1 }
command = { type = dissent value = -5 }
command = { type = belligerence value = -5 }
}

}


Btw, I'l start a seperate thread about these evvents, this could be interesting also to gamers that don't care about the CAG-bug workaround.

 

[unmerged(57311)]

Great job, thanks.
I'll use it and tell you if I find anything odd.