Baitball

I think that was the issue. Thanks so much for the response!:thumbup:

I'm experiencing an odd issue with my TGP. My parameters are: TGP set to AG mode, weapons set to AG mode, CCRP mode selected, Master Arm on, Laser Code set, Laser on, SOI on TGP and TMS down to reset view to center. However, although doing this does show the TGP box on my HUD and pushing TMS up on the target does ground lock to the target I was pointing at, the box then continues to sit centered on the HUD and does not cage itself to the locked target on the ground. (Slewing from my locked target also does not move my TGP box on the HUD) I also see a steering cue with heading corrections at the top of my HUD heading tape that I never selected or want. This results in the lack of a pickle countdown on my HUD along with a wrong CCRP vertical steering line on the HUD (The pickle countdown and vertical steering line both seem to be slaved to whatever my heading steering cue seems to be pointed at, but I cannot get the aircraft to ignore this point) I'm obviously missing something here, what am I doing wrong?

Sorry to add another problem here, but I'm experiencing an odd issue with my TGP. TGP is set to AG mode, weapons set to AG mode, CCRP mode selected, Master Arm on, Laser Code set, Laser on, SOI on TGP with TMS down to reset to center. However, although doing this does show my TGP box on my HUD and TMS up on the target does ground lock to the target I was pointing my box at, the box then continues to float on the HUD as bore sight and does not cage to the locked target on the ground. I also see a steering cue with heading corrections at the top of my HUD heading tape that I never selected or want. This results in the lack of a pickle countdown on my HUD along with a false CCRP vertical steering line on the HUD. What am I doing wrong?

I updated the driver and replugged into a different port, it works! Thanks for everyone's help!

The mapping dialogue does open, but moving the pedals fully in either direction does not register. My left/right toe brakes registered just fine.

Yes, this is what I have been doing. Making sure I am clicking on the correct column that correlates to my pedals. And yet, it still will not recognize the pedal inputs.

Surely I must be missing something obvious, but I can't seem to be able to get the rudder axis to recognize my TFRP Rudders. What am I doing wrong?:helpsmilie:

I ran a repair on the game from the bin folder and it is now working! I still have no idea why this happened but the repair seems to have worked.

I recently decided to try DCS with my HTV Vive, and I have run into an issue I cannot seem to figure out. I am using the Warthog HOTAS, and my Gun Trigger is assigned to my second detent on the trigger (which DCS recognizes and I have tried multiple times resetting this bind). However, in multiple servers now, with my Master Mode armed, my AA selected, and a good lock on radar, I cannot get any missiles or guns to fire. My weapon release for GBU's, Mav's, rockets, and bombs are working. With TrackIR, I have no issues with the trigger. What the hell is going on?:joystick:

After today's update, my trigger does not work in either beta or stable. I tried remapping the trigger and indeed the trigger on my Warthog itself does register into DCS, but it will not fire in game. The color of the row containing the trigger in the settings page is a different color as well. Has anyone else experienced this?

Thanks! Understood, thanks for your testing! You do mean a solid shoot cue and not at range of no escape, correct?

At what point does the missile go pitbull? Theoretically speaking, as long as I'm within max range, and with a shoot cue on the HUD, can I fire and break lock?

That is correct. Bore, Wide, and Vertical are all part of the ACM modes under the "Sensor Control Switch" in the settings. Once you have those binded, you will be able to cycle through the various modes with your A/A armed. *currently the only radar modes implemented are RWS, STT, and ACM. RWS being the normal scanning when you turn the radar on, STT once you're locked onto an aircraft, and ACM being the ideal locking method for dogfights or anything 10nm and under.

1. RWS is active when your radar is on Operate and not locked, TWS is when a target is locked (Do I have that backwards?) 2. Not sure what that is 3 + 4 + 5 are all part of the sensor control switch (ACM modes) pushing it forward defaults to Bore. Set your forward, aft, left, right sensor control switch and you will see your ACM modes cycle through during flight

Indeed you are correct, I was confusing it for the list of things to come Wags had posted:doh:

Roger that:thumbup: I guess we'll wait!

I'm not sure if you're having these issues too, but here are two things that I noticed before the latest update (and was supposed to be fixed in the update) but I am still having issues with: 1. STT Lock is still changing locks to another aircraft if there are multiple aircraft around (the aircraft is within visual range, and is not maneuvering into cover such as behind a hill) 2. When attempting to Bore Sight acquire a lock with multiple aircraft around (but only the aircraft I want to lock inside my bore circle), the radar continuously locks a different aircraft (and usually will continue to try to lock that specific aircraft) Is this a fault on my end or was the update also ineffective for you?

I've been reading on Reddit that AACQ is working now for people after the last update on Beta but I have had no luck with it on instant action. I don't remember seeing a patchnote for the AACQ system, so should mine be working by this stage?

I'll try it out, thanks! But where exactly is that file before /Saved Games? *found it!

I doubt this is the problem, but is your OBOGS on?

Is there an easier way to bring all my mappings from Stable DCS along with the plane specific controls and binds to Beta DCS without doing it by hand after installing Beta?

Understood, thanks for the insight!

Gotcha. I am rather new to DCS, how long does it usually take before a Beta update is applied to the Stable? In other words, should I be reinstalling Beta and remapping?

Understood. So if I do fly on Beta, am I still connected to the same server sets as those flying through the stable DCS?

The title says it all; after the update today, I don't understand what is going on. The last DCS Stable update placed the Hornet into the Stable, at which point I (and I'm guessing alot of other people) downloaded the Hornet onto Stable and uninstalled Beta. However, today's update involves the Hornet and it is only available for Beta. Can anyone explain to me why this is? Were we supposed to stay on Beta for the Hornet? Is there a delay between the beta update vs the stable update?