Jump to content

l_jayma

Frozen-Inactivity
  • Posts

    164
  • Joined

  • Last visited

  • Donations

    0.00 USD 

Reputation

6 Neutral

Profile Information

  • Gender
    Male
  • Location
    New Jersey
  • Interests
    Formula One,Flying Simulated and Real

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Recent Profile Visitors

1,329 profile views
  1. The PMDG 777 & 737NGX..two of my favorite aircraft that have provided me a return on my investment way beyond the cost I paid for them.
  2. I would recommend reading the following FAA(Federal Aviation Administration) publications to give you the insight your are looking for when comes to what real pilots do. Pilots Handbook of Aeronautical Knowledge Instrument Procedures Handbook These are two solid publications I refer to after many years of real flying from time to time. I don't know the (JAA)European version of the these documents, but I am sure someone here will respond with that answer. Happy Flying.
  3. I changed it CTRL+F12 and the problem was resolved. Perhaps a corrupted file or CTRL+F12 is conflicting with something else. Worse Case..delete and re-install ASN
  4. I was doing a little research and the forum post below had a similar issue with VATSIM interfering with VORs. http://forums.pilotedge.net/viewtopic.php?t=3931&p=25025
  5. Are you sure you flipped the frequency to be active? I am sitting on the active runway - 33 at Perth. Dialed in 110.40 PTH and the CDI is centered on course 348. It makes sense since the VOR is NE of my position. The DME reads 0.0 nm
  6. I was asked to change the shortcut from the default CTRL+F11 to something else..I have not had the chance to full test if this is the solution but sounds likely it is the answer.
  7. Anyone have the issue with the ASN Weather Request popup window just open up without activating it from the addon menu? I did select it once but i closed the window, but it keeps appearing. I am running ASN 5921 P3dv3.2
  8. Elaine, I followed your steps..resolved. Back in business..Thanks
  9. In AppRoaming should I delete this entry as well? AppRoaming> dll.xml </Launch.Addon> <Launch.Addon> <Name>Addon Manager</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>bglmanx.dll</Path> </Launch.Addon> AppRoaming>exe.dll Use this to remove the references to coutl and fsdreamteam <?xml version="1.0" encoding="windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>exe.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>as_btstrp_config_manager</Name> <Disabled>False</Disabled> <Path>as_srv\as_btstrp_config_manager.exe</Path> </Launch.Addon> </SimBase.Document> ProgramData Folder > dll.xml - No change becuase there is no reference to bglmanx.dll </Launch.Addon> <Launch.Addon> <Name>Addon Manager</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>bglmanx.dll</Path> </Launch.Addon> ProgramDate>exe.dll No change - to confirm <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="AceXML" version="3,0" id="exe"> <Descr>AceXML Document</Descr> <Filename>exe.xml</Filename> <Launch.Addon> <Name>SODE</Name> <Path>C:\Program Files (x86)\12bPilot\SODE\SimObjectDisplayEngine.exe</Path> <CommandLine>P3Dv3</CommandLine> </Launch.Addon> </SimBase.Document>
  10. Here are the entries in the exe.dll and dll.xml exe.xml <?xml version="1.0" encoding="windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>exe.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>Couatl</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>fsdreamteam\couatl\couatl.exe</Path> </Launch.Addon> <Launch.Addon> <Name>as_btstrp_config_manager</Name> <Disabled>False</Disabled> <Path>as_srv\as_btstrp_config_manager.exe</Path> </Launch.Addon> </SimBase.Document> dll.xml <Launch.Addon> <Name>Addon Manager</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>bglmanx.dll</Path> </Launch.Addon> Mark, Based on what I added in Poppet's question is this still the case to copy the dll.xml to the program folder? Additionally, my dll.xml file in the ProgramData folder is the following: <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="AceXML" version="3,0" id="dll"> <Descr>AceXML Document</Descr> <Filename>dll.xml</Filename> <Launch.Addon> <Name>SODE Animation Module</Name> <Path>C:\Program Files (x86)\12bPilot\SODE\SimObjectAnimationModule.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Flight Recorder</Name> <Path>Aerosoft\Flight Recorder\AS-FlightRecorder.dll</Path> </Launch.Addon> </SimBase.Document>
  11. Any suggestions, I was looking around to see if anyone had this error but I could not find similar issues in my search. I installed P3d v3.2 and at startup when loading a scenaro, I am now getting a fatal error Faulting application path: D:\Prepar3Dv3\Prepar3D.exe Faulting module path: D:\Prepar3Dv3\bglmanx.dll I know it has to do with the fsdt/couatl applications but I dont own any of the sceneries or GSX. I did own have the QW757 but I deleted it from 3.1. Anyone else run into this issue? Also are there other developers who use this..I forget.(Flightbeam,etc..) I dont think so but I want to be sure. Thanks in advance.
  12. At the very minimum update to 3.2 for the Client update. It will allow future updates to prevent reinstalling all your add-ons every update. The Shader and Content update should not be overlooked as well. Any improvements to content and/or shader functionality is welcome anytime just like any other application that has an update. Plus most add-on developers have updated to 3.2, so you should not have any issues with incompatibility.
  13. The annunciator on the AP used to work on the other version now the light is replace with the tag. IN THE REAL PLANE...the light is the indicator(s) From the Garmin Perspective Manual "status and mode annunciations that are simultaneously displayed on both the Perspective™system AFCS Status Box and the S-TEC Fifty Five X Autopilot Display and/or Remote Annunciator Display, the Perspective™system displays an additional status annunciation of ‘AP’ when the autopilot is engaged. This provides the pilot with a dedicated annunciation showing the status of the autopilot engagement"
  14. Issue Resolved...I checked back in and no issue. Thanks.
  15. Anyone notice the login to the fullterrain forum is broken? I logged in and I had to reconfirm for signature but the popup for WelshPool keeps refreshing and not loading completely not allowing me to click the AGREE check box.
×
×
  • Create New...