Posts by rairic

    I'm trying to build a VR home cockpit and I need to map some stuff to keyboard buttons instead of using the mouse, namely the range and mode switches for the Nav Display on the a320.

    Is there a way to add these functions to the gc-map config file?


    Thank you for your help

    Hey guys

    So first of all let me tell you that AFS2 in VR is just the bomb, so much better than MFS2020.


    I just built a new sim rig for IFR and I mapped the MCP controls for selected heading, VS , course 1 and 2, NAV 1 and 2 to keyboard keys and it works great (if I hold the button down the value increases constantly) but for Selected Airspeed and Selected Altitude I have to keep mashing the button (the autorepeat isn't registered). Is there something I can do to fix this?


    Thanks a lot!

    Sorry about the title changes, I thought it would help as we're looking at a layered issue trying to get to the root of it.


    I looked at the thread Thruster posted (Thanks buddy :thumbup:) and I can confirm that rolling back the drivers to the GeForce 442.74 release fixes the Vulkan issue on my system; so it does look to be related to the latest 445.87 drivers.

    Hey thank you for looking into this :)


    specs are the following:


    i7 3770K CPU

    GTX 970 GPU

    8 GB DDR3 RAM

    Win 10

    Oculus Rift DK2


    (Vulkan VR worked great on this setup in January - last time I checked before the issue appeared)


    TM log :


    tm.log

    Can confirm, no error message but Vulkan is still broken in VR. On the other hand OpenGL seems to be working much better than before, I wasn't able to hold good performance @ 1.5 ss / Ultra without Vulkan before but now I can.

    I FIXED IT !!!!


    I deleted main.mcf in the documents/ Aerofly Fs2 folder and let the game rebuild a new one.


    Still gives me the error but if I press "ok" everything works just fine.


    What a relief :whistling:


    Thanks for the help!


    Might be useful to keep the thread up if anybody else has this issue, your call.

    Yes I did, got quite the neck pain after :D. HMD is dead as disco, pitch black and no output.


    I just tried to downgrade the game to the jan 30 executable (100% worked fine) via the Steam console with the:

    download_depot 434030 434032 5110625937057247326 command...


    the result is:

    Depot download failed : Manifest not available


    I can only download the latest manifest (may 6) with this procedure.


    Can someone in the dev team share the Jan 30 exe?


    thanks

    So I logged into Steam today and i can't start AFS2 on my Oculus Rift DK2 anymore. I know it's old but It works fine with every other VR application (War Thunder, IL2...) and up until 3 months ago (last time I checked) it worked great with AFS2 (over 300 hrs on it).

    if I Try to start it in Oculus VR I get the "AFS2 does not support your currently active headset" message, if I click "OK" the game starts in VR mode with Oculus Home but the Headset screen is dead. I can start it in Steam VR mode but the performance/ tracking is awful and it makes it unplayable.


    Can somebody please help ? I'm heartbroken, first my airline career is destroyed by COVID19 and now I can't even fly my favorite flight sim :(


    Maybe it's an update issue, is there a way to downgrade the game to a compatible version?



    Thanks for taking the time <3


    EDIT (May 7th):


    I Fixed the issue by deleting the main.mcf config file in the Documents/ Aerofly FS2 folder.

    I still get the error message but if I press "OK" it works perfectly fine! No need to downgrade. ^^


    EDIT (May 16th):


    Vulkan is causing the blackout issue on Oculus headsets.

    The error message was fixed via steam update.

    The sim works just fine in OpenGL mode, waiting for a Vulkan fix.


    EDIT (May 17th):


    The Vulkan issue seems to be related to the 445.87 GeForce drivers.

    Rolling back to 442.74 fixes the issue at the moment but it's not a definitive solution.

    Hey, I'm trying to find a way to map the MCP bugs to my keyboard and Yoke but there's no way to hold the buttons down to make the process less tedious. As of right now I need to hit the increase/ decrease heading bug button 179 times to turn around and that's just not cool at all. Any ideas?


    Thanks

    Hey guys, I just got a pro flight yoke and I'm trying to set up an amazing VR home simulator so that I can start my MCC/JOC with confidence!

    I'm flying the 737 at the moment and I'm trying to do some IFR LVO flying. I gotta say the experience is amazing, pretty close to the 600k euros FNPT II I used a couple of weeks ago in training so hats off to the devs for the amazing job.

    I got most of the stuff mapped to the yoke but the frequency/ course switching is a little bit of a pain so I came up with an idea: using my Impulse 25 MIDI keyboard (it has a bunch of knobs on it) to map all the bugs to. Problem is that I cannot figure out how to do it properly. I managed to get it to work in the sim but I can't configure the knobs to work with the autopilot. Maybe there's some tweaking to do in the config to make it behave like a wheel and not an axis?


    Thanks a lot for your time and enjoy the flight!

    I've been flying with LiveATC audio in the background via VLC lately and I gotta say it greatly improves immersion. It would be great if it could get implemented in the game, kinda like the online radio in Euro Truck 2, maybe with auto frequency switch en route :love:. What do you guys think?

    I noticed the rpm settings for the King Air are off. Full forward prop settings only produce 1900 RPM (cruise). Sholud be 2200 RPM for takeoff and 2000 for climb, right ? :/

    I noticed a weird change in the throttle steps in the King Air after the last update. I looks like the throttle doesn't do anything in the first 50% travel of the axis. Looking at the throttle quadrant in the cockpit I noticed that what used to be 50% power is now Idle. This is kind of weird as now the rpm range compared to the axis motion is very crammed and it's really hard to get the right amount of thrust for any given flight stage that isn't touch down or takeoff. It would be nice to have "thrust reverse" and "ground fine" in this 50% range but now it's just a dead zone. Is there a way to offset the axis so that a 0% axis value equals a 50% (idle) throttle setting in game ?


    Thanks