void68

So what AG ordnance do you use with Mavericks broken, CBU105 broken, JSOWs broken? Not so much left despite dumb WWII era bombs...

I got the Winwing FS F-16. You are right, force sensing changes everything. However in my case it took just a mere week from China to central Europe and an additional 100€ for VAT and tax.

pre beta the Mave boresighting doesn't work. Pre latest update it worked. They already fixed it with the new beta. Wait for it when it goes final.

To the blood pressure cuffs inflate behind your neck? I don't get it, but as a testing device it sounds ok. You can start a simple Arduino program to get triggered when the chair moves back and closes a circuit and make the Arduion trigger another relay bank (switching up to 380V opto coupling) to start a compressor or something. Even with a analog read you can check how much the chair moved back and put it into an analog output.

Exactly, LeCuvier's .lua edit is the simple solution. In a simpit, you don't need hardly any key at all anymore, and there's no simple "oh, I hit the ejection button by accident". The problem with 3rd party util programs like RS Mapper is they work fine... for a certain period. They aren't maintenanced, they may be buggy and especially RSMapper collapses if one USB device gets unplugged. I tried to get rid of all these aux program and with some .lua editing (check out LeCuvier's guide!) my...5 Bodnarboards and several Arduinos don't need any intermediate program anymore, not even for 3 state switches. Just remember to edit the ...\DCS World\Mods\aircraft\yourAircraft\Input\yourAircraft\joystick\default.lua to route the 1x Eject directly to the joystick or boards, not the keyboard.

yes, but you can edit it, check here

Any solution for the VR players? While dragging / resizing the kneeboard with the mouse is a nice workaround still it got its hard boundaries and no way to move it to the knee. Perhaps with .lua editing, but what .lua and what parameters? Anybody did this already?

Hello Lord Vader, sure, still with 14kts it's 300'+ deviation and that's just 4Bft mid breeze. I guess with 1Bft and BA2500 calculated wind correction will be still way off target (time for another test) With insane 60kts I would understand that it's out of the limitation if the BLUs drift in a somewhat chaotic manner. But... they hit the ground always at the same spot, so there is calculation. And that calculation is wrong. Like playing darts, you aim for the bullseye and all your darts hit exactly the same 1cm² 5cm off to the right. All the time. So the shooter is excellent at aiming, he just has to correct his aiming offset. It was the same with CBU-97, always off the same distance / direction.

Thank you, I'll try once it's out of beta state.

Missed this thread, so I did a lot of CBU-105 testing in vain. However I use just preplanned, no TGP correction needed, just from the Mission Editor into flight. I just put the WP plain into the target group's center. Zero winds, full hit. 60kts wind, some logic lets the CBU fly a certain lead into the wind, it ejects the BLUs not over the target like before but windward like it should. The poles drift and explode like they should but not where they should. The higher the wind and the BA the stronger the drift. With BA1200 and ca 15° windspeed I had to move the WP around 300ft windward. So from my observation: There is indeed some calculation in the WCMDs but it's wrong - like it was in the CBU-95 before. Perhaps same cause? iooinoin.trk

Boresighting does *not* work pre actual beta and with latest stable. When you hit active pause and try it 5 times or so, sometimes it works. Has nothing to do with parallax problems if the seeker head is off several 10° degrees and the seeker head icon on the hud is everywhere else but there where it should be. I wonder why there hasn't been a hotfix yet. So there is no use going through the startup process, takeoff and try to boresight and there you are, with 6 crosseyed Mavericks. Ok, VIS and BORE aiming modes still work as long as you haven't tried to BORESIGHT them before. PRE is messed up.

I got .284 and it didn't work with native support. I wonder why PiTools didn't tell there was a new version.

Yes, of course. However in my setting the pilot has no LOS on target, so no HUD, no TGP at that altitude. Ground units tell him "bombs fall 300' short of target to the south". My idea: move SOI 300' to the north.

Simple setting: You got a target coordinate as a waypoint. You go in lowest level, no chance for TGP to scan the area. You use a weapon in PRE mode. While you are close to the target you eyeball the target area and notice the target(s) are actually off around 1500' to the southsouthwest. With a scan zone of 500*1500ft² of the CBU105 no BLU/skeet will reach the target. What do yo do now? Do trigonometrics and add the coordinates to a new STPT? I don't know, but low level and doing calculations on a calculator may be a bad decision. Or just edit your already active WP to "offset 200° 1500'"? While I find VRP and VIP less useful a target offset input would be ideal.

New day, new chances. So, today I took your openvr_api.dll attachment file from the post (and not the one - to me identical(!) - version on my drive and amazingly it runs, too (the original .dll worked amazingly well)! I remember OpenComposite Switcher updated 2 weeks ago and the mess started and then I updated all other tools. As I neither get version info on the switcher nor the openvr_api.dll so I considered them being the same. How do you know that this is 0.6.3? I checked version history in the file's properties, no info at all. I'm back in the skies, guys!

From what I understood - but I am lost already - that native OpenXR support comes with the actual beta version of DCS only? The Openvr_api.dll does not run... error. So I use the old version like you, the Composite Switcher and the DCS original openvr_api.dll. Strange

I noticed the same problems with my 2076 model. Ran fine 1 month ago or so. Totally wrecked after any of the updates, I think it began with the OpenComposite update and then I switched through PimaxXR and OpenXR Toolkit like you. A question, do you use the OpenComposit openvr_api.dll or the DCS native one? With the native one I got no microstutters but all Texture setting above low lead to an OpenComposite error. With the OpenComposite .dll I get these stutters. Then: opencomposite 0.6.3 solved the issues I fail to locate this file, do you have a link? Do you mean the Open Composite Runtime Switcher? I just found one file without any versions. edit: error with the OC .dll (1,7MB), back to DCS .dll (580KB) and it runs. Didn't change the updated OC Runtime switcher. System runs again, thank you! Tried to get it back running for almost a week!

yes, amazingly the ingame OpenXR FPS counter tells me 40-50fps (before I accepted 30fps) but tearing effects and microstuttering leading to trail the image a fracture of a second behind my head movement leading to a seasick "experience". Also on Pimax8KX, but when I switch back to (<profanity>ty) SteamVR with less resolution it still runs good.

My Pimax8KX now gets tearing effects and microstuttering, but 15+fps than before patch. Unplayable!

Pimax8KX here, too. Where did you get that "DCS World (DCS.exe)" entry? I just have "OpenComposite_DCS(DCS.exe)". My HMD ran fine before these updates, now I face micro-stuttering.

Well, it ran almost perfect before either the latest DCS or OpenComposite patch 2 weeks ago.... over here Pimax8KX, newest Nvidia driver and Pitools update. DCS runs at around 45fps, PimaxXR runtime to "PimaxXR", OpenComposite... well, I just used it for switching Steam<->OpenXR, so I let it "stuck" to OpenXR and don't start it anymore, ok. Added "--force_enable_VR --force_OpenXR " to my exe. I get some tearing effects, the pic in flight is jumping a tiny bit, not in the lobby (the virtual hangar at start) and not in flight in map view, just in cockpit / outside view this sickening view latency at way above 30fps. I hadn't had this with even 20fps before. I changed MotionReprojection, SmartSmoothing, HiddenAreaMask... no change. Unplayable ATM. i12700, 64 GB, 3080 and M.2. I just checked, DCS update replaced the openvr_api.dll with the original one (god, I hate that!). So I put the OpenXR one back into the folder (1,77MB)but no change! Wrong or right, no damn change! So the big one for OpenComposite, the small one for "--force_enable_VR --force_OpenXR", right. I can do it either way, DCS runs and doesnt crash, it's just that bad flickering.

Do boresighting a target far away, the further, the better (Parallax errors!). Also, hitting Boresight Button a few times more than necessary (>1!) helped in my case a lot of times - no joke. Give it a try. Edit: no, doesn't work, sometimes it does, sometimes not. In active pause it worked after 3 times, all of a sudden.

Since when is it not possible to launch 4 HARMs from a single ship? I did so multiple times. HARMs might be inaccurate due to the targeted emitter shutting down or bad resolution bc of having a target modes not best suited for this situation. HARMs against SAMs with ABM is a bad idea as long as you don't overwhelm them with the shere amount (I don't remember exactly but they track like 30 targets or so and shoot 4x4 per site). HARMs or JSOWs are no choice against a (fully ammunitioned) SA10 site or SA15 (can attack 2 missiles at the same time with 2x4 racks). Low level attack or hiding behind terrain is the best thing to do. As long as there are no SHORAD. Hide behind trees, in a river bed, use every hill or building complex for terrain masking, set your dumb bombs for pop-up. Or locate one of the emitters with the TGP / HTS, MARK the point, have your Mavericks boresighted and set to PRE mode, go in lowest level, do a pop up 20s before reaching the target, lock the Maverick seeker, "Rifle!", hit the deck, throw chaff (and flares, you never now) and you should be safe from now on. The Maverick will reach its target before the SA10 gets a lock on it, even if it's not inside the min reaction range. HARMs are just for clearing a path through SAMs / AAA quickly. But everything with ABM isn't impressed at all and it just leads to waste of payload. SEAD (which means supression, not destruction) of course is possible... 4 times / aircraft exactly. Don't know if the AI crew in the Flap Lid / Command Unit counts your HARM attacks and just ignores you after having counterd four launches and look for other threats / targets, which means your SEAD mission ends exactly at that point as you got no A/G ordinance left. There are quite some vids on the tube how to kill SA-10. As I said, as long as there are no AAA and short range IR / MANPADS or even small arms fire if you are out of luck they are quite easy to take out. In a setting which reflects reality... single ship no way. With neither weapon. In neither situation.

dcs_updater 2.16.0.10.exe starts with little white window "checking for updates", then loads into DCS (I think) and blackscreens. DCS.exe 2.7.18.30765 works without problems, game runs smooth.

So any idea on how to set curves in SimAppPro? VirtualDevice, adjust curves and then just "start mapping" leads to a 2s run and then stops. Mapping is saved, curve adjustment profile green. No change in the curves however. Never thought I would like to have T.A.R.G.E.T. back one day...