GHD

My mother used to say "I want, never gets".

They are in the "Learning Centre":

Google is your friend: https://alaska.guide/Locale/Denali-Base-Camp But you will be very disappointed with the FSX default scenery: George

Oops, yes, you are correct. But, we use miles and mph on the roads. .NM and knots in the air and at sea.

In the UK, we use Imperal Gallons!

Can someone explain the problem with sloped runways in FSX/P3D? The only limitation is that AI can't use them. George

And it wouldn't work 😄

APX23260.bgl 0203

Thank you Luke, that was it 🙄 George

Thanks Charlie, The engine and flap sounds are ok. It is only ATC and the responses are not being displayed in the ATC window. I do have a file backup of FSX but restoring the files made no difference. I also have a working system on my other (W10) machine from which I could copy files. I need to know which files output to the ATC window. George

The ATC window opens and I can tune traffic or ground, but I don't get any output: Announce clear: top exotic girl names No display or sound. Select runway: Still no sound and no sound from AI. Any ideas?

Select an area. Click on MoveUup or MoveDdown. Press <return> to repeat.

You need to start the second leg from EGUY not EGUN.

Thanks Oliver, It will still work using DLL.XML. However, I needed to delete the SDK directory tree before installing so that it created the new TrafficToolbox folder.

Has anyone been able to run Traffic Toolbox? If so, how did you do it?

