peachmonkey

if you read the comments they all stopped working sometime in 2020, probably due to the core engine update in DCS. "With the latest DCS 2.5.5 openbeta release, ED dropped support for the older model format which is used by this mod, hence we getting invisible model in game.... I want the zero from this mod to play with the tomcat.."

yeah, the FFB is something I don't have.. btw, I noticed I16 is trimmed to a cruise speed of ~300kmh, it actually needs very little pitch correction if at all, but it does roll to the right a bit and there's no trim for that..

does it happen on ANY hotas button or specifically when using Bodnars buttons?

good call, I've noticed it too during some of my missions. The outer tanks were 80% full while the main tanks had 0% fuel in them. I thought it was my error in something, but I've flown this mission couple more times since then it's the same situation, i.e. the main tanks have 0 fuel in them...

I think if you look in Options->Miscellaneous there's an option to activate ForceFeedback... yeah, sorry I can't be of help anymore Now it's all down to finding the gremlins in your drivers..

yup, I was continuously pressing the button on the bodnar to retract/lower the gear whilst controlling the plane with the joystick. I've got a bunch of junk connected to my computer, i.e.: - vkb gun fighter pro - vkb gladiator - saitek x55 throttle - virpil vpc panel - 2 x bodnars (32 button ones) - PCPanel - Mini (usb), for app volume control.. no stutters.. I've got the MSI x570 Tomahawk wi-fi mobo + 5900x cpu.

hi, @DD_FT so I did some tests yesterday and I got zero delay/stutter with my bodnar's.. First of all I16 is a fun little plane, too bad there's no updated damage model but that's due to the closed SDK per my understanding. The landing gear mechanism is a total circus, just like the rest of the plane. I'm still trying to figure out the logic of the drum brake that has to be in "released/fwd" position to retract the gear but in "closed/aft" position to lower the gear... scratching my head on this one.. As far as my controller test: - assigned a rotary on the VPC panel for gear retract/lower - assigned 2 buttons on one of my bodnars, one for retract, another for lowering operated both the rotary and the buttons (continuing press/push to retract/release) <-- no delays/stutters.. Hotplug was disabled, didn't try it with 'enabled', saw no need for that. Did you get the latest chipset drivers in as well ?

thank you for the update, you comment about the buffer is an interesting one. I will definitely give it a try tonight (last night hadn't worked out that well) with different controllers... Do you have any keyboard-to-joystick virtual button mapping apps running ? (like joy2key)...

so .. 5900x + 3090+3600mhz16cal vs 5800x3D + 3090+3600mhz16cal who wins at VR in DCS?

a-ha.. that might be your smoking gun.. fingers crossed..

so I re-read your points and you mentioned "hot-plug". Do you actually have it enabled or disabled in Controls? On my machine it's disabled due to the reported stuttering way back in 2018/2019. Make sure you disable it next time you test. See this topic:

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.