Finnerz

I haven't run plan-g on my setup yet and I'm by no means an expert on any of these things, but it sounds like you have pause on task switch ticked somewhere in setting (it might be in general setting but I really don't know) - if you deselect this the when you switch to a different program like plan-g FSX will continue flying, whether you're in windowed mode or full screen mode. I think it's normal not to have plan-g listed in the FSX menus because it runs as a separate program (just like an internet browser or email program) that links to FSX as opposed to running inside the sim. This means that just like when you're in you're in a normal program and you switch to another one which "covers up" the first one, switching to FSX will cover up anything else "underneath" it (unless you put it in windowed mode and then resize the window so you can see plan-g behind it, probably not a great idea since you'll end up with FSX running in a smaller window than you'd probably want). As to whether there's a similar program that actually runs within FSX allowing you to view it as a pop up in FSX like a 2D panel, I couldn't say. However, I expect this wouldn't be as good as having plan-g on another monitor or, better still, another computer because being inside FSX, such a program would use up resources that could be put into other in-sim things, and might reduce performance a little - not great because FSX is hungry enough as it is, even on a monster PC. Like I say, I'm no expert but hopefully this helps a bit and I expect someone will be good enough to correct me if I'm wrong on anything. Good luck and let me know if anything I said is unclear. Finlay

I also often find myself wondering about some of the people my age, so have been reading this topic with interest. I have just finished state school in the UK and am going on to a good university, as are a lot of people in my year and I can see both the side for education being to blame for the situation under discussion, but also the people. While my school isn't in a particularly rich area (in fact, more the opposite), it has a very strong, almost old fashioned attitude. In our recent prize giving, the guest of honour was the first headmaster and he said how the school was set up in the time of grammar schools being abolished, and how while most schools were trying to cast out all the principles involved with that style of learing, they tried to make "grammar school opportunities for everyone". And I think it has worked. I realise a lot of people aren't that lucky and just looking at some of the schools in the neighbouring, richer area I can see what might be the stem of a lot of the problems we're seeing. But on the other hand, there are these opportunities out there, even if (like me) you don't go to a public school. I often wonder why people have these opportunities but don't seem to take them; why, like others have said, there seems to be a lack of motivation in some people my age. And while I have nothing against people who are into celebrities and sports, why you are considered wrong or boring for not going with the crowd. It's certainly a tough question! Finlay

Thanks for the replies. I had a feeling it might be something like this. Is the EAD basic account something anyone can set up to look at the charts? Thanks again, Finlay

Hello all First of all, before anyone says anything I want to make it clear that I am aware that this is a much discussed topic, and the answer I'm looking for is probably out there; I just can't find it! I have been doing a lot of UK domestic flights since I got FSX but have now started doing more European flights since joining a virtual airline. While flying in the UK, I have been enjoying clear and seemingly complete airport charts from NATS, namely at http://www.nats-uk.ead-it.com/public/index.php%3Foption=com_content&task=blogcategory&id=6&Itemid=13.html. However, for general European charts, I haven't been able to find anything this good. I have been mainly using charts.aero, but haven't found the charts as easy to use, or as complete - for EBBR (http://charts.aero/airport/EBBR) I haven't found a docking guide(s) that will cover the whole airport. Also looking at the chart numbers there seem to be gaps. Today I also found the Eurocontrol EAD website - http://www.ead.eurocontrol.int/eadcms/eadsite/index.html - through the forum but haven't tried it yet. What I was wondering is whether any of these charts are official, i.e. used in the real world, even if they are out of date. Many thanks, and again sorry for bringing this up yet again, Finlay Waller

Fantastic. I'll download the dll and check my .net framework later on today. Thank you again for all your help, Finlay Waller

Thank you very much for your quick response. Unfortunately I now seem a bit of an idiot - after two days last week of the continual error with the plane and only just getting round to putting up a post today, I have just tried the PAD original and virtual airline versions for a start up to shut down airport circuit flight with no problems whatsoever. I really am sorry for bringing up something that appears to have resolved itself. In case it returns though, I haven't got uiautomationcore.dll installed, and would like to know the best place to get it from (I'm worried about viruses if I just google it). I installed AppCrashView and looking at the last of the crashes before I gave up I got this: "Version=1 EventType=APPCRASH EventTime=130239078905957031 ReportType=2 Consent=1 UploadTime=130239078910654296 ReportIdentifier=cfb0eac0-1fb3-11e3-ab90-002522e25e22 IntegratorReportIdentifier=cfb0eabf-1fb3-11e3-ab90-002522e25e22 WOW64=1 Response.BucketId=3827804616 Response.BucketTable=1 Response.type=4 Sig[0].Name=Application Name Sig[0].Value=fsx.exe Sig[1].Name=Application Version Sig[1].Value=10.0.61637.0 Sig[2].Name=Application Timestamp Sig[2].Value=46fadb14 Sig[3].Name=Fault Module Name Sig[3].Value=ntdll.dll Sig[4].Name=Fault Module Version Sig[4].Value=6.1.7601.18229 Sig[5].Name=Fault Module Timestamp Sig[5].Value=51fb1072 Sig[6].Name=Exception Code Sig[6].Value=c0000005 Sig[7].Name=Exception Offset Sig[7].Value=000337a2 DynamicSig[1].Name=OS Version DynamicSig[1].Value=6.1.7601.2.1.0.256.48 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=2057 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=0a9e DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=0a9e372d3b4ad19135b953a78882e789 DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=0a9e DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=0a9e372d3b4ad19135b953a78882e789 UI[2]=C:\MSFS\Microsoft Flight Simulator X\fsx.exe UI[3]=Microsoft Flight Simulator® has stopped working UI[4]=Windows can check online for a solution to the problem. UI[5]=Check online for a solution and close the program UI[6]=Check online for a solution later and close the program UI[7]=Close the program LoadedModule[0]=C:\MSFS\Microsoft Flight Simulator X\fsx.exe LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll LoadedModule[2]=C:\Windows\syswow64\kernel32.dll LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll LoadedModule[4]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll LoadedModule[7]=C:\Windows\syswow64\GDI32.dll LoadedModule[8]=C:\Windows\syswow64\USER32.dll LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll LoadedModule[14]=C:\Windows\syswow64\LPK.dll LoadedModule[15]=C:\Windows\syswow64\USP10.dll LoadedModule[16]=C:\Windows\syswow64\SHLWAPI.dll LoadedModule[17]=C:\Windows\syswow64\ole32.dll LoadedModule[18]=C:\Windows\system32\apphelp.dll LoadedModule[19]=C:\Windows\AppPatch\AcGenral.DLL LoadedModule[20]=C:\Windows\system32\UxTheme.dll LoadedModule[21]=C:\Windows\system32\WINMM.dll LoadedModule[22]=C:\Windows\system32\samcli.dll LoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dll LoadedModule[24]=C:\Windows\system32\MSACM32.dll LoadedModule[25]=C:\Windows\system32\VERSION.dll LoadedModule[26]=C:\Windows\syswow64\SHELL32.dll LoadedModule[27]=C:\Windows\system32\sfc.dll LoadedModule[28]=C:\Windows\system32\sfc_os.DLL LoadedModule[29]=C:\Windows\system32\USERENV.dll LoadedModule[30]=C:\Windows\system32\profapi.dll LoadedModule[31]=C:\Windows\system32\dwmapi.dll LoadedModule[32]=C:\Windows\syswow64\SETUPAPI.dll LoadedModule[33]=C:\Windows\syswow64\CFGMGR32.dll LoadedModule[34]=C:\Windows\syswow64\DEVOBJ.dll LoadedModule[35]=C:\Windows\syswow64\urlmon.dll LoadedModule[36]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll LoadedModule[37]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll LoadedModule[38]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll LoadedModule[39]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll LoadedModule[40]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll LoadedModule[41]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll LoadedModule[42]=C:\Windows\syswow64\normaliz.DLL LoadedModule[43]=C:\Windows\syswow64\iertutil.dll LoadedModule[44]=C:\Windows\syswow64\WININET.dll LoadedModule[45]=C:\Windows\system32\MPR.dll LoadedModule[46]=C:\Windows\AppPatch\AcLayers.DLL LoadedModule[47]=C:\Windows\system32\WINSPOOL.DRV LoadedModule[48]=C:\Windows\AppPatch\AcSpecfc.DLL LoadedModule[49]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\COMCTL32.dll LoadedModule[50]=C:\Windows\system32\mscms.dll LoadedModule[51]=C:\Windows\system32\DDRAW.dll LoadedModule[52]=C:\Windows\system32\DCIMAN32.dll LoadedModule[53]=C:\Windows\syswow64\COMDLG32.dll LoadedModule[54]=C:\Windows\syswow64\IMM32.dll LoadedModule[55]=C:\Windows\syswow64\MSCTF.dll LoadedModule[56]=C:\Windows\syswow64\WS2_32.dll LoadedModule[57]=C:\Windows\syswow64\NSI.dll LoadedModule[58]=C:\Windows\system32\msi.dll LoadedModule[59]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL LoadedModule[60]=C:\MSFS\Microsoft Flight Simulator X\language.dll LoadedModule[61]=C:\MSFS\Microsoft Flight Simulator X\API.DLL LoadedModule[62]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll LoadedModule[63]=C:\MSFS\Microsoft Flight Simulator X\ablscpt.dll LoadedModule[64]=C:\MSFS\Microsoft Flight Simulator X\flight.dll LoadedModule[65]=C:\MSFS\Microsoft Flight Simulator X\ai_player.dll LoadedModule[66]=C:\MSFS\Microsoft Flight Simulator X\acontain.dll LoadedModule[67]=C:\MSFS\Microsoft Flight Simulator X\controls.dll LoadedModule[68]=C:\Windows\system32\DINPUT8.dll LoadedModule[69]=C:\MSFS\Microsoft Flight Simulator X\fsui.dll LoadedModule[70]=C:\MSFS\Microsoft Flight Simulator X\atc.dll LoadedModule[71]=C:\MSFS\Microsoft Flight Simulator X\facilities.dll LoadedModule[72]=C:\MSFS\Microsoft Flight Simulator X\demo.dll LoadedModule[73]=C:\MSFS\Microsoft Flight Simulator X\main.dll LoadedModule[74]=C:\MSFS\Microsoft Flight Simulator X\fe.dll LoadedModule[75]=C:\MSFS\Microsoft Flight Simulator X\util.dll LoadedModule[76]=C:\MSFS\Microsoft Flight Simulator X\simprop.dll LoadedModule[77]=C:\MSFS\Microsoft Flight Simulator X\g2d.dll LoadedModule[78]=C:\Windows\system32\d3dx9_34.dll LoadedModule[79]=C:\Windows\system32\d3dx10_34.dll LoadedModule[80]=C:\Windows\system32\d3d9.dll LoadedModule[81]=C:\Windows\system32\d3d8thk.dll LoadedModule[82]=C:\MSFS\Microsoft Flight Simulator X\g3d.dll LoadedModule[83]=C:\MSFS\Microsoft Flight Simulator X\panels.dll LoadedModule[84]=C:\MSFS\Microsoft Flight Simulator X\multiplayer.dll LoadedModule[85]=C:\MSFS\Microsoft Flight Simulator X\ui.dll LoadedModule[86]=C:\MSFS\Microsoft Flight Simulator X\sound.dll LoadedModule[87]=C:\MSFS\Microsoft Flight Simulator X\sim1.dll LoadedModule[88]=C:\MSFS\Microsoft Flight Simulator X\simscheduler.dll LoadedModule[89]=C:\MSFS\Microsoft Flight Simulator X\visualfx.dll LoadedModule[90]=C:\MSFS\Microsoft Flight Simulator X\window.dll LoadedModule[91]=C:\MSFS\Microsoft Flight Simulator X\terrain.dll LoadedModule[92]=C:\MSFS\Microsoft Flight Simulator X\weather.dll LoadedModule[93]=C:\Windows\system32\DSOUND.dll LoadedModule[94]=C:\Windows\system32\POWRPROF.dll LoadedModule[95]=C:\MSFS\Microsoft Flight Simulator X\symmap.dll LoadedModule[96]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18120_none_72d2e82386681b36\gdiplus.dll LoadedModule[97]=C:\Windows\system32\MSIMG32.dll LoadedModule[98]=C:\MSFS\Microsoft Flight Simulator X\xuipc.dll LoadedModule[99]=C:\MSFS\Microsoft Flight Simulator X\livingwater.dll LoadedModule[100]=C:\MSFS\Microsoft Flight Simulator X\fs-traffic.dll LoadedModule[101]=C:\MSFS\Microsoft Flight Simulator X\gps.dll LoadedModule[102]=C:\Windows\system32\MSWSOCK.dll LoadedModule[103]=C:\Windows\system32\SHFOLDER.dll LoadedModule[104]=C:\Windows\system32\CRYPTSP.dll LoadedModule[105]=C:\Windows\system32\rsaenh.dll LoadedModule[106]=C:\Windows\syswow64\WINTRUST.dll LoadedModule[107]=C:\Windows\syswow64\CRYPT32.dll LoadedModule[108]=C:\Windows\syswow64\MSASN1.dll LoadedModule[109]=C:\Windows\syswow64\CLBCatQ.DLL LoadedModule[110]=C:\Windows\system32\wbem\wbemprox.dll LoadedModule[111]=C:\Windows\system32\wbemcomn.dll LoadedModule[112]=C:\Windows\system32\RpcRtRemote.dll LoadedModule[113]=C:\Windows\system32\wbem\wbemsvc.dll LoadedModule[114]=C:\Windows\system32\wbem\fastprox.dll LoadedModule[115]=C:\Windows\system32\NTDSAPI.dll LoadedModule[116]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL LoadedModule[117]=C:\Windows\system32\dxgi.dll LoadedModule[118]=C:\Windows\system32\d3d11.dll LoadedModule[119]=C:\Windows\system32\aticfx32.dll LoadedModule[120]=C:\Windows\system32\atiu9pag.dll LoadedModule[121]=C:\Windows\system32\atiumdag.dll LoadedModule[122]=C:\Windows\system32\atiumdva.dll LoadedModule[123]=C:\Windows\system32\atiuxpag.dll LoadedModule[124]=C:\Windows\system32\D3DCompiler_34.dll LoadedModule[125]=C:\Windows\system32\WindowsCodecs.dll LoadedModule[126]=C:\Windows\system32\d3d10_1.dll LoadedModule[127]=C:\Windows\system32\d3d10_1core.dll LoadedModule[128]=C:\Windows\SysWOW64\dxdiagn.dll LoadedModule[129]=C:\Windows\SysWOW64\d3d10.dll LoadedModule[130]=C:\Windows\SysWOW64\d3d10core.dll LoadedModule[131]=C:\Windows\system32\winbrand.dll LoadedModule[132]=C:\Windows\system32\WTSAPI32.DLL LoadedModule[133]=C:\Windows\system32\WINSTA.dll LoadedModule[134]=C:\Windows\SysWOW64\gameux.dll LoadedModule[135]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll LoadedModule[136]=C:\Windows\SysWOW64\XmlLite.dll LoadedModule[137]=C:\Windows\SysWOW64\wer.dll LoadedModule[138]=C:\Windows\System32\Wpc.dll LoadedModule[139]=C:\Windows\System32\wevtapi.dll LoadedModule[140]=C:\Windows\System32\msxml6.dll LoadedModule[141]=C:\Windows\system32\SAMLIB.dll LoadedModule[142]=C:\Windows\system32\netutils.dll LoadedModule[143]=C:\Windows\system32\uiautomationcore.dll LoadedModule[144]=C:\Windows\syswow64\PSAPI.DLL LoadedModule[145]=C:\Windows\system32\OLEACC.dll LoadedModule[146]=C:\Windows\System32\MMDevApi.dll LoadedModule[147]=C:\Windows\System32\PROPSYS.dll LoadedModule[148]=C:\Windows\system32\AUDIOSES.DLL LoadedModule[149]=C:\Windows\system32\RICHED20.DLL LoadedModule[150]=C:\Windows\system32\HID.DLL LoadedModule[151]=C:\Windows\system32\XInput9_1_0.dll LoadedModule[152]=C:\Windows\system32\wdmaud.drv LoadedModule[153]=C:\Windows\system32\ksuser.dll LoadedModule[154]=C:\Windows\system32\AVRT.dll LoadedModule[155]=C:\Windows\system32\msacm32.drv LoadedModule[156]=C:\Windows\system32\midimap.dll LoadedModule[157]=C:\Windows\system32\dinput.DLL LoadedModule[158]=C:\Windows\SysWOW64\slffdriver07.dll LoadedModule[159]=C:\Windows\System32\wship6.dll LoadedModule[160]=C:\Windows\System32\wshtcpip.dll LoadedModule[161]=C:\MSFS\Microsoft Flight Simulator X\Modules\FSUIPC4.dll LoadedModule[162]=C:\Windows\system32\IPHLPAPI.DLL LoadedModule[163]=C:\Windows\system32\WINNSI.DLL LoadedModule[164]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll LoadedModule[165]=C:\Windows\syswow64\imagehlp.dll LoadedModule[166]=C:\Windows\system32\ncrypt.dll LoadedModule[167]=C:\Windows\system32\bcrypt.dll LoadedModule[168]=C:\Windows\SysWOW64\bcryptprimitives.dll LoadedModule[169]=C:\Windows\system32\GPAPI.dll LoadedModule[170]=C:\Windows\system32\cryptnet.dll LoadedModule[171]=C:\Windows\syswow64\WLDAP32.dll LoadedModule[172]=C:\Windows\system32\SensApi.dll LoadedModule[173]=C:\Windows\system32\msadp32.acm LoadedModule[174]=C:\Windows\SysWOW64\ieframe.dll LoadedModule[175]=C:\Windows\SysWOW64\api-ms-win-downlevel-shlwapi-l2-1-0.dll LoadedModule[176]=C:\Windows\SysWOW64\api-ms-win-downlevel-advapi32-l2-1-0.dll LoadedModule[177]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll LoadedModule[178]=C:\Windows\system32\Secur32.dll LoadedModule[179]=C:\Windows\SysWOW64\mshtml.dll LoadedModule[180]=C:\Windows\system32\msimtf.dll LoadedModule[181]=C:\Windows\system32\msls31.dll LoadedModule[182]=C:\Windows\system32\d2d1.dll LoadedModule[183]=C:\Windows\system32\DWrite.dll LoadedModule[184]=C:\Windows\system32\D3D10Warp.dll LoadedModule[185]=C:\Windows\system32\MLANG.dll LoadedModule[186]=C:\Windows\system32\ntmarta.dll LoadedModule[187]=C:\MSFS\Microsoft Flight Simulator X\GAUGES\KingAir.DLL LoadedModule[188]=C:\MSFS\Microsoft Flight Simulator X\GAUGES\737-400.DLL LoadedModule[189]=C:\MSFS\Microsoft Flight Simulator X\GAUGES\KINGAIR_RADIO.DLL LoadedModule[190]=C:\MSFS\Microsoft Flight Simulator X\GAUGES\MOONEY_BRAVO.DLL LoadedModule[191]=C:\MSFS\Microsoft Flight Simulator X\GAUGES\BELL_206B.DLL LoadedModule[192]=C:\MSFS\Microsoft Flight Simulator X\SimObjects\Airplanes\B1900D_AirNZ_x\panel.B1900-2\BK_Radio.GAU LoadedModule[193]=C:\MSFS\Microsoft Flight Simulator X\SimObjects\Airplanes\B1900D_AirNZ_x\panel.B1900-2\cad_kln90brored.GAU LoadedModule[194]=C:\MSFS\Microsoft Flight Simulator X\SimObjects\Airplanes\B1900D_AirNZ_x\panel.B1900-2\GPWS_Sound.GAU LoadedModule[195]=C:\MSFS\Microsoft Flight Simulator X\SimObjects\Airplanes\B1900D_AirNZ_x\panel.B1900-2\master.GAU LoadedModule[196]=C:\MSFS\Microsoft Flight Simulator X\SimObjects\Airplanes\B1900D_AirNZ_x\panel.B1900-2\cad_kln90brored1.GAU LoadedModule[197]=C:\Windows\system32\EhStorShell.dll LoadedModule[198]=C:\Windows\system32\ntshrui.dll LoadedModule[199]=C:\Windows\system32\srvcli.dll LoadedModule[200]=C:\Windows\system32\cscapi.dll LoadedModule[201]=C:\Windows\system32\slc.dll LoadedModule[202]=C:\MSFS\Microsoft Flight Simulator X\SimObjects\Airplanes\B1900D_AirNZ_x\panel.B1900-2\RCB_Groundhandling5_Sound.DLL LoadedModule[203]=C:\MSFS\Microsoft Flight Simulator X\SimObjects\Airplanes\B1900D_AirNZ_x\panel.B1900-2\cad_kln90brored2.GAU State[0].Key=Transport.DoneStage1 State[0].Value=1 FriendlyEventName=Stopped working ConsentKey=APPCRASH AppName=Microsoft Flight Simulator® AppPath=C:\MSFS\Microsoft Flight Simulator X\fsx.exe" I recently reinstalled my operating system and in the automatic updates there was Microsoft.net Framework 4 so I am just installing 4.5. I downloaded the zip file from the PAD website and ran that, but just ran the virtual airline installer normally. However, I ran as administrator in today's reinstallation. I'm not sure about UAC - I have my own computer with myself as administrator. I run Windows 7 Professional 64 bit on what was originally a basic Compaq desktop which I've upgraded slightly so I now have: the original AMD Athlon II X2 215 Processor with a give rating of 2.70 GHz that I haven't overclocked; 6.0 GB of memory (one 2 GB and 4 GB of DDR3 if memory serves) and my graphics card is slightly tricky. Device manager advertises it as an AMD Radeon HD 6450 card and indeed it runs AMD drivers but it seems to be made by VTX - I don't fully understand the relationship between VTX and AMD for my card. Again thank you so much for getting back and really sorry if this has just sorted itself out and I've wasted your time. Finlay Waller

