Juha Holopainen Posted October 18, 2023 Report Share Posted October 18, 2023 (edited) Changes from beta 5: Aircraft that have entered Stable or SuperStable state will not revert to a "lesser" state (from stable to unstable for example) unless their time to feeder fix is greater than the time to enter that state PLUS a buffer which is 5 minutes by default in both cases. Edited Friday at 20:32 by Juha Holopainen Link to comment Share on other sites More sharing options...
Max Kuhla (1157125) Posted October 26, 2023 Report Share Posted October 26, 2023 Any chance to add the posibility for slave to show the Flight Information Window? Link to comment Share on other sites More sharing options...
Juha Holopainen Posted October 28, 2023 Author Report Share Posted October 28, 2023 I really thought of it as nothing more than one less "greyed out" item in the menu, barely more useful than the Blinking Window in TopSky, but if it's actually being used I don't see why not. Link to comment Share on other sites More sharing options...
Erik Wachters (815026) Posted November 8, 2023 Report Share Posted November 8, 2023 (edited) Hello Juha, Can you implement the option in the dataset to have different feeder fixes connected to the runway config? We have this in the real system. Like X & Y is 25L&R are in use and Y & Z if runway 19 in use. * for all runways. Maybe in the FEEDER line? FEEDER:FeederName:FeederID:Icao:runways:FixList:Color Example: FEEDER:ANT:A:EBBR:01,07L,07R:ANT:255,255,255 FEEDER:KERKY:K:EBBR:01,07L,07R:KERKY:255,255,255 FEEDER:BUN:B:EBBR:25R,25L:BUN:200,200,200 FEEDER:BUB:BB:EBBR:19:BUB:200,200,200 FEEDER:FLO:F:EBBR:*:FLO:200,200,200 runways = comma separated list of arrival runways. Thank you for concidering, Erik Edited November 9, 2023 by Erik Wachters (815026) Link to comment Share on other sites More sharing options...
Juha Holopainen Posted November 17, 2023 Author Report Share Posted November 17, 2023 Runway-specific feeders won't make it into this version as it would potentially need a lot of changes into otherwise pretty-much-ready-to-release code. I'll look into it later though. 1 Link to comment Share on other sites More sharing options...
Lukas Agerskov (1226374) Posted February 8 Report Share Posted February 8 On 18/10/2023 at 22:26, Juha Holopainen said: Beta 6 attached. Changes from beta 5: Aircraft that have entered Stable or SuperStable state will not revert to a "lesser" state (from stable to unstable for example) unless their time to feeder fix is greater than the time to enter that state PLUS a buffer which is 5 minutes by default in both cases. Mplugin11b6.zip 1.17 MB · 92 downloads Hello Juha. One small request, not sure if it would make a difference or not, but I would really like to try it out. A possibility of freezing airplanes once they pass the feeder fix. Its a thought because their sequence sometimes gets wrongly update in APP airspace from vectors, and the routing not properly updating until they are back on course, leading to subsequent delays for other airplanes further back, just because a routing is not properly updated. As said, I am not completely sure if it will make a noticable difference, but could it be added as an option to time freeze when they pass the feeder fix, meaning that it officially only cares about the landing time until it is in the sequence? Link to comment Share on other sites More sharing options...
Erik Wachters (815026) Posted February 8 Report Share Posted February 8 1 hour ago, Lukas Agerskov (1226374) said: Hello Juha. One small request, not sure if it would make a difference or not, but I would really like to try it out. A possibility of freezing airplanes once they pass the feeder fix. Its a thought because their sequence sometimes gets wrongly update in APP airspace from vectors, and the routing not properly updating until they are back on course, leading to subsequent delays for other airplanes further back, just because a routing is not properly updated. As said, I am not completely sure if it will make a noticable difference, but could it be added as an option to time freeze when they pass the feeder fix, meaning that it officially only cares about the landing time until it is in the sequence? That's what almost what happens in the real system too by the way. IRL we have a default time from the FF to the runway. 1 Link to comment Share on other sites More sharing options...
Juha Holopainen Posted February 12 Author Report Share Posted February 12 The next version will introduce a setting that makes the calculations assume a shortest possible vectoring path with the current groundspeed instead of the EuroScope predictions for aircraft with an assigned heading set. This should improve the predictions for the cases where the EuroScope predictions get confused because of the vectoring. The assumed vectoring path is a direct route from the current position to a point on the final track a pre-defined distance from the threshold, and then to the threshold. If the current position is "upwind" from the final track point a base leg is also calculated. Freezing landing times, aircraft category-specific FF-runway times, etc., would mean a major change to the whole sequencing code, and are not planned to this version. 1 Link to comment Share on other sites More sharing options...
Lukas Agerskov (1226374) Posted February 12 Report Share Posted February 12 5 hours ago, Juha Holopainen said: The next version will introduce a setting that makes the calculations assume a shortest possible vectoring path with the current groundspeed instead of the EuroScope predictions for aircraft with an assigned heading set. This should improve the predictions for the cases where the EuroScope predictions get confused because of the vectoring. The assumed vectoring path is a direct route from the current position to a point on the final track a pre-defined distance from the threshold, and then to the threshold. If the current position is "upwind" from the final track point a base leg is also calculated. Freezing landing times, aircraft category-specific FF-runway times, etc., would mean a major change to the whole sequencing code, and are not planned to this version. A small bug report I had tonight. Once airplanes are "De-Sequenced" if you resume them into the stack again I could not move them manually. For the rest, this sounds excellent! It would definitely help, because it suffers from euroscope not always updating the path, and the sequence gets super screwed. This should fix it. Link to comment Share on other sites More sharing options...
Juha Holopainen Posted February 14 Author Report Share Posted February 14 Aircraft in unstable state cannot be moved. Any aircraft added to the sequence, whether new or previously de-sequenced, will remain unstable at least a minimum time - 1 minute by default - until it can change state. 1 Link to comment Share on other sites More sharing options...
Stephen Odgaard (811390) Posted April 17 Report Share Posted April 17 @Juha Holopainen I think I have discovered one of the issues disruption MAESTRO functioning. See here: https://forum.vatsim.net/t/euroscope-plugin-cradartarget-getcorrelatedflightplan-getextractedroute-sid-star-and-rwys/5240/5 Stephen Slot Odgaard C3 - DK A320 MSFS FBW VR and Skalarki panels w converted real sidestick and tiller. Link to comment Share on other sites More sharing options...
Juha Holopainen Posted April 18 Author Report Share Posted April 18 Yes, there's little the plugin can do about wrong predictions, it just works with whatever it gets from EuroScope. While it's obvious to a human what's going on there, coding that kind of intelligence to the plugin is not feasible. Hopefully Gergely can improve the situation based on that feedback (should be an easy fix by just publishing the coordinated clearance on the network just like other direct-to clearances). Link to comment Share on other sites More sharing options...
Recommended Posts