Matrix Games Forums

As a new player I just wanted to chime in and give thanks for the continued support of the game. It makes recommending the game to friends so much easier when the devs obviously care about the game and community.

Per this thread I started:

VS Squadrons disband 2 months before VB's resize?

and this previous thread:

VS-8 Where are you??

All of the VS squadrons are *AUTOMATICALLY* disbanding on January 1st, 1943. I am playing agains the AI, in Scen 1 using the latest beta patches. From what I can gather, this is *not* intended. Instead, they should disband on March 1st, the same time the VB's resize. In my game, I still have every single VS squadron, and every single one *AUTOMATICALLY* disbanded on January 1st - I had no choice in it.

Let me know if you need a save or anything. But its pretty obvious - just fire up any game and the VS squadrons say under the reszie line 'Disbanding Jan 1943'. I checked in the editor and could not see why it was happening. Something coded deeper?

Thanks

Chad

The disbanding and resizing happens whenever the correct conditions are met.
The date this happens is controlled by data, not code.

Looking at scenario 1, the VS group doesn't have a re-size setting which causes a default sizing template, based on original WITP which had disbanding starting from Jan 43. This template is copied into the starting data for the game.
The VB group on the other hand does have a defined re-size setting (Mar 43) so doesn't use the default template.

I'll move the default template to use Mar 43 as the default for VS groups, but the original intent was that the code would not set these values. When I removed the template in the first patch, most scenarios failed as the re-size data hadn't been entered into the data. So it was left in as a fallback.

For proper use, the VS should have a re-size in 4303 of '0' to force it to disband.

Sounds good Michael. Thanks for all your hard work.

Michael,
CannonFodder discovered this beta bug about Pilot Training HI use. tm.asp?m=3253721

At the end of month it appears that no HI is used for Pilot training.

I tested under a full scenario and found the same, files attached.

Also zipping two files under the beta takes it above the 5000kb, can this be enlarged?
File #1

File #2

Found it. I put the values into the wrong array in build 1110.
Next build will set the default values if not set, and put starting values in right place.
Silly mistake.[:@]

Your just a Japanese fanboy Michaelm, admit!!!!!

Outstanding support!
Thank you very much [:)]

I think the 'Confirm upgrade button', bottom left, missing from ship upgrade screen. I did say think as I might be thinking of a similar button on the ship convertion screen. The upgrade does take place. Latest patch but might be 1123.

Is there a chance we could get the "*" behind the AA devices for ships also on the update screens for that ship?

And could the current Version be show there too? Would make comparing easier because one could simply switch forth and back.

ORIGINAL: Chris H

I think the 'Confirm upgrade button', bottom left, missing from ship upgrade screen. I did say think as I might be thinking of a similar button on the ship convertion screen. The upgrade does take place. Latest patch but might be 1123.

The "Upgrade .. Yes/No" button is on the main screen of the ship, not the upgrades.

ORIGINAL: BigDuke66

Is there a chance we could get the "*" behind the AA devices for ships also on the update screens for that ship?

Should be there. Must have missed it

And could the current Version be show there too? Would make comparing easier because one could simply switch forth and back.

Not possible to show 2 screens with way it is configured

ORIGINAL: michaelm

ORIGINAL: Chris H

I think the 'Confirm upgrade button', bottom left, missing from ship upgrade screen. I did say think as I might be thinking of a similar button on the ship convertion screen. The upgrade does take place. Latest patch but might be 1123.

The "Upgrade .. Yes/No" button is on the main screen of the ship, not the upgrades.

Thanks, just getting confused in my old age.

@michaelm
Thanks.
Regarding the upgrade screen, I don't want to show 2 screens at the same time but have the current layout of the ship also as a page under upgrades.

Michaelm, never-mind had a senior moment (I almost said disr...rd but did not want to start that again)
Thanks daryl

Made the same mistake, latest version is in the first post.

lol thanks time for some coffee!

ORIGINAL: BigDuke66

Made the same mistake, latest version is in the first post.

Michael,

A report on the reconfiguration of the USN carrier dive bomber squadrons circa March 1, '43. You made changes/fixes to this since the last time I had a game get to that point, so I wasn't sure what to expect. I had two different set ups, and one of them went well while the other went poorly.

Set up 1) Before the fateful day, some carriers had their dive bomber squadrons moved to bases. In all cases, the two squadrons from each carrier were together at the same base. When the orders phase for March 1 arrived, in all cases the two squadrons had combined, both planes and pilots. This was splendid!

Set up 2) Some carriers still had their DB on board. As of March 1st orders, nothing had happened.

2a) I transferred the two squadrons to a land base. 'Disband' was 'not allowed', but 'Withdraw' combined the two, planes and pilots.

2b) I transferred the two squadrons to a land base. But, the squadron due to withdraw left behind a 1-plane fragment that was undergoing maintenance. Both 'Disband' and 'Withdraw' buttons are not available for either the parent or the fragment of that group, which is due to withdraw. It looks like I will take a PP hit on that group.

Is this working as intended? It would be an improvement if the squadrons on board a carrier also automatically combined just like the ones at a land base do.

The default settings I changed only affect a new game started with 1123 - the dates are set in the data. Was this a new game or a continuing one?

The groups should re-size on the CV though.

Sample save (a beta only)
1. Load and Run the save and the VS on Saratoga will disband, and VB will change size.
2. Load save, and change the VB on Saratoga to accept replacements, and run. It will do re-sizes and VB will take replacements
3. After the first run, move Enterprise back to Noumea and it too will re-size.