Jump to content
Sign in to follow this  
b738pilot

Runway closed for landings, AI aircraft landing...

Recommended Posts

Yep, 18L and 18R are in use, aircraft are landing at those runways and ATIS says they're in use.The north config works perfectly :)Maybe it is important to add that I am also using New Spanish Airports add-on, which contains Madrid Barajas. There was a not-up-to-date scenery of Barajas with only two runways so I additionally installed a freeware Madrid Gran Barajas (LEMDGB) add-on from avsim, which added the runways and terminals to aerosoft scenery.Before installing Mega Airport Barajas X I uninstalled LEMDGB and, not wanting to uninstall whole New Spanish Airports, I deleted Barajas scenery from the scenery library in FS and Barajas folders from New Spanish Airports directory.Maybe there is still some .bgl file from one of the previous sceneries that allows traffic to land at 15R ?
That is the only reason that comes to my mind too, there may be in fact an overlapping Afcad file somewhere in the senery files. Maybe the AF2 files are in a separate folder in the Spanish Airport scenery, I truly can't say anything...?Try this, change the runway assignments, set the landings on 15L/R and the take-offs on 18L/R, see what happens. :(

Share this post


Link to post
Share on other sites

Here's a no cost way to check some things:Go to http://forums.simflight.com/viewtopic.php?...4946659e9ec076c and download http://fsuipc.simflight.com/beta/TrafficLook.zip .Go to and download FSUIPC and makerwys.exe.makerwys.exe should go into your FS9 folder and if necessary be set to run as an admin. FSUIPC is self installing to go into your FS9 modules folder. If necessary you can force it eventually to browse for that FS9 folder if needed. Again, if necessary, run the fsuipc.exe installer as an admin and set it to run as an admin.Install Traffic-Look into its own folder and make a shortcut to it set to run as an admin if necessary.Traffic-look monitors in real time AI operations. Activate the AFCAD in question and start FS and park at the airport in question at a time when traffic is busy.Alt-tab to start traffic-look. It will present a table showing eventually AI taxiing and arriving and runways in use for each as soon as the arriving AI get within approach range. Give at least five minutes for the AI to get going especially the arrivals.When you are done observing close FS and traffic look.After anytime your FS has reindexed its scenery files close it. Go to your your FS9 folder. Run makerwys.exe and wait the few minutes until it finishes. In that same folder open in worpad the file runways.txt That is a log of what it found.Search for each occurrence of the airport by ICAO code. Each occurrence will have a large section and the last section found has priority. For the last section (you'll see the path of the afd type file) note the runway descriptions. This will show the properties of each afd (afcad type) file and if one with more priority is having a negative effect on what you are setting. Note that runways.txt is huge and it can take quite some time to load in wordpad.I have New Spanish Airports and this is what Makerwys.exe reports:Area.140 "Madrid-Barajas2004_LC" (Layer=142)Local=aerosoft\New Spanish Airports\Madrid-Barajas2004_LC=============================================================================Area.141 "Madrid-Barajas2004_SC" (Layer=143)Local=aerosoft\New Spanish Airports\Madrid-Barajas2004_SC=============================================================================aerosoft\New Spanish Airports\Madrid-Barajas2004_SC\scenery\AF2_LEMD.BGL=============================================================================Deletions check for Airport LEMD: Delete all taxiways! Delete all runways and starts! *** DelBth *** LEMD0150 Lat 40.484863 Long -3.576034 Alt 1999 Hdg 145 Len 13484 Wid 197 *** DelBth *** LEMD0181 Lat 40.490936 Long -3.562824 Alt 1999 Hdg 183 Len 12120 Wid 148 ILS 109.30, Flags: GS DME BC *** DelBth *** LEMD0182 Lat 40.531746 Long -3.574844 Alt 1999 Hdg 183 Len 14279 Wid 197 ILS 110.70, Flags: GS DME BC *** DelBth *** LEMD0330 Lat 40.455612 Long -3.546282 Alt 1999 Hdg 325 Len 13484 Wid 197 ILS 109.90, Flags: GS DME BC *** DelBth *** LEMD0361 Lat 40.492577 Long -3.574628 Alt 1999 Hdg 3 Len 14279 Wid 197 *** DelBth *** LEMD0362 Lat 40.457695 Long -3.562626 Alt 1999 Hdg 3 Len 12120 Wid 148 ILS 110.30, Flags: GS BC Delete all taxiways! COM: Delete all frequencies![Ron Note: This following is what is effective:]=============================================================================aerosoft\New Spanish Airports\Madrid-Barajas2004_SC\scenery\AF2_LEMD.BGL=============================================================================Airport LEMD :N40:28:14.8318 W003:33:42.3978 1999ft City Name="Madrid" Airport Name="Barajas" in file: aerosoft\New Spanish Airports\Madrid-Barajas2004_SC\scenery\AF2_LEMD.BGL Runway 33 /15 centre: N40:28:12.8557 W003:33:40.1691 1999ft Runway 33 closed for take-off <<<<<<<<<<<<<<<<< Runway 15 closed for landing and take-off <<<<<<<<<<<<<<<<<< Start 33 : N40:27:21.5755 W003:32:47.9720 1999ft Hdg: 322.3 true Computed start 33 : Lat 40.455612 Long -3.546282 Offset Threshold primary: 3445 feet Start 15 : N40:29:04.1036 W003:34:32.3465 1999ft Hdg: 142.3 true Computed start 15 : Lat 40.484863 Long -3.576034 Hdg: 322.270 true (MagVar -3.000), ASPHALT, 13484 x 197 ft Secondary ILS ID = MAA *** No matching ILS record - assume provided by another layer *** Runway *** LEMD0330 Lat 40.455612 Long -3.546282 Alt 1999 Hdg 325 Len 13484 Wid 197 <<<<<<<< *** Runway *** LEMD0150 Lat 40.484863 Long -3.576034 Alt 1999 Hdg 145 Len 13484 Wid 197 <<<<<<<<< Runway 1 /19 centre: N41:36:18.4612 W003:34:52.7641 1999ft Runway 1 closed for landing and take-off <<<<<<<<<<<<<psuedo runway>>>>> Runway 19 closed for landing and take-off Hdg: 330.170 true (MagVar -3.000), CONCRETE, 10 x 10 ft <<<<<<length for psuedo runway>>>>>> Runway 2 /20 centre: N41:36:18.4612 W003:34:52.7641 1999ft <<<<<<pseudos to: Runway 2 closed for landing and take-off Runway 20 closed for landing and take-off Hdg: 338.070 true (MagVar -3.000), CONCRETE, 10 x 10 ft Runway 3 /21 centre: N41:36:18.4612 W003:34:52.7641 1999ft Runway 3 closed for landing and take-off Runway 21 closed for landing and take-off Hdg: 345.970 true (MagVar -3.000), CONCRETE, 10 x 10 ft Runway 4 /22 centre: N41:36:18.4612 W003:34:52.7641 1999ft Runway 4 closed for landing and take-off Runway 22 closed for landing and take-off Hdg: 353.870 true (MagVar -3.000), CONCRETE, 10 x 10 ft Runway 36L/18R centre: N40:30:44.0077 W003:34:28.9235 1999ft <<<<next non-pseudo>>>>> Runway 36L closed for landing <<<<<<< Runway 18R closed for landing and take-off <<<<<<< Start 36L: N40:29:35.0078 W003:34:28.6709 1999ft Hdg: 359.8 true Computed start 36L: Lat 40.492641 Long -3.574584 Start 18R: N40:31:52.5541 W003:34:29.6332 1999ft Hdg: 179.8 true Computed start 18R: Lat 40.531811 Long -3.574818 Hdg: 359.740 true (MagVar -3.000), ASPHALT, 14279 x 197 ft Primary ILS ID = IMR *** No matching ILS record - assume provided by another layer *** Runway *** LEMD0361 Lat 40.492641 Long -3.574584 Alt 1999 Hdg 3 Len 14279 Wid 197 <<<<<<< *** Runway *** LEMD0182 Lat 40.531811 Long -3.574818 Alt 1999 Hdg 183 Len 14279 Wid 197 <<<<<<< Runway 36R/18L centre: N40:28:27.5304 W003:33:45.8097 1999ft Runway 36R closed for landing and take-off <<<<<<<<<<<<< Runway 18L closed for landing and take-off <<<<<<<<<<<<< Start 36R: N40:27:28.8642 W003:33:45.4075 1999ft Hdg: 359.7 true Computed start 36R: Lat 40.457695 Long -3.562633 Offset Threshold primary: 3445 feet Start 18L: N40:29:25.6458 W003:33:46.1540 1999ft Hdg: 179.7 true Computed start 18L: Lat 40.490936 Long -3.562816 Offset Threshold secondary: 2287 feet Hdg: 359.760 true (MagVar -3.000), ASPHALT, 12120 x 148 ft Primary ILS ID = MDZ *** No matching ILS record - assume provided by another layer Secondary ILS ID = BJS *** No matching ILS record - assume provided by another layer *** Runway *** LEMD0362 Lat 40.457695 Long -3.562633 Alt 1999 Hdg 3 Len 12120 Wid 148 *** Runway *** LEMD0181 Lat 40.490936 Long -3.562816 Alt 1999 Hdg 183 Len 12120 Wid 148(continues) Any short pseudo runways for the "STAR" method are the 10x10 surfaced ones I noted. These make non-parallels simultaneously active.

