ES 3.2 FSD simulator - blip driving - route modifying error?

[Michael Pike]

I am using a scenario created for 3.1d and running it on the FSD server on my own. I am simulating the aircraft and when I display the Route Commands ribbon, the route is displayed from left to right. IE, the next waypoint is on the left and the next is to the right of it. I think in 3.1d it was the other way round. Is there a difference in the format of scenario files for 3.2?

 

The significance of this is that using the Go Direct to Next Waypoint button goes to the next on the right (which is always the last one in sequence). You can never go direct to any waypoint except the last one!

 

For example the scenario file has this line:

 

$ROUTE:BARMI LOGAN SABER LAM

 

for a flight inbound to London Heathrow. After it p[Mod - Happy Thoughts]es BARMI, the route is displayed in the route ribbon as:-

 

LOGAN SABER LAM

 

To direct the plane to route direct to LOGAN, I click Go Direct to Next Waypoint and expect the plane to turn towards LOGAN. What seems to happen is that the route changes so that only LAM remains and the plane turns direct to LAM.

 

Similarly Skip Next Waypoint always clears the whole route.

 

I hope I'm missing something simple!

[Eric Bocaneanu 906549]

Michael,

 

After p[Mod - Happy Thoughts]ing BARMI in your example it would already be direct LOGAN. So pressing Direct Next would delete LOGAN and go to SABER.

 

Also when loading the scenario file the route should say just LOGAN SABER LAM. The active waypoint is removed from the list of waypoints and moved in the active waypoint box to the left of the route field. As far as I know in this box there is no change from 3.1. So after p[Mod - Happy Thoughts]ing BARMI, LOGAN is removed from the list, put in the active point box and the route would remain SABER LAM. It seems to be what you described.

[Michael Pike]

Thanks Eric. I'm afraid my memory let me down there! I have now run the same scenario file in both 3.1 and 3.2 and of course the routes are displayed exactly the same.

 

However!

 

The Go Direct to Next Waypoint does indeed work differently on my installation. I didn't describe my example very well above. Clicking the button always makes the last waypoint the active one. So it will always go direct to LAM in my example. There is no way to go to SABER. With other routes with many waypoints, clicking the button always makes the last one the active and clears the whole route from the list.

 

Just reporting unexpected behaviour, that's all.

[Eric Bocaneanu 906549]

I should test this. You are surely pressing the next waypoint, not the skip waypoint button?

 

Just send me the sector and scenario via PM and tell me the name of the aircraft to test.

[Michael Pike]

In view of the lack of anyone else experiencing this, I thought I would try running the scenario differently. I can now reproduce both the correct behaviour and the error! It is simulated controllers that causes the problem. Stand by for PM.

[Eric Bocaneanu 906549]

Wow Michael,

 

That's some bad[Mod - Happy Thoughts] testing there. I don't think I could have tracked it down to the controllers. I have reproduced both with your scenario and mine. I have to concede that the simulated controllers was never tested by me in beta. I have added it to the list and it should be fixed in an upcoming update.

 

Thanks a lot!

[Michael Pike]

No problem - thought I was going crazy there for a minute!