Bertcoin

Been flying the A-10 since the A model. The ONLY experience I have with the OP's issue is the threshold float- which I believe is improper modeling of the WIND over the runway threshold since about 2.9.0 or so. It never was there before, then it was every time in the last 12 months, so not sure which update did it. It happens on the A-10, and the F-16, etc., so I don't think it's A-10 related. It ONLY happens to me when I land into the wind (headwind). If I land with a tailwind, it never happens. (Many 100's of landings). So for some reason, I get a 10 to 20 knot increase (wind shear) that can really float an empty A-10. It's a go-around in a light and empty F-16. A fully loaded A-10 is almost not affected, hence it correlates to the lift vs. weight and drag calculation kicking in. Regarding the overhead break scenario (or any other run-away trim issue). When the A-10 drops from 300 knots to 150 knots (or accelerates in the dive) you're going to need a large trim adjustment. I've never had it where the trim issue was not me holding the trim hat too long, or to short. I also believe that a non-axis input like a plastic hat can not necessarily be smoothly transmitting keys or handled smoothly by the computer. I don't usually just hold it aft like IRL which is an electric current running a smooth electric motor. A jittery joystick hat and an overloaded computer keyboard buffer can result in overshoot in the sim as it catches up on keyboard inputs. I have also had it where a key or control binding got interjected into my config like the first answer above. For example, I fly in VR, so a few times all of a sudden the hand controller sticks got activated on pitch and roll, or the setting changed for the controller laser pointer to grab the stick and it would overpower my TM stick. But absent any key bind or axis issue, just holding back pressure as I slow to AOA speed and pulling and pulsing the trim hat aft has always worked. Trim the pressure off in real time short pulses, thumb, hand coordination. It's muscle memory now. So IMHO, software wise, the into-the-wind-threshold-wind-shear is the only trim issue I've ever experienced and on multiple airframes over multiple computers.

Something did change in the last couple patches on AAR. Been flying and refueling since the A-10A, and it was always a lesser AOB and the roll out to race-track heading was reasonably gentle and did not oscillate. @Foka - I didn't see anything in 2024 patch notes about AAR, roll or bank angles.... Can you point to it for me? (Thx!) It appears that the they did increase the AOB to 25 degrees, then didn't adjust the roll out rate or roll out degrees before heading, causing roll oscillations after the roll out on non-circular orbits.... One of our squadron mates opened a support ticket.... Initial feedback was they are targeting 22 degrees and they know about the oscillations.

Fixed. Back to the old bug of the bombs can fall asleep (turn white on DSMS), and a violent airframe maneuver (like an aileron roll) will wake them up (turn green).

A-10C II - AGM-65D: No problems locking on using SPI or slew. In fact, it seemed to improve so I can do multiple shots on one pass. It had been worse for a couple years.

I'm using the standard hand controllers that come with the HP Reverb G2. I can hardly remember, but when I moved from Oculus 1 to Reverb G2, I set up something simple in OpenXR to get the left X and Y buttons and the right A button to be visible in the DCS config tools so I could do Center Cockpit View, Escape (menu), and VR Zoom respectively. Note that when in 2D I see a checkbox on the VR tab. When in VR, I see a drop down. (see image) When in VR only: Config menu. VR tab. Drop down on right is "Hand Controllers". Under that is unchecked everything except Hand Interaction Onl When Palm Grip is Obtained (Use on both hands). (see image). I am using OpenXR. My controllers worked fine today on multi-player Persian Gulf including the three buttons I have configured (the only ones I could get working before).

DLSS has given me about a 30% increase in frame rate and I think a sharper image (I have a slower CPU, but RTX3080TI), but the jitter issues and shadow issues are really significant. So I've disabled all shadows, and SSS. Air-to-Air refueling is really hard when the boom is shaking all over. Bunch of YouTube videos on this subject, so I'm hoping it's high the list. This was a huge update, so we'll have some cleanup!

I just loaded up first time in 2.9, and yes my hand controllers were "gone". But while in VR, I went to Config->VR, The "Use Hand Controllers" had been turned OFF. I think that used to be a check box, now is a drop down. I selected Hand Controllers (and not Tracker) and they seem to be working. (HP Reverb G2 w/ Controllers). Did not make any other setting changes in other tools - left them all the same. Edit: Not sure about the buttons yet. I had Esc and Zoom on and those don't appear to be working.