Share this post


Link to post
Share on other sites

I just did it and I got two results:Airport LEMD :N40:28:20.0149 W003:33:39.3996 1999ft City Name="Madrid" Airport Name="Barajas" in file: Scenery\EURW\scenery\AP947170.BGL Runway 18L/36R centre: N40:28:27.5304 W003:33:45.8097 1999ft Start 18L: N40:29:25.6458 W003:33:46.1540 1999ft Hdg: 179.7 true Computed start 18L: Lat 40.490936 Long -3.562824 Offset Threshold primary: 2287 feet Start 36R: N40:27:29.4149 W003:33:45.4654 1999ft Hdg: 359.7 true Computed start 36R: Lat 40.457695 Long -3.562626 Hdg: 179.740 true (MagVar -3.000), Asphalt, 12120 x 148 ft Primary ILS ID = MDZ Primary ILS: MDZ 109.30 Hdg: 179.7 , Flags: GS DME BC "ILS/DME 18L" Secondary ILS ID = BJS Secondary ILS: BJS 110.30 Hdg: 359.7 , Flags: GS BC "ILS 36R" *** Runway *** LEMD0181 Lat 40.490936 Long -3.562824 Alt 1999 Hdg 183 Len 12120 Wid 148 ILS 109.30, Flags: GS DME BC *** Runway *** LEMD0362 Lat 40.457695 Long -3.562626 Alt 1999 Hdg 3 Len 12120 Wid 148 ILS 110.30, Flags: GS BC Runway 15 /33 centre: N40:28:12.8557 W003:33:40.1691 1999ft Start 15 : N40:29:04.1360 W003:34:32.3209 1999ft Hdg: 142.3 true Computed start 15 : Lat 40.484863 Long -3.576034 Start 33 : N40:27:21.5755 W003:32:48.0173 1999ft Hdg: 322.3 true Computed start 33 : Lat 40.455612 Long -3.546282 Offset Threshold secondary: 3445 feet Hdg: 142.270 true (MagVar -3.000), Asphalt, 13484 x 197 ft Secondary ILS ID = MAA Secondary ILS: MAA 109.90 Hdg: 322.3 , Flags: GS DME BC "CAT III ILS/DME 33" *** Runway *** LEMD0150 Lat 40.484863 Long -3.576034 Alt 1999 Hdg 145 Len 13484 Wid 197 *** Runway *** LEMD0330 Lat 40.455612 Long -3.546282 Alt 1999 Hdg 325 Len 13484 Wid 197 ILS 109.90, Flags: GS DME BC Runway 18R/36L centre: N40:30:43.7809 W003:34:29.0490 1999ft Start 18R: N40:31:52.5217 W003:34:29.4289 1999ft Hdg: 179.8 true Computed start 18R: Lat 40.531746 Long -3.574844 Offset Threshold primary: 3232 feet Start 36L: N40:29:35.0078 W003:34:28.6709 1999ft Hdg: 359.8 true Computed start 36L: Lat 40.492577 Long -3.574628 Hdg: 179.760 true (MagVar -3.000), Asphalt, 14279 x 197 ft Primary ILS ID = IMR Primary ILS: IMR 110.70 Hdg: 179.8 , Flags: GS DME BC "CAT III ILS/DME 18R" *** Runway *** LEMD0182 Lat 40.531746 Long -3.574844 Alt 1999 Hdg 183 Len 14279 Wid 197 ILS 110.70, Flags: GS DME BC *** Runway *** LEMD0361 Lat 40.492577 Long -3.574628 Alt 1999 Hdg 3 Len 14279 Wid 197and then data bout the taxiways stands etc...The next result:=============================================================================Area.125 "Madrid 2008_SC" (Layer=126)Local=Aerosoft\Madrid 2008_SC=============================================================================Aerosoft\Madrid 2008_SC\scenery\AF2_LEMD-SUD.bgl=============================================================================Deletions check for Airport LEMD: Delete all taxiways! Delete all runways and starts! *** DelBth *** LEMD0150 Lat 40.484863 Long -3.576034 Alt 1999 Hdg 145 Len 13484 Wid 197 *** DelBth *** LEMD0181 Lat 40.490936 Long -3.562824 Alt 1999 Hdg 183 Len 12120 Wid 148 ILS 109.30, Flags: GS DME BC *** DelBth *** LEMD0182 Lat 40.531746 Long -3.574844 Alt 1999 Hdg 183 Len 14279 Wid 197 ILS 110.70, Flags: GS DME BC *** DelBth *** LEMD0330 Lat 40.455612 Long -3.546282 Alt 1999 Hdg 325 Len 13484 Wid 197 ILS 109.90, Flags: GS DME BC *** DelBth *** LEMD0361 Lat 40.492577 Long -3.574628 Alt 1999 Hdg 3 Len 14279 Wid 197 *** DelBth *** LEMD0362 Lat 40.457695 Long -3.562626 Alt 1999 Hdg 3 Len 12120 Wid 148 ILS 110.30, Flags: GS BC Delete all taxiways! COM: Delete all frequencies!=============================================================================Aerosoft\Madrid 2008_SC\scenery\AF2_LEMD-SUD.bgl=============================================================================Airport LEMD :N40:28:14.2163 W003:33:42.5330 1999ft City Name="Madrid" Airport Name="Madrid-Barajas" in file: Aerosoft\Madrid 2008_SC\scenery\AF2_LEMD-SUD.bgl Runway 15R/33L centre: N40:28:12.6290 W003:33:40.9977 1999ft Runway 15R closed for landing Runway 33L closed for landing Start 15R: N40:29:03.1641 W003:34:38.5858 1999ft Hdg: 52.8 true Computed start 15R: Lat 40.484936 Long -3.576225 Computed start 33L: Lat 40.455410 Long -3.546551 Offset Threshold secondary: 4593 feet Hdg: 142.600 true (MagVar -3.000), Asphalt, 13550 x 450 ft Secondary ILS ID = MAA Secondary ILS: MAA 109.90 Hdg: 322.5 , Flags: GS DME BC "CAT III ILS/DME 33L" *** Runway *** LEMD0152 Lat 40.484936 Long -3.576226 Alt 1999 Hdg 146 Len 13550 Wid 450 *** Runway *** LEMD0331 Lat 40.455410 Long -3.546551 Alt 1999 Hdg 326 Len 13550 Wid 450 ILS 109.90, Flags: GS DME BC Runway 15L/33R centre: N40:28:57.9162 W003:32:44.6296 1999ft Runway 15L closed for landing Runway 33R closed for landing Start 15L: N40:29:43.7218 W003:33:37.9512 1999ft Hdg: 91.4 true Computed start 15L: Lat 40.496052 Long -3.559097 Offset Threshold primary: 656 feet Computed start 33R: Lat 40.469456 Long -3.532363 Offset Threshold secondary: 3937 feet Hdg: 142.600 true (MagVar -3.000), Asphalt, 12205 x 350 ft Secondary ILS ID = MBB Secondary ILS: MBB 109.10 Hdg: 322.5 , Flags: GS DME BC "CAT III ILS/DME 33R" *** Runway *** LEMD0151 Lat 40.496052 Long -3.559097 Alt 1999 Hdg 146 Len 12205 Wid 350 *** Runway *** LEMD0332 Lat 40.469456 Long -3.532363 Alt 1999 Hdg 326 Len 12205 Wid 350 ILS 109.10, Flags: GS DME BC Runway 16L/34R centre: S80:21:20.6631 W003:34:50.0507 1999ft Runway 16L closed for landing and take-off Runway 34R closed for landing and take-off Hdg: 150.400 true (MagVar -3.000), Concrete, 11 x 11 ft Runway 16R/34L centre: S80:21:20.8899 W003:34:50.2197 1999ft Runway 16R closed for landing and take-off Runway 34L closed for landing and take-off Hdg: 158.200 true (MagVar -3.000), Concrete, 11 x 11 ft Runway 17L/35R centre: S80:21:20.8899 W003:34:50.2197 1999ft Runway 17L closed for landing and take-off Runway 35R closed for landing and take-off Hdg: 166.000 true (MagVar -3.000), Concrete, 11 x 11 ft Runway 17R/35L centre: S80:21:20.8899 W003:34:50.2197 1999ft Runway 17R closed for landing and take-off Runway 35L closed for landing and take-off Hdg: 173.800 true (MagVar -3.000), Concrete, 11 x 11 ft Runway 18L/36R centre: N40:30:59.2006 W003:33:32.9045 1999ft Runway 18L closed for take-off Runway 36R closed for take-off Computed start 18L: Lat 40.533092 Long -3.559102 Offset Threshold primary: 3281 feet Start 36R: N40:30:00.9232 W003:33:37.9256 1999ft Hdg: 79.0 true Computed start 36R: Lat 40.499798 Long -3.559178 Offset Threshold secondary: 492 feet Hdg: 180.100 true (MagVar -3.000), Asphalt, 12138 x 350 ft Primary ILS ID = IML Primary ILS: IML 111.50 Hdg: 180.1 , Flags: GS DME BC "CAT III ILS/DME 18L" *** Runway *** LEMD0181 Lat 40.533092 Long -3.559102 Alt 1999 Hdg 183 Len 12138 Wid 350 ILS 111.50, Flags: GS DME BC *** Runway *** LEMD0362 Lat 40.499798 Long -3.559178 Alt 1999 Hdg 3 Len 12138 Wid 350 Runway 18R/36L centre: N40:30:41.1894 W003:34:28.7512 1999ft Runway 18R closed for take-off Runway 36L closed for take-off Computed start 18R: Lat 40.531464 Long -3.574607 Offset Threshold primary: 4265 feet Start 36L: N40:29:30.5697 W003:34:24.6957 1999ft Hdg: 271.2 true Computed start 36L: Lat 40.491417 Long -3.574699 Offset Threshold secondary: 328 feet Hdg: 180.100 true (MagVar -3.000), Asphalt, 14600 x 400 ft Primary ILS ID = IMR Primary ILS: IMR 110.70 Hdg: 180.1 , Flags: GS DME BC "CAT III ILS/DME 18R" *** Runway *** LEMD0182 Lat 40.531464 Long -3.574607 Alt 1999 Hdg 183 Len 14600 Wid 400 ILS 110.70, Flags: GS DME BC *** Runway *** LEMD0361 Lat 40.491417 Long -3.574699 Alt 1999 Hdg 3 Len 14600 Wid 400

