4.11 General debugging

[Aviar]

I came across a quirky little bug in the FMB in version 4.11.1. It concerns the 'Waypoint Options' feature.

If you use this feature and set a particular waypoint to 'Patrol', the flight (in the MIS file) might look something like this:

[USN_VF_10A00]
Planes 1
Skill 1
Class air.P_38J
Fuel 100
weapons default
[USN_VF_10A00_Way]
TAKEOFF 39257.95 18077.12 0 0 &0
NORMFLY 34876.31 20568.50 500.00 300.00 &0
TRIGGERS 0 0 0 5 0 0 <-----------------------Patrol Settings!
NORMFLY 24124.97 17979.00 500.00 300.00 &0
NORMFLY 42218.69 11161.08 500.00 300.00 &0
LANDING 40639.26 17279.62 0 0 &0


In the example above, the 'Triggers' line contains the Patrol settings. So far, no problems.

If you load this mission into the FMB and click on the Patrol waypoint and change it to a 'GAttack' waypoint, you will have problems. If you try to reload the mission, you will get a 'Loading Mission' error (see 1st screenshot). That particular flight will not load into the mission. Also, depending on the particular mission, you may lose other flights or even other units, such as vehicles and ships. Below is what the MIS file will look like if this happens:

[USN_VF_10A00]
Planes 1
Skill 1
Class air.P_38J
Fuel 100
weapons default
[USN_VF_10A00_Way]
TAKEOFF 39257.95 18077.12 0 0 &0
NORMFLY 34876.31 20568.50 500.00 300.00 &0
GATTACK_401 31500.13 28009.22 500.00 300.00 &0
TRIGGERS 0 0 0 5 0 0 <--------------------------This line should not be here!!
NORMFLY 24124.97 17979.00 500.00 300.00 &0
NORMFLY 42218.69 11161.08 500.00 300.00 &0
LANDING 40639.26 17279.62 0 0 &0


The bug is that the TRIGGERS line is not deleted when the GATTACK line is added. This leads to the 'LOADING MISSION' error. In any case, this flight will not appear in the mission.

A quick workaround is to manually delete the TRIGGERS line from the MIS file. To prevent this issue from happening in the first place, always change your Patrol waypoints back to normal, SAVE, and then proceed.

*Just a little comment from me; One reason this problem may arise is because the 'Normfly' waypoints and the 'Patrol' waypoints all look the same. I could have sworn we had requested that DT add something to the Patrol waypoints so that the mission builders could tell the difference between the two.

The way it is now, we have to click on every waypoint in order to find out which are Normfly and which are Patrol. Clicking the 'Prev' or 'Next' waypoint buttons does not help because a Patrol waypoint is still displayed as 'Normfly' (see 2nd screenshot). You would need to click on the 'Waypoint Options' tab and then click on each tiny waypoint to find the information (see 3rd screenshot). We really need a graphical clue that a particular waypoint is a Patrol waypoint.....please. Thank you.

Aviar

[Aviar]

Here is another little map (Kyushu) bug:

Vehicles cannot completely cross the bridge in grid AO-10. They get stuck on the eastern end of the bridge (see screenshot).

Aviar