BluesRocket

When I switched from a VKB Gladiator to a WinWing ViperAceEX (first with standard Orion II base, then with the MFSSB base), I've lost the ability to perfectly trim the roll axis. Nothing I have done in SimAppPro or adding the roll trim control on the left hip panel to another axis can get a perfect trim. I don't know if this is accurate and you need constant stick input. Drives me nuts. I wish the roll trim axis could be tuned like the stick pitch and roll, I need really minute control, I think, to get an asym load trimmed enough to give me heads down time working a mission activity.

Reviving this: I received the MFSSB base for my F-16 stick and man this will take some tweaking and getting used to it. That said, are you guys using the F-16 stick and deadzone settings on the Special tab, and/or adding in values on regular control pitch and roll axis tuning?

For general mission and training ops, I find the F-15EX stick and Orion 2 base just fine. But for formation flying with a lot of pitch and roll change, and for A/A refueling, it's the biggest pain in the ass I've encountered. I have both a TM Warthog stick and VKB Space Combat edition that I think I'm going to switch to while I wait for the force sensing base to come. I find the fine control on this particular base with the default springs and cams nearly useless for AAR...that said, some have mastered it but for me (in the F-16 module, uh uh, I'm done.

This has happened twice this week: After a cold start I move the throttle forward (the two throttles are locked together) to taxi to a runway and the thrust axis goes dark on me either right at the first push on the throttle or on the runway. All buttons and hats continue to work but the thrust axis is dead. This is fixed by unplugging and plugging back in but happened about two days apart, with maybe five hours without incidents in between. Any idea what might be happening? SimAppPro current version updated last week, and both Windows 11 and the NVidia graphics card had updates. DCS up to date, repaired and cleaned up folders.

Ahhhhhh, now I see. THanks for taking the time to explain all that and providing the video! Props...

Nearly everyone I know in my two F-16 groups has this stick but without the shaker attachment, and do well with formations and AAR. My VKB stick was all over the place no matter what I tried to do with tuning and control with my hands. I'd had enough and went back to my TM F-16 stick since I could at least sit in formation acceptably (still no luck with AAR). THat didn't last long so it was a long shot so I placed my order and got the ViperAce EX stick and throttle (EX). I went with the shaker kit for the stick as I enjoy the experience I get with my haptic pad, and thought that would be cool to have haptic sensations all over. My understanding is that this stick, with or without the shaker kit with the two extra hats, is NOT a force feedback stick. It's just force sensing. So the force feedback checkbox remains unchecked. BUT, the newer F-16 settings under special should be checked to take advantage of actual stick. How well it mimics it is beyond me, but those deadzones are huge. How best to use them? Also, any recommendations on what file to download for the shaker option. Frankly, I've tried three and I can't actually feel much. Perhaps that's how it really works. Thanks in advance.

I JUST got this stick (the WW ViperAce EX) but haven't yet installed the little attachment with extra hats and rumble activation. But, if I understand you correctly, you have the same stick and kept the force sensing options on in the Special menu, but put the dead zones to zero? Then used the regular pitch/roll axis tuning popup to add the deadzones back in? Do you know why this behaves differently? I've been flying this jet for a while but want to ensure I have the micro control to attempt AAR without crazy pitch changes...

I JUST added curves for this. It didn't occur to me I might need a larger dead zone. Formation flying is pretty much routine now in most cases, but the fine movements throw me off. For example, it's clear micro movements on the stick require micro movements on the throttle. Need to slow a bit, the nose comes down, so just a TOUCH of pitch up. But not too much! The pitch oscillations are killing me, roll not so much. I'll try a larger pitch curve. Also, I swapped in the stiffer springs which is helping. I've come so close!

I have about 40 hours in the F-16 and joined a squadron for training and running missions together. It's been fun. The various systems are complex but even with the minimal time so far I'm learning fast. Like many, air to air refueling has been a problem. Look, I get it, it will come with time and practice--much more. I've read this over and over and really understand that. BUT, my stick, at center, is way too oversensitive. I'm going to open it up today and tighten up the axis screws just a bit, but I'm also wondering if there are custom axis tuning curves for pitch/roll that can help with movement near center. If I understand the tuning correctly, I can set up a gradient with less sensitivity with micro movements at center and then expand back to a linear setting to ensure the aircraft is still manueverable farther from center. I just don't understand the curves enough to start playing with that. I've seen several examples with both positive and negative values but need to understand what they mean in terms of stick control. Any examples with an explantion I could try? Thanks!

