I was going through the files generated by WITPload while getting ready to start working on my own personal mod and noticed these "new" values...

Sec_Attr Sec_Eff Sec_Pen Sec_Acc

I know that they have something to do with the new values for AA guns that was implemented with BigBabes, but beyond that don't have a bunch of information.

What do these control?

What are reasonable values if I want the devices to work well with BigBabes devices in the file already (ie how were the generated if possible)?

Please let me know if there is any other information that you need, and thank you in advance for your help.

Yes. This was something that michaelm did in support of the Babes AA tweaks. It's a bit complex, but once understood, perhaps helpful.

There's some attributes that need to be set and and some understanding of Nav v AA for DP Guns and AA Guns. Would take pages of text if I tried to explain it here, and the usual suspects would howl in outrage, so if you are really interested, send me a pm, and I'll send you the stats. Of course, you are free to post anything sent to you.

Ok, Mate. Responded to your pm. I think everything in it is ok for you to post if you want. Nothing violates the NDA. I would be very judicious about showing the spreadsheet, though. As you can imagine, there's a lot of room for misinterpretation without an understanding of the last 2 years of development work. But, as I said in my initial post, your call, Mate.

Given your examination of the csv files, I expect you may have found some other land mines. In the Class file, there's a MaxDiveDepth in column AD that tweaks the ASW code. That one is highly interactive with a particular device file and is NOT used for any release version of Babes or Stock. It only exists in short, small map, tactical, Babes scenarios with special device files and restrictive rules for sub ops.

That's about it. Further questions accepted by pm, and will be answered. Ciao, JWE

Ok, Mate. Responded to your pm. I think everything in it is ok for you to post if you want. Nothing violates the NDA. I would be very judicious about showing the spreadsheet, though. As you can imagine, there's a lot of room for misinterpretation without an understanding of the last 2 years of development work. But, as I said in my initial post, your call, Mate.

Given your examination of the csv files, I expect you may have found some other land mines. In the Class file, there's a MaxDiveDepth in column AD that tweaks the ASW code. That one is highly interactive with a particular device file and is NOT used for any release version of Babes or Stock. It only exists in short, small map, tactical, Babes scenarios with special device files and restrictive rules for sub ops.

That's about it. Further questions accepted by pm, and will be answered. Ciao, JWE

Hmm ... (putting on best deerstalker hat and cape whilst picking up a violin) ...

Would the somewhat mysterious spreadsheet referred to above be the same as that provided in post #17 of this thread?

Nope, not that one. And Nope, the dog didn't bark. Spreadsheet isn't mysterious and it doesn't violate any NDAs, it's just old and uses some language in some of the explanation fields that might cause misunderstanding vapors. It's on how we did the calcs for the Sec_ values.

I have an open-door policy for Babes, but I prefer the door to swing for the serious modding community. Openly posting some things just annoys and iritates the usual suspects and leads to a plethora of "well, 'my' website says ...." I'm sure you know exactly what I mean.

I'll be glad to send you a copy, along with the explanations I sent to Mate. There's no magic, and nothing up my sleeve. Just want to keep some distance from the latrine.

"wiptload" has been updated to allow the setting of the LCU Ops Mode (currently all are in Combat). The new version is 9.0 and can be found in the latest beta (1123) in the beta directory. Additionally, a new CSV is created from the 'cam' file which allows you to set how much HI/MP/OIL is used to train a Japanese pilot (if production on).

ORIGINAL: michaelm "wiptload" has been updated to allow the setting of the LCU Ops Mode (currently all are in Combat). The new version is 9.0 and can be found in the latest beta (1123) in the beta directory.

Thank you!

One question - what values are to be entered in the LCUopMode column for the different op modes?

Checked the readme and what's new, but found nothing.

Edit: Just made a test with the most likely values: 0 is combat, 1 is move, 2 is strategic move, 3 is reserve (no pursuit). Not tested yet but I guess 4 is either reserve (pursuit) or rest.

ORIGINAL: michaelm "wiptload" has been updated to allow the setting of the LCU Ops Mode (currently all are in Combat). The new version is 9.0 and can be found in the latest beta (1123) in the beta directory.

Thank you!

One question - what values are to be entered in the LCUopMode column for the different op modes?

Checked the readme and what's new, but found nothing.

Edit: Just made a test with the most likely values: 0 is combat, 1 is move, 2 is strategic move, 3 is reserve (no pursuit). Not tested yet but I guess 4 is either reserve (pursuit) or rest.

Am happily modding along on my "quickstart" scenario with the new LCU Ops Mode option. But I noticed something strange: When loading my mod after a fresh start of WitP, the scenario loading process is unusually fast and all the LCUs I have modded to move or strategic move ops mode are set to move EAST without exception - although the dest coordinates and dest hexes point to other directions. I double-checked the values I have entered in the editor and then reloaded the scenario - this time the loading process took more time and everything was fine. It is repeatable - after each fresh start of WitP, the first scenario load is quick and has the move directions pointed East, closing and reloading the scenario takes more time but the mod is WAD. No big issue, just mildly irritating.

Follow up: Does not matter whether movement mode is set to "strat" or "move" - affected units keep taking wrong directions. However, if I change the destination for 25th MG Bn and 12th RAAF Base Force to Perth, they hop on the trains and go to Perth just fine. Pains me to tell you, but it seems that Perth has more lure than Sydney...

Just fire up any GC Scenario, and check 417 Battambang with Guards Division, and friends (actually the only units I know, that have movement orders set). They always march into jungle, not by roads, and they do not fix it after turn run.