VarAction 02 on variable E6 misbehaves (loading states too.)

[DaleStan]

The Osprey does not work as I think it should. There's a bug list there, but I'll give more detail on the first bug here:

Sprites 32 and 156 function inconsistently, and usually incorrectly. When an Osprey arrives at a gate (var E6 values 01-03), it is supposed to raise its nacelles to the vertical position. Under most circumstances, this does not happen. However, checking the vehicle details window reveals that it thinks the nacelles are in the vertical position. Furthermore, if the vehicle details window is open when the Osprey arrives at the gate, the rotors will rise to their correct (nacelles-vertical) position, but the nacelles don't follow.

These pseudo-sprites work correctly for entering the hangar (var E6 value 00)

Further checking shows that the Osprey is not the only aircraft with this problem. The attached test_p.grf is supposed to create planes that display the current value of the variable passed as a parameter. If you set the parameter to 230 (0xE6), the exact same bug is observed: although the vehicle details window is aware that the value has changed, the main view is not.

EDIT: Fixed B6->E6, as noted below

[Patchman]

This probably means the sprite does not get updated when the variable changes. In the vehicle window, the sprite is recalculated every time it is redrawn, so it works there.

If it gets the right sprite when you click the grf status "apply" button, that'll be the reason.

Also, don't you mean variable E6?

[Patchman]

Yep, that was it. Fixed in a46.

[DaleStan]

I thought I'd work around this bug by using loading states, and I discovered that loading states for aircraft aren't updated (until I click Apply in the GRF status window)

If you need a sample GRF, I can provide one easily.

I also discovered that rotors don't have loading states, but this doesn't seem like a bug to me.