Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

60 Good

About alepro21

  • Rank

Profile Information

  • Gender
  • Location
    SYD, AU

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

About Me

  • About Me
    Previously known as Alex_YSSY in these forums (could not recover my account for some reason).

Recent Profile Visitors

612 profile views
  1. Just bought it. Overall much improved, and performance is finally good. I do run 4K max texture resolution and noted that with AI the graphics memory peaked at 7.5Gb. Not an issue for me (I got 16Gb), but just FYI for folks with 8Gb cards or less. A couple of other observations: - The new north runway is completely devoid of tire marks. Is this runway only used for takeoff? - The ADF layout is causing some odd parking arrangements with my traffic (AIG). Some very remote parking locations are in use but most gates are empty, especially with regards to Qantas aircraft at the domestic terminal. - I miss the palm trees at the domestic terminal (as present in the previous version. I liked those. Are they gone in real life? - Dynamic light at night is great if a bit too bright. - The “grass” effect looks off. I disabled that all together now. - Overall I found the airport a bit lifeless and sterile. Some dynamic vehicle traffic would help here, but it’s the same in other ORBX hubs. I think there is room for improvement here. All told I’m happy with the purchase, and glad to have another good Australian airport. Thanks ORBX!
  2. Can’t wait to try this. Thanks Kai!!!
  3. A question mark in the thread title wouldn’t go amiss. Got excited there for a second 😉
  4. It’s not unusual for Navigraph to issue the same AIRAC multiple times because of data issues. If this is indeed AIRAC related then it might go away with the next revisions. Otherwise it might be worth sending your flight plan to Qualitywings so that they can try to replicate your issue.
  5. Does the issue occur anywhere else? Could be AIRAC related (maybe try an update or different revision if that’s what’s happening).
  6. Not a particularly differentiated opinion you are voicing there, and you are giving us nothing usable in terms of actual information to offer help. For reference, here is an example of someone doing a great job of raising an issue. Personally all I can tell you is that I have had about four flights with 1.4 and had no issues.
  7. I am much in the same boat. PMDG releases used to be instant buying decisions for me and I usually struck on release day. I think they got the pricing wrong and would imagine that they would generate more revenue overall if they dialled the price point back to that of previous releases (~$40 mark), but that’s just wild speculation on my part. They probably have a solid idea how to price their product and decided they can do just fine without my cash or yours.
  8. I had a very similar observation with the -300ER and found that hand flying the approach was very difficult. I was flying “on the numbers” i.e. I was flying the correct approach speed as calculated by the FMC, yet I had to apply constant pitch up elevator input. I have the FBW indicator selected to display on the PFF speed tape, so I’m sure the trim was set correctly. I have flown the 777 since the original release for FSX and always found it a joy to fly, but something is definitely off about the pitch command logic of the FBW or the elevator sensitivity with this release.
  9. Thanks a lot for the tip and explanation Ray! I’ll certainly give this a shot.
  10. Interesting Ray! Do you use that information to tune your settings? I only ever looked at this when making a hardware change, but perhaps I’m missing a trick here?
  11. I’d like to argue the counter point to @Ray Proudfoot. You don’t need to achieve >60fps to benefit from a 144 Hz monitor as I recently found out when I upgraded my 60 Hz 34” ultra-wide to a 144 Hz ultra-wide display. Even when you not using VRR (for example when your FPS are below the required refresh rate for VRR (Gsync or Freeaync, VRR range depends on the screen but usually starts at 40 or 48 Hz)) you will wait on average 58% less (going from 60 Hz to 144 Hz) for a rendered frame to refresh on screen. I used to be a big fan of locking the screen to 30 Hz to provide a fluid experience, but no more. 144 Hz has been great for fluidity and when VRR kicks in it’s fantastic! Only issue I have with the screen is flickering when moving in/out of the VRR range (at 48 Hz in my screens case) but I can live with that. The issue would go away if I disabled VRR of course, but I’d rather keep it on.
  12. P3Ds “HDR” isn’t actually real HDR. I have a HDR monitor and the P3D app never sends an HDR signal to the screen. When in windowed mode and with HDR enabled in windows, the OS sends an HDR signal, but the P3D content is unchanged. Think of it as a video effect, rather then a HDR10 signal.
  13. Great data, thanks for putting it together! The VRAM data make me glad that I opted for a 6800 XT. Looking forward to getting my 4K texture resolution back while cranking up all other settings.
  14. This sounds very encouraging. Thanks a lot for that update. Results for some of the mainstream games seem to indicate anything from no improvement to 10% improvement are on the cards, so it depends a lot on the application. I use P3D exclusively except for checking on MSFS once a month (still a hot mess in my opinion), so curious if SAM makes a difference in P3D and if so, how much?
  • Create New...