Ok, thanks for the feedback. 1. Deleting the launcher.sqlite3 file fixed the odd characters in module names. Thanks. 2. I've changed to the non-MT binary. Will be testing throughout the week. 3. I did a COMPLETE reinstall while saving a copy of my Saved Games folders. Added back in Voice Attack. No issues and everything was splendid. Then SRS. Works like a charm. SimAppPro for WinWing stuff and NF8 Haptic pad plus the SimShaker software. I'm gold. Then TacView. It all went to crap. Total freezes. Left it sitting 15 minutes. No help. Delete the program, it all goes away. Something is amiss as I would think my system could handle it. Perhaps I'm configuring it wrong. I'll look into that later but for now I just want my sim time back. I appreciate all the insights. I'm on the latest Win11 updates, nVIdia updates and the system passed all hardware checks. Life is always twitchy, never perfect. Good flight fellas... Deleting the sqllite db did it. Thanks. TacView crushed DCS and freezes everything without recovery.

After either the latest fix or hot fix this week, my DCS game is unusable. First thing I noticed, in the Launcher, is the appearance of Chinese characters in module names for aircraft and terrain. That's new. Tried a complete repair and cleanup. No help. Reinstalled the complete game twice. Didn't fix that. Minimal install the last time, no paid modules. Su-25 is missing, tried Instant Action with the TF-51. When the briefing screen comes up, I can see my head movements (TrackIR) behind the briefing screen. But when I choose the "Fly" button. Everything freezes. I am completely baffled. Latest updates for Windows and my nVidia 4080 Super card. Log attached. dcs.log

same problem and complete reinstall not fixing it. Frustrating.

Oops, my bad. I've been testing Voice Attack on the menus and forgot teh RAlt key while hitting the "\" key. Thanks!

Sorry, thought I did. Here's one with an instant action tanker flight. Never responds. Com1 freq is correct. FailedCommsTanker.trk

I cannot get the tankers to respond whatsoever after the last update.

Ok, I'm not the only one that finds this behavior in VR a challenge. Worse still, sometimes my mouse cursor disappears in VR and I can't get it back (usually in the heat of battle)...

Several members on my discord use it without issue. Not sure what's going on with my end. I'll try to figure it out tomorrow. It's too valuable a tool.

Well, I tried both development branches. Both work but once I send to the jet (F-16) the game completely freezes up. Tried uninstall/reinstalls a few times and have up. Nice concept though.

I skimmed through this pretty quickly. Seems awesome (F-16 here). But are there two development branches? It looks like the original stopped development July last year on GitHub (https://github.com/aronCiucu/DCSTheWay Then another here, apparently to fix an update with F-16 waypoint entry from DED (https://github.com/jonsky752/DCSTheWay) this past January. Is the latter the latest is there another development branch?

I use both now that I have hands passthrough in Virtual Desktop (see specs). It allows me to easily use a keyboard, grab the mouse or use the F-16 ICP panel (WinWIng). The hands passthrough is just slightly larger than your hand, so USUALLY it doesn't impair access to VR cockpit controls. I have more problems with finding the mouse cursor in VR than anything else...

Thanks for the feedback guys...

As I learn DCS and the F-16, using my VR headset has really helped with flying the jet since my 2D screen's TrackIR's head movements were never really smooth for me. Plus, Virtual Desktop's hand passthrough feature is really a game changer for using the keyboard and mouse. The resolution seems fine, mostly, both external to the jet and the cockpit controls. BUT, the text on the two MFDs is about unreadable. I found a user file for improving the MFD font somewhat, but it's still a struggle to read or discern objects on the screens. In the heat of A/A or A/G, the ability to read these items at a glance is crucial. It's not clear to me if the resolution on my headset is optimized. I recall a setting in the Meta Link software, before Meta kept breaking with each update, that allowed me to push the resolution. In VD, it's not clear what I can do. Any ideas? Having readability on the two MFDs would be a game changer for me. Third party software maybe? If its a limitation of the Quest 3, do any of the other headsets provide better resolution??? I don't have the money now but I might be able to save up for a better headset over the next couple of months. Thanks.

Is this still broken? My Quest 3 is consuming a full charge in an hour, despite being physically connected to a wall charger. I think the wall charger us underrated and ordered a 45W power delivery charger, but I'd like to go back to the Link software as it seemed less trouble prone compared to VD...well, until Meta breaks it with updates... EDIT 6/13: I updated my Quest to the latest, downloaded Link again, installed all fresh, and it worked. BUT, despite my settings the textures and detail were sub par compared to VD. Plus, I'm missing my hands passthrough for keyboard manipulation. Back to VD...

Now that VR is getting pretty useable for me through Virtual Desktop, I'm loving it. BUT, head movement is really limited to 90 degrees up or down, left or right via my neck. Even if I stretch out of the seat, seeing behind me is pretty rough. Is there an alternative to vrnecksafer? It appears to be abandoned.

Fixed it by lowering interpupillary distance setting.