Jump to content

Mr Unicorn

Members
  • Content Count

    25
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

Profile Information

  • Gender
    Male

Flight Sim Profile

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

Recent Profile Visitors

1,244 profile views
  1. I have looked into a bunch of other posts about screen tearing, but none seem to have the issue I am having. From my experience with screen tearing, it happens all the time and across the entire screen. Mine is specifically on the top right corner of my monitor and occurs and random times. It may happen as soon as I fire up the sim, it may be months before I see it again. But its infuriating because not only is it disorienting to some degree, it blocks the landing lights and other such lights in the external view and certain angles. This happens with any aircraft and any time of day or night. SU10 Latest NVIDIA drivers Tested with sim VSYNC on, NVIDIA VSYNC off, and vise versa. Settings high Specs: Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz 3.60 GHz NVIDIA GeForce RTX 2070 32.0 GB RAM 64-bit operating system My monitors are quite dated compared to modern ones available, but I don't have the funds to buy new ones or even find one for testing. But since MSFS is the only game that does this, I find it hard to believe it's my monitors that is the issue. This only temporary fix is to restart the sim. Image links: https://imgur.com/0bVpJTz https://imgur.com/7Za9xxn https://imgur.com/UoFLHqY
  2. Hi all! I know this is an old post, however, since 5 years have elapsed, I was wondering if there was any update regarding the Failures: Reserved feature. Cheers
  3. Oh sweet! That's great to hear. Any chances of adding it to other aircraft?
  4. Many aircraft such as PMDG and FSLabs have the option to connect an ASU in the event of an inop APU. Is it possible to maybe add an airstart procedure in the case of an inop APU? I myself have performed airstarts on 737s when I worked the ramp so I have a general idea of how its performed on a 737.
  5. I just leave it as custom pushback (face "direction") But I am glad to hear that this can be replicated! 😄
  6. After creating a custom pushback route out of gate C39 at Flightbeam Denver, I couldn't get out of the editor. When ever I would click anywhere after "creating" my custom route, it would go right back into the birds eye view. I clicked on "minimize" something and then my screen in the sim went completely black and does not recover. Restarting the sim is the only thing that fixes it. I am on the latest UGCX version 1.7.0.0 on P3D v4.5 with the hot fix.
  7. I installed P3Dv4.4, but never actually tested. I recently did a full reinstall of 4.4 and treated myself to the new PMDG 747-8 and actually got to test FS2Crew and it works just fine.
  8. Ok its working now. I guess V4.4 was required lol. Thanks for the help.
  9. There is an addon conflicting with 4.4 and I am unsure of which one it is. Pete, I do know how to update P3D, that is not the issue. The issue is something is not allowing it. I've read that the FSLabs A320 or 319 could be part of the issue but I have yet to look into it. I'm not going to post here wanting support on how to update lol, so I will just keep it at that.
  10. I am having issues with updating to 4.4. Any way I can get it to work with 4.3?
  11. I read previous topics on this but all the stuff the support staff suggested didn't work. I am on the latest version of both the 747 and FS2Crew. I still use P3Dv4.3 so I am not sure if version 1.3 of FS2Crew for the 747 or even 747 itself requires v4.4. This has worked in the past with no issues until now.
  12. So recently, I have run into this weird an annoying bug where if I go into the FMC and change certain things on the aircraft such as equipment used, callouts etc, the aircraft goes completely dark and I cannot restore power since I cannot turn on the battery at all. The only way to regain power is to cheat and force the FMC on by holding the 'Menu' button. From there I have to cycle the default states until the fire alarm stops which says I have an engine fire and that can't be removed even in the failures page. This was before a clean reinstall of P3Dv4, and this is on the latest version on the PMDG 737NGX which is version 1.20.8885 for the base 8/900 and for the 6/700 it is 1.20.8465 and it happens with both products. If anyone has experience this and figured out a fix, let me know :)
  13. Alt-Tab isn't working for me. I am on 0.4.101 and even the previous version and still doesn't work.
  14. I'll give that a go whenever it happens. Thanks Keven!
  15. This is a rather frustrating issue. When I first spawn in, the camera will either work or it won't. I can still use the middle mouse to pan and look around and even use the hat switch but any marked keys that are assigned to a view do not work. Its honestly hit or miss. I have tried reinstalling and messing with the Experimental Versions tab but hasn't done much. When changing to exterior I have CTRL + another key and when it is working, I will click the one key to fly around the vc but it will change to the exterior view. P3Dv4.1, v0.4.77 beta of Chaseplane, NO EZCA what so ever.
×
×
  • Create New...