Announcement

Collapse

PMDG Forum Rules

1) SIGN YOUR POSTS. Since 1997, we have asked users to sign their real name, first and last, to all posts in the PMDG forum. We do this in order to keep conversations personal and familiar. You took the time to be here, we want to get to know you. This is one of the few rigid rules that we enforce regularly. We do so because we feel that forums in which users must engage one another personally are generally warmer, more collegial and friendly. Posts that are unsigned will be quietly removed without comment by the moderators, so to make your life easy- we recommend enabling your forum signature so that you never need to remember. Do this by clicking the username pull-down at the top right, then selecting "User Settings." You will find the signature editor on the ACCOUNT tab, about half way down the page. Look for "Edit Post Signature." Be sure to click the "Show Signatures" box.

2) BE NICE. We are all simmers here and no matter our differences of opinion, we share a common love of aviation, computing and simulation. Treat everyone else in the forum with respect even when you disagree. If someone frustrates you, walk away from the conversation or ask for a moderator to get involved. Speaking of Moderators, they prefer not to be treated as "The Thought Police" but if any behavior infringes on the enjoyment of another user or is otherwise considered to be unacceptable in the moderator's judgment, it will be addressed in keeping with our view of ensuring that this forum remains a healthy environment for all simmers.

3) BE LAWFUL: Any behavior that infringes upon the law, such as discussion or solicitation of piracy, threats, intimidation or abuse will be handled unsympathetically by the moderators. Threats and intimidation may, at the moderator's discretion, be provided to law enforcement for handling.

4) BE FACTUAL: When you post, always be factual. Moderators will remove posts that are determined not to be factually accurate.

5) RESPECT COPYRIGHTS: Posting of copyrighted material such as flight manuals owned by Boeing or various airlines is not allowed in this forum. If you have questions related to copyrighted material, please contact a forum moderator for clarification.

6) RESPECT PMDG: We love to hear what you like about our products. We also like to hear what you think can be improved, or what isn't working. Please do tell us and we will always treat your feedback with value. Just be sure to treat the team respectfully, as they do put a significant amount of effort into building and maintaining these great simulation products for you.

7) RESPECT PMDG DEVELOPERS: All of the developers will spend some time here. Given the ratio of developers-to-users, it simply isn't possible for us to answer every post and private message individually. Please know that we do try to read everything, but developer workload is simply too high to manage personal contact with tens-of-thousands of users simultaneously. In most cases, members of the development team will stick to conversations in the forum and will not answer private messages.

8) RESPECT OTHER DEVELOPERS: PMDG has always advocated for a strong development community and we have many friends within this community. Every developer offers something unique that helps to make the simming community larger and more vibrant. We insist that you treat our friends respectfully.

9) RESPECT MODERATORS: Moderators have a tough job, and none of them enjoy having to stomp out negativity. If a moderator has to weigh in to keep a thread peaceful, please respect that effort and refrain from giving the moderator any grief.

10) If you require official support for any of our products please open a support ticket through the support portal, https://support.precisionmanuals.com

11) This forum is designed primarily as a vehicle for the PMDG development team to interact with our customers, and for customers to interact with one another in a manner that is positive, supportive and assists in the general advancement of understanding the simulation and helping to make this and future simulations better. Any other use of this forum is not permitted, including but not limited to discussion of pricing policies, business practices, forum moderating policies, advertising of non-PMDG products, promotion of events, services or products that are not approved in advance by PMDG or any other topic deemed unacceptable by any forum administrator

12) HAVE FUN: This is the whole point of it all.
See more
See less