Share this post


Link to post
Share on other sites

The problem is that something's broken down after installing these things... FS crashes all the time, either just after loading at an airport or when I change the view... What could've happened??????I checked the reason twice and at first the module with error was G2D.DLL and the second time FE.DLL (both are in Modules folder of FS9)EDIT: I checked it a few times again and the FS crashes ONLY when I start at Barajas. It's weird because today in the morning I flew to Barajas and everything worked fine. So apparently makerwys.exe or traffic look.exe screwed something up... I deleted all the files (I think so...) related to both applications but still the same...

Share this post


Link to post
Share on other sites
The problem is that something's broken down after installing these things... FS crashes all the time, either just after loading at an airport or when I change the view... What could've happened??????I checked the reason twice and at first the module with error was G2D.DLL and the second time FE.DLL (both are in Modules folder of FS9)EDIT: I checked it a few times again and the FS crashes ONLY when I start at Barajas. It's weird because today in the morning I flew to Barajas and everything worked fine. So apparently makerwys.exe or traffic look.exe screwed something up... I deleted all the files (I think so...) related to both applications but still the same...
I think that's unlikely, I think they are both programmes that only work with Flight Simulator data, rather than write or modify anything.I'm going to take a shot in the dark and suggest you try Barajas with AI traffic turned off. You may have a faulty aircraft causing this.John

