DragonSoulkin Posted October 23 Posted October 23 So I've got a friend who's using Tobii Eye Tracker and with this new update, he's got head tracking available for everything else in DCS, to include the Phantom, but not the F-14s. In his keybinds in other aircraft he has the columns for head tracking filled and functions just fine, but in any of the F14 models, his keybinds for axis commands under the head tracking column are grayed out. Any ideas as to what's going on here and why it's just the F14 that this is happening to and not other airframes?
MAXsenna Posted October 24 Posted October 24 First report I've seen of this, so I will assume it's a local issue. Have him try to right click the headtracking column and reset it to default.Cheers! Sent from my SM-A536B using Tapatalk
DragonSoulkin Posted October 24 Author Posted October 24 2 hours ago, MAXsenna said: First report I've seen of this, so I will assume it's a local issue. Have him try to right click the headtracking column and reset it to default. Cheers! Sent from my SM-A536B using Tapatalk Tried that, also had him re-install his tobii software. The problem is it's grayed out like you can't keybind anything in the axis commands for head tracking at all, so resetting to default won't do anything because there's nothing available to fill in, and the weirdest part is all of his other modules are not affected. His tracking works just fine in the F-4, F-16, F-5, just not the F-14s. The only thing I can think of at this point is to have him uninstall the F-14 and re-install it, and if that doesn't work have him do a cleanup and repair.
MAXsenna Posted October 24 Posted October 24 1 minute ago, DragonSoulkin said: The only thing I can think of at this point is to have him uninstall the F-14 and re-install it Won't do you any good. It's probably a corruption in the Saved Games folders. 1 minute ago, DragonSoulkin said: and if that doesn't work have him do a cleanup and repair. Always perform a repair first. It's exactly the same as a reinstallation, only quicker. Have him rename, (as a backup), the Saved Games folder first, as a repair/reinstallation won't touch that.
Starspeed Posted October 24 Posted October 24 I'm having the same issue using Trackhat. It's only in the front seat though, no issue in the backseat or other modules. I've tried running a full (slow) repair with no luck, also reinstalling the F-14 module and deleting all costum binds didn't solve the issue. I also know at least two others that had this problem, they were able to solve the problem with a full repair.
draconus Posted October 24 Posted October 24 Well, from the last update log "Inputs: Fixed some functions not being bindable to mouse" so there's high chance they got something the wrong way but first try to reset your controls by renaming the DCS profile in saved games as Max suggests and of course do a full DCS repair and clean. 1 Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 MiG-29A F-14A/B F-15E CA SC NTTR PG Syria
MAXsenna Posted October 24 Posted October 24 I'm having the same issue using Trackhat. It's only in the front seat though, no issue in the backseat or other modules. I've tried running a full (slow) repair with no luck, also reinstalling the F-14 module and deleting all costum binds didn't solve the issue. I also know at least two others that had this problem, they were able to solve the problem with a full repair.Like I wrote above, I repair is quicker than a reinstallation, and basically does the same thing as it resets everything to vanilla, except files in Saved Games. Exit DCS, perform a full repair. Rename Saved Games for backup purposes, and perform a full repair. OR you can rename all F-14 related folders in the input folder. I assume the error is there.Cheers! Sent from my SM-A536B using Tapatalk
Starspeed Posted October 24 Posted October 24 vor einer Stunde schrieb draconus: Well, from the last update log "Inputs: Fixed some functions not being bindable to mouse" so there's high chance they got something the wrong way but first try to reset your controls by renaming the DCS profile in saved games as Max suggests and of course do a full DCS repair and clean. Tried that as well, again no luck.
MAXsenna Posted October 24 Posted October 24 Tried that as well, again no luck. You're not using Quaggles Auto Injector by chance? Sent from my SM-A536B using Tapatalk
Starspeed Posted October 24 Posted October 24 vor 46 Minuten schrieb MAXsenna: You're not using Quaggles Auto Injector by chance? Sent from my SM-A536B using Tapatalk Nope, I don't even know what that is
MAXsenna Posted October 24 Posted October 24 Nope, I don't even know what that is I'm losing hair here! Damn! Sent from my SM-A536B using Tapatalk
VirusAM Posted Sunday at 12:28 PM Posted Sunday at 12:28 PM (edited) I have the same issue, with trackir,...VR is working correctly Edited Sunday at 12:28 PM by VirusAM R9-9950X3D 96GB RTX-4090 LG-38GN950 Sony PSVR2 Moza AB9 FFB Base + Moza MH-16 Grip, VKB Stecs Max, VKB T-Rudder MKV, Razer Tartarus V2 Secrets Lab Tytan, Monstertech ChairMounts
DragonSoulkin Posted Wednesday at 11:00 PM Author Posted Wednesday at 11:00 PM Via remote desktop on my friend's computer, I renamed his DCS.openbeta folder in SavedGames and did a cleanup and full repair, launched DCS, and his head tracking tab in Axis Commands is still grayed out and not bindable still. So I uninstalled the Tomcat module, and re-installed it, and it's still greyed out and not bindable. Although, similar to what @Starspeed noticed, I checked the F14 RIO controls and what did I find? You can keybind the headtracking in Axis Commands, just not for F14 Pilot. 1
MAXsenna Posted Wednesday at 11:10 PM Posted Wednesday at 11:10 PM Via remote desktop on my friend's computer, I renamed his DCS.openbeta folder in SavedGames and did a cleanup and full repair, launched DCS, and his head tracking tab in Axis Commands is still grayed out and not bindable still. So I uninstalled the Tomcat module, and re-installed it, and it's still greyed out and not bindable. Although, similar to what @Starspeed noticed, I checked the F14 RIO controls and what did I find? You can keybind the headtracking in Axis Commands, just not for F14 Pilot. read in another thread that one user had copied some of the RIO lines to the Pilot so he didn't have to switch seats to do some stuff, and it led to the same issue. Obviously your friend is not in that situation after a repair. But that user eventually solved it by copying the headtracking lines from the RIO to the Pilot. You can try that.Cheers! Sent from my SM-A536B using Tapatalk 1
DragonSoulkin Posted Wednesday at 11:16 PM Author Posted Wednesday at 11:16 PM 2 minutes ago, MAXsenna said: read in another thread that one user had copied some of the RIO lines to the Pilot so he didn't have to switch seats to do some stuff, and it led to the same issue. Obviously your friend is not in that situation after a repair. But that user eventually solved it by copying the headtracking lines from the RIO to the Pilot. You can try that. Cheers! Sent from my SM-A536B using Tapatalk Yup, I've actually created my own keybinds for the Tomcat in the past like the air source switches and creating an axis for the radar altimiter set knob so it should be simple enough to transfer over the RIO keybinds for headtracking to the pilot keybinds to open up the availability. Just didn't think about it beforehand. 1
MAXsenna Posted Wednesday at 11:21 PM Posted Wednesday at 11:21 PM 3 minutes ago, DragonSoulkin said: it should be simple enough to transfer over the RIO keybinds for headtracking to the pilot keybinds to open up the availability. Just didn't think about it beforehand. Me neither, then I read that other post and tried to find this thread again, and it popped up. Best of luck!
Recommended Posts