Airplane freeze

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #91
    Originally posted by GLC222 View Post
    Emi had a freeze captured on a recent live stream and he messaged PMDG about it.
    Same happened to me today at the MPTO ILS approach 1 min later I put a waypoint after VECTORS. So probably vectors is a problem.

    OFF: Has Emi got fired by his real airline? He films very long videos every single day!

    Sincerely yours
    Clifford Sherman

    Comment


      #92
      Just happened to me. I was adding a pseudo waypoint to a STAR. I down selected the waypoint I wanted to serve as the basis for the pseudo waypoint and FMC froze and everything in the cockpit froze and became nonfunctional but airplane kept flying. Interestingly this pseudo wapoint was also after vectors.
      Greg Clark
      AMD 5900X
      NVIDIA 3090
      32GB RAM
      Win 10 Pro

      Comment


        #93
        Greg-

        Can you attempt to recreate EXACTLY what you did- and if it succeeds in repeating, open a support ticket with EXACTLY the replicable steps?

        One of the things that modern programming tools do is to capture what are known as "Exceptions" that cause code to cease executing normally. Unfortunately, the platform designers have decided that developers of complex, modern aircraft like the ones we create should not be given modern programming tools to work with. It is a ridiculous shortcoming that makes finding these sorts of things incredibly more complicated than it would otherwise be.... So instead we have to resort to the sort of debugging techniques that many of us used back in 1992- thus having a replication case that ALWAYS works goes a long way toward allowing us to code the problem into a corner from which we can identify the specific code callback that fails...

        It can take months of developer time that unfortunately should to to building actual products.

        We love having to waste time this way- but with your help we can find it.

        Robert S. Randazzo
        PMDG Simulations
        http://www.pmdg.com


        Comment


          #94
          I just want to say I can somewhat consistently replicate the issue by simply increasing the simulation rate. Every time I speed up the simulation rate during a flight the probability of the freeze seems to significantly go up. I tried getting it to freeze on a flight from Vancouver to Kelowna at 8 times speed while rather carelessly clicking around the mcdu changing STARs/ Approaches/ also changing A/P modes, basically whatever came to mind and sure enough after a while the full cockpit just froze... anyways if that helps you replicate it and you have some time to look at it just thought I'd share my two cents

          Best,
          Andrew

          Comment


            #95
            Just had an issue just like the one seen in Emi's recent video linked on the previous page, and thought I would add it to this thread.
            Flying from EKCH to EDDV on Vatsim, in the 737-600 (version 3.0.63), I was ~17 NM out being vectored for 27L.
            On the legs pages I clicked (LSK 1L) on the current waypoint (ODINI) to insert it again just for a quick update of my vertical situation. I had previously performed this updating minutes earlier to the same waypoint with no issue.
            Just as seen on Emi's stream, all cockpit switches and instruments froze except for the whiskey compass. Equally, my keybinds and controllers still work and i kept flying in the sim. I disconnected from Vatsim and landed+taxied in, with the weird experience of having the plane hovering over the ground as the external model also appears frozen and doesn't show the gear down.

            Unlike Emi I am running on the SU12 beta (1.31.22.0).
            For EDDV I am running this scenery (https://flightsim.to/file/46554/eddv...tional-airport). Navdata is updated to the current AIRAC-2302 via Navigraph. I have previously landed here once (on 09L) as well as departed with no issues.
            I never touched the simulation rate, or do anything out of my ordinary procedures in this flight, and it is first time experiencing this.

            Screenshot of the cockpit parked at the gate with instruments reading 250kts and 4700 feet still.
            737_600.png

            Still have the sim running with the frozen panel right now if someone reads this now and wants me to try to do anything specific.


            -Morten Nor
            Attached Files
            Morten Nor

            Comment


            • Avionic
              Avionic commented
              Editing a comment
              Using FSLTL for model-matching on vatsim, connecting via vPilot.
              But once i disconnected no other traffic should be in the sim. I will have to see if i can bind something to change transponder mode, but will likely not be able to visually confirm if it has been turned off.

            • Avionic
              Avionic commented
              Editing a comment
              Looks like there is no ingame binding for changing transponder mode. I don't have Axis and Ohs, spad.next, or other programs already installed, so with the simulator still running the flight I would probably be unable to get them set up to try and change away from TA/RA.

            • Avionic
              Avionic commented
              Editing a comment
              Shutting down the sim now after having tried all sorts of keybinds out. Never got out of its frozen state, but starting up vPilot again I can see that it is still able to detect when I adjust radio frequency in the sim using my ingame keybinds. Additionally, it is not lighting up in “Mode C”, which seems to indicate that I might have succeeded in turning off the transponder one way or another.

            #96
            Originally posted by rsrandazzo View Post
            Greg-

            Can you attempt to recreate EXACTLY what you did- and if it succeeds in repeating, open a support ticket with EXACTLY the replicable steps?

            One of the things that modern programming tools do is to capture what are known as "Exceptions" that cause code to cease executing normally. Unfortunately, the platform designers have decided that developers of complex, modern aircraft like the ones we create should not be given modern programming tools to work with. It is a ridiculous shortcoming that makes finding these sorts of things incredibly more complicated than it would otherwise be.... So instead we have to resort to the sort of debugging techniques that many of us used back in 1992- thus having a replication case that ALWAYS works goes a long way toward allowing us to code the problem into a corner from which we can identify the specific code callback that fails...

            It can take months of developer time that unfortunately should to to building actual products.

            We love having to waste time this way- but with your help we can find it.
            Robert,
            I was unaware how challenging it is for a developer to find a bug like this in MSFS, appreciate the detailed explanation. I find now that I thought I recalled the exact steps that led up to the freeze, but am unable to reproduce it on several attempts despite having the same aircraft setup, approach, etc. If it happens again, I will document it and send to support.
            Greg Clark
            AMD 5900X
            NVIDIA 3090
            32GB RAM
            Win 10 Pro

            Comment


              #97
              Had a Freeze on the ground flight from KABQ to KTUS (B737-900) landed rolled out and turning off the runway the airplane would not taxi. all controls would move but the airplane would not taxi. Possibility it was my fault, had a 8 knot tailwind so I had a high touchdown speed and some heavy breaking, could have overheated the brakes, and caused my own problem.
              Ken Hand
              AMD 3900X, EVGA RTX 380 XC, X570 wifi, 128GB ram.

              Comment


                #98
                Did you hit the pause button or go into active pause by accident?
                George Morris

                Comment


                  #99
                  Not sure but that is a possibility. I will watch out for that in the future. THANKS
                  Ken Hand
                  AMD 3900X, EVGA RTX 380 XC, X570 wifi, 128GB ram.

                  Comment


                    Well, seems I was lucky until today, because I didn't have any freeze issues yet. However, just flew into EDVE today, finished the STAR and vectored myself on the ILS26. On 2.7NM final and 1200ft, the airplane completely froze and nothing could be clicked anymore. The displays were stuck. I could land the aircraft however manually.

                    This is the last frame of the instruments, when it froze.

                    Boeing 737-800 - Latest version 3.0.64 - MSFS Store version. Never had any problem like this before, since release and I got a couple hundred hours in this aircraft.

                    Flightinfo - No TCAS RA or any other TCAS traffic. Pressed LSK1 to enter the FAF again for the vector, however that happened before the freeze and I've passed that waypoint about 4NM already.

                    EDIT: Flew the exact same approach yesterday, without any problem or freeze :/


                    138543gf61.png
                    Last edited by gvert; 27Mar2023, 13:50.
                    Regards, Tobias

                    Comment


                    • DDowns
                      DDowns commented
                      Editing a comment
                      No RA but you do have TA/RA turned ON and TFC selected on the ND EICAS.

                    • gvert
                      gvert commented
                      Editing a comment
                      True, but that's a normal setting, which I use everytime and never had any problems with, since release... :/

                    • DDowns
                      DDowns commented
                      Editing a comment
                      Granted, but it might be a factor in the bug that hasn't been fully understood yet. If you are using traffic injection try turning changing to mode c (ALT) and fly the approach without TA/RA mode and see if it ever freezes. The more information we gather the better.

                    For the sake of documenting, I had my first frozen cockpit last week while approaching to KEWR RWY 22L.
                    A few miles out of the runway, I had a resolution advisory with an incoming traffic. Since I was flying offline, I set my transponder in stand by mode and once clear, I turned back to TA/RA. A few seconds later I realized everything was frozen.
                    I raised a ticket but I got a very vague answer, blaming FSLTL.
                    Eduardo Cavalieri

                    Comment


                      just wanted to add I have not had any freeze since doing flights with the TCAS in only TA mode. I use PSXT for traffic injection

                      thanks,
                      David Schleck
                      David Schleck

                      Comment


                        Hi there,

                        Just wanted to add my experience: just had my first cabin freeze ever. On short final, after RA situation with FSLTL.

                        Cheers,
                        Daniel
                        Daniel Kovacs

                        Comment


                          Just happened to me when flying to KSYR.

                          I can still roll and pitch but nothing moves in the VC and I can't interact with anything. Displays are frozen too.

                          Was trying to make a direct between CAM VOR and STODA (ILS 28 transition) when it happened.

                          First time I meet this issue.
                          Hadi Kamar

                          Comment


                            1. Delete MSFS data file
                            2. Delete Nvidia Shader cache
                            3. Delete DirectX shader cache

                            "Light on addons" means nothing. Any addon can have a negative impact if it is not done/installed properly. Even if you are not "using that addon". For example, a bad airport in Uzbekistan can cause a problem with flying the 737 from KSAN to KLAX. A bad livery for the CRJ when flying the 737 can do the same. Everything you have in your community folder loads on sim start up. EVERYTHING. I use Addons Linker from .to to mitigate this problem.
                            Mark "Crabby" Crabtree AAL311 | PHL
                            I7-9700KF | 2070 Super | Honeycomb Alpha/Bravo | MFG Crosswind

                            Comment

                            Working...
                            X