My co-pilot's name is Sid and he's a star!

http://www.adventure-unlimited.org

Share this post


Link to post
Share on other sites
I think that's unlikely, I think they are both programmes that only work with Flight Simulator data, rather than write or modify anything.I'm going to take a shot in the dark and suggest you try Barajas with AI traffic turned off. You may have a faulty aircraft causing this.John
But, as I said, the scenery was working fine in the morning... Maybe I'll try to reinstall it

Share this post


Link to post
Share on other sites

Makerwys and Traffic Look do not modify your scenery files. Traffic Look is only a real-time monitor for AI. Makerwys only creates data files used by Radar Contact and a few other applications. (Makerwys.exe should not be running with FS or any component/add-on running. It is used just to create scenery related data files for other applications.) If you added FSUIPC.dll to use traffic look make sure it is current for your FS version. That would have been the only active element you have added that would run all the time.Your first section:Airport LEMD :N40:28:20.0149 W003:33:39.3996 1999ftCity Name="Madrid"Airport Name="Barajas"in file: Scenery\EURW\scenery\AP947170.BGLis your default scenery.The next section:Area.125 "Madrid 2008_SC" (Layer=126)Local=Aerosoft\Madrid 2008_SC=============================================================================Aerosoft\Madrid 2008_SC\scenery\AF2_LEMD-SUD.bgland=============================================================================Aerosoft\Madrid 2008_SC\scenery\AF2_LEMD-SUD.bgl=============================================================================occurring again is the way that make runways works in insuring deletions are in the correct priority. If these are the only sections then I don't see any other afd (afcad) type layers that could cause problems.If your crash seems to have something to do with direction of flight you could have an ATC tuning problem where in some instances a repetition of a comm frequency among airports in sequence can cause an atc.dll crsh.I noticed that several of your pseudo runways appear more than 7.5 degrees apart. I believe that 7.3 or 7.5 degrees is the maximum spread allowed for the "STAR" system to force non-parallel runways to be simultaneously available.This might be an easier way to look at your actual runways. Makerwys created a file in your FS folder called r5.csv. Open it with Notepad and search for LEMD. Here are my rows from the Spanish Airports collection:LEMD,0150,40.484863,-3.576034,1999,145.270,13484,0,197,-3.000,40.470238,-3.561158,0,CT,CLLEMD,0181,40.490936,-3.562816,1999,182.760,12120,109.30BDG,148,-3.000,40.474316,-3.562725,2287,CT,CLLEMD,0182,40.531811,-3.574818,1999,182.740,14279,110.70BDG,197,-3.000,40.512226,-3.574701,0,CT,CLLEMD,0330,40.455612,-3.546282,1999,325.270,13484,109.90BDG,197,-3.000,40.470238,-3.561158,3445,CT,LEMD,0361,40.492641,-3.574584,1999,2.740,14279,0,197,-3.000,40.512226,-3.574701,0,,CLLEMD,0362,40.457695,-3.562633,1999,2.760,12120,110.30BG,148,-3.000,40.474316,-3.562725,3445,CT,CLThe four digit numbers indicate the runway number for the first three digits and the fourth is nothing(0), left (1), tight (2), center (3). Toward the end of each row CT is closed for take-off and CL is closed for landing. See how your looks for the way you have set your runways.Your pseudo runways are excluded from this data file.MakeRwys ReadMe.txt in your FS folder explains the data fields in the .csv files if you are interested such as what has been supplied for your localizer if present.Finally, if you register LEMD 2008 on the aerosoft.com site in the FAQ/Update section lower left of that page, you'll have access to a knowledge base and links to updates for that product.

