Guard72nd

Hello guys. Reverb G2 user here. I might have successfully registry-blocked the dreaded update, but I know I am living on borrowed time. My question is, what is the best eye tracking/head tracking option nowadays? Used to use TrackIR for many years, but I understand there are new (and maybe better?) options out there. I am looking for this both as a backup for when/if my G2 bricks and I need to get a new headset and also as an option alongside VR to use for shorter flight/procedure training when you dont need to/want to don the headset.

Cougars working on my end. Thankfully no auto-binding in the module, as that would give adverse effects depending on what device is registered as MFD 1, 2 and 3 on your system, set them up manually and they work.

For EA I find it one of the best releases I have experienced in DCS. She flies beautifully, low speed handling feels great. Systems are usable, no gamebreaking stuff left out, all in all I am looking forward to spending a lot of time with this module, and watching it grow!

The A-10 throttle as far as I know was appropriated from the F-15, so most of the throttle HOTAS functions can be bound as pr the real bird. We are lacking the radar antenna elevation on the Warthog, but the "throttle friction" slider works for that. Also there is no pinky CM dispense switch, but that can be mapped to the upper four way hat on the throttle, as only forward and aft are used for radios for now. I chose to switch the auto-acq from the CMS to the TMS (and vice versa) on the warthog, to get the castle switch depress function. I also use the NWS/Missile step as a modifier to allow for other functions that are handy on the HOTAS, but are not realistic. This setup actually leaves me with the DMS unbound this far in my exploration of the mudhen, and maybe the dispense stuff will get moved over there to prevent me from dispensing chaff/flares when I want to talk on the radios and the adrenaline levels are up

Thanks mate. You answered my question perfectly.. Cheers

Hello fellas. Stupid question, I was wondering whether you bind the toe brake axis(es) as a regular or slider axis? I havent found anything specific on this when searching around, but it "feels" like I have a bit more minute control over the toe brakes in fidgety birds like the F-16 for that initial differential braking control after the aerobrake when bound as slider . Im just curious what other people are running.

Yes, "View Center", sorry. I have never had those bindings in use before this patch, only the recenter in UI layer. Once I removed all these new binds in "general", it works just as it did before the patch, and I am able to use the numpad for other binds (read ICP) as I did before.

I found the solution. After the last update, under the "General" tab (not UI layer or plane specific) every controller now has button 5 (for DX controllers as well) assigned to the function "Reset view" If you go in there and un-assign it for every controller it will work. This explains why some of my other HOTAS setups for other planes were suddenly lacking buttons as well, it takes every DX5 button from every controller, and assigns it to this function post last patch.

I have checked in UI layer, thanks. Sorry for not clarifying, that is where I have had it bound for a long time. My "true" recenter VR button (DX on hotas) still registers there, and works as it used to, only that the numpad 5 key replicates it, without showing up as a keypress in either the UI layer or the F-16.

Hello peeps. I have my keyboard numpad set up as ICP controls. After the latest update, numpad 5 recenters the VR headset, even if not bound to that command in the UI part of settings in DCS (I already have that bound somewhere else, no double binds) Anyone else experiencing this? To the mod that moved this, it got moved from F-16 bugs to F-18 controller bugs/questions. Could you please move it to F-16 controller bugs/questions?

Thanks mate. I was able to replicate something that seems more like a proper deep stall by employing MPO while in high alpha condition, and it gave me maybe two cycles of pitch oscillating stall, but still self-recovered at 160cas the moment the nose dropped the second cycle. Tried checking AOA and found that without MPO input she starts buffeting a bit at 26-27 AOA and then departs at around 28, but still self-recovers really easily.

Regards folks. I am having a hard time to get the F-16 to depart in to the typical nose-wagging deep stall that requires use of MPO to break the cycle. Tried different profiles of high altitude/low speed with different controls input, and I am getting buffeting and sort of a departure that usually involves a rollover on to inverted, nose lowers and then the airplane self-recovers when airspeed reaches about 150kt CAS. Have any of you guys been able to depart into a confirmed pitch-oscillating deep stall, and if so, can you please give me some advice on how to do it? Cheers.

