Jump to content

threegreen

Members
  • Content Count

    1,463
  • Donations

    $10.00 
  • Joined

  • Last visited

Community Reputation

737 Excellent

1 Follower

About threegreen

  • Rank
    Member - 1,000+

Profile Information

  • Gender
    Male

Flight Sim Profile

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

Recent Profile Visitors

4,750 profile views
  1. Do report back! I haven't really taken off with v5 yet due to my own crash issues (sim crashes that is, not myself crashing 😉).
  2. At least since P3D v5 I have quite some spare FPS to share myself 🙂 .
  3. -4000 fpm on average from FL100 downward, yes. But you can see the descent rate goes to over -6000 fpm (close to -8000 fpm) at glide slope capture and that's just a no-no. You can also see another dip to above -2000 fpm while on final which is again well over the limit, commonly not more than -1000 fpm descent rate on approach. Factoring in the speed as well which presumably kept the gear from extending this is bordering on criminal negligence to be honest. I guess that's what the PIA spokesperson was referring to when they said the crew didn't follow SOPs.
  4. Excuse me for not taking this the humorous way, but why would you want to spread fake news? They said the NGXu comes after the 747 is out so I assume they are working on right now after clearing some bugs of the new 747 for v5. Then comes the 777. The 747 gave us a benchmark and for the NGXu they said they aren't expecting more than a few weeks of testing. So probably still some 2 weeks or so. I'm using the NGXu in P3D v5 and I have to turn off HDR because otherwise the cockpit will be very dark. Also PBR in general seems in need to be reworked slightly to account for changes in lighting in v5. The EFB performance pages can't be used because you can't load the airport databases since it's obviously still looking for v4 paths. Other than that it works fine. Although I can't rule out the NGXu is the reason I keep getting blue screens in P3D v5, although I doubt it.
  5. 5.6 Mbps. Sigh. Unless I buy that wireless thing for I don't know how much to get 28-ish Mbps. And some of you are contemplating upgrading from 100 Mbps. Maybe share some of your Mbps with others 😄.
  6. Entire active product line (not the NGX) including the 777 will be updated to v5 for free, so no.
  7. To add my 2 cents of crashing experiences: What I've tried so far is flying the NGXu (regedit method) with ASP3D, airport addons, Orbx and Pro-ATC X in VR and around an hour or so into the sessions (minutes after reaching TOC usually) I keep running into blue screens. My CPU is slightly overclocked to 5 GHz using a preset saved by the manufacturer in the BIOS.
  8. Not via the monitor menu or not even via Windows' display settings?
  9. Here's a graph of the descent profile from FL100 onward, courtesy of a poster on PPRUNE via FR24. They were racing down already from FL100 with something of a 6000-ish fpm rate to capture the glide slope. 4 minutes from FL100 to 'touch down'. Talk about chasing that descent path.
  10. But that's what I said. I agreed on number 1 to abort the approach. My point is without the CVR and FDR data there's not really a way to judge the decisions taken after the ill-fated 'touch down' because I would say it was a warning concert going on with systems failing and ultimately the engines shutting down. Couple that with the process of realizing or trying to realize what just happened on that runway and I'd argue that you're at the limit of what's humanely possible in terms of dealing with a situation mentally pretty fast. After going around it was just a matter of trying to keep the thing in the air and reach that runway somehow. So while the decision to keep going on that highly unstable approach was utterly inconceivable (unless a good reason is found during the investigation) and in that way clear pilot error, I don't think there was much they could have done after they went around given all the mental capacity was likely just exhausted by trying to maintain altitude. I'm not sure you would be thinking of the military field in a moment like that for example.
  11. My monitor is set to 100HZ since it is Gsync. I have no idea as to the difference of Gsync and Vsync. although i read about it i dont know how it applies to the sims. So you are saying to reduce my 

    refresh rate to 30 hz?and in the sim itself set it to ??

    can you specificaly tell me what setting to use as a trial?

    my monitos is Gsync the graphics card is an ASUS RTX 2080ti strix. My monitor is capable of 100Hz and it is selected to 100 Hz .

    the limiting frames in NVIDIA control panel to 40 frames, and in the sim i have the vsync the triple buffering and the slider to unlimited as well as the variable refresh rate ON.

    Given what you see above can you reccomend any settings to reduce the stutters and blurries ?... thank you

     

    1. threegreen

      threegreen

      I didn't know you had a gsync capable monitor. In P3D v5, there is a gsync option. Use that instead of vsync and see what it does for you. Otherwise, I would recommend trying out the option I posted in the thread. I'm speaking from experience here. I had stutters in P3D until I reduced my TV to 30 Hz with the frame rate limiter set to unlimited within P3D and vsync plus triple buffering on. I also used

      [MAIN]
      FIBER_FRAME_TIME_FRACTION=0.10

      in the Prepar3d.cfg file to help with blurries in P3D v4.5. The experience was much smoother. I've since switched to VR flying so I'm not sure how this will play out in P3D v5. In any case, everyone's system is different so YMMV.

  12. What is your monitor refresh rate? If you don't know, you can right click on the desktop > display settings > advanced display settings and check there. If it's 60 Hz or higher, my suggestion would be to change it to 30 Hz with P3D's frame rate limiter unlimited and Vsync checked. Vsync will sync your frame rate to your monitor's refresh rate, in this case it will limit frames to 30 for a refresh rate set to 30 Hz. I don't know your current settings, but my guess would be that your monitor's refresh rate is higher than 30 Hz (60 probably) and P3D won't give you anywhere near 60 FPS. In this case the CPU is trying to compute all the extra frames trying to get to 60 FPS but it can't. This will cause stutters. For me it works much better if I set my TV to 30 Hz with the frame rate limiter unlimited and Vsnyc (plus triple buffering) on. Now it just stays at 30 FPS and there are no stutters because it's not trying to produce a frame rate it can't achieve anymore. The issue with this argument is that you can't compare P3D running on a home PC to a level-d sim with all kinds of extra computing units for all sorts of processes.
  13. Number 1, absolutely yes. But I can't even imagine the confusion going on on that flight deck onward from the point when you realize you just touched down on your engines. Perhaps they didn't even realize that. Then you have both engines quitting and from there it was probably a warning concert going on. While we do have facts, a lot is still not known. The approach doesn't seem good at all, but I don't think it's fair or even possible to judge at this point.
  14. This is a really good post, thanks. That's what I was assuming, that even slightly better conditions, whether weather-wise or in terms of handling the aircraft or both could possibly have made a huge difference. It's heartbreaking how close they were to at least avoiding the buildings. Though it's a miracle still that only 4 people on the ground suffered injuries and even the buildings hit are reported to have suffered 'minor' damage, considering an aircraft crashed into the place. Same goes for the 2 passengers surviving and being able to give interviews just 2 days after. This could have easily been even worse.
  15. The reply above was probably not very clear on what I meant because of the way I used the 250 ft. I wasn't trying to indicate they were 250 ft higher or lower in itself, but rather that the difference in pressure altitude, even if just 250-ish ft, and its penalty on performance may play a role in just making it or not, especially if combined with one of the other factors (lower AOA for better gliding, for example).
×
×
  • Create New...