PLund

Members
  • Content count

    58
  • Joined

  • Last visited

About PLund

  • Rank
    Member

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    VATSIM
  • Virtual Airlines
    Yes

Profile Information

  • Gender
    Male
  1. If you run the Long Turnaround, then once it´s finished loading turn off the GPU generator and the battery. Wait a few seconds and turn the battery back on and the GPU generator.
  2. Hi Bryan, Sorry for the late response. unfortaunately I had the pleasure of reinstalling WIN10 and P3Dv4 a couple of times before I got it to work. Regarding by problem above it hears Start engine one, but pulls the ENG 4 starter right after ENG 1 has been pulled. Another problem I have started to experience with the 747F (RR) is I ask for the shutdown checklist where I have 2 problems. 1. He starts the checklist and sometimes he stops reading out dispite the answers are given correctly. 2. The shutdowns check list is completed and he says shutdown checklist complete, but when running the Secure procedure it jumps back to shutdown checklist.
  3. I have started after loading the long panel state to switch off EXT PWR and turn of the battery so it goes dark. After a few seconds I put the battery back on along with the EXT PWR.
  4. Hi guys, I got a small problem when starting the engines one-by-one. When I ask for Engine 4 start sometimes the FO pulls the ENG 4 start and other times she pulls ENG 1 and then ENG 4. Also, when it works and she is starting ENG 1, ENG 4 is also pulled even though it´s up and running.
  5. Got the same issue and used the default long turn around. The only way to get rid of the caution is to do a complete power down (Generators and battery off).
  6. P3D V4

    Have you manually added the scenery in the Scenery Library ?
  7. It looks like my problem might have been solved by a friend of mine. By turning off "Enable Scenario Error Reporting" and "Enable Content Error Reporting" seems to do the trick for me. Since I turned off "Enable Scenario Error Reporting" (the other wasn´t on) I have done 3 long haul flights across the pond without any problems. They can be found in Options-> General-> Application.
  8. I experience the same error twice today. One 4 hours into a overnight flight and once 30 minutes after take off from Seattle. One thing I have noticed is 1 second before the terrain.dll error there is a .net error also on Prepar3D. I have now ran the CCleaner and reduced the autogen from high to medium. If it works time will tell, but I really hope so.
  9. Funny I experienced the same error yesterday flying Shanghai-Luxembourg with the 747. At that time I was over Russia where I have absolutely no add-on sceneries. I was told it might be the graphic card driver that needed an update which I did yesterday evening.
  10. Thanks Jim, I am using CH Products yoke and hadn´t thought the axis could be the reason. Since I don´t fly GA I have deleted the 2 other axis so hopefully I won´t encounter those problems again.
  11. Hi guys, I have a few times experienced a sudden and unexplainable power loss with the 744. There are no system to it as it have happened while taxiing out, initial climb and today 3 times on final approach. It has mostly happened with the RR Freighter, but today it was the PW pax version for the first time. What happens electric power and engines fail leaving me with a almost cold and dark cockpit for a few seconds until it comes back alive as just before it goes out. There are plenty fuel and I use AS16 for weather which fairly quiet.
  12. I can really relate it this topic. In FSX it was 2D all the way and I hated flying the 777 in VC, but now I really like VC (most of the time). But what changed. I swapped to P3D in January just before the 747 came out and had though of changing from FSX and decided that was the right time so I only had to buy it for one platform.I used TrackIr during most critical parts and then the normal shift+mouse. In FSX the view would change during turns, but that is changed in P3D so the view goes back to normal after a turn. I still use 2D for FMC and radios and the only aircraft I only use 2D with is FSL A320 as I find the display too small in VC. The NGX can also be a bit difficult and hard to see the displays, but is still better than 2D after I got used to VC.
  13. Hi Kyle, The simulator is run as admin and the liveries for the 747 are all installed from the Livery manager. I noticed the difference with Atlas N475MC which had digital MCP and LCD displays when I used it on my old computer, but on the new it´s the old screen and analog MCP.
  14. Hello, I have after I installed P3D on my new computer experienced that the configuration settings are not installed on the 747 or NGX for that matter. Both the 747 and NGX is installed as admin and Operation Center is also run as admin. The reason I found out is with the NGX I have some liveries where the settings are metric, but the weight is in lbs. With the 747 one of the liveries was with digital MCP, but after installing it on my new computer it have become analog.
  15. Hi guys, I have for some time experienced an error when closing the Operation Center. It started after installing the 747 and it only comes up if I have added or removed something. The messsage is: An exception has occured! Please contact PMDG support by submitting a ticket at http://support.precisionmanuals.com for help with resolving this issue. Press "Copy to clipboard" below and then paste the information into your support ticket. Additionally, a log file has been created at: c:\users\peter\appdata\roaming\pmdg\pmdg operations center\PMDG Operations Center.log Please attach this file to better help us fix this issue. The application will now exit. 04/10/17 18:05:35 Exception: Access Violation at 0x0 747F0000 C:\Windows\System32\USER32.dll +0002D2B3 (1608A2, 5, 0) 747F0000 C:\Windows\System32\USER32.dll +0001E2F5 (396040, 1608A2, 5) 747F0000 C:\Windows\System32\USER32.dll +0001D960 (1608A2, 5, 0) 747F0000 C:\Windows\System32\USER32.dll +0001C015 (1993170, 0, 5) 747F0000 C:\Windows\System32\USER32.dll +0002D2B3 (1608A2, 5, 0) 747F0000 C:\Windows\System32\USER32.dll +0000E88A (76F22340, 1608A2, 5) 747F0000 C:\Windows\System32\USER32.dll +0000E4C0 (76F22340, 0, 5)