Hi all I recently joined a virtual airline and a lot of the routes that I would like to fly use the Beechcraft 1900D. I have installed the Premier Aircraft Design freeware model provided on the website (both automatically and installing away from the FSX root directory and manually moving the folders myself) but am having problems. Whenever I load the aircraft one of two things happens: the flight loading bar stays at 0% with the curser in the circular loading shape - it normally moves beyond this point almost immediately and I have tried leaving it like this for several minutes - or either immediately or within a few minutes of loading the flight I get a fatal error; if it doesn't happen straight after loading it often happens when clicking a gauge or loading an FS menu. Upon checking the logbook, the faulting module appears to be the ntdll.dll in the Windows/SysWOW64 folder. I have tried this many times and installed the aircraft many times, always getting the same problems, usually the fatal error. However, I do not get this with any other aircraft, and I have been flying different planes from the same virtual airline downloads and also from Premier Aircraft Design while the B1900D is still installed without any problems. The reason I have put this on this forum as opposed to the VA forum is because I also tried downloading the plane directly from Premier Aircraft Design without the VA livery but get the same problems, even after removing the VA package. I have looked on the forum and on Google for a solution but all the ntdll.dll problems seem to relate to other products or are too general - like I say I have the problem with no other aircraft or programs. Also, I could find nothing related to this plane on the forums. Many thanks and sorry for bringing up this type of error yet again Finlay Waller

Well, I've half answered my own question - unfortunately badly. By comparing the original eyepoint and the eyepoint once moved into the vc with the exterior model, I have found that the VC is not correctly located. It is probably where it would be for a 757 in relation to the datum position as opposed to the 767 location, meaning the cockpit is further back than it should be but a few meters. I now therefore ask the question: Is it possible to move the FSX native virtual cockpit model in relation to the exterior model, and is there an easy way to check it is in the right place after moving. Again many thanks Finlay

Thanks for your replies. I think I have pretty much the same except the Rolls Royce model (I'm a bit of a BA fan). I'm guessing that the BWL model is with winglets, and BL without. I'm pretty sure it's fine, I'm just slightly worried that putting my eyepoint in the vc model will put it in a place that isn't where the cockpit of the plane actually is. I believe that the safe-dock systems on some airport scenery rely on this being correct and I have to admit to being a bit pedantic! Once I've done the eyepoint relocation it's just a matter of trying to adapt the fmc to work for the 767 not 757. Finlay

Firstly, two apologies. 1: sorry if this is somewhere else on the forum, I did have a look and only found something close, but not specific to my question. 2: sorry if this is in the wrong section of the forum - other topics related to VC merges were also in this section. I have been trying to merge the Just Flight freemium B757 virtual cockpit with the skyspirit2010 B767-300ER Rolls Royce FSX model, and all is fine except for one thing. As others have found in merges, the default vc eyepoint is somewhat forward of the vc model. I have been reading about how to change this so the eyepoint is in the vc, but I was wondering if this is the correct eyepoint in relation to the rest of the aircraft. Is the default eyepoint (i.e. forward of the vc model where the real 767 cockpit actually would be is in relation to the central aircraft point (datum point?), with the virtual cockpit model in the position it would be in for a 757, or is the cockpit in the correct position for a 767 and just the eyepoint provided wrong. If the vc has been incorrectly placed, is there any way to rectify this. Many thanks and please ask if I have been unclear. Finlay

Hi. Let me first start by apologising if this is in the wrong forum, but I had a look and couldn't find one relating to sounds. My question about how individual sounds are used in a sound cfg file - I am trying to add a few extra sounds to a 747 RR sound pack I was given. While I am happy with the basics of flap and gear sounds etc, the problem I am having is with apu and air conditioning sounds (I am aware this has been discussed before but was unable to find what I needed on the forum). From looking at other sound files and with a little experimenting, I have found the GYRO_SOUND to come on whenever the plane is energised and thus I have used this for an air conditioning sound - the best I could find from various freeware packages compared with a youtube video from inside a 747 cabin before engine startup. However, I am at a loss when it comes to apu sounds. I have seen from other threads that this sound will not be heard in the cockpit, but I would like to find out how it works in the sound file first. I have seen the apu interior and exterior sound files used in various points in the the normal engine running sequence (eg jetwine/combustion) in the configuration file but do not understand how to add them to my particular sound file and how to make them come on. I have the posky 747 with Alejandro Rojas Lucenda's improved VC which I have seen to have an apu switch. I would also like to confirm whether the loud sound normally heard when entering a plane is the external apu sound I should be hearing when the apu is turned on. Many thanks and sorry if I am unclear, Finnerz

Thank you very much. I will contact him when I get a chance. On a slightly different note, I have noticed that some switches (namely the fuel cuttoff switches and the seatbelt/no smoking controls) don't work together in the 2D and 3D cockpit. Is this something that can be sorted easily enough? Thank you again. Finnerz

Hello all. I recently recieved assistance on the pfd and mfd in the Posky 747-400 with Alejandro Rojas Lucenda's improved VC running on FSX and now I have another panel question. I am considering using a different 2D panel but I want to integrate it well with the improved VC. However, I cannot find anything in the panel folder or config file that relates to many of the switches, knobs or buttons in the VC. For example, there are XML files for every swich in the default 2D overhead but I cannot find anything that equivilant for the many added controls in the VC overhead. Similarly the engine fuel cuttoffs, the signs knobs and the glass display swaping knobs. I can appreciate that the animation may be in the un-editable model file but I am hoping there is a way to get an XML-style file for the VC functions. Many thanks in advance, Finnerz

Sorry, I didn't make myself clear. I mean in the 2D cockpit background image, the recatangles where each of the glass displays should be is not a solid colour, but is kind of a fuzzy gray, which I have never seen on any television, crt or lcd when off. Shouldn't it be more like the second picture below than the first?

Thanks for responses. Bob, the reason I wanted a transparrent background rather than opaque black was because I am using the 737 pfd and mfd in the 2d cockpit as well and the background jpeg doesn't have a solid black background for the electronic displays. This means that the opaque black parts of the rose and arc appeare out of place - in the vc the bakcground is solid black from when it was updated but the old background remains in the 2d view. I have attached a picture of both kinds of map in 2d cockpit view to help clarify. Today I was thinking though that surely the real 747 would have an solid black screen background on the glass insturments and the texture that can be seen in the 2d cockpit below is incorrect and I should make the texture behind the glass displays solid black like in the vc. Of course if this is more accurate it would also get rid of my other problem as black on solid black is not noticeable. Finnerz

Thank you all for your replies. I should have made clearer in my original post that I had managed to edit the bitmap files but the map part of the display hadn't changed. Roman's first idea had made the gauges go black which is fantastic but I was wondering if there was a value to put into the background colour that would make that part of the gauge go transparrent? I ask because I have used the pfd and mfd on the 2d panel and the rest of it has gone transparrent. Sorry I'm asking so much! The information about how gauge folders are read was also very helpful as this was not something I had undsertood until now. Thanks again and any transparrency suggestions would be much appreciated. Finnerz

Hi I have the Posky 747 with Alejandro Rojas Lucenda's improved VC running on FSX and I have been trying to get the pfd and mfd backgrounds to go black, with near success. The only problem is inside the mfd arc/circle when in fms map mode, which will refuse to go black (see attached). It will however go black in APP or VOR mode. I have no experience editting gauges and changing the textures in the B737_800 gauges folder in the new 747 panel folder is about all I can manage. If it is something in the xml file that is easy enough to edit then guidance would be much appreciated (I have the SDK if that helps). I was wondering if there is somewhere where all the textures for the map parts of the mfd displays on all default jets are stored but couldn't find anything like that to change. Any advise (or links to another solution I haven't been able to find) would be much appreciated. Many thanks Finnerz

Thanks again. I will have a look in a bit. I am seriously considering getting the UK2000 scenery, but at the minute want to improve my frame rates (bad enough with default scenery) so I can enjoy it if I get it.

Thank you both for your replies. I had a look at the linked scenery files but unfortunately they both have a terminal 5 made from default objects (or at least no like the real one) and an older control tower, so wouldn't work with my current scenery. Is there a way to either edit my existing AFCAD file (I'm afraid I have no experience with this) or to combine two different scenery objects (i.e. the best bits of both sets of scenery) that isn't massively complicated?

Hi, sorry if this is the wrong forum - I wasn't sure if the scenery builder forum would be better but I am not a builder, just looking to change one setting. I run the default Heathrow scenery with a freeware terminal 5 addon but I find it irritating that both runways are used for takeofff and landing whereas in real life one is used for takeoff and the other landing and then they swap round at 15:00 (I think). Is there a way of putting this into FSX? I have attached the "FILE_ID" document from the original download folder in case that helps. Thanks very much

This is probably a stupid question but I was wondering how you can get up 2d panels above shift+9? For example in the Panel CFG file of one plane I have it says "Window13=FMC" and I would like to know how to view the FMC. Thanks

That seems to have done the trick, thank you so much. I can't believe it was something as simple as a USB device!

Originally in the programme files x86 then in a new folder i called fsx in the c drive root folder and then most recently back in the default programme files location

I am aware that this has been brought up before but I still haven't found a solution: A few days ago I was repeatedly attempting a certain part of a flight (from a saved point) until I got a fatal error - I don't exactly remember if this was when it happened - but was not particularly worried as this has happened a few times before. However, when I went to start FSX the next day, I would get a little way into the starting blue box before a little window appeared saying a fatal error had occured and FSX would have to close. I tried the UIAutomationCore fix but this didn't work, nor did starting as administrator or launching in compatibility mode (I am running windows 7 professional 64 bit). I also tried deting the cfg file and the logbook? file. I then copied into a folder on my desktop my world of ai planes (as they took so much hassle to put on) and a few other planes to put back on when everything worked and then unistalled service pack 2 and fsx, checking nothing was left behind. I then tried a reinstall and got a window about Microsoft Flight Simulator stopping working a little bit into startup. After trying service pack 1, this changed to the fatal error window. I have now tried a repair and a complete reinstall and am still getting the mfs has stopped working window on startup. In case it helps, I saw in another post saying something about the event viewer and the faulting module path is C:\windows\system32\HID.DLL If anyone can help I would be massively greatful, thanks.