If you want a Honeycomb Alpha for Christma you better order fast because we are quickly running out of stock!

Jump to content

Meese

members
  • Content Count

    28
  • Joined

  • Last visited

Community Reputation

17 Good

About Meese

  • Rank
    Flight Student - Groundwork

Recent Profile Visitors

696 profile views
  1. 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.
  2. 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?
  3. A fix, or at least a working option to ignore airspace and restrictions on levels (or at least not ignore me when I select a MIN Alt/FL), would be nice.
  4. Meese

    False FOB indication

    No problem, good luck!
  5. Meese

    False FOB indication

    319 CFM, fuel and payload loaded instantly via 3rd MCDU (only on ground, not redone airborne after loading save). Flight was first leg since restart, no slew or change after default F22 was positioned on stand and A319 loaded. Cold and Dark state loaded as DEF. Fuel/payload was not revisited or checked after loading save file, as MCDU 1&2 and ECAMs showed expected values on load. PS., there are posts on the forum where I mention changing cfg files for camera/view reasons, however no such changes has been made. All files are as per clean install plus updater, no extra liveries installed or other changes made.
  6. Meese

    False FOB indication

    1.2.2.1, P3D v4.3, Win10
  7. Meese

    False FOB indication

    Coincidentally, on setting up the return leg now, I've loaded 13800kgs. On INIT page 2, clicking the block fuel LSK to bring up the actual fuel shows me 12.6, while the third MCDU, the FOB and P3D's fuel&payload all agree the number is 13.8. Interestingly, 12.6 seems to be a rounding error away from having full wing tanks and nothing in the centre tank. This could mean nothing at all, of course, but it's an oddity I thought worth mentioning.
  8. There's a few threads on this already, but I thought I'd make a new one for simpleness' sake. I decided to cut a flight short yesterday, making a save enroute to GCLP on cruise, and disabled the DEF aircraft state before I shut down the sim. This morning I picked it back up, and loading the save was happily successful, all systems correctly in whatever state and with whatever data they'd had yesterday evening (except the chronometer, but that's to be expected). After a (hard) landing and shutdown, I took a look at the flight log printout, and finally noticed that the FOB had been stuck since 1 hour before landing (the time at which my savefile was made), as the printout was reading the true fuel state while the FOB was doing it's own thing. I've added whatever log files I found, two screenshots, and the savefiles used in two zip archives attached, in the hope t hat this should help n arrowing down the cause. Prepar3D v4 Files.zip AS319 fuel.zip
  9. I've seen this a few times too, and we're not alone.
  10. This is true, but also a necessity when someone messes with my muscle memory actions linked to operating basic functions in the sim. Would definitely be happy to see a config option.
  11. I'm having this issue as well. Tried both raw and the other native P3D input, with/without FSUPIC assignments and/or calibration, recalibrated in P3D, reassigned axis and adjusted sensitivities and blind zones. No change. Seen it on two out of three flights, both using checklists and copilot. The first time, initiating taxi made it snap back to centre and enabled full deflection up and down. The second time it didn't, so I skipped the item and tried to depart to see how it reacted. I had pitch authority in flight and autoflight seemed fine, but then the -150ft pressure cabin issue reported elsewhere started happening, so I abandoned the flight. I'll try to tinker some more to see if I can find any rhyme or reason to these weird symptoms (yes I'll make the log files).
  12. Meese

    Cabin Pressure

    Had the exact same issue on my third total flight (done today). Up to date product, only ActiveSky, FSUIPC, 737 NGX, MJC Q400 and ORBX addons installed, on a two month old clean v4.3-install.
  13. ^This is the solution, and I'd like to note my bafflement on the philosophy of changing the function of elementary view key assignments without having it as an option in config/installer or at least mention somewhere what's going on.
  14. I had this issue tonight, flying EINN-KJFK in the A318. Loaded 18000kg at EINN, landed at JFK with the FOB indicator and Fuel page both claiming I had 2980kg on board, except I'd had that excact value since Newfoundland, however the total fuel burned value on the Fuel page correctly indicated the burned level of 17700kg (Yes, I landed with 300kgs... I apparently need to tweak the bias in PFPX for such long distance flights). I had not run the updater, but I bought and installed the product today so this was version whatever is currently packed in the installer. Prior to departure I had some issues with my graphics driver and used a save-file made just prior to push to avoid re-preflighting after a few sim restarts (though I had to preflight everything anyway, panel states didn't save). I also used the aircraft state page to set "ready to taxi" to expedite the departure as I had to get around to something else. I know all of these things are in general dumb decisions if you are aiming for a stable flight, but I thought I'd use this flight to see what gremlins would appear following such abuse.
  15. Here in Norway Wideroe has upgraded even their old DH8-100 series with P-RNAV approach capability since they operate on so many non-precision approach aerodromes in often adverse weather. If Bombardier can fix up the old turbopros as such, I'm sure they can do the old turbofans as well.
×
×
  • Create New...