nairb121

Aircraft with hydraulically boosted flight controls are generally equipped with artificial feel, to give the pilot some feedback on their control inputs. I'm trying to get realistic behavior from my force feedback stick, but I'm having a hard time finding any specific info. I'm mostly wondering whether the feel system accounts for airspeed (increasing stick forces as the aircraft accelerates), or if it's just a static spring system. Does this vary between aircraft? Or between hydraulic and FBW? If there are any solid sources anyone can recommend for more info on this, I'd really appreciate it.

I think this would be an awesome module. First real multi-crew WW2 module (Mossie navigator isn't really very necessary), radar unlike anything else we have, remote turret... lots of unique features. Plus it served in both the European and Pacific theaters, and within our late-war DCS timeframe.

OK, mystery solved... After experimenting with removing (via renaming) various directories, I eventually found that my issue resolves when I rename config/input/F-5E-3. I eventually narrowed it down further to a specific input device. Renaming that one .diff.lua file fixed it. So what about that file caused the problem? I went into my input settings after naming it back to see what was bound to it. Just a couple latching ON/ON switches, one for nose strut, and one for NWS. I look down... and sure enough, the NWS switch is on. Flip it back off, and ground crew can hear me again! This must be related to the usage of the NWS button as radio while airborne (coincidentally(?) it's currently bugged per another report). It appears that you can't talk to the ground crew while the NWS is engaged (at least with the engine off). So while I've found the source of my particular issue, this does seem to be a (very) minor bug.

I tried a few more things, but no luck so far. @BIGNEWY I ran your track. When I watch it, the comms come up fine, like they should. If I take over at any point though (even after the successful connection of the air supply) they no longer work. I ran through the rest of my modules (I can list if you need me to), this is the only one having this problem. I've also tried on other terrains, same thing. All signs point to it being corruption in the module - but I would think completely deleting and redownloading it should've worked. Are there any other files that might affect this?

I tried the slow repair before I posted, in addition to deleting and reinstalling the module. DCS is standalone open beta. I'll try the track tonight.

Yeah, this is the built-in instant action Caucasus cold start mission (went with that to rule out user error), but it's the same in any mission I've tried. The mission (and presumably any others) work fine on my laptop, I can only imagine something got corrupted in the files somewhere on my desktop (where this was recorded), wherever the comms functions are defined. Just don't know where to look, since I already deleted and repaired dcs.openbeta/mods/aircraft/F-5E. I think it has to be the module though, not something else, because I tried it with the Hornet and it worked fine. I don't think it's a mission issue either, since it happens on any I've tried, including a new one in the editor. Even if it was a coalition issue, I still think I'd get the "Connect ground air supply" voiceover, just not the "Copy". If you have any troubleshooting suggestions though, please let me know.

Yesterday I had a game crash while flying the F-5E online, and when I restarted, the comms menu wasn't working anymore. When I select something from the menu (e.g. "Connect ground air supply") my pilot doesn't say anything, there's no response, and the thing I asked for doesn't happen. Doesn't work either for ground crew (canopy open) or for ATC (Radio on and properly tuned). I've tried other modules and they still work normally. I've tried restarting the game, restarting the PC, running the repair (both fast and slow), and deleting the module files, then repairing. Does anyone have any other suggestions for fixing this? Track attached. F-5 comms issues.trk

Thanks for the suggestion. I messed around with that a bit last night before I posted, but I couldn't get it to affect the controllers. I figured, based on the name, that it was more for setting up emulation of controllers with hand tracking. I'll try some more tonight, maybe there was something I missed.

I've successfully installed OpenXR for DCS, and I'm liking the performance improvements, but I'm having an issue with my VR controllers now - the angle is no longer correct, they are rotated downward. (Reverb G2). How can I adjust the orientation of the VR controllers?

Is anyone else having trouble with the CBU-1 and CBU-2 dispensers with V2.01? CBU-2/A and CBU-2B/A on single racks are almost 13,000 lb (looks like it's already reported on the GitHub issues page). I'm also having another issue where the bomblets (seems to be in all variants), instead of dropping out of the dispensers neatly, burst out in all directions (frequently hitting and destroying the plane). I don't see this one reported so I wanted to check if I'm alone.