This issue is showing as REPORTED over in the A-10 section:

@NervousTestPilot_n2 After downgrading to 02/08/2022, where you still able to use some of the hand controller buttons? I have one set for Esc (to bring up the in flight menu) and one set for VR Zoom which matched my old Oculus. Secondly, are the pointers still accurate (straight off the fingers) or are they at a strange angle, usually downward as I remember in earlier attempts to use OpenXR? Thanks for this idea! The downgrade to the dll at 1,407kb worked for me. The buttons I like, X for VR re-center, Y for Esc and A for VR Zoom all work. The angle of the "laser" is correct to the visible glove, but the glove position is a little downward to my hand position, like a pistol grip. I can get used to that.

That was it! I was doing the VR tab, not the Special for the A-10C II. Thanks @lobo!

In my Oculus Rift I was able to use the left eye for the HMCS. When I "upgraded" to Reverb G2, even with the configuration on "Left eye" or "Both", I only get it in the right eye. Since my right eye is blurry, it has become almost useless to me. Is this a Reverb G2 issue, or has the game changed with an update in the last few months to be more like IRL?

I had to set "recenter VR headset" to the spacebar. Hopefully ED can get the button inputs into the sim so we can assign them again. Still showing up as Vive, which doesn't do anything.

Yes - I'd definitely like to see the buttons assignable as well and the G2 controller in the key mapper. I'll keep searching for answers for this as well. I definitely got used to VR Zoom, Esc menu and Recenter VR with Oculus, but just upgraded to the G2 setup for clarity. Now I had to remap the space bar to recenter and search in the dark for the Esc key. VR Zoom is on my Thrustmaster HOTAS stick, but doesn't help if I have my G2 controller in my hand.....

+1 I have to set TGP to standby, then AG to get back to bore sight mode.

