Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About intelfx

  • Rank

Recent Profile Visitors

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

  1. Yes, in fact I can reconfigure the hardware to emit "level-triggered" events but I'd prefer not to do that because it would mean I'll have to reflash the HOTAS every time I'm going to fly a different airplane or play a different game.
  2. Currently, the CL650 has just one command to operate the parking brake (CL650/pedestal/park_brake). It would be very helpful for HOTAS owners if there could be separate commands to set and release the parking brakes, which then could be bound to separate positions of a hardware parking brake lever.
  3. Given the FO configuration demonstrated in the attached file, when flying, the FO will automatically read, confirm and advance multiple checklist items in a row, despite actually performing no actions.
  4. It would seem that the automatic FO keeps its own track of the current checklist/item and does not pay attention to the checklist and item that's currently selected on the MFD. If a wrong checklist is started or the current checklist/item is advanced by mistake, even if you re-select the correct checklist/item on the MFD, the FO will continue to track its own position in the checklists and not what is being shown on the MFD right now. Even if it's not a bug, it's unintuitive/unrealistic behavior because I'd expect my co-pilot to actually read stuff from the MFD, instead of going "hey
  5. For anyone else victim to the games that Russia is apparently playing with DNS infrastructure on a national level, you can try adding an override for navcen.uscg.gov into your hosts file (/etc/hosts on Linux, C:\WINDOWS\System32\drivers\etc\hosts on Windows): navcen.uscg.gov (At least in this country, it would seem that the host itself is not being blocked, just the DNS entry is being filtered.)
  6. Understand that a proper/matching CSL for CL650 (CL60 code) is planned, but very low on the list. In the meantime, does anyone has an idea which publicly available CSL model of a similar jet can be used as an interim solution?
  7. Isn't it supposed to be in public domain, like all other data released by the US government?
  8. Yes, it is connected to the Internet. And indeed, that seems to be the problem: 2022-01-08 08:49:57 CL650[alm.c:151]: Unable to download GPS almanac from https://navcen.uscg.gov/?pageName=currentAlmanac&format=sem: Couldn't resolve host name
  9. After completing the flight compartment checklist, the GPS subsystem appears to be stuck in a weird state with debug screens not working and nothing apparently happening.
  10. Yes, of course, I've double checked that the built-in failures were all disabled (i. e. "always working"). So, I just flew the same route (that I unsuccessfully tried to fly twice yesterday) without time acceleration and the problem did not occur. This is far from hard evidence but it supports the theory. So, is it a bug? IOWs, should I expect this to be fixed someday or should I just view this as an inherent limitation and refrain from using time acceleration?
  11. intelfx

    Oxygen Mask

    I'm sorry for necroposting, but I have just reproduced this exact bug, can confirm and also provide a possible explanation. It happens when UI scale is not set to 100% (which explains the reproducibility — @robder likely has a high-DPI Retina screen which probably necessitates the use of UI scaling). Any chance this could be fixed (along with other bugs that manifest when UI scaling is used)?
  12. (Okay, now I'm embarrassed about the amount of topics I created in recent days, but this one is a serious question.) In recent days, I made four simulated flights with TBM900 (not counting various experiments and training — that is, long flights). During all four of these, the TBM900 broke in (almost) the same way. Three times (#1, #2 and #4), the engine suddenly caught fire and the crash bar dropped without any intervention on my part. One time (#3), ITT suddenly spiked to 1000°C and continued to raise extremely rapidly through 2500°C, at which point I pulled fuel and ITT started to
  13. Hmm, so I flew with this cabin in "deathtrap" condition up to 30000 ft, and it did pressurize okay. Is it going to slowly leak air or something?
  • Create New...