peachmonkey

yup, will do tonight, although I do like learning the modules the proper way from the cold start Upgraded BIOS is great, but also look in to getting the latest chipset drivers, lots of I/O goes through them.

I use the 2 x 32 button Bodnars (plus a bunch of other HOTAS/buttons/extensions, it's a circus) to fly the A8, no issues there. I do have I16, however never even tried flying it, lol. I guess I can give it a try and see if I run in to a similar issue. Just out of curiosity: did you update the motherboard Chipset drivers recently? If not, give that a try, you never know if there are bugs in the USB controller chipset drivers.. If you can apply a latest BIOS as well that'd be great...

There's a default keyboard mapping to select the appropriate engines, which then uses the general throttle/rpm assignment, i.e. when you press 9 (both engines selected) the throttle/rpm moves for both engines (i.e you don't need to assign throttle/rpm controls PER engine) Select active engine to both = press 9 select active engine left = press 8 select active engine right = press 0

5900x / 3090 watercooled

yup, was running like that for the past 2 months. I tried the FSR at 80% yesterday + post processing + FixedFovRendering = can't tell if I see much of the improvement in the 'smoothness', however the map I was flying on had some serious stormy weather all the way to the deck (wwII N20 server). I'll try to dial-it in during the next couple of days, however I feel that my CPU is probably a bottleneck at this point..

thanks, man.. I've been flying the wwii birds at 35ppd without the toolkit and it's a more or less smooth experience: - flying on the deck: looking forward: very smooth looking to the sides: slight choppiness - flying at 300-500meters: looking forward: very smooth looking to the sides: very smooth i'll try your settings in my 5900x/3090wcooled/3800cl16 setup

can you give us some specs on your config? - VB ppd? 35? 37? - scaled down to what % in Toolkit?

I've raised all 5 hands. If that helps.

thank you, @Supmua, it looks like your .ini file is substantially different than the original .ini. I'll use your contents, will report if there are issues. original .ini: ;Mirror mode outputs a shared texture for use by OBS plugin mirrorMode=disabled ;Performance stats enables writing of performance stats ; If enabled press F11 to start stats capture to file ; File is currently output to \Program Files (x86)\Steam\steamapps\common\Assetto Corsa Competizione\AC2\Binaries\Win64\teststats.csv performanceStats=disabled ;Hidden area mesh fix for G2, may work on other headsets enableHiddenMeshFix=enabled ;Use OpenXR layers to handle GUI overlays and HUDs, if set to false will render internally directly onto swap chain before submitting enableLayers=true @Supmua .ini ;Mirror mode outputs a shared texture for use by OBS plugin ;mirrorMode=disabled ;Performance stats enables writing of performance stats ; If enabled press F11 to start stats capture to file ; File is currently output to \Program Files (x86)\Steam\steamapps\common\Assetto Corsa Competizione\AC2\Binaries\Win64\teststats.csv ;performanceStats=disabled ;Hidden area mesh fix now is autogenerated you no longer need to put in manual values see changeling V0.6.1 ;enableHiddenMeshFix=enabled ;Use OpenXR layers to handle GUI overlays and HUDs, if set to false will render internally directly onto swap chain before submitting enableLayers=true forceConnectedTouch=disabled renderCustomHands=disabled

I had G2, then VP2, now Varjo. Clarity bump with Varjo is dramatic, however you need the top of the top system to fully appreciate it, i.e. 3090, fast ram, latest cpu, etc. Meaning if you're running 1080p on Varjo it will look like 1080p, hence you need all of the resolution you can get to reach the experience.

