Jump to content

JeffF

Members
  • Content Count

    22
  • Donations

    $0.00 
  • Joined

  • Last visited

Posts posted by JeffF


  1. I’ve got a weird one here with the PMDG 737-800. “Reset Cockpit View” should result in a view looking out the pilots side windshield. I have it mapped to button 2 on my joystick. I also should have this view when clicking “Fly” in the sim. I was flying last week, still on SU9. In flight when pressing the button to reset the view instead of looking out the windshield it points down to the pilots control column under the yoke. Prior to takeoff and through most of the flight it worked correctly but the view when clicking Reset changed while enroute.

    From that point on, when clicking Fly to get started it defaults to looking at the control column. This happens ONLY with the 737-800 passenger aircraft. The cargo -800’s, all variants of the -700 and every other aircraft I checked works properly, looking out the windshield.

    To troubleshoot I uninstalled the -800 and deleted the directory C:\Users\Username\AppData\Local\Packages\Microsoft .FlightSimulator_8wekyb3d8bbwe\LocalState\packages \pmdg-aircraft-737\work which will cause a recompile on the next startup.

    I reinstalled the -800, started the sim and still have the same view. This morning I remapped all the Cockpit Camera settings and still have the same result. I know it must be something specific to the -800 since all my other aircraft work correctly.

    Does anybody have any thoughts on what might fix it? Thanks in advance!


  2. 4 hours ago, AvAngel said:

    I just get a little sad of seeing even positive topics get someone trashing the best thing we had in years. It's not perfect no, it's delusional to say so, but it's a bloody good start for a new generation of sims.

    Eh, personally I just let it slide off by thinking back to what we said in my Army days - "A complaining soldier is a happy soldier." 😉


  3. On 4/28/2022 at 9:33 AM, AnkH said:

    Reason: Asobo continues to have basically no clue about their own engine and simply plays around with it. Sometimes they get stuff fixed by chance, sometimes they break things. If they would really KNOW their own engine, such things should not happen 2 years after release... /sarcasm off.

    At times I think they use the million monkey development methodology - Give a million monkeys a million piano's and one of them will eventually play Beethoven.


  4. 4 hours ago, Dillon said:

    I hope people are seeing now why this cloud/constantly hacking on software doesn't work.  Endless development in real time with no oversight or accountability.  I'm not a fan of the cloud and a developer's free will to keep monkeying with the product.

    Thank you.  A couple years ago I retired from a career in corporate software development. My last few years I had to suffer through the "Agile Development Methodology", which based on what I'm seeing with MSFS is what MSObo is using.  To me it was a developers nightmare.  Slam dunk software updates on a monthly schedule solely so IT Management could pat themselves on the back trying to justify their existence.  At the same time what the users really needed got put on a "roadmap" to be implemented who knows when and when implementation for their needs finally arrived, they usually got half of what they asked for.

    I'm done ranting.  Please carry on. 😁

    • Like 8
    • Upvote 2

  5. 10 hours ago, Krakin said:

    I've seen him admit that updates were rushed out the door and I've seen him speak candidly many times about issues 3PDs are facing with the SDK. Y'all need to stop.

    All that does is make Neumann a master of the incredibly obvious and telling us what he thinks we want to hear.  We've seen little to no positive effort in resolving these issues.

    • Like 1

  6. 20 hours ago, pmb said:

    I think the gist of David's analogy isn't just insufficient testing. They may do quite some isolated testing of different modules in - from what I heard - quite a number of different builds in parallel. The point is missing final testing of the complete release with all the modules cooperating (or not).

    Or, as some suggested: They should task a couple of their fellows with just normally flying the complete pre-release version for at least one day before release.

    Kind regards, Michael

    Ok class, can we spell i-n-t-e-g-r-a-t-i-o-n t-e-s-t-i-n-g?  It's only been common IT practice since the punch card days.  Until now, that is.

    I somehow survived and a couple years ago retired from a 35 year career in corporate IT, software development.  A common saying/joke among the developers was, and still is, "we never have time to do it right but we always have time to fix it."

     

    -Jeff

    • Like 5

  7. 8 hours ago, RobJC said:

    Since this problem did not exist in the early builds, then got nerfed, fixed and then nerfed again. Was this part of the code overwritten accidentally when other changes were being added? If the code is truly modular/object oriented a call would be made to set the draw distance, which itself is a standalone module/object/class. But if the draw distance is commingled with a bunch of other code, when people are working in this area they can accidentally hammer the draw distance.  

    At this point i pretty much expect any part of this sim to be broken anytime we get an update. Here’s a new airplane. Now gauges stopped working on another airplane. I hope i am wrong but we’ve seen a lot of evidence that this is a real problem. 

    Exactly this.  (I too spent 35 years in software development before I retired a couple years ago.)

    Remember a few World Updates ago where they fubar'd the flaps and we were all floating down the runway and couldn't land?  A WU should have *no* effect on aircraft handling.  I still laugh at Asobo's first "fix" - users edit the individual aircraft config files and divide the exist flap parameter by 2.

    • Like 2
    • Upvote 2
×
×
  • Create New...