BlueNose

Ok, this happened again. Symptoms are exactly the same. This time I was on the ground at KDAL, refueling at realistic speed, IRS still aligning. I'm making a video now, and will post a link here when its ready. EDIT: never mind, problem went away when I started the screen recording. Perhaps I can try doing screen recordings to fix this if it happens again? [IMPORTANT] EDIT 2: At first I tried to do an AVI recording from inside x-plane, and got a warning message that this 'cannot be done while running a desktop FCM app' (probably something to do with the way IXEG does route editing externally). I then tried to do a quicktime screen recording and found that the problem had gone away. However, I just checked the log.txt - again there are a few hundred lines of 'no such error message' from the JAR Ground Handling plugin, however these stop after X-Plane throws out the 'cannot do an AVI recording' message. This shows two things: 1) the ground handling error was somehow causing all displays in the cockpit to freeze, as this was the same log.txt message as last time, and 2) attempting to do a an AVI recording through File>Toggle AVI Movie solves the issue.

@Litjan Thank you for your reply. I'll post updates here if it happens again. And since you're reading this thread I'd also like to briefly go off topic and say that the IXEG 737 is an incredibly pleasant aircraft to fly and pretty much perfect (discounting some rare FMC shenanigans)!!!

@mmerelles I apologize, I tried to explain my problem as clearly as possible. When I make changes in the FMC, I do not experience any problems. What happened here has only happened once. Framerate was perfect (30-50fps the whole time). This happened while I was in cruise, and I did not touch the FMC. All elements of the aircraft were working perfectly and smoothly with no drops in framerate. However, all six screens in the cockpit (the PFD, MFD, and FMC screens on both sides) got stuck, not showing any changes. This included the altitude and speed indicators and the artificial horizon which all did not move. The 'moving map' was also stuck. When pressing keys on the FMC, nothing changed on the FMC screen. It seemed that the information was all there, just not being shown on the screens, as they would all update (including the FMC) if I changed the MFD settings in any way (ie changed the range, the mode, brightness). There is no youtube video and I cannot reproduce this, but it was quite obviously not caused by any antivirus or by editing the route. Since this happened I have flown another flight of similar length (Grand Cayman to Belize City), and nothing out of the ordinary happened. Once again, I did not have any framerate drops when editing the route, so this is not caused by antivirus.

The thing is though, I do not actually have any antivirus program installed that could be causing this. It also did not occur while editing a route. Also, the symptoms of the problem are nothing like what is described by other users experiencing that antivirus-caused framerate drop. I was at 30-50 fps the whole time, and everything else worked perfectly, only three (ok technically six) screens that froze. If this was an issue occurring because of antivirus software would there not be a framerate drop every time I edited the route? Again, this only happened on this one flight, and hasn't happened before or since (yet).

This is a pretty big one. During a brief flight KEYW-MWCR, shortly after reaching T/D, I looked at the FMC to insert an arrival (GORAN3, VOR approach rwy 08). The FMC would not react in any way to any button I pushed (page selection, prev/next, keyboard). It was on the LEGS page at the time and showing direct TADPO, which I had selected straight after takeoff. I tried changing the map range and it switched to showing me almost on top of UCL, way past the south coast of Cuba and 15 minutes past TADPO. At the same time the FMC switched to the DEP/ARR page, which I had tried to select previously. Basically what I figured out was that the PFD, MFD, and FMC were all completely frozen, and only updated once I touched something on the MFD control panel. This could be the range, mode, brightness... anything that makes the little MFD pop up in the bottom left hand corner of the screen would update the PDF, MFD, and FMC. All the background processes were working though: the aircraft followed the route, descended at the correct point, decelerated at 10,000 feet, etc. I was able to input an arrival by pressing one key at a time and updating the FMC by changing the map range every time. At some point I noticed that if I kept holding the range selector (or brightness selector or any other MFD control) with the cursor to keep the popup map up, that would actually move and show everything properly. Basically I used a combination of standby instruments (as the PFD was also frozen), VOR DME and a visual approach to land at MWCR. I'm on mac, so it can't be anything to do with that Windows Defender problem. After closing x-plane I checked the log.txt, and beginning at around 48 minutes into the session (the flight took 58 minutes, so the whole session was probably around an hour and a half as I spent some time on the ground at KEYW before taking off) there are a few hundred lines of 'no such error' readouts produced by the JAR Design ground handling plugin. These continue until the end of the session. There is nothing else in the log.txt after the first 'no such error' message appears except for hundreds of lines of the same thing. This was fine due to the short nature of the flight, but I can predict that on longer flights such a freeze of the PFD, MFD, and FMC would make continuing the flight very difficult. If this was somehow caused by ground handling, that's a pretty big deal, as its highly likely that people using the 733 also have that plugin installed.