Jump to content

ruudmeij

Members
 View Profile  See their activity

  • Content Count

    49

  • Donations

    $0.00 

  • Joined

  • Last visited

Posts posted by ruudmeij

  1. Posted

    15 hours ago, briansommers said:

    The altitude set is at 99000 and stays there. I can't change it.

    I can't click on CDI to change my indicator to GPS.

    this is the latest .6 from the store.

    Anyone else?

    I'm about ready to go back to steam gauges.

    Hi look here WT G1000 NXI does not work with LOGITECH PANEL - Page 3 - Microsoft Flight Simulator (2020) - The AVSIM Community

    This will solve your problem.

    • Like 1

  3. Posted · Edited by ruudmeij

    This is not related to the WU6, this was the same after the latest G1000 NXi update so there lay's the problem.

    If you switch to the old G1000 version this problem is gone.

    Here is another forum message tread regarding this problem including a comment from the Working Title guy.

    WT G1000 NXI does not work with LOGITECH PANEL - Page 3 - Microsoft Flight Simulator (2020) - The AVSIM Community

    Cheers,

    Ruud

    • Like 2

  5. Posted

    There is a bug in the new updated version and that is the cause they are looking into it.

    From there discord server:

     

    Matt (nishmaster) [Z-5] — vandaag om 14:24
    We are investigating some AP keybinds not working at the moment

    @Petrokova
    Hey WT team, thank you for the hard work on this project, the new additions are fantastic. I took the nxi for a quick hop, and ran into a couple things.   1) alt setting for ap dont report back to prehipherals, and adjusting alt causes weird jumps in displayed values, ie 14700>14800>1849900.   2) DIS and ETE did not update for the duration of the flight.   Thanks again and cant wait for the next update! https://puu.sh/I8yOc/aa0b503bab.png   https://puu.sh/I8yBH/e982222ebf.jpg

    Matt (nishmaster) [Z-5] — vandaag om 14:25
    As of 0.5.0, you must configure you peripherals to use altitude slot 1 and not 0 to read and write. We expect that workaround to no longer be necessary after Sim Update 6

    @DustNinja
    Would you rather want me to record a small video showcasing the issue i'm experiencing than me moaning about it btw? 

    Matt (nishmaster) [Z-5] — vandaag om 14:26
    We are aware of some reports on it and have it logged internally, but have not been able to consistently reproduce it yet

  7. Posted

    8 hours ago, Cmcollazo71 said:

    May that as it be - but why can the authors of mods update their mods within hours and yet Carenado not do the same?

     

    Because in this case Carenado isn't to blame but Asobo, with there latest released patch and they are working on a hotfix again.

    It's a real disapointment that every time that there is a new patch other things get broken over and over again.

     

    Cheers,

    Ruud

  10. Posted

    You have to restore the original P3D v4.5 ShaderHLSL files that was the solution for me.

    First thing I do when installing a new P3Dv... version is make a backup copy off the ShaderHLSL directory and put it aside.

     

    Cheers,

    Ruud

×
×
  • Create New...