Random;y I get the following crashes. Initially I thoght it was due to autogen, but the latest was with autogen off. The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {7022A3B3-D004-4F52-AF11-E9E987FEE25F} and APPID {ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D} to the user MY-W10\Home SID (S-1-5-21-1331579449-1637342475-3560807425-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000041cb8b7f, 0x0000000000000002, 0x0000000000000000, 0xfffff8011f17a35a). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 8d6fb8a5-7182-4cca-9781-d9dcc3ef2dfa. ?Version=1 EventType=BlueScreen EventTime=131989401703934875 ReportType=4 Consent=1 ReportStatus=2049 ReportIdentifier=b539deee-be8b-499e-a7d9-55faa1e89a6d IntegratorReportIdentifier=8d6fb8a5-7182-4cca-9781-d9dcc3ef2dfa Wow64Host=34404 NsAppName=BlueScreen OriginalFilename=WerFault.exe AppSessionGuid=00000000-0000-0000-0000-000000000000 BootId=40 IsFatal=4294967295 EtwNonCollectReason=1 Response.type=4 Sig[0].Name=Code Sig[0].Value=a Sig[1].Name=Parameter 1 Sig[1].Value=41cb8b7f Sig[2].Name=Parameter 2 Sig[2].Value=2 Sig[3].Name=Parameter 3 Sig[3].Value=0 Sig[4].Name=Parameter 4 Sig[4].Value=fffff8011f17a35a Sig[5].Name=OS version Sig[5].Value=10_0_17763 Sig[6].Name=Service Pack Sig[6].Value=0_0 Sig[7].Name=Product Sig[7].Value=256_1 DynamicSig[1].Name=OS Version DynamicSig[1].Value=10.0.17763.2.0.0.256.48 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=2057 OsInfo[0].Key=vermaj OsInfo[0].Value=10 OsInfo[1].Key=vermin OsInfo[1].Value=0 OsInfo[2].Key=verbld OsInfo[2].Value=17763 OsInfo[3].Key=ubr OsInfo[3].Value=379 OsInfo[4].Key=versp OsInfo[4].Value=0 OsInfo[5].Key=arch OsInfo[5].Value=9 OsInfo[6].Key=lcid OsInfo[6].Value=2057 OsInfo[7].Key=geoid OsInfo[7].Value=242 OsInfo[8].Key=sku OsInfo[8].Value=48 OsInfo[9].Key=domain OsInfo[9].Value=0 OsInfo[10].Key=prodsuite OsInfo[10].Value=256 OsInfo[11].Key=ntprodtype OsInfo[11].Value=1 OsInfo[12].Key=platid OsInfo[12].Value=10 OsInfo[13].Key=sr OsInfo[13].Value=0 OsInfo[14].Key=tmsi OsInfo[14].Value=36917 OsInfo[15].Key=osinsty OsInfo[15].Value=3 OsInfo[16].Key=iever OsInfo[16].Value=11.379.17763.0-11.0.115 OsInfo[17].Key=portos OsInfo[17].Value=0 OsInfo[18].Key=ram OsInfo[18].Value=32708 OsInfo[19].Key=svolsz OsInfo[19].Value=476 OsInfo[20].Key=wimbt OsInfo[20].Value=0 OsInfo[21].Key=blddt OsInfo[21].Value=180914 OsInfo[22].Key=bldtm OsInfo[22].Value=1434 OsInfo[23].Key=bldbrch OsInfo[23].Value=rs5_release OsInfo[24].Key=bldchk OsInfo[24].Value=0 OsInfo[25].Key=wpvermaj OsInfo[25].Value=0 OsInfo[26].Key=wpvermin OsInfo[26].Value=0 OsInfo[27].Key=wpbuildmaj OsInfo[27].Value=0 OsInfo[28].Key=wpbuildmin OsInfo[28].Value=0 OsInfo[29].Key=osver OsInfo[29].Value=10.0.17763.379.amd64fre.rs5_release.180914-1434 OsInfo[30].Key=buildflightid OsInfo[30].Value=35E7721B-DA04-440A-8553-A2A4C4CC55FE.1 OsInfo[31].Key=edition OsInfo[31].Value=Professional OsInfo[32].Key=ring OsInfo[32].Value=Retail OsInfo[33].Key=expid OsInfo[33].Value=RS:2B96 OsInfo[34].Key=containerid OsInfo[35].Key=containertype OsInfo[36].Key=edu OsInfo[36].Value=0 File[0].CabName=040519-32875-01.dmp File[0].Path=040519-32875-01.dmp File[0].Flags=851970 File[0].Type=2 File[0].Original.Path=\\?\C:\WINDOWS\Minidump\040519-32875-01.dmp File[1].CabName=sysdata.xml File[1].Path=WER-32968-0.sysdata.xml File[1].Flags=851970 File[1].Type=5 File[1].Original.Path=\\?\C:\WINDOWS\TEMP\WER-32968-0.sysdata.xml File[2].CabName=WERInternalMetadata.xml File[2].Path=WER88F6.tmp.WERInternalMetadata.xml File[2].Flags=851970 File[2].Type=5 File[2].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER88F6.tmp.WERInternalMetadata.xml File[3].CabName=WERInternalRequest.xml File[3].Path=WER88F7.tmp.xml File[3].Flags=851970 File[3].Type=5 File[3].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER88F7.tmp.xml File[4].CabName=memory.csv File[4].Path=WER8906.tmp.csv File[4].Flags=589826 File[4].Type=5 File[4].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8906.tmp.csv File[5].CabName=sysinfo.txt File[5].Path=WER8916.tmp.txt File[5].Flags=589826 File[5].Type=5 File[5].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8916.tmp.txt File[6].CabName=Report.zip File[6].Path=Report.zip File[6].Flags=65536 File[6].Type=11 File[6].Original.Path=\\?\C:\WINDOWS\system32\Report.zip Ns[0].Name=stopcode Ns[0].Value=0000000A Ns[1].Name=p1 Ns[1].Value=0000000041CB8B7F Ns[2].Name=p2 Ns[2].Value=0000000000000002 Ns[3].Name=p3 Ns[3].Value=0000000000000000 Ns[4].Name=p4 Ns[4].Value=FFFFF8011F17A35A FriendlyEventName=Shut down unexpectedly ConsentKey=BlueScreen AppName=Windows AppPath=C:\Windows\System32\WerFault.exe NsPartner=windows NsGroup=windows8 ApplicationIdentity=00000000000000000000000000000000 MetadataHash=2129941258 Any idea?

Thanks Jim. George

Can you please supply a link? George

Occasionally while running P3D I get a CTD with the following event log: The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID Windows.SecurityCenter.WscDataProtection and APPID Unavailable to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Any ideas? George

Deleted.

Why not use the in-built W10 "Optimise"? It uses Trim for SSDs and defrag for rotating disks.

FSX has several photographic areas, see FSX\Scenery\Cities\\Berlin\Scenery

No, AI take-off is hard coded.

You can create exclusion polygons to exclude parts of the default hydro-polygon.

You need to exclude the default hydro-polygons and re-define them to fit the photo textures.