!! Windows 7 no longer supported !!

As Microsoft will stop supporting Windows 7 on Jan 20th we will be unable to test any of our
products on that platform. It may work, or it may not, but no guarantees from our side. 

Jump to content

Meese

members
  • Content Count

    41
  • Joined

  • Last visited

Community Reputation

18 Good

About Meese

  • Rank
    Flight Student - Groundwork

Recent Profile Visitors

759 profile views
  1. The crew voices remain the same with voice on or off, seemingly 100%. I'd like to just lower the volumes a bit, but nothing either in P3D or the 3rd MCDU actually makes any changes to the checklist volume.
  2. No, 330, I'm at 1% and there's no change in volume. If I set one voice at 1% and the other at 100%, they're still the same
  3. Hehe, great stuff, thanks! Any word on checklist volume settings?
  4. This: https://streamable.com/xt8la Loading turnaround state, and at after start checklist complete the floods come back on. In the middle of the day? That's just a waste of light bulbs!
  5. Whatever I do, the volume percentages for the checklist PM and PF does not seem to change their actual volume at all. 1% is the same as 100%, even after a sim restart. And while I'm happy with the latest hotfix sorting out landing lights and GSX integration, could the cockpit lighting auto features please be given an on/off-option? The ghost-operated table and foot rests are already breaking immersion, but someone suddenly changing all my lights is even more bothersome. Thanks!
  6. The lack of this function is a bit annoying, especially since all the gremlins aren't quite ironed out yet. I'm now little over halfway on a 9h trip, but for some reason I've ended up with 10 metric tonnes more than expected compared to what I uplifted, and will probably have to circle for 20mins at the destination to get below MLW, when planned landing fuel would put me 8 tonnes under that limit. It's not a fuel planner error, it's not a bad PFPX performance file, I did my first fuel check about 2 hours into flight, and for some reason the climb and initial cruise only spent 6 tonnes when it should have spent 16. My memory, fuel used, MCDU3 listed uplift, and PFPX planned block fuel amount all check out, and every single fuel check carried out in the following 3 hours has been right on the money, except with the same difference above the expected fuel level. My suspicions fall to some back and forth between panel states I had going on before and after push, as I was combatting a checklist problem already brought up elsewhere. The point: As long as it's not a 100% failproof software with a 100% failproof user base (which, obviously is literally impossible), it would be nice to have an alternative to splashing into the ocean short of the destination or holding for X minutes overhead for your MLW. Whether it's the product or the user, it's never gonna not happen, and this very basic function could make their day just that little bit better.
  7. Should being the operative word. I tried everything bar verbally convincing my virtual copilot to continue, but continue they didn't. (Pardon my double posting, keeping further posts in this thread)
  8. Should being the operative word. I tried everything bar verbally convincing my virtual copilot to continue, but continue they didn't. I'll keep further replies in the more visible/relevant thread:
  9. Same problem, though it occured without me having updated anything manually (I usually ignore FSDT updates for a while). I don't know if GSX does anything automatically. The workaround is to start the engines without checklist and copilot, do the after start flows, then select the taxi aircraft state, reload the loadsheet with instant, check baro ref, squawk and the PERF page (I got Vspeeds in the 240s and had to reenter the flap config). Rest of the flight should be fine.
  10. I had these after install as well. My fix was to restore P3D defaults from the ENVSHADE software I use, then delete the AppData\Local\lockheed martin\Prepar3D v4 folder and the Prepar3D v4\ShadersHLSL folder, then reapply my third party shaders. In searching for a fix, I've also seen people recommending using the Repair-function in the P3D v4 Client installer after deleting both shader folders.
  11. Same problem, though it occured without me having updated anything manually (I usually ignore FSDT updates for a while). I don't know if GSX does anything automatically. The workaround is to start the engines without checklist and copilot, do the after start flows, then select the taxi aircraft state, reload the loadsheet with instant, check baro ref, squawk and the PERF page (I got Vspeeds in the 240s and had to reenter the flap config). Rest of the flight should be fine.
  12. I won't deny this is a grumpy request, but I would be very thankful if the options for all the realism actions could be extended to switch off the heart attack & hearing impairment inducing flightdeck door buzzer, and magically moving tables and foot rests in the cockpit. I realise a lot of people really appreciates this, but for me nothing breaks immersion like MY table being folded out infront of me like I'm actually the toddler I mentally am! If the customer base largely prefers all these things, by all means leave them as standard, but please keep us no-fun grumps in mind?
  13. Piling on, there's something odd about the continued motion after a return to neutral stick (not with a max deflection snap to center, but a calm measured return to center which even in a non-FBW would be expected to at least almost null rates). Besides that it did fly fine on departure, but on landing I had severe roll delay coupled with pitch over-sensitivity, and had there been any gusts or crosswinds I would have had to go around.
  14. Thanks, but the arrival is not the issue, I never care what PFPX plans for SID and STAR (unless in the US, of course), as long as the start/end waypoint makes sense. The fuel difference will be marginal as long as it's the appropriate runway planned, and less than contingency anyway. Srcooke: Thanks, I've used Cruise alt MAX and OPT a lot without any change at all. I've not deselected stepclimb. In any case it's obvious that the max/opt dropdown doesn't do what it's supposed to as it changed nothing in the original example (and neither did MIN, both were simply ignored). I don't mind that there's an optimization function, most of the time it's really good! But I want to be able to turn it off when it goes haywire. The problem is that the mentioned options in place to modify/deselect only works when the funciton isn't going haywire, which isn't helpfull.
  15. The profile doesn't seem to be the problem, I get this completely arbitrarily, but with any profile for any aircraft at any odd time. This never happened with v1.x, but in v2.x it's been every 5-10 flights. I put the exact same parameters in now, and it spit out N0322F110 instead. Not great still, but at least the route isn't a subway line anymore. Whatever addition in v2.x that causes this should be completely deselectable for those types of flights this level optimisation function isn't good at dealing with. And why does it arbitrarily ignore MIN FL?
×
×
  • Create New...