markbam

Mine is probably the newer one from Andre, about 2 years old.

Vibration intensity is working fine for me with the latest update. No change at all.

I really enjoy checking in and seeing what everyone else comes up with! Here's my Version 2: Still not the prettiest, but much more compact and gave me a reason to play around with microcontrollers. The board is a Seeed Studio XIAO BLE Sense nRF52840 running CircuitPython 8 and emulating both a keyboard and a mouse. (The chip has an IMU but I haven't integrated it for anything quite yet.) The buttons are a 5-way hat switch: Up is Mouse Wheel Down: Down is Mouse Wheel Up: Left is Left Mouse Click: Right is Right Mouse Click: Press is ESC key. I loved the feel of the haptics on my V1 (Switch Joycon) so I added a small motor that vibrates when I use the buttons. It charges a 50mAh battery via onboard USB-C that I connect with a magnetic cable to reduce wear. It lasts a full day of flying even with the haptics. The ring was 3D printed out of TPU from a Ring Sizer on Thingiverse, It ended up being the perfect mounting system for my needs, so I didn't design anything further.

I'm on Windows 11 with KB5018427 installed. No issues with Sim Shaker for Aviators.

I got general effects working by adding the following to line 429 in this* location (You probably need to have the M-2000C for this to work). elseif obj.Name == "Mirage-F1CE" then dataTable.name = "M-2000C" *"C:\Program Files (x86)\SimShaker\SimShaker for Aviators Beta\Data\SimShaker.lua" This is only a workaround so that the Mirage doesn't feel so dead right now. It does not replicate the usual spot on work that f4l0 produces. --- Editing with more information as I find it: Engine rumble is missing but I found that argument 1027 returns the engine RPM. I've normalized this return to 0-100 which is what SSA appears to be looking for. However, engine rumble is still not present even though the DCS debug from SSA shows RPM@29 while idle and RPM@84 in burner. My code for this so far is as follows: local Engine_RPM = string.format("%.0f", MainPanel:get_argument_value(1027)*100) dataTable.rpm = Engine_RPM --- I've attempted to inject Mirage-F1CE into the C# model table to work around the need for the M-2000C, but have been unsuccessful. I've added "MirageF1CE=46" to the Model declarations and "this.modelTable.Add(Model.MirageF1CE, new ModelTableEntry(Model.MirageF1CE, "Mirage-F1CE", AircraftType.Jet));" to the SetupModelTable of the SettingsDatabase. Core.MasterManager and Core.DCS.Jets houses the specific aircraft properties and the references I was looking for, but it's quite involved. This is much more in-depth than I was expecting. The amount of work that happens behind the scenes for these effects is amazing.

Allow me to present my current setup for the "most ugly solution" award. It's bulky, but man, does it work well. Leap Gemini tracking has handled this like a champ and I have zero tracking issues (outside the ordinary). I even have haptics buzz on button presses and joystick movements.

Feedback for 2.3.4.0: Dampening at 100 is now working as intended. Engine rumbles on the ground, but not in the air. (I kind of missed it though, so I left it at 85) Change-log error related to Start With Windows has been resolved.

I am experiencing the same on MFG Crosswinds.

Feedback for Beta 2.3.3.0: "Start with Windows" appears to be working for me. However, (and this is minor) when trying to view the change log, I receive an Unhandled Exception error. (Could not find the path "C:\Windows\system32\data\CHANGELOG.md") This error does not appear when I launch SSA manually. The "Reduce Engine Effect While Airborne" - 100% dampening still doesn't have any effect for me. The engine rumble is the same on the ground, as in the air.

The kneeboard subpages are still unable to be bound to anything other than the keyboard.

Often my internet will act up and this will result in a "Failed to get authorization data". DCS will then deauthorize and unload all of my modules as expected. However, upon a DCS restart with successful module authorization, all of the special settings related to those modules are returned to their defaults. (Ex: Static Cockpit/MFD Reflections are turned back on)

I went in to map this as well as the new Kneeboard Subpages. None are mapable for me either.

Same, Reverb G2 and Quest 2.

Just adding my vote for a slew bind. I really appreciate the work done on the QEYES and QHEAD and I do find that they have their place and use cases. However, I often find myself needing just a bit more precise control than the head movement in VR provides.

+1

This change is extremely disappointing.

I also have noticed this issue with the Reverb G2 controllers as well as the Quest 2 controllers when running through the SteamVR API.

Just switched from a Quest 2 to a Reverb G2 and running into these issues as well. Would love to be able to map the buttons!

https://developer.oculus.com/blog/oculus-all-in-on-openxr-deprecates-proprietary-apis/

I'm a Quest 2 user and have been running into DCS performance issues that I believe are related to the low VRAM of my 3080. Using a plugin for MSI Afterburner, I have been monitoring VRAM *usage* (*NOT allocation*) specifically for DCS. I have come across a strange occurrence that is always repeatable and gives credence to the accounts I've read of people switching windows and performance improving. Whenever the DCS window goes out of focus, a good chunk of VRAM is freed. However, this only happens once per aircraft spawn. Something about the initial aircraft load adds a bunch of data to the VRAM that does not usually get cleared. But, for some reason, clicking a different non-DCS window causes DCS to run a garbage collection(or something), thereby freeing up precious VRAM. Please reference the included graph: You will see that I load DCS; load into a multiplayer server (in this case Syria@War); then load into an F14. (VRAM usage goes up as expected) I let DCS sit for a bit, then click away from DCS to the Task Manager in order to shift it out of focus. (You will see zero VRAM usage because afterburner is now polling the usage of the new active window: Task Manager) When I click back to DCS, a portion of VRAM is cleared. I click away again a few times, and the VRAM usage now stays the same. I now respawn into another aircraft. (You are able to follow the increasing VRAM usage each time I do this) I repeat the same process again on multiple aircraft with the same results. Not sure what this means in the grand scheme; perhaps this is a bug and DCS has room for a VRAM optimization step. At the very least, maybe this information could help someone in my position who is trying to diagnose performance issues related to their VRAM usage. (Side note: I have to run Textures- Medium and Terrain Textures- Low in order to not saturate my 3080's 10Gb VRAM on Syria.) Update: I have received the same results utilizing 2D mode, OculusAPI VR, and SteamVR. This happens in both single player and multiplayer. I have also noticed that subsequent switches to different aircraft(without changing window focus) will increasingly grow the VRAM usage. However, the game will quickly stutter and garbage collection does appear to happen when the VRAM completely fills up in this way. My Specs: i9-11900K @ 5.4ghz on water 64GB RAM @ 3600mhz GeForce RTX 3080 FE 2TB NVMe Quest 2: Wired Link 5408x2736@90hz

The downscale is definitely happening and the FPS gain is real. My log is showing "Created Upscaled Texture/Sharpening of size...." But I'm not sure I can actually tell a difference. The labels in the cockpit textures are quite blurry and I don't really feel a difference in the aliasing. I also got the same error as above but it only happened in a mission. The main menu was error free. It might be caused by a desync when DCS freezes during loading and the steamVR background pops up for a second. For reference: Quest 2 3080

I fully support this request. The immersion it adds would be immeasurable.

My wish list: HDG/CRS knobs, Increment/Decrement binds for dials (for use with encoders), and potentiometer support across the board (where applicable).

On Beta v27 and I am still experiencing this issue. What OTT tweaking worked for you?

I am also experiencing this issue as described in the first post. i9-9980, 32GB, 3080, Quest 2 with official Link cable.