Jump to content

andreasxb

Members
  • Content Count

    23
  • Joined

  • Last visited

Community Reputation

6 Neutral

About andreasxb

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks for the workaround, I'll be trying that in the meantime!
  2. As in, literally not entering. I can select COM or NAV for frequency entry and if I enter numbers on the keypad they will appear in the standby frequencies slot, but pressing the enter button will not do anything. Pressing the transfer button will move the previously existing frequency into the main and back. After a while the entered frequency will disappear again, just as it would if you enter a few digits and don't press enter. Also there is no cursor or anything, pressing a number will show up but there is no indication where. It is the enter button above the alphabetic keys, right?
  3. So you can cancel Cautions and Warnings with the rightmost softkey on the left G1000 display, but this doesn't work when the second display isn't running. And it's not enough to just have both batteries on, you have to have gone through all the boot up information screens on the second display until you are on the normal map or engine displays until you can cancel cautions and warnings. I have no idea if this is true to life, but it feels like it isn't.
  4. I was flying the normally aspirated SR22 over SoCal when X-Plane froze some time later shut down. The log says it's because of the Cirrus SR22 Physics Engine plugin. X-Plane 11.50r3 with Vulkan, ActiveSkyXP, SkyMaxx, PilotEdge. I chose the beta Gizmo when I installed the 1.1 update for the Cirrus. The end of the log prior to the crash has SkyMaxx finding a new METAR.rwx file, but according to the file modification dates that was updated ~3 minutes before the crash. The area had strong winds at the time but there was not much turbulence I experienced, if that is relevant. Log.txt
  5. Hm, too bad. Apparently it's relatively easy for me to reproduce, it's happens to me maybe twice within an hour of flying. Also weird that X-RAAS also restarts.
  6. It's loading "default" textures and immediately afterwards loading the current season's textures and that happens multiple times during a flight. This appears to match what was described in the original conflict thread: I also tried fixing it to autumn in the configuration window, but it still loaded default and then autumn at irregular intervals.
  7. So I finally got around to flying the TBM900 more and I've seen TerraMaxx do these things. If I understand it correctly, what I have is the same issue: during flights, X-Plane freezes after TerraMaxx pops up a windows saying it is loading default textures, then it's barely a second until it freezes again with TerraMaxx saying it is load autumn textures. Also, after the default texture loading and before the seasonal texture loading, X-RAAS is also reinitializing. Some other plugins might also, but I can't tell since they don't pop up a message. Now what can I do to get this fixed oth
  8. Not really a request for support, but I want to remark on a few things that came up in the tutorial flight that might be useful for improving the tutorial. Actually it's been a few weeks since I bought this and did the tutorial flight, I hope I remember everything. Configuring the CTOT wasn't mentioned, I guess in an earlier version it was already set to 108% in cold&dark. Similarly the nosewheel steering wasn't mentioned. page 11, Takeoff says to advance power levers with armed CTOT and leave it once CTOT takes over. Together with the later deactivation of CTOT and not
  9. I just tried it once. Planned a pushback turning to one side and a short straight push, pushback guy ended up doing donuts with my plane.
  10. I don't think you can extend TOPCAT with new profiles anyway, only the programmer can do that.
  11. It didn't fix it unfortunately, also it doesn't appear to log much more? The "firmware" version in the log doesn't match the version number on the package, don't know if it's supposed to. Logs are for default King Air -> IXEG -> reload IXEG. GizmoLog.txt Log.txt
  12. Well I was wrong, navdata has nothing to do with it. I completely removed and reinstalled the XP11 IXEG install and updated Gizmo, and I found that like the others, it works if I load IXEG first but it crashes if I load any other plane first (even default X-Plane aircraft) and after a crash, the reload aircraft command from the developer menu gives a working IXEG. GizmoLog.txt Log.txt
  13. Sorry about being unclear, but yes, as I remember it was the same at least in the respect of "OnKickstart" and "GateKeeper". I tried to reproduce it again but couldn't. The one thing I changed between then and now is that I installed current navdata (1802, before it might have been the navdata that comes with the installation), which I missed before since the FMS didn't work after all. That's all I have time for right this moment.
  14. Forget pilots doing stupid things, are you serious about one single device failure being able to take down all of a 737's systems without backup or redundancy? I find it hard to believe that such a death trap would be permitted to fly much less carry passengers. I mean, I was able to divert to EDDF after I decided to treat this as an emergency rather than abort the flight, but after all I was able to just flip the battery switch back on which is not an option when it fails. Anyway, using this schematic as a reference, the generator power control should be on the hot battery bus. Acco
×
×
  • Create New...