I noticed the same thing in multiplayer yesterday. Clicking the command for polarity once just briefly changes polarity from WHOT to BHOT before it pops back. Now you have to "doubletap" the keybind to make it stick to the new polarity. This must have changed since the last patch, as I have not seen this exact behaviour before.

Hello, I just got myself some foot switches to enable the same com setup as in the bird, especially for front seat work. I cant however seem to find the keybinds for binding the in-cockpit foot transmit switches. in either cockpit. I have expended my search-fu. Any tips guys?

This problem seems intermittant. After countless reboots&restarts to try and remedy the problem it suddenly works again, no settings or keybinds changed. Same instant action missions I was using for testing this half an hour ago... Now I am not able to replicate it myself anymore either.

Just to add to the original post. I can see the actual button moving on the right handgrip, I can see the polarity change when on the IHADSS monocle, but it no longer seems to affect the TDU display itself. Same goes for the FLIR gain/int

Hello. I suddenly noticed today that the Rgh polarity switch no longer changes the polarity of the CPG FLIR TADS display. At the same time, the FLIR GAIN/INT switches have stopped affecting the actual screen. I can confirm that they are working when using the TADS trough IHADSS (both polarity and the Gain/int knobs, when I pull the symbology up on the monocle both as sight and as sensor. I have confirmed that the keybinds are still working in DCS, and I have tried repairing the installation etc, to no effect. I am also aware of the difference of FLIR and DTV, and I have had this work in FLIR before, it just suddenly stopped working for me. I also have no problems changing the polarity on either the PNVS or TADS when called up in the backseat. Anyone else had problems to this effect?

I know there are realism factors playing in here, doppler/ground clutter/look down etc, but I am noticing a new tendency after recent patches where the AN/APG-68 isnt able to keep an ACM STT lock at all. Even on close, high radar profile targets that I have a solid track on and follow in BFM, whenever they pull up from a vertical dive, my track is instantly lost, seemingly at the same point every time, regardless of target size, terrain and range. The F-18 radar is supposed to have similar capacity to the F-16 radar, but does not replicate this problem, and can keep a lock and provide a gun solution trough the vertical on a solid STT target everytime. Where as the F-16s radar seems to loose lock at the same point every fight now. Any of you guys experiencing the same stuff? Bug or feature of the nerfing of the -68?

Hello fellas. Just a quick question to hear if any of you guys know if this is implemented? In this vid you can see the pilot changing his squawk trough the ICP IFF page, instead of having to use the switches on the left panel. I have not been able to confirm if this is implemented/working in DCS. I can apparently enter a squawk trough the ICP, but have not had a chance to test this in MP, and to see if it works as intended. Any of you guys know? Vid: (timestamp for transponder entry around 0.47)

Hello peeps. I am having a hard time here figuring out whether my memory serves me incorrectly or if I have misunderstood something. When locking a target in dogfight override in any of the ACM sub-modes, whenever I reposition the dogfight switch to the middle (off/nav) position, or transition over to MRM mode the lock does not carry over into CRM(RWS/TWS) mode. This applies even if the air to air radar is active in nav mode. The reason im asking is that I remember using this method to snap lock someone within visual range, then switching over and being able to carry on prosecuting that contact as a CRM-STT contact or using TMS aft to enter RWS-SAM. I am not sure if this is behaviour I have seen before in DCS or if it is old F4 knowledge messing with me. Any help would be appreciated

Yeah, revenge from beyond the grave. (Cue horror flick violins) :D

And that one solved the problem. I deleted it, and this one did actually generate and let me start the sim. Wohoo, and thanks. Now back to learning how to fly the damn thing :)

Found something now, called players.lua. That one seems to be empty, and I'm willing to bet that is my problem. Gonna try to get a new one of those, and see. Thanks for the help.

It looks like the me_loogbook.lua mostly has to do with the structure and function of the logbook part of the sim? There's lots of code in there, but I can't find any spesific reference to any player names. Yeah, I guess there could be a "player" file or something, but I can't find anything by that name in the folder. Perhaps it's a missing file, and I would not know which one it is, since it's missing.

Thanks for the speedy reply bud. I tried getting a me_logbook.lua file from a mate, but I got the same error message with that one. I'm gonna try and move my file out of there and see if it generates a new one. EDIT: Tried removing it, but that only generates a new error message about it not being there, hehe. Cheers. Guard.