Share this post


Link to post
Share on other sites
But, as I said, the scenery was working fine in the morning... Maybe I'll try to reinstall it
Precisely.There are two possible things that I can think of that could cause different things to happen at different times of visit too a specific location:1. Different AI traffic present2. Different time of day/season for scenery display.FE.DLL has known connections with display of AI aircraft.Hence my suggestion. Why not try it before assuming it won't help? If it is the cause, reinstalling the scenery won't help at all. If it isn't, it has only cost you a couple of minutes.John

My co-pilot's name is Sid and he's a star!

http://www.adventure-unlimited.org

Share this post


Link to post
Share on other sites
Precisely.There are two possible things that I can think of that could cause different things to happen at different times of visit too a specific location:1. Different AI traffic present2. Different time of day/season for scenery display.FE.DLL has known connections with display of AI aircraft.Hence my suggestion. Why not try it before assuming it won't help? If it is the cause, reinstalling the scenery won't help at all. If it isn't, it has only cost you a couple of minutes.John
Especially, FE.dll will always cause a crash if an AI plane texture folder and the main FS texture folder both contain the same texture file (usually it's a lightmap), but the dimensions are not the same. Might also get upset if one is DXT3 and the other 32-bit...Geoff

Share this post


Link to post
Share on other sites

I reinstalled it and everything works fine :) I have already contacted aerosoft but yet got no answer so I think I'll leave the AFCAD as it is, as it seems there's no solution :DSo thank you all very much for help :)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...