Jump to content

werver

Members
  • Content Count

    73
  • Donations

    $0.00 
  • Joined

  • Last visited

Posts posted by werver


  1. Hi All,

    Same problem here after updating the 737NGX yesterday.

    Windows 7 64 bits, FSX

    AppCrashView report:

    Version=1
    EventType=APPCRASH
    EventTime=131444182863347324
    ReportType=2
    Consent=1
    UploadTime=131444182863947325
    ReportIdentifier=f0fd803c-67bc-11e7-ace6-240a645544a4
    IntegratorReportIdentifier=f0fd803b-67bc-11e7-ace6-240a645544a4
    WOW64=1
    Response.BucketId=1647498135
    Response.BucketTable=25
    Response.type=4
    Sig[0].Name=Application Name
    Sig[0].Value=fsx.exe
    Sig[1].Name=Application Version
    Sig[1].Value=10.0.61472.0
    Sig[2].Name=Application Timestamp
    Sig[2].Value=475e17d3
    Sig[3].Name=Fault Module Name
    Sig[3].Value=PMDG_737NGX_2.dll
    Sig[4].Name=Fault Module Version
    Sig[4].Value=11.14.0.0
    Sig[5].Name=Fault Module Timestamp
    Sig[5].Value=572b6e57
    Sig[6].Name=Exception Code
    Sig[6].Value=c0000005
    Sig[7].Name=Exception Offset
    Sig[7].Value=00002689
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=6.1.7601.2.1.0.256.1
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=1033
    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]=F:\FSX\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]=F:\FSX\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\syswow64\USERENV.dll
    LoadedModule[30]=C:\Windows\syswow64\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.18837_none_ec86b8d6858ec0bc\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:\program files (x86)\internetbeveiliging\apps\computersecurity\hips\fshook32.dll
    LoadedModule[61]=C:\Windows\syswow64\PSAPI.DLL
    LoadedModule[62]=F:\FSX\language.dll
    LoadedModule[63]=F:\FSX\API.DLL
    LoadedModule[64]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll
    LoadedModule[65]=F:\FSX\ablscpt.dll
    LoadedModule[66]=F:\FSX\flight.dll
    LoadedModule[67]=F:\FSX\ai_player.dll
    LoadedModule[68]=F:\FSX\acontain.dll
    LoadedModule[69]=F:\FSX\controls.dll
    LoadedModule[70]=C:\Windows\system32\DINPUT8.dll
    LoadedModule[71]=F:\FSX\fsui.dll
    LoadedModule[72]=F:\FSX\atc.dll
    LoadedModule[73]=F:\FSX\facilities.dll
    LoadedModule[74]=F:\FSX\demo.dll
    LoadedModule[75]=F:\FSX\main.dll
    LoadedModule[76]=F:\FSX\fe.dll
    LoadedModule[77]=F:\FSX\util.dll
    LoadedModule[78]=F:\FSX\simprop.dll
    LoadedModule[79]=F:\FSX\g2d.dll
    LoadedModule[80]=C:\Windows\system32\d3dx9_34.dll
    LoadedModule[81]=C:\Windows\system32\d3dx10_34.dll
    LoadedModule[82]=C:\Windows\system32\d3d9.dll
    LoadedModule[83]=C:\Windows\system32\d3d8thk.dll
    LoadedModule[84]=F:\FSX\g3d.dll
    LoadedModule[85]=F:\FSX\panels.dll
    LoadedModule[86]=F:\FSX\multiplayer.dll
    LoadedModule[87]=F:\FSX\ui.dll
    LoadedModule[88]=F:\FSX\sound.dll
    LoadedModule[89]=F:\FSX\sim1.dll
    LoadedModule[90]=F:\FSX\simscheduler.dll
    LoadedModule[91]=F:\FSX\visualfx.dll
    LoadedModule[92]=F:\FSX\window.dll
    LoadedModule[93]=F:\FSX\terrain.dll
    LoadedModule[94]=F:\FSX\weather.dll
    LoadedModule[95]=C:\Windows\system32\DSOUND.dll
    LoadedModule[96]=C:\Windows\system32\POWRPROF.dll
    LoadedModule[97]=F:\FSX\symmap.dll
    LoadedModule[98]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.23807_none_5c02a265a011fb02\gdiplus.dll
    LoadedModule[99]=C:\Windows\system32\MSIMG32.dll
    LoadedModule[100]=F:\FSX\xuipc.dll
    LoadedModule[101]=F:\FSX\livingwater.dll
    LoadedModule[102]=F:\FSX\fs-traffic.dll
    LoadedModule[103]=F:\FSX\gps.dll
    LoadedModule[104]=C:\Windows\system32\MSWSOCK.dll
    LoadedModule[105]=C:\Windows\system32\SHFOLDER.dll
    LoadedModule[106]=C:\Windows\system32\RICHED20.DLL
    LoadedModule[107]=C:\Windows\system32\CRYPTSP.dll
    LoadedModule[108]=C:\Windows\system32\rsaenh.dll
    LoadedModule[109]=C:\Windows\syswow64\WINTRUST.dll
    LoadedModule[110]=C:\Windows\syswow64\CRYPT32.dll
    LoadedModule[111]=C:\Windows\syswow64\MSASN1.dll
    LoadedModule[112]=C:\Windows\syswow64\CLBCatQ.DLL
    LoadedModule[113]=C:\Windows\system32\wbem\wbemprox.dll
    LoadedModule[114]=C:\Windows\system32\wbemcomn.dll
    LoadedModule[115]=C:\Windows\system32\RpcRtRemote.dll
    LoadedModule[116]=C:\Windows\system32\wbem\wbemsvc.dll
    LoadedModule[117]=C:\Windows\system32\wbem\fastprox.dll
    LoadedModule[118]=C:\Windows\system32\NTDSAPI.dll
    LoadedModule[119]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL
    LoadedModule[120]=C:\Windows\system32\dxgi.dll
    LoadedModule[121]=C:\Windows\system32\d3d11.dll
    LoadedModule[122]=C:\Windows\system32\bcrypt.dll
    LoadedModule[123]=C:\Windows\system32\D3DCompiler_34.dll
    LoadedModule[124]=C:\Windows\SysWOW64\bcryptprimitives.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\system32\winbrand.dll
    LoadedModule[129]=C:\Windows\system32\WINSTA.dll
    LoadedModule[130]=C:\Windows\SysWOW64\gameux.dll
    LoadedModule[131]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_41e855142bd5705d\COMCTL32.dll
    LoadedModule[132]=C:\Windows\SysWOW64\XmlLite.dll
    LoadedModule[133]=C:\Windows\SysWOW64\wer.dll
    LoadedModule[134]=C:\Windows\System32\Wpc.dll
    LoadedModule[135]=C:\Windows\System32\wevtapi.dll
    LoadedModule[136]=C:\Windows\System32\msxml6.dll
    LoadedModule[137]=C:\Windows\system32\SAMLIB.dll
    LoadedModule[138]=C:\Windows\system32\netutils.dll
    LoadedModule[139]=F:\FSX\uiautomationcore.dll
    LoadedModule[140]=C:\Windows\system32\OLEACC.dll
    LoadedModule[141]=C:\Windows\System32\MMDevApi.dll
    LoadedModule[142]=C:\Windows\System32\PROPSYS.dll
    LoadedModule[143]=C:\Windows\system32\AUDIOSES.DLL
    LoadedModule[144]=C:\Windows\system32\HID.DLL
    LoadedModule[145]=C:\Windows\system32\wdmaud.drv
    LoadedModule[146]=C:\Windows\system32\ksuser.dll
    LoadedModule[147]=C:\Windows\system32\AVRT.dll
    LoadedModule[148]=C:\Windows\system32\msacm32.drv
    LoadedModule[149]=C:\Windows\system32\midimap.dll
    LoadedModule[150]=C:\Windows\system32\dinput.DLL
    LoadedModule[151]=C:\Windows\System32\wship6.dll
    LoadedModule[152]=C:\Windows\System32\wshtcpip.dll
    LoadedModule[153]=F:\FSX\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow.dll
    LoadedModule[154]=C:\Windows\system32\Secur32.dll
    LoadedModule[155]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll
    LoadedModule[156]=C:\Windows\system32\IPHLPAPI.DLL
    LoadedModule[157]=C:\Windows\system32\WINNSI.DLL
    LoadedModule[158]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll
    LoadedModule[159]=C:\Windows\system32\DNSAPI.dll
    LoadedModule[160]=C:\Windows\system32\dhcpcsvc.DLL
    LoadedModule[161]=C:\Windows\System32\netprofm.dll
    LoadedModule[162]=C:\Windows\System32\nlaapi.dll
    LoadedModule[163]=C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live\WLIDNSP.DLL
    LoadedModule[164]=C:\Windows\system32\dhcpcsvc6.DLL
    LoadedModule[165]=C:\Windows\system32\rasadhlp.dll
    LoadedModule[166]=C:\Windows\System32\npmproxy.dll
    LoadedModule[167]=C:\Windows\System32\fwpuclnt.dll
    LoadedModule[168]=F:\FSX\ORBX\FTX_AU\FTXAA_YWOL\Scenery\ObjectFlow_YWOL.dll
    LoadedModule[169]=C:\Vliegen\AFX Demo\AFXModuleFSX.dll
    LoadedModule[170]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll
    LoadedModule[171]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
    LoadedModule[172]=C:\Windows\system32\ntmarta.dll
    LoadedModule[173]=C:\Windows\syswow64\WLDAP32.dll
    LoadedModule[174]=C:\Windows\system32\msadp32.acm
    LoadedModule[175]=C:\Windows\SysWOW64\ieframe.dll
    LoadedModule[176]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll
    LoadedModule[177]=C:\Windows\SysWOW64\mshtml.dll
    LoadedModule[178]=C:\Windows\system32\msimtf.dll
    LoadedModule[179]=C:\Windows\system32\msls31.dll
    LoadedModule[180]=C:\Windows\system32\d2d1.dll
    LoadedModule[181]=C:\Windows\system32\DWrite.dll
    LoadedModule[182]=C:\Windows\system32\MLANG.dll
    LoadedModule[183]=C:\Windows\SysWOW64\uiautomationcore.dll
    LoadedModule[184]=C:\Windows\system32\NETAPI32.dll
    LoadedModule[185]=C:\Windows\system32\srvcli.dll
    LoadedModule[186]=C:\Windows\system32\wkscli.dll
    LoadedModule[187]=C:\Windows\SysWow64\XAudio2_7.dll
    LoadedModule[188]=F:\FSX\Gauges\PMDG_737NGX_2.dll
    LoadedModule[189]=C:\Windows\system32\snmpapi.dll
    LoadedModule[190]=C:\Windows\system32\icmp.Dll
    LoadedModule[191]=C:\Windows\system32\napinsp.dll
    LoadedModule[192]=C:\Windows\system32\pnrpnsp.dll
    LoadedModule[193]=C:\Windows\System32\winrnr.dll
    LoadedModule[194]=C:\Windows\system32\wshbth.dll
    LoadedModule[195]=F:\FSX\Aerosoft\AES\ViMaCli.dll
    State[0].Key=Transport.DoneStage1
    State[0].Value=1
    State[1].Key=DataRequest
    State[1].Value=Bucket=1647498135/nBucketTable=25/nResponse=1/n
    FriendlyEventName=Stopped working
    ConsentKey=APPCRASH
    AppName=Microsoft Flight Simulator®
    AppPath=F:\FSX\fsx.exe

    Werner Verwaal

     


  2. Hi Alex,

     

    On the Jeppesen charts the position of Navaids is in Mminutes only, precision 2.

    Example: VOR SPY on the JeppView chart: N52 32.4, E004 51.2.

    This position can also be entered in de PMDG 737NGX FMC as N5232.4E00451.2

     

    In JeppView, options you can choose from three different Lat/Lon Display settings:

    a. Minutes only. See above

    b. Show seconds. N52° 32' 25.01", E004° 51' 13.61"

    c. Decimal degrees. N52. 54°, E04.85°

     

    b and c are already in Little Navmap

     

    It would be very nice to have option Minutes only also in Little Navmap for the reasons I described before.

    Furthermore it would very handy if it's possible to enter the geographic coordinates in the search section.

     

    Thanks for all the effort you make for this magnificent program.

     

    Werner Verwaal


  3. Hi Alex,

     

    I have installed v1.2.2 beta and the ILS-problem was solved.

    Both Plan-G and Little NavMap use the FSX scenery.cfg file to build their database. But there is a difference between those two programs when I look at the maps.

    In Plan-G I see for instance on the North Sea the intersections SULUT, EH606, NIRSI, EH607. All those intersections are missing in Little NavMap.

     

    Is there a way to get them also in Little NavMap. These waypoints are importent for the approach to EHAM.

     

    Greetings

     

    Werner Verwaal


  4. Hello Alexander,

     

    In the original FSX Nav database (year 2006) the airport EBOS has only one ILS on Rwy 26. Nowaday both runways are equiped with an ILS.

    After updating the FSX Nav database with the program found on http://www.aero.sors.fr, this problem is solved.

    In Plan-G I now see both ILS feathers on the map. However in Little NavMap v1.2.0 beta, after rebuilding the scenery library, I only see the ILS for Rwy 26 (109,50 258 degrees).

    Do you have any idea how come?

     

    By the way: I'm really impressed that you have built this excellent program!! Many thanks about that.

     

    I wish you a merry christmas and a happy new year

    I'm looking forward to the updates of this very nice program

     

    Greetings

     

    Werner Verwaal

    member of FSHolland (http://www.fs-holland.nl/)

     

     

     


  5. Forget it. PMDG does nothing for the owners of this aircraft. We are already waiting years for a patch for the bezel shimmering in the VC.

    PMDG used this airceaft to study their technique of designing an aircraft. We had to pay for that and after that you are on your own.

    I think this is a shame.

     

    Werner Verwaal

     

     

     

    PMDG 737NGX 600 - 900 and JS4100


  6. firehawk44, on 29 Mar 2014 - 01:26 AM, said:http://forum.avsim.net/index.php?app=forums&module=forums&section=findpost&pid=2953932'>

    The Scenery Config Editor does not work with FTX Central very well and I would not recommend anyone try to disable/enable FTX scenery using the SCE. I learned that myself the hard way and had a lot of scenery corruption. I finally was able to get FTX Central working properly again. It's just as easy to enable/disable FTX scenery via their FTX Central utility.

     

     

    I have FTX PNW with some airports and Northern California. How is it possible to switch off for instance only the airports in PNW via FTX Central.??

     

    Best Regards

     

    Werner


  7. If you see that the VAS is nearing 4 GB (mostly on final), what can you do to lower the VAS

    .

    Save the flight, end flight and after that load the saved flight, didn't lower the VAS very much.

    Save the flight, shut down FSX and restart it and than load the saved flight, lowers the VAS very much, but than you loose you IVAO connection.

    After reloading the flight and connect again to the network is very annoying for ATC.

     

    Is there a better solution for this problem?

     

    Wener Verwaal


  8. For the 737NGX and de JS4100 I use the Saitek Pro Flight Yoke and two Saitek throttle quadrants.

    I use a number of the switches on the throttle quadrants for the landings-, taxi- and strobe-lights. Moving the switch up, light goes on, moving the switch down, the light goes off. This works perfect for the JS4100.

    But I don't know how to do this on the 737NGX. In the FMC I saw under External Light only the possibility to toggle the lights.

    For instance Ctrl + L toggles the landings lights on/off. So moving up light on , moving up again lights off. Also FSUIPC give me no solution.

    Is there a possibility to switch the lights as I described for the JS4100??

     

    Werner Verwaal


  9. It would be far better to have the push back which you can use via the IVAO interface. Before push back you give the direction for the turn and than press the "Start push back"" button. When the plane is at the turning point, push the "Start turn" button. Very easy to use, no push back distance needed.Werner Verwaal


  10. When I click on the CDU and than undock it, I can pull it to my second montor and it works ok. But, because the CDU is used very often and the information is importent , I want the CDU , let say, 1.5 times as big.But when I resize it with my mouse (draw the right edge), the CDU doesn't work anymore or even the windows is black. When I push the buttons nothing happens, but when I push the CDU back to my main monitor I can see that the CDU is still working.I use a Geforce GTX 470 with a Samsung 22" monitor 1650x1050 32 bits 60Hz (main monitor) and a Dell 19" monitor 1280x1024 32 bits 60 Hz (second monitor).What is the better way to resize the CDU?? Werner Verwaal

×
×
  • Create New...