August 27, 201213 yr Commercial Member I usually go from 512, which was working on the older FSUIPC. I've tried various gates around T1, T2, T3 and T5, none seem to work though Very strange. I often start from EGLL terminal 5 (with a fictiious BA 738!), using the latest update of UK2000 EGLL Extreme, and have never once had this problem with RC. I don't understand what's different on your system, though the 6 fps shown in your pics worries me. I'm wondering if it is related to the very low frame rate and maybe RC not managing to read things properly. Srely you don't manage to fly with such a feeble frame rate? Pete There have been other complaints regarding UK2K EGLL regarding this. Have there? How odd. Not seen one before. I'll retry at EGLL again tomorrow, but as I said I've never seen this. I have frame rates of around my limit of 30 or a little below at T5, but down to perhaps 18-22 on other parts of EGLL, depending on the weather and traffic density. Regards Pete Win10: 22H2 19045.2728 CPU: 9900KS at 5.5GHz Memory: 32Gb at 3800 MHz. GPU: RTX 24Gb Titan 2 x 2160p projectors at 25Hz onto 200 FOV curved screen
August 27, 201213 yr Author It is odd, I'm sure it used to work before I reinstalled windows. 6FPS is only at Heathrow during the recording, it's usually at 10, it's up in the 30's outside of London, It's the amount of AI traffic I use, I really should drop that down.
August 27, 201213 yr Commercial Member It is odd, I'm sure it used to work before I reinstalled windows. 6FPS is only at Heathrow during the recording, it's usually at 10, it's up in the 30's outside of London, It's the amount of AI traffic I use, I really should drop that down. Hmm 10 fps wouldn't be flyable for me either. Just as a test turn off all traffic to get the frame rates right up. I'm concerned that it may simply be RC reading problems when fully loaded both reading all the aI and your plan details and may be having an error which it doesn't check for when reading the location. I actually run RC on a WideFS client so it isn't really affected by FS frame rates at all. RC should really notice errors (timeouts) on data reading, and retry, but you never know. Again, a proper RC log submitted to JD would certainly help. (But it won't help me -- I can't support RC, only FSUIPC). Regards Pete Win10: 22H2 19045.2728 CPU: 9900KS at 5.5GHz Memory: 32Gb at 3800 MHz. GPU: RTX 24Gb Titan 2 x 2160p projectors at 25Hz onto 200 FOV curved screen
August 28, 201213 yr Author Seems looking at the clouds can kill the fps, got it to 20fps by playing with the scenery sliders. But drops to about 10 when I look up a bit. But I can live with that, doesn't seem to sort Radar Contact out though Radar Contact did seem to work if I fly out of EGLL and come back in again then load it, or it did when I just tested it after doing a quick jump to EGLC and back I understand Pete, you've been a great help so far.
August 28, 201213 yr Here are other threads on this issue; http://forum.avsim.net/topic/365837-starting-rc4-makes-aircraft-jump-to-centre-of-the-filed-airport/page__hl__egll#entry2329291 http://forum.avsim.net/topic/330058-aicraft-moved-on-start-of-rc/page__hl__egll
August 28, 201213 yr One more thought to consider: The airport coordinates in the flight plan should be checked against the coordinates in the scenery to see if they are close. Some flight planners put a starting gate or other parking location in the plan that might have an effect on the discrepancy. Is the flight plan placing the aircraft into the parked position at destination? I don't run FSX so I do not know if that has any effect on setting up a flight. Open up the afd type file with ADE9X (installed for FSX) and locate the coordinates of the airport center. When RC ran makerwys as part of the scenery rebuild in your FSX folder it created a very large log file called runways.txt. There are single sections for the default scenery (APxxxx.bgl file) and then two sections for each add-on afd file. Those sections may be adjacent or separated somewhat. Each section has a line pointing to the path of the scenery folder used. For an add-on folder there should be two sections pointing tothe same add-on location. The first is a deletion section and the next is the locations of the afd elements such as runways, taxi path nodes, navaids, etc. The last instances of each type take priority and these furnish the details for the RC scenery data in r5.csv that rc uses. Make sure that these paths point to the UK2K EGLL scenery and there is no other conflicting scenery data present. For example here is a deletion section extract for a KMSP add-on: Area.063 "KMSPAirport" (Layer=64) Local=..\..\..\CommonAddonScenery\KMSPAirport ============================================================================= ..\..\..\CommonAddonScenery\KMSPAirport\scenery\AF2_KMSP.bgl ============================================================================= Deletions check for Airport KMSP: Delete all taxiways! Delete all runways and starts! *** DelBth *** KMSP0040 Lat 44.872253 Long -93.238335 Alt 841 Hdg 43 Len 10999 Wid 150 ILS 109.30, Flags: GS BC *** DelBth *** KMSP0121 Lat 44.892944 Long -93.221008 Alt 841 Hdg 119 Len 8189 Wid 150 ILS 110.70, Flags: GS DME BC *** DelBth *** KMSP0122 Lat 44.887779 Long -93.234154 Alt 841 Hdg 119 Len 9987 Wid 200 ILS 110.30, Flags: GS DME BC *** DelBth *** KMSP0220 Lat 44.893608 Long -93.208260 Alt 841 Hdg 223 Len 10999 Wid 150 ILS 110.50, Flags: GS BC *** DelBth *** KMSP0301 Lat 44.873512 Long -93.201149 Alt 841 Hdg 299 Len 9987 Wid 200 ILS 110.30, Flags: GS DME BC *** DelBth *** KMSP0302 Lat 44.881248 Long -93.193939 Alt 841 Hdg 299 Len 8189 Wid 150 ILS 110.70, Flags: GS DME BC Delete all taxiways! I highlighted what path and file was used. Here is the extract for the scenery elements: ============================================================================= ..\..\..\CommonAddonScenery\KMSPAirport\scenery\AF2_KMSP.bgl ============================================================================= Airport KMSP :N44:52:49.9652 W093:13:00.9194 841ft Country Name="United States" State Name="Minnesota" City Name="Minneapolis" Airport Name="Minneapolis-St Paul Intl" in file: ..\..\..\CommonAddonScenery\KMSPAirport\scenery\AF2_KMSP.bgl Runway 4 /22 centre: N44:52:56.2173 W093:13:27.0822 841ft Runway 4 closed for landing and take-off Runway 22 closed for landing and take-off Start 4 : N44:52:31.4357 W093:14:02.0030 841ft Hdg: 45.0T, Length 11699ft Computed start 4 : Lat 44.870926 Long -93.240188 Offset Threshold primary: 2250 feet Start 22 : N44:53:35.7708 W093:12:31.4365 841ft Hdg: 224.9T, Length 11699ft Computed start 22 : Lat 44.893639 Long -93.208191 Offset Threshold secondary: 988 feet Hdg: 44.950 true (MagVar 2.300), Concrete, 11699 x 150 ft Primary ILS ID = IAPL Primary ILS: IAPL 109.30 Hdg: 45.0 , Flags: GS "ILS 04" Secondary ILS ID = ISIJ Secondary ILS: ISIJ 110.50 Hdg: 224.9 , Flags: GS "ILS 22" *** Runway *** KMSP0040 Lat 44.870926 Long -93.240189 Alt 841 Hdg 43 Len 11699 Wid 150 ILS 109.30, Flags: GS *** Runway *** KMSP0220 Lat 44.893639 Long -93.208191 Alt 841 Hdg 223 Len 11699 Wid 150 ILS 110.50, Flags: GS Runway 12R/30L centre: N44:52:52.1033 W093:13:07.5947 841ft Start 12R: N44:53:15.1356 W093:14:00.8955 841ft Hdg: 121.4T, Length 10700ft Computed start 12R: Lat 44.888786 Long -93.236452 Offset Threshold primary: 700 feet Start 30L: N44:52:25.5399 W093:12:06.2040 841ft Hdg: 301.4T, Length 10700ft Computed start 30L: Lat 44.873497 Long -93.201093 Hdg: 121.390 true (MagVar 2.300), Concrete, 10700 x 200 ft Primary ILS ID = IHKZ Primary ILS: IHKZ 110.30 Hdg: 121.4 , Flags: GS DME "ILS/DME 12R" Secondary ILS ID = IMSP Secondary ILS: IMSP 110.30 Hdg: 301.4 , Flags: GS DME "CAT II ILS/DME 30L" *** Runway *** KMSP0122 Lat 44.888786 Long -93.236450 Alt 841 Hdg 119 Len 10700 Wid 200 ILS 110.30, Flags: GS DME *** Runway *** KMSP0301 Lat 44.873497 Long -93.201096 Alt 841 Hdg 299 Len 10700 Wid 200 ILS 110.30, Flags: GS DME Runway 12L/30R centre: N44:53:13.5483 W093:12:26.9093 841ft Start 12L: N44:53:33.7300 W093:13:13.5910 841ft Hdg: 121.4T, Length 8189ft Computed start 12L: Lat 44.892944 Long -93.221007 Start 30R: N44:52:53.3666 W093:11:40.2276 841ft Hdg: 301.4T, Length 8189ft Computed start 30R: Lat 44.881248 Long -93.193940 Hdg: 121.380 true (MagVar 2.300), Concrete, 8189 x 150 ft Primary ILS ID = IPJL Primary ILS: IPJL 110.70 Hdg: 121.4 , Flags: GS DME "ILS/DME 12L" Secondary ILS ID = IINN *** No matching ILS record - assume provided by another layer *** There were ILS matching errors. Here's a list of ILSs: ID=IBMA: Freq 110.95 Heading 350.3 (Primary), Range 1.49, "CAT III ILS/DME 35" ID=IAPL: Freq 109.30 Heading 45.0 (Primary), Range 0.44, "ILS 04" ID=IPJL: Freq 110.70 Heading 121.4 (Primary), Range 0.74, "ILS/DME 12L" ID=IMSP: Freq 110.30 Heading 301.4 (Secondary), Range 1.24, "CAT II ILS/DME 30L" ID=ISIJ: Freq 110.50 Heading 224.9 (Secondary), Range 1.75, "ILS 22" ID=IHKZ: Freq 110.30 Heading 121.4 (Primary), Range 0.96, "ILS/DME 12R" *** Runway *** KMSP0121 Lat 44.892944 Long -93.221008 Alt 841 Hdg 119 Len 8189 Wid 150 ILS 110.70, Flags: GS DME *** Runway *** KMSP0302 Lat 44.881248 Long -93.193939 Alt 841 Hdg 299 Len 8189 Wid 150 Runway 13R/31L centre: N44:49:06.1528 W093:01:14.1598 841ft Runway 13R closed for landing and take-off Runway 31L closed for landing and take-off Hdg: 129.000 true (MagVar 2.300), Concrete, 10 x 10 ft Runway 13L/31R centre: N44:49:17.2641 W093:01:29.7898 841ft Runway 13L closed for landing and take-off Runway 31R closed for landing and take-off Hdg: 136.000 true (MagVar 2.300), Concrete, 10 x 10 ft Runway 14R/32L centre: N44:49:31.7443 W093:01:25.0439 841ft Runway 14R closed for landing and take-off Runway 32L closed for landing and take-off Hdg: 143.000 true (MagVar 2.300), Concrete, 10 x 10 ft Runway 14L/32R centre: N44:49:43.9894 W093:02:08.8867 841ft Runway 14L closed for landing and take-off Runway 32R closed for landing and take-off Hdg: 150.000 true (MagVar 2.300), Concrete, 10 x 10 ft Runway 15R/33L centre: N44:49:12.8260 W093:02:07.4157 841ft Runway 15R closed for landing and take-off Runway 33L closed for landing and take-off Hdg: 157.000 true (MagVar 2.300), Concrete, 10 x 10 ft Runway 16 /34 centre: N44:50:07.3781 W093:01:45.3003 841ft Runway 16 closed for landing and take-off Runway 34 closed for landing and take-off Hdg: 164.000 true (MagVar 2.300), Concrete, 10 x 10 ft Runway 17 /35 centre: N44:52:35.6469 W093:14:21.2584 841ft Runway 17 closed for landing Runway 35 closed for take-off Start 17 : N44:53:13.5483 W093:14:30.3785 841ft Hdg: 171.0T, Length 7800ft Computed start 17 : Lat 44.887112 Long -93.241778 Start 35 : N44:51:58.4907 W093:14:12.4184 841ft Hdg: 350.3T, Length 7800ft Computed start 35 : Lat 44.866024 Long -93.236691 Hdg: 170.300 true (MagVar 2.300), Concrete, 7800 x 160 ft Secondary ILS ID = IBMA Secondary ILS: IBMA 110.95 Hdg: 350.3 , Flags: GS DME "CAT III ILS/DME 35" *** Runway *** KMSP0170 Lat 44.887112 Long -93.241776 Alt 841 Hdg 168 Len 7800 Wid 160 *** Runway *** KMSP0350 Lat 44.866024 Long -93.236694 Alt 841 Hdg 348 Len 7800 Wid 160 ILS 110.95, Flags: GS DME COM: Type=8 (APPROACH), Freq=119.30, Name="MINNEAPOLIS" Notice that in these sections the airport center coordinates are shown as well. Compare that to your flight plan. If you decide to examine the afd file with ADE the file is named in the section header.
August 28, 201213 yr Commercial Member Here are other threads on this issue; http://forum.avsim.n...ll#entry2329291 http://forum.avsim.n.../page__hl__egll One of those seems to be more about missing data for EHAM and RC plonking the aircraft at (0,0) -- solved with MakeRunways updated data. That's what I thought this current thread was about originally. The other seems to be derived from a rogue AFCAD for EGLL installed by MyTrafficX. If RC is computing airport centres by use of runway positions then it might get fooled by some of the fiddles used to get AI traffic using specific runways. "Ghost" runways to do this are somethimes a long way from the airport -- if they are short enough they'd be ignored, but there's no guarantee they will be. Seems odd for RC to check positions based on runways when the airports files provide the standard airport LAT/LON. Maybe he does it because some of those are on the edge rather than in the centre, but surely he'd use a sensible distance like 3nm or so in any case? Seems looking at the clouds can kill the fps, got it to 20fps by playing with the scenery sliders. But drops to about 10 when I look up a bit. But I can live with that, doesn't seem to sort Radar Contact out though Could you load the r4.csv file from your FSX folder into a text editor (like Notepad), and find the entries for EGLL, extract them and paste them in a repy here, please. I'd like to see exactly what data RC is using and why you get this odd thing happening and I don't, even with the same scenery. These are the lines for the FSX default EGLL (My cockpit isn't on at present so I can't access the UK2000 one, but I will this afternoon). EGLL,0091,51.477486,-0.489342,83,92.690,12786,110.30,164,-3.000,51.477581,-0.461186,1014 EGLL,0092,51.464767,-0.486783,83,92.700,11978,109.50,164,-3.000,51.464855,-0.460414,1001 EGLL,0230,51.476376,-0.431797,83,225.000,6437,0,148,-3.000,51.469814,-0.441280,0 EGLL,0271,51.464943,-0.434046,83,272.700,11978,109.50,164,-3.000,51.464855,-0.460414,0 EGLL,0272,51.477676,-0.433031,83,272.690,12786,110.30,164,-3.000,51.477581,-0.461186,0 Runway 23 isn't a runway any more of course, but MS didn't know that it seems! ;-) Regards Pete Win10: 22H2 19045.2728 CPU: 9900KS at 5.5GHz Memory: 32Gb at 3800 MHz. GPU: RTX 24Gb Titan 2 x 2160p projectors at 25Hz onto 200 FOV curved screen
August 28, 201213 yr a4.csv coordinates are built from r5.csv (copied as r4.csv to the rc\data folder) so "ghost runways" are not an issue as they are excluded from r5.csv. The OP stated the default EGLL works. I'm waiting for him to post the UK2K2 EGLL data from a4.csv and the coordinates from his flight plan for EGLL. I was not on the beta team during the design of RC3 nor RC4 so I don't know if any issues were faced and why a4.csv was calculated from the runway data and not taken directly from the afd data. If any Heathrow Extreme FSX UK2K user can post the r4.csv runway data and the a4.csv data we would have a comparison. I am also waiting for a confirmation that the last relevant sections in runways.txt point to Heathrow Extreme.
August 28, 201213 yr Commercial Member If any Heathrow Extreme FSX UK2K user can post the r4.csv runway data and the a4.csv data we would have a comparison. I'll post mine in the morning. I have Heathrow Extreme and no problems. I am also waiting for a confirmation that the last relevant sections in runways.txt point to Heathrow Extreme. Yes, indeed. I am also thinking that there's another AFD BGL at work here. Regards Pete Win10: 22H2 19045.2728 CPU: 9900KS at 5.5GHz Memory: 32Gb at 3800 MHz. GPU: RTX 24Gb Titan 2 x 2160p projectors at 25Hz onto 200 FOV curved screen
August 29, 201213 yr Commercial Member I'll post mine in the morning. I have Heathrow Extreme and no problems. Okay. As I said, RC is okay with my UK2000 Heathrow Extreme. Here are the r4.csv entries for EGLL: EGLL,0091,51.477440,-0.490358,83,91.467,13006,110.30DG,164,-1.800,51.477543,-0.461718,1190,CT, EGLL,0092,51.464764,-0.488023,83,91.520,12344,109.50DG,164,-1.800,51.464848,-0.460849,1304,,CL EGLL,0271,51.464931,-0.433674,83,271.520,12344,109.50DG,164,-1.800,51.464848,-0.460849,100,,CL EGLL,0272,51.477646,-0.433079,83,271.467,13006,110.30DG,164,-1.800,51.477543,-0.461718,180,CT, and the a4.csv: EGLL, , 51.4712 ,-0.4612835 , 1.8 , 83 , 13006 And this is the last entry in Runways.TXT file for EGLL: ============================================================================= D:\UK2000 scenery\UK2000 Heathrow xtreme\scenery\egll_AFX_UK2xTRM.bgl ============================================================================= Airport EGLL :N51:28:11.6212 W000:27:26.2798 83ft Country Name="United Kingdom" State Name="" City Name="London" Airport Name="London Heathrow" in file: D:\UK2000 scenery\UK2000 Heathrow xtreme\scenery\egll_AFX_UK2xTRM.bgl Runway 9R/27L centre: N51:27:53.4479 W000:27:39.0546 83ft Runway 9R closed for landing Runway 27L closed for landing Start 9R: N51:27:53.2212 W000:29:03.6987 83ft Hdg: 89.7T, Length 12344ft Computed start 9R: Lat 51.464764 Long -0.488023 Offset Threshold primary: 1304 feet Start 27L: N51:27:53.7395 W000:26:06.8258 83ft Hdg: 269.7T, Length 12344ft Computed start 27L: Lat 51.464931 Long -0.433674 Offset Threshold secondary: 100 feet Hdg: 89.720 true (MagVar -1.800), Asphalt, 12344 x 164 ft Primary ILS ID = IBB Primary ILS: IBB 109.50 Hdg: 89.7 , Flags: GS DME "ILS/DME 09R" Secondary ILS ID = ILL Secondary ILS: ILL 109.50 Hdg: 269.7 , Flags: GS DME "ILS/DME 27L" *** Runway *** EGLL0092 Lat 51.464764 Long -0.488023 Alt 83 Hdg 92 Len 12344 Wid 164 ILS 109.50, Flags: GS DME *** Runway *** EGLL0271 Lat 51.464931 Long -0.433674 Alt 83 Hdg 272 Len 12344 Wid 164 ILS 109.50, Flags: GS DME Runway 9L/27R centre: N51:28:39.1563 W000:27:42.1865 83ft Runway 9L closed for take-off Runway 27R closed for take-off Start 9L: N51:28:38.8648 W000:29:10.4211 83ft Hdg: 89.7T, Length 13006ft Computed start 9L: Lat 51.477440 Long -0.490358 Offset Threshold primary: 1190 feet Start 27R: N51:28:39.4803 W000:26:05.2344 83ft Hdg: 269.7T, Length 13006ft Computed start 27R: Lat 51.477646 Long -0.433079 Offset Threshold secondary: 180 feet Hdg: 89.667 true (MagVar -1.800), Asphalt, 13006 x 164 ft Primary ILS ID = IAA Primary ILS: IAA 110.30 Hdg: 89.7 , Flags: GS DME "ILS/DME 09L" Secondary ILS ID = IRR Secondary ILS: IRR 110.30 Hdg: 269.7 , Flags: GS DME "ILS/DME 27R" *** Runway *** EGLL0091 Lat 51.477440 Long -0.490358 Alt 83 Hdg 91 Len 13006 Wid 164 ILS 110.30, Flags: GS DME *** Runway *** EGLL0272 Lat 51.477646 Long -0.433079 Alt 83 Hdg 271 Len 13006 Wid 164 ILS 110.30, Flags: GS DME Regards Pete Win10: 22H2 19045.2728 CPU: 9900KS at 5.5GHz Memory: 32Gb at 3800 MHz. GPU: RTX 24Gb Titan 2 x 2160p projectors at 25Hz onto 200 FOV curved screen
August 30, 201213 yr Author Okay. As I said, RC is okay with my UK2000 Heathrow Extreme. Here are the r4.csv entries for EGLL: EGLL,0091,51.477440,-0.490358,83,91.467,13006,110.30DG,164,-1.800,51.477543,-0.461718,1190,CT, EGLL,0092,51.464764,-0.488023,83,91.520,12344,109.50DG,164,-1.800,51.464848,-0.460849,1304,,CL EGLL,0271,51.464931,-0.433674,83,271.520,12344,109.50DG,164,-1.800,51.464848,-0.460849,100,,CL EGLL,0272,51.477646,-0.433079,83,271.467,13006,110.30DG,164,-1.800,51.477543,-0.461718,180,CT, Mine matches that EGLL,0091,51.477440,-0.490358,83,91.467,13006,110.30DG,164,-1.800,51.477543,-0.461718,1190,CT, EGLL,0092,51.464764,-0.488023,83,91.520,12344,109.50DG,164,-1.800,51.464848,-0.460849,1304,,CL EGLL,0271,51.464931,-0.433674,83,271.520,12344,109.50DG,164,-1.800,51.464848,-0.460849,100,,CL EGLL,0272,51.477646,-0.433079,83,271.467,13006,110.30DG,164,-1.800,51.477543,-0.461718,180,CT, and the a4.csv: EGLL, , 51.4712 ,-0.4612835 , 1.8 , 83 , 13006 Here's mine: EGLL, , 51.4712 ,-0.4612835 , 1.8 , 83 , 13006 And this is the last entry in Runways.TXT file for EGLL: ============================================================================= D:\UK2000 scenery\UK2000 Heathrow xtreme\scenery\egll_AFX_UK2xTRM.bgl ============================================================================= Airport EGLL :N51:28:11.6212 W000:27:26.2798 83ft Country Name="United Kingdom" State Name="" City Name="London" Airport Name="London Heathrow" in file: D:\UK2000 scenery\UK2000 Heathrow xtreme\scenery\egll_AFX_UK2xTRM.bgl Runway 9R/27L centre: N51:27:53.4479 W000:27:39.0546 83ft Runway 9R closed for landing Runway 27L closed for landing Start 9R: N51:27:53.2212 W000:29:03.6987 83ft Hdg: 89.7T, Length 12344ft Computed start 9R: Lat 51.464764 Long -0.488023 Offset Threshold primary: 1304 feet Start 27L: N51:27:53.7395 W000:26:06.8258 83ft Hdg: 269.7T, Length 12344ft Computed start 27L: Lat 51.464931 Long -0.433674 Offset Threshold secondary: 100 feet Hdg: 89.720 true (MagVar -1.800), Asphalt, 12344 x 164 ft Primary ILS ID = IBB Primary ILS: IBB 109.50 Hdg: 89.7 , Flags: GS DME "ILS/DME 09R" Secondary ILS ID = ILL Secondary ILS: ILL 109.50 Hdg: 269.7 , Flags: GS DME "ILS/DME 27L" *** Runway *** EGLL0092 Lat 51.464764 Long -0.488023 Alt 83 Hdg 92 Len 12344 Wid 164 ILS 109.50, Flags: GS DME *** Runway *** EGLL0271 Lat 51.464931 Long -0.433674 Alt 83 Hdg 272 Len 12344 Wid 164 ILS 109.50, Flags: GS DME Runway 9L/27R centre: N51:28:39.1563 W000:27:42.1865 83ft Runway 9L closed for take-off Runway 27R closed for take-off Start 9L: N51:28:38.8648 W000:29:10.4211 83ft Hdg: 89.7T, Length 13006ft Computed start 9L: Lat 51.477440 Long -0.490358 Offset Threshold primary: 1190 feet Start 27R: N51:28:39.4803 W000:26:05.2344 83ft Hdg: 269.7T, Length 13006ft Computed start 27R: Lat 51.477646 Long -0.433079 Offset Threshold secondary: 180 feet Hdg: 89.667 true (MagVar -1.800), Asphalt, 13006 x 164 ft Primary ILS ID = IAA Primary ILS: IAA 110.30 Hdg: 89.7 , Flags: GS DME "ILS/DME 09L" Secondary ILS ID = IRR Secondary ILS: IRR 110.30 Hdg: 269.7 , Flags: GS DME "ILS/DME 27R" *** Runway *** EGLL0091 Lat 51.477440 Long -0.490358 Alt 83 Hdg 91 Len 13006 Wid 164 ILS 110.30, Flags: GS DME *** Runway *** EGLL0272 Lat 51.477646 Long -0.433079 Alt 83 Hdg 271 Len 13006 Wid 164 ILS 110.30, Flags: GS DME Regards Pete This is mine from that file ============================================================================= C:\FSX\UK2000 scenery\UK2000 Heathrow Xtreme\scenery\egll_AFX_UK2xTRM.bgl ============================================================================= Airport EGLL :N51:28:11.6212 W000:27:26.2798 83ft Country Name="United Kingdom" State Name="" City Name="London" Airport Name="London Heathrow" in file: C:\FSX\UK2000 scenery\UK2000 Heathrow Xtreme\scenery\egll_AFX_UK2xTRM.bgl Runway 9R/27L centre: N51:27:53.4479 W000:27:39.0546 83ft Runway 9R closed for landing Runway 27L closed for landing Start 9R: N51:27:53.2212 W000:29:03.6987 83ft Hdg: 89.7T, Length 12344ft Computed start 9R: Lat 51.464764 Long -0.488023 Offset Threshold primary: 1304 feet Start 27L: N51:27:53.7395 W000:26:06.8258 83ft Hdg: 269.7T, Length 12344ft Computed start 27L: Lat 51.464931 Long -0.433674 Offset Threshold secondary: 100 feet Hdg: 89.720 true (MagVar -1.800), Asphalt, 12344 x 164 ft Primary ILS ID = IBB Primary ILS: IBB 109.50 Hdg: 89.7 , Flags: GS DME "ILS/DME 09R" Secondary ILS ID = ILL Secondary ILS: ILL 109.50 Hdg: 269.7 , Flags: GS DME "ILS/DME 27L" *** Runway *** EGLL0092 Lat 51.464764 Long -0.488023 Alt 83 Hdg 92 Len 12344 Wid 164 ILS 109.50, Flags: GS DME *** Runway *** EGLL0271 Lat 51.464931 Long -0.433674 Alt 83 Hdg 272 Len 12344 Wid 164 ILS 109.50, Flags: GS DME Runway 9L/27R centre: N51:28:39.1563 W000:27:42.1865 83ft Runway 9L closed for take-off Runway 27R closed for take-off Start 9L: N51:28:38.8648 W000:29:10.4211 83ft Hdg: 89.7T, Length 13006ft Computed start 9L: Lat 51.477440 Long -0.490358 Offset Threshold primary: 1190 feet Start 27R: N51:28:39.4803 W000:26:05.2344 83ft Hdg: 269.7T, Length 13006ft Computed start 27R: Lat 51.477646 Long -0.433079 Offset Threshold secondary: 180 feet Hdg: 89.667 true (MagVar -1.800), Asphalt, 13006 x 164 ft Primary ILS ID = IAA Primary ILS: IAA 110.30 Hdg: 89.7 , Flags: GS DME "ILS/DME 09L" Secondary ILS ID = IRR Secondary ILS: IRR 110.30 Hdg: 269.7 , Flags: GS DME "ILS/DME 27R" *** Runway *** EGLL0091 Lat 51.477440 Long -0.490358 Alt 83 Hdg 91 Len 13006 Wid 164 ILS 110.30, Flags: GS DME *** Runway *** EGLL0272 Lat 51.477646 Long -0.433079 Alt 83 Hdg 271 Len 13006 Wid 164 ILS 110.30, Flags: GS DME
August 30, 201213 yr Author Ok this is just bizarre, it now seems to be working fine. I'm just confused. Scratch that, still not working I think I've gotten it fixed. Need to wait for the full cold and dark on AirbusX to kick in and the FPS to get up to 20. If I start RC straight off when the FPS is ~10 it seems to cause the issue.
August 30, 201213 yr Commercial Member I think I've gotten it fixed. Need to wait for the full cold and dark on AirbusX to kick in and the FPS to get up to 20. If I start RC straight off when the FPS is ~10 it seems to cause the issue. From what we discussed earlier I thought it must be something to do with performance. Probably RC reads are timing out and it is just processing the zeroes it would have because the data didn't arrive in time. Evidently either it doesn't do any retries or checks for errors, or it really is getting held off for over 2 seconds, at times (the default interface library timeout, assuming RC is actually using the default library). I did suggest trying to get the frame rates up earlier, if you recall. Regards Pete Win10: 22H2 19045.2728 CPU: 9900KS at 5.5GHz Memory: 32Gb at 3800 MHz. GPU: RTX 24Gb Titan 2 x 2160p projectors at 25Hz onto 200 FOV curved screen
August 30, 201213 yr Author It's better than it was, it wasn't working before I tweaked my scenery sliders. Thanks for your help Pete, just need to remember to wait 10 seconds after cold and dark is clicked, before hitting the start button
August 30, 201213 yr Not familiar with the Airbus model but in the PMDG legacy (FS9) B737NG series I usually minimize RC (before start), and a weather app (before activating), then load up FS with the almost C&D 737, after a minute activate the weather app, and then prep the systems/FMC entries as much as possible except for the runway data. By that time RC can start and look at the ai behavior and give you the runway assignment so you can finish prepping the FMC performance entries (departure weather) and change the anticipated runway to the assigned runway (on the 737 this causes a need to refresh the V speeds). The point is you by the time you activate RC enough time with initial prepping of the aircraft should allow performance to stabilize.
Create an account or sign in to comment