DaBigBabes C ver.14: LCU bugs

[Yaab]

Unit 5503 - wrong name. The name right now is !/23rd FA Batallion.

Unit 5505 - US Corps HQ. The unit has devices, but no TOE.

Units 6444, 6452, 6453 - Indp Indian Bdes. No TOE.

[Symon]

ORIGINAL: Yaab
Unit 5503 - wrong name. The name right now is !/23rd FA Batallion.

Actually, it's the 1/23rd PS FA Bn. Just what name are you thinking of?

Unit 5505 - US Corps HQ. The unit has devices, but no TOE.

The game engine defaults to the LCU TOE in the absence of another pointer.

Units 6444, 6452, 6453 - Indp Indian Bdes. No TOE.

Actually they have pointers to 2845.

But thank you for your concerns.

[Yaab]

The FA Batallion is named ! (exclamation mark)/23. Do you see 1/23 or !/23? I have !/23 on Dec 7.

The HQ --- it says something like 1000/3000 in the LCU screen for active device/TOE percentage. When I click on the "Show unit TOE" I have blank space and no TOE. The other Corps HQ has the proper TOE.

Indian Bde --- have to recheck. They show as TOE ?2369 in Tracker.

[Symon]

We don't use Tracker. We don't care what Tracker says. Tracker is not the game engine. If you are getting an HQ "IN BABES" with 1000/3000 of something or other, for HQs, you are screwed. You are likely getting whacked by an engine instability. Turn OFF ALL your sidebar apps; Dump EVERYTHING to desktop; Restart from Desktop and see what you got.

I have been running for six years on the 'official' exe and michaelm's 'betas'. I think you people have "twisted" michaelm into making a nice, "accommodting", forum friendly, exes that break the bank. But you wouldn't know that, because you aren't there, are you?

Woof. JWE

[wdolson]

I wouldn't throw stones at Michael.

Of the work I've seen from him since release, most is fixing bugs, second is UI improvements to make the clicks a little less, and third are changes for Babes, like the stacking limits and the split torpedo tubes on subs. I may be missing something, but I can't think of any features added by request from the forum that aren't disabled if the supporting data changes aren't there.

Can you give me an example of something done for forum members that doesn't fall into one of the above three that broke the game? I know we recently discovered something in another thread that may be a recently introduced bug, but that's the only one I am aware of.

Bill

[witpqs]

ORIGINAL: Yaab

The FA Batallion is named ! (exclamation mark)/23. Do you see 1/23 or !/23? I have !/23 on Dec 7.

The HQ --- it says something like 1000/3000 in the LCU screen for active device/TOE percentage. When I click on the "Show unit TOE" I have blank space and no TOE. The other Corps HQ has the proper TOE.

Indian Bde --- have to recheck. They show as TOE ?2369 in Tracker.

Try using witploadAE to dump the scenario files to csv files, open the LCU one in a spreadsheet, then see what is there. BTW the scenario files that actually get loaded are the ones on the Japanese player's PC so make sure that you have the exact same files.

[Yaab]

This is what I have in my game

Using: DaBigBabes C, ver.14, latest beta, against Jap AI, 8 Dec 1941.

[Symon]

ORIGINAL: wdolson
I wouldn't throw stones at Michael.
<>
Bill

Bill,
Not throwing stones at michaelm at all. I think he is the hardest working and most diligent “Keeper” there is. Throwing stones at the entitlement mentality of the forum; representing less than 5% of the people who purchased and actively play the title.

As changes accumulate over time, however, I am seeing more and more reported instances of instability; more data incongruities, unit data changes, greater memory requirements, unit disappearance, incongruous combat results and movement.

This is certainly not michaelm’s fault. He has been incredibly helpful and innovative in establishing the ‘hooks’ that implement or data changes. Also, each of the features, tweaks, changes, fixes, taken in isolation, is reasonable and well executed. In the aggregate, however, there appears to be a growing cloud of unintended consequences, as manifested in bizarre instabilities that have never happened before and do not happen in early, or other, installations.

This is exactly in keeping with, and indeed was the impetus for, our conversations back in Sept/Oct. You do remember these, perhaps?

[Symon]

ORIGINAL: Yaab
This is what I have in my game.

#1 is a simple typo. ! instead of 1. Must have hit <shift> during typing. You can fix that yourself.

#2 is bizarre. I Corps was never edited in the past several years, and works fine for most folks. It looks like you slipped over the stability event horizon. It is fixable, but the fix implies a major look at the database and revisions for every unit with similar characteristics: characteristics that have worked correctly since 2009.

#3 has been poking people in the butt recently. Once again, this unit (and the others) was not edited in the past several years. The issue is a combination of data and the stability event horizon. It can be fixed by simply making 2845 the TOE ID. But the data fix implies a major look at the database and revisions for every unit with similar characteristics.

Don’t forget that no TOE in the TOE ID field means the engine uses the unit TOE as the basis; or at least that’s how it was supposed to work, and how it worked for the last five years. Seems like it has changed over time.

[Yaab]

#1 -fixed in the Editor

#2 -fixed in the Editor.

#3 - I am at a loss. Editor says the brigades use 2845 TOE ID.

EDiT: #1 works correctly. #3 works correctly only when the scenario is restarted. # 2 doesn't work neither in the continued campaign or new campaign. Damn!

[witpqs]

ORIGINAL: Yaab

#1 -fixed in the Editor

#2 -fixed in the Editor.

#3 - I am at a loss. Editor says the brigades use 2845 TOE ID.

Just guessing - look at that 2845 TOE and see if it is pointing at something wrong in your copy.

[Yaab]

Editor says the I Corps HQ should use TOE 2689. But location slot 2689 is empty...

Tracker has TOE slot 5512 for the other II Corps HQ. I will use this one and see what happens...

EDIT: I used slot 5505 for the Ist Corps instead. The TOE is derived from the units itself, since the unit ID is 5505. All corrections work ,albeit only with the restart. Another restart! Wargaming is hell!

[Symon]

Many people think Tracker is a defining application. It is not. Hate to tell ya, but the actual war in the Pacific didn't have much to do with Tracker.

Some people would rather play Tracker in the Pacific. That's cool. Just don't think it has relevance to anything.