Jump to content

Lennart320

Member
  • Posts

    5
  • Joined

  • Last visited

Lennart320's Achievements

0

Reputation

  1. Newest version installed, flew from KSFO to VHHH in the A359 B-LQA Cathay livery. Following Route: KSFO/28L N0497F340 GNNRR3 ALCOA DCT CEPAS DCT COBAD DCT 40N140W/N0496F360 41N150W 40N160W 38N170W 37N180E/N0487F380 35N170E 33N160E 31N150E/N0482F400 DCT NOGAK DCT BIXAK DCT RYUKI Z34 TETTA Y342 IGURU G581 ELATO V522 ABBEY ABEY4A VHHH/07R When I inserted the STAR (Runway 07 - ILS07 - ABEY4A - TMPY INSERT), it lagged for a minute and my whole ND was messed up. Checked the KCCU and saw that parts of the STAR and the Standard Go Around Procedure were inserted multiple times. Never had this before, might be VHHH ABEY4A Specific.
  2. Apparently it is right. Most real life pilots apparently do not use rings around their points but just use the fix page to enter the coordinates/Waypoints to be displayed which is obviously sufficient
  3. I had a WASM crash when I entered the arrival into the KCCU (clicking INSERT TMPY) Happened when: VABB, Arrival, entering RWY 27, Entering ILS Z 27, Entering Insert, Clicking INSERT TMPY -> Crash Information: A350-900 MSFS 2020 SIM Default Navdata WASM Error: WASM: Exception c0000005 in gauge MFD in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-900/panel/inibuilds-A350.wasm Specs: RTX 4080, I9 12900k, 64 GB Ram
  4. it's due to FSrealistic or head tracker for example. The Cursor needs to be completely still. Turn off anything that makes it vibrate a little then it works first time.
  5. Hello, following problem: especially the KCCU is hard to click, when you either have a system such as head tracking active or third party systems such as FSRealistic with breathing simulation or vibrations. I believe the cursor only works when completely still, because with these vibrations and little movements it's not still. Maybe you could change that behaviour to work even when (slightly) moving! Thanks 🙂
×
×
  • Create New...