March 24, 200422 yr When we fetch a METAR is it stored inside FS2004 for use in case we move the aircraft there or is it information only ?It would be nice to have this operational because AI traffic at airports initiates on scenery load based on weather at current location. Sometimes local winds dictate other runway(s) in use from the one that FS9 starts with by default when moving to a certain airport.So say FS9 with nil WX starts at an airport always with rwy 36 in use and a particular day winds are 180/20. You move the aircraft there, scenery loads and AI starts using rwy 36. After you load WX with AS2004 and 180/20 becomes active AI will still use rwy 36 while you will have to use rwy 18. If the WX station data was stored before moving there from another location (i.e. by fetching the metar) then AI traffic would initiate from rwy 18.Kyprianos Biris :-cool[link:avsim.com/greece/hvacc]Hellenic vACChttp://vateud.org/images/vatsim-eurs.gifhttp://vatsim.pilotmedia.fi/statusindicato...tor=OD1&a=a.jpg Hellenic vACC - Olympic Aegean Virtual Prepar3D 5.3 | CPU i9 10900K | VGA: RTX 3070 | RAM: 32GB DDR4 | Monitor: 3440x1440
March 24, 200422 yr Commercial Member Hi Kyprianos,As far as I understand the FS9 AI/ATC system, the active runway will switch appropriately but only after the current AI departing and arrival aircraft (who have been given taxi or approach clearance to a certain runway) have finished their departure/arrival. This can take a few minutes after new wx loads (more like 10-20 minutes at busy airports with many AI). Unfortunately it's not always convenient to wait 20 minutes for the AI to reset before getting underway.The wx available at scenery load, as you said, determines the "starting runway", so in order to support this as you describe we must load the wx before the scenery in that region is loaded. Since we can't write the wx until a flight is loaded (to prevent FSUIPC communication problems), the only solution to me seems to move your aircraft to a remote region (well away from your planned departure), load the flight, load AS2004 wx for your flight per flight plan (which will set all wx along that route incl departure and dest, and ALTERNATE if any), THEN move to your planned departure airport. Another possible solution is to manually set your departure airport surface winds via FS wx dialogue before loading the flight to be consistent with the correct runway in use, then load the flight followed by AS2004.I must admit I am not very familiar with the AI particulars, but this "issue" has been something we've been dealing with for a long time and I would love to find a better solution. I have an idea that includes a pre-flight global write using the old FS98 wx interface (which should not be effected by the communication issue preventing NWI/localized station writes prior to flight load).For example, you check a new option in AS2004 to "send departure winds to FS prior to flight load", and AS2004 (assuming AS flight plan loaded) will begin sending this FS98 global wind information (from the departure wind data) at regular intervals until the actual flight is loaded and the aircraft is moved to the departure airport. Then processing resumes normally. Sounds good on paper but we'll have to see. Can you let me know if the 2 initial suggested work-arounds do as expected? If so, I'll begin work on trying to implement the pre-flight write as described, which SHOULD do the trick :) Let me know, and your feedback is much appreciated!-Damian Damian ClarkHiFi Simulation Technologies
March 24, 200422 yr One other option is to set everything for departure, apart from clearance if using M$ ATC, but then advance the time by e.g. 1 hour. This gets the correct runways in use.Steve
March 24, 200422 yr Author >For example, you check a new option in AS2004 to "send>departure winds to FS prior to flight load", and AS2004>(assuming AS flight plan loaded) will begin sending this FS98>global wind information (from the departure wind data) at>regular intervals until the actual flight is loaded and the>aircraft is moved to the departure airport. Then processing>resumes normally. Sounds good on paper but we'll have to see.> Yeap, that'll do the job fine.It will do automatically what I describe below as a manual procedure:Make a local WX station METAR import & write in FS9 data when you fetch a METAR for that station from AS2004. That way you are say in airport AAAA , fetch BBBB's WX and then "Go to Airport" -> BBBB will get you with correct AI straight away.Kyprianos Biris :-cool[link:avsim.com/greece/hvacc]Hellenic vACChttp://vateud.org/images/vatsim-eurs.gifhttp://vatsim.pilotmedia.fi/statusindicato...tor=OD1&a=a.jpg Hellenic vACC - Olympic Aegean Virtual Prepar3D 5.3 | CPU i9 10900K | VGA: RTX 3070 | RAM: 32GB DDR4 | Monitor: 3440x1440
March 25, 200422 yr Hi Kyprianos,don't know if i understand your question correctly - but regardless of fetching, i use the following to "force" AI using the correct rwy according to the metar:start fs9 and let as2004 weather settle WITHOUT any AI traffic - when weather update has finished, enable AI traffic - i never ever had any problems with AI departing the wrong runway.cheers,harald / loww
Create an account or sign in to comment