the original file package (from the first post in this thread) just needs the dll's. I've also tried using the openvr_api.dll from a new/updated build (https://gitlab.com/znixian/OpenOVR/-/tree/openxr) however DCS threw an error saying the .ini file was missing. I replaced it back with the old .dll file after that. Haven't messed with the .ini configs yet, maybe it just needs a blank file, maybe some config lines.. will take a look at it this week..

it's a confusing issue for sure. I'd try the following: 1) unplug all of your HOTAS (joystick/throttle/rudder/everything) 2) remove all control assignments for each HOTAS device, i.e. blank them all out 3) start I16 in the air and control it with your mouse a) if the issue disappears then there's some physical conflict in buttons/assignments. Try adding a single HOTAS at a time (for example: throttle only) without control assignments. If no issues - assign controls to it. Then keep adding other devices until you run into the issue again b) if the issue persists then go to Device Manager/Human Interface drivers and start disabling all of the USB devices one by one, i.e: - disable one then launch I16, if issue continues then re-enable it - disable the next device, launch i16, issue continues = re-enable it back - etc.. Question: when you said you removed I16 did you make sure all of its .lua files were gone? If not, maybe start with that first, i.e. remove i16, then clean all of its files from the DCS installation folder.

you creation is truly awesome. I need it!!

make sure to use v2 base stations with Aero. Even though Varjo claims Aero supports v1 the reality is extremely poor tracking/or not tracking at all. if you disable OpenVR in VarjoBase you'll get that SteamVR error, just fyi.

I'd scale the expectations down a bit. We still haven't gotten the delayed fusing for this bird so we could attempt to recreate the very missions this plane got its fame for. The lack of wwii release consistency or an indication of even a slightest hint to a 'roadmap' that ED operates by all of the "wants" raised by the community members turn wwii2 forum section in to a simple gossip soup. Do I want all of these ideas come to fruition? Absolutely. Will they actually happen? 100% nope.

anything is possible at this point it'd be nice if ED introduced a procedure check, i.e. report with "negative" when requesting the conflicting/overlapping tasks.

@grafspee @VIKBELL thank you, guys, I guess i'll just stick to what's working..

In a thread about K4's tendency to pitch up at all times/tail heavy behavior I saw yo-yo's response how he didn't see a problem in operation since they're using the FFB system (he didn't state the manufacturer) without the pesky springed return-to-center 'conventional' joysticks. Not sure if it translates to ED's using FFB for the actual AC testing though...

hi, all, is anyone having an issue with P47 when requesting the ground electric power it only gets turned on if there are no other requests being processed? Example of it not working: 1) press \ 2) request ground electric power to ON 3) get a 'copy' back 4) request refueling 5) get a 'copy' back 6) refuel completes, get "fueling completed" 7) electric power never gets turned ON Above is one of the examples. Another is rearming, or essentially with any command that gets a 'copy' after I request electric power the power never gets delivered. The only way to successfully request/receive electric power is when the procedure never overlaps with any other requests, i.e.: 1) request electric power 2) get a copy back 3) wait for it to get delivered and only after that start with other procedures, such refueling/rearming..etc... I understand that compared to the real life such servicing procedures are sequential, however if in-game we can request refueling/rearming in a single take why is electric power is so different?

please tell me ED will release it soon, as in like.. soon soon.. Since the teaser video that's literally the ONLY thing I've been waiting for pretty please!

I tried the destruction levels as triggers on the Channel Map and even though the visuals were really fascinating the performance hit to my VR was extreme, the fps dropped to 10fps or less, this was about 6-8 months ago, not sure if there were any improvements done to optimize the destroyed scenery.

it was a one click before

hi, Andre, I have a question about the Engine Beat in A8 using the Sound Module: - when on the ground, just started the engine there's some serious variations in sound intensity that seem to go in and out when the engine is on idle, and it's not repeating in any standard pattern, it may happen every 10 seconds, or every 30 seconds, or less frequent. It's very difficult to describe. I'm not sure if you'd have any insight into that.. can they tied be to some sort of engine resonance ? Is there any debug options to see what DCS is outputing to your app so I can capture the moment when it's happening? (not sure if it'd help with anything). I've been trying to figure this out for quite some time as it's been pretty annoying. I want to have the engine beat at a maximum so I know the bird is alive, but these huge fluctuations are rather aggressive...

navigating to the subforums is a pain in the ass. Why such a drastic change, was it hurting something/someone? Imagine a noob trying to find anything now..

can't find Virtual Reality forum anymore... wth did it go...