DirkDP

Hi, Replace the file. Just use one, not both. You can close the other RWYs both for landing and takeoff at both ends, so only 14/32 remains open. You say the wind usually comes from 300 to 270, then it's RWY32 or RWY26 that will be active. For RWY14 you need wind from around 140, south east. Regards, DDP.

Hi, That's TDS simulating MCAS...? :D Or how about editing the aircraft.cfg load stations to set the CG at a realistic position? In the [WEIGHT_AND_BALANCE] empty_weight_CG_position= Changing the 1st number (longitude) will move the CG. Then change the longitude of station_load.0... accordingly. CG should be at around 25% MAC. Like below: Also check payload weights and fuel load. The aircraft does not need to be at MTOW to fly... Regards, DDP.

Hi, It's defined as ILS, so it's always active, regardless of the weather. But it still depends on wind direction. The 6500ft is the alt at Alpha transition. In reply #14 there's a link to the approach charts I used. I just uploaded another version, where you can choose to get vectored to the IF, alt 2040ft. Only difference is AI approach code is now more "straight in". See reply #18. Regards, DDP.

Hi, It's because I defined a different FAF in the header, to create the AI curved approach. So it'll look like AI tries to do some of the DME arc. Here's the file with the FAF set the same as in the approach legs. Vectors do work now, but AI does a straight in approach. https://drive.google.com/file/d/1UylUspahMox6izQSCUu-7621PLD3p2PO/view?usp=sharing @Miggers The APR file does not contain any freq. or airport data. It only contains waypoints and XML data for the AI and the FS9 GPS. To test fly this approach you need to load it in the GPS (see screenshots) and set the A/P to GPS. Of course you need an aircraft that can do that, like the stock FS9 aircraft. The ILS beam your radio tunes to is completely separate from this. Hope this helps. Regards, DDP.

Hi, The FS9 GPS and ATC give the choice to either vector or use the transition. I just used the transition for the screenshot. And for now it's only for RWY14, since that was the OP's main interest. The other RWYs have PAR approaches. BTW, here's my source: https://www.airfieldresearchgroup.org.uk/community/117733=10969-Valley%20-%20EGOV.pdf Regards, DDP.

Hi, I was lucky to get one of the last available boxed editions of FS Global 2010 from Amazon Germany last year. I got it because it was for FS9 and it had Greenland data. Regards, DDP.

Hi, What I've also done for Win7x64 is make fs9.exe Large Address Aware... Addition/edit: I'm not using any compatibility mode in Win7x64. That seems to break the Wx radar on the FT/Wilco Airbus Evos... DDP.

Hi, Here's what I've come up with. Hope the link works... https://drive.google.com/file/d/1TiTIGXsPrAkY9YeAKwY9sJ-85sQ-12IP/view?usp=sharing Put EGOV_ADE9_APR.BGL in the same folder as your JF EGOV airport file. AI coming from the south and west will kinda mimmick the final part of the DME arc before turning onto the final approach course. I've kept the RWY at 14, but it seems it's become RWY13 now (magnetic north change...). If you ever decide to change the RWY to 13 the appoach file will need to be updated as well. Regards, DDP.

Hi, That DRM issue is this I suppose? https://www.flightsim.com/vbfs/showthread.php?293174-This-is-a-warning-to-all-fs2004-users-who-run-this-program-on-microsoft-windows-7!!!! That was a nice one M$ pulled... :D Personally, I'm sticking with Win7 until there's a game I absolutely have to have (most new games don't support Win7 anymore), and then I'll upgrade. I'll probably need a new PC as well then... Regards, DDP.

Hi, Well, if you don't already have it, download the manual165.pdf from here: https://www.fsdeveloper.com/forum/threads/ade-version-1-65-english-manual-released.433288/ It does explain the basics of how to create an approach. Approach codes are not an easy matter. I'll take a look at EGOV and see if I can get an approach working for RWY14. Regards, DDP.

Hi, Well, several utilities I'm using have become 64bit only (ADE, AIFP...), so for my WinXPx86 system I'm using the older versions, which I've kept over the years. Main use is for editing stuff and testing. For my actual VA flying, I'm using a modern-ish (~2014) system with Win7x64Pro. There's other utilities that use newer versions of .NET... For freeware airports or aircraft I don't think there will be problems, I haven't found any. Maybe some newer payware installers won't work. Hope this helps a bit... Regards, DDP.

Hi, TrackIR 5? I got it several months ago for use with ETS2/ATS and FS9. VC flying is fun now. But one does need to spend some time setting it up, as well as the VC viewpoint. As I lean forward, the panel comes closer (like a zoom), but the outside stays the same (no zoom). Regards, DDP.

Hi, There is a difference between the ILS beam you tune your NAV radio to, and the ILS approach code ATC/AI use. If that code is not there, then as far as ATC/AI is concerned, there is no ILS. A very good detailed and long explanation by Jim Vile here: https://www.fsdeveloper.com/forum/threads/tutorial-approaches.14074/ With ADE in approach mode you can add ILS approach code for ATC/AI to use. The AI only uses info from the header of that code. Regards, DDP.

Hi, And run it as admin? I haven't used it, but both my Active Sky 6.5 and Evo need to run as admin, or they won't connect to FS9. Regards, DDP.

Hi, I think it's not an FS9 problem, it's a Win 7 problem. The FS9 I've installed on those Win7s is exactly the same. The Win7 installs are not. One is for online use, so it's got AV and Firefox etc. The other Win7 is strictly offline. No AV or Firefox and several services needed for online have been disabled (as per http://www.blackviper.com). I use the offline Win7 to fly, which does not have the problem. That's why I never investigated it any further. Maybe it's the AV, or one of those services, but imo it's not FS9. Regards, DDP.

Maybe there's a scientology convention, hosted by you know who... DDP.

Hi, I have a multi-boot system with 3 Win 7x64 Pro installs. FS9 is installed on 2 of them. On one of them I have that problem too, not on the other. Just remembered, that at the time I did come across posts about this, just dug'em up. It's that stupid Game Explorer... https://www.flightsim.com/vbfs/showthread.php?311500-FS9-needs-second-startup&highlight=FS9+startup http://ubeogesh-things.blogspot.com/2012/08/resolve-it-finally-game-explorer-aka.html DDP.

Hi, If you want something somewhat readily set up, there's MyTraffic 2006, freeware for FS9. Get it here: https://secure.simmarket.com/aerosoft-online-mytraffic-2013.phtml Scroll down a bit and click on 'Read More' to get the DL link. It'll install updated stock airports that have enough parking, it also includes GA, military aircraft and a voice file to use with Editvoicepack to update ATC. It also comes with a .pdf manual. But... remember, this is from 2006. The AI models and textures are... not AIA or TFS quality... Regards, DDP.

Hi, Here's why the RWY numbers are changing more nowadays. https://www.bbc.com/news/science-environment-52550973 At BGTL (Thule AFB USAF) in Greenland, the RWYs are numbered 08T/26T, according to true north. Otherwise they'd have to repaint those numbers every year. Regards, DDP.

Hi, Apparently that July 04 date is hardcoded in the FMS, so no matter what AIRAC is installed, it'll keep showing July 04. Look in your FS9 install folder, there should be a Feelthere\NavData folder. That's where the CRJ AIRAC files are. Open the cycle_info.txt to see the dates. Also be aware that Navigraph does not offer Terminal Procedures (SIDSTARS) for the FS9 Feelthere CRJs. The Procs.ftd is not updated. But, Dmetrey Taborko, over at Avsimrus.com made some updates himself, the latest was 1808: https://avsimrus.com/f/fs2004-effects-and-addons-46/wilco-crj-sidstar-airac-1808-update-procs-ftd-rwy-ftd-62529.html?action=comments Hope this helps. DDP.

Hi, Copy/paste from a post in 2010 by D.Scobie (feelThere support) at Avsim. "The issue is a hidden character in the aircraft.cfg file for the CRJ 700 and 900. When a livery is added notepad kills the 'hard return' and this causes a fault in the contact points. Look at the aircraft.cfg. Look for a text line that looks out of place ... you should notice an excessively long contact point reference. Without the 'hard return' the aircraft only has two landing gear points (if i remember correctly). Put in a hard return where text looks out of place and save the cfg." See here: https://www.avsim.com/forums/topic/232742-wilco-crj-gear-problems/ Regards, DDP.

Hi, That's a good thing. It's Fox Propaganda, not even "news". And anyway, didn't Hannity, Pirro and the other idiots there call COVID a hoax? DDP.

Hi, Could it be this? https://www.flightsim.com/vbfs/showthread.php?188417-Soaring-in-FSX See reply #2 and #5. Regards, DDP.

Hi, If you mean static_cg_height, that only has effect in slew mode, as does static_pitch. This is what the numbers stand for: //0 Class //1 Longitudinal Position (feet) //2 Lateral Position (feet) //3 Vertical Position (feet) //4 Impact Damage Threshold (Feet Per Minute) //5 Brake Map (0=None, 1=Left, 2=Right) //6 Wheel Radius (feet) //7 Steer Angle (degrees) //8 Static Compression (feet) (0 if rigid) //9 Max/Static Compression Ratio //10 Damping Ratio (0=Undamped, 1=Critically Damped) //11 Extension Time (seconds) //12 Retraction Time (seconds) //13 Sound Type //14 Airspeed limit for retraction (KIAS) //15 Airspeed that gear gets damage at (KIAS) I think there's an error in the main gear wheel radius setting (0.512). That entry is in ft. and it seems a little low, looking at the screenshot. Try changing that, but backup your aircraft.cfg first. Regards, DDP.