Bug Report: E-3 lands and goes to 1092min ready

[hermanhum]

E-3 lands and goes to 1092min ready

E-3 lands and goes to 1092min ready time.

• Run test scen.
• Order both Sentries to land
• One Sentry will have 30min ready time and the other 1092min ready time
• Do not believe that this is a DB problem because both a/c are identical (except for the name)
  
  Sample file has been attached for PlayersDb.

StrategyZoneOnline

[jpkoester1]

ORIGINAL: hermanhum

E-3 lands and goes to 1092min ready

E-3 lands and goes to 1092min ready time.

• Run test scen.
• Order both Sentries to land
• One Sentry will have 30min ready time and the other 1092min ready time
• Do not believe that this is a DB problem because both a/c are identical (except for the name)
  
  Sample file has been attached for PlayersDb.

StrategyZoneOnline

Hello again, and thank you for this bugreport.

Our programmers have investigated this issue a while ago and the conclusion is that this bug is caused by a bad ready event that was created by certain versions of the game in a short timespan during the beta period and then saved into the scenario file. The release version does not produce the problem. This means that the bug is only present in scenarios that were saved with certain builds during the beta phase. In order to fix your scenario please do the following:

• Load the scenario in the editor.
• Select the base.
• Click "Edit" on the Menu Bar.
• Click "Units" on the Menu
• Click "Edit Aircraft" on the submenu
• Click "Continue" on the Edit Aircraft Dialog

This will remove the bad event.

Cheers,
JP

[hermanhum]

Thanks for the suggestion, but the units in the test scenario start airborne.  This remedy is simply not a possibility.

[jpkoester1]

Can this behaviour be reproduced with a scenario built from scratch with the release version?

[hermanhum]

Made a small test scenario, as suggested, and this phenomenon did not appear.

Are the causes for this behavior known well enough to identify future events?

Are all pre-existing scenarios susceptible to this problem?

Does it occur for all scenarios with aircraft inserted directly into the scenario and not launched from bases?

[jpkoester1]

ORIGINAL: hermanhum

Made a small test scenario, as suggested, and this phenomenon did not appear.

Are the causes for this behavior known well enough to identify future events?

Are all pre-existing scenarios susceptible to this problem?

Does it occur for all scenarios with aircraft inserted directly into the scenario and not launched from bases?

Our programmers tell me that this particular bug was only present during a short time during the beta phase and only scenarios edited with one of those beta scenario editor versions might be effected. Scenarios created with 3.6.3 scenedit or ANW-release scenedit should not be effected by it.

Cheers,
JP