Big fan of TTI servers. Thanks to all the authors! Needed some practice so I downloaded the Georgia mission and have been practicing. Only oddity I noticed is none of the A2G "kills" (that's all I do) seem to be logged at mission end or the game's pilot history. The detail is shown, but the killed target is just a number, not a unit. Is that just an unfortunate limitation of the way missions and units are dynamically generated?

Hello, Mine locked up as well. Same place - unable to exit mission editor. CTRL-ALT-DEL/Sign off required to close.... Sequence: End flight in VR (Oculus). Options - turn off VR/Save. Go to Mission Editor via mouse and regular monitor. Open existing mission. Make edits. Save. Exit fails. Thanks! (Hope helpful) === Log opened UTC 2018-02-21 00:42:49 2018-02-21 00:42:49.320 INFO VFS: Using 'Saved Games': "C:\Users\BarryLoveland\Saved Games" 2018-02-21 00:42:49.440 INFO DCS: DCS/2.5.0.14304 (x86_64; Windows NT 10.0.16299) 2018-02-21 00:42:49.440 INFO DCS: DCS revision: 134271 2018-02-21 00:42:49.440 INFO DCS: Renderer revision: 15803 2018-02-21 00:42:49.440 INFO DCS: Terrain revision: 15779 2018-02-21 00:42:49.440 INFO DCS: CPU cores: 4, threads: 8, System RAM: 16324 MB 2018-02-21 00:42:49.449 INFO EDCORE: (dDispatcher)enterToState_:0 2018-02-21 00:42:49.453 INFO Dispatcher: 2018/2/20 18:42 V1704040900 2018-02-21 00:42:49.465 INFO INPUT: Device [Keyboard] created deviceId = 1 2018-02-21 00:42:49.476 INFO INPUT: Device [sideWinder Force Feedback 2 Joystick {3F0C69E0-01C6-11e7-8004-444553540000}] created deviceId = 2 2018-02-21 00:42:49.500 INFO EDCORE: try to write dump information 2018-02-21 00:42:49.502 INFO EDCORE: # -------------- 20180221-004249 -------------- 2018-02-21 00:42:49.503 INFO EDCORE: C:\Windows\System32\pid.dll 2018-02-21 00:42:49.504 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 675E2456 00:00000000 2018-02-21 00:42:49.505 INFO EDCORE: 00000000 00000000 0000:00000000 2018-02-21 00:42:49.507 INFO EDCORE: 675E2456 00AFE020 0000:00000000 C:\Windows\System32\pid.dll DllCanUnloadNow()+C66 2018-02-21 00:42:49.508 INFO EDCORE: 675E3E1C 00AFE0B0 0000:00000000 C:\Windows\System32\pid.dll DllCanUnloadNow()+262C 2018-02-21 00:42:49.509 INFO EDCORE: 675E47F0 00AFE230 0000:00000000 C:\Windows\System32\pid.dll DllCanUnloadNow()+3000 2018-02-21 00:42:49.510 INFO EDCORE: 467D8F63 00AFE280 0000:00000000 C:\WINDOWS\SYSTEM32\DINPUT8.dll GetdfDIJoystick()+92B3 2018-02-21 00:42:49.510 INFO EDCORE: 467DD87F 00AFE2C0 0000:00000000 C:\WINDOWS\SYSTEM32\DINPUT8.dll DllGetClassObject()+3B8F 2018-02-21 00:42:49.511 INFO EDCORE: 467DD185 00AFE2F0 0000:00000000 C:\WINDOWS\SYSTEM32\DINPUT8.dll DllGetClassObject()+3495 2018-02-21 00:42:49.511 INFO EDCORE: 467D5830 00AFE340 0000:00000000 C:\WINDOWS\SYSTEM32\DINPUT8.dll GetdfDIJoystick()+5B80 2018-02-21 00:42:49.512 INFO EDCORE: 4D8A3435 00AFE4A0 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\Input.dll ??4Input@@QEAAAEAV0@AEBV0@@Z()+1B05 2018-02-21 00:42:49.512 INFO EDCORE: 4D8A326E 00AFE500 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\Input.dll ??4Input@@QEAAAEAV0@AEBV0@@Z()+193E 2018-02-21 00:42:49.512 INFO EDCORE: 4D8A5949 00AFE570 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\Input.dll ?isImmediate@ForceFeedback@@AEBA_NXZ()+11F9 2018-02-21 00:42:49.512 INFO EDCORE: 4D8B3721 00AFE8F0 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\Input.dll ?isHeadTrackerDeviceAttached@Input@@QEBA_NXZ()+4AA1 2018-02-21 00:42:49.512 INFO EDCORE: 4D8B22B8 00AFE930 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\Input.dll ?isHeadTrackerDeviceAttached@Input@@QEBA_NXZ()+3638 2018-02-21 00:42:49.513 INFO EDCORE: 467C2230 00AFEDF0 0000:00000000 C:\WINDOWS\SYSTEM32\DINPUT8.dll 2018-02-21 00:42:49.513 INFO EDCORE: 4D8B2681 00AFEEB0 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\Input.dll ?isHeadTrackerDeviceAttached@Input@@QEBA_NXZ()+3A01 2018-02-21 00:42:49.513 INFO EDCORE: 4D8B24EC 00AFEFC0 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\Input.dll ?isHeadTrackerDeviceAttached@Input@@QEBA_NXZ()+386C 2018-02-21 00:42:49.513 INFO EDCORE: 4D8AE548 00AFF010 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\Input.dll ?initialize@Input@@SAXPEAX@Z()+148 2018-02-21 00:42:49.514 INFO EDCORE: 2ABFB8CB 00AFF0F0 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe 2018-02-21 00:42:49.514 INFO EDCORE: 2A87CFBD 00AFF800 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe 2018-02-21 00:42:49.515 INFO EDCORE: 2AD90113 00AFF840 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe 2018-02-21 00:42:49.517 INFO EDCORE: 6F3C1FE4 00AFF870 0000:00000000 C:\WINDOWS\System32\KERNEL32.DLL BaseThreadInitThunk()+14 2018-02-21 00:42:49.517 INFO EDCORE: 718CEFC1 00AFF8C0 0000:00000000 C:\WINDOWS\SYSTEM32\ntdll.dll RtlUserThreadStart()+21 2018-02-21 00:42:49.624 INFO EDCORE: Minidump created.