@16th-ACCW-Android

I did and it was pretty weird - I’d purchased a Razer V2 headset with a charging station. Had the station plugged into a USB port on my PC and this problem started. It took a while to figure out because it would not happen on every single mission but was intermittent. However, it always happened when the base station was plugged in.
So had to reinitialize plugging and calibrating my Cougar and TQS (with the charging station unplugged) and it seemed to have solved the issue. As I said a weird one but it was the only thing I’d changed in how my rig was configured so I focused on eliminating it. So both the headset and charging station sit on my desktop un-used today. I’m using an Astro A40 w TrackIR without any issues going forward.

Duke

Turned out to be user error. Did not realize my fingers were reaching over the top of the right throttle displacing the XY cursor. Not sure why my target WPs in the DED did not change but I had a flight subsequent to posting this and changed my grip and not issues. User error on my part…

@GhastlyTT Thanks had not used that prior, It gives me a large window which is movable so it can be placed on one side of the screen. This would allow muting the Discord mike and starting a remote server. Good hint and thanks.

Duke

@SgtT11B-0 Icarus assisted me, I was using the exact file on Foxy you have above, the biggest thing about the changeover was finding the numbered axis for each HOTAS axis and once we had the HOTAS Control Panel set up as Icarus has indicated above it went quickly together. The key assignments went quickly once axis were assigned. Good luck and ask if more questions.

Duke

So I admit I’m brand new to the Warthog having used a TM Cougar w FSSB until it died two weeks ago.
I have a pretty simplistic setup for the stick and throttle - nothing for the base of the stick.
Also have two TM MFDs that I use.

Situation;

Dive bombing (mid level) practice mission at Kotar.
My target is the southern most large circle target in a cluster of five - one on each compass point and one in the middle
My target is designated as WP15 N38.08.087/E130.20.586 2854 elevation.

I have WP 15 and the details displayed in the DED. These never change throughout six pattern runs.

Climb out and over the mountains make a right turn to get into the bombing pattern and up to altitude.

Downwind, base and the DED still displays the target as designated above.

Roll in and no diamond on my HUD for the designated WP. I knew where I was to bomb on this mission so did it by the Mark One Eyeball. Completed five more runs with no tag on the target circle, WP15 called up in the DED and the correct Lat and Long/Elevation.

This never happened with the Cougar so obviously I’m missing something basic (I hope).

Any thoughts on how to resolve would be welcomed.

Thanks in advance,
Duke

Got it working today, was as you suspected, a freq issue… so mark this off as a momentary lapse of reason on my part.
Dukera

@Doc0301Ok so it is ON, are you in NAV mode? Will not work otherwise.

Not sure about No Plan, but inactive units are those which are not yet participating in the campaign but fragged to join at some point in the future. They can be displayed or not displayed on the 2D map, based on, I believe, an option in MC on the ground units page. Hope this helps some.

The flashing AR box goes out when you turn the radar altimeter to ON.

@Damir If you are using 4.37 version of BMS, all keypresses and axis definitions are set up via the launcher. I’m not fluent on your HOTAS set up but basically you will need trim, TMS, DMS and CMS set up on the stick along with trigger(s) 1 & 2, and pickle switch for AA or AG weapons release. There was a definition of this in the old Dash 1 manual, not sure if it is in the 4.37 version.

No reason to use your own specific keyfile on 4.37 onward.

Hope this helps,

Duke

@LorikEolmin Flight of 4 F-16 50s.
@Oakdesign - that worked but curious - should I copy the new 16.txtpb file into my campaign folder so the TE build will pick it up?

Thanks by the way.

@oakdesign Will give it a try.

Not sure if this is new to the latest release but I have not seen before.
Building a TE for A2A practice with a 4 ship and AWACS.
On either full engine start or just taxi no Link 16 for the fighters and AWACS.
Nothing shows on HSD and no circles on the a/c at taxi out.
Looked at the Link16 file and noticed no assigned radio freqs for MC or FC channels. All other details correct in the jet.
Tried to enter 076 and 006 for MC and FC - they seemed to save but was not able to call them back up.
I’m certain had not seen in prior TE builds.
Any thoughts would be welcome.
Thanks
Duke

Hey SoBad.

Just came across your document early this morning.
I’ve been doing a lot of the setup steps you document in setting up my campaigns.
Will enjoy picking up some new ideas, so thanks for putting it out.

Duke

Turned out to be user error. Did not realize my fingers were reaching over the top of the right throttle displacing the XY cursor. Not sure why my target WPs in the DED did not change but I had a flight subsequent to posting this and changed my grip and not issues. User error on my part…

So I admit I’m brand new to the Warthog having used a TM Cougar w FSSB until it died two weeks ago.
I have a pretty simplistic setup for the stick and throttle - nothing for the base of the stick.
Also have two TM MFDs that I use.

Situation;

Dive bombing (mid level) practice mission at Kotar.
My target is the southern most large circle target in a cluster of five - one on each compass point and one in the middle
My target is designated as WP15 N38.08.087/E130.20.586 2854 elevation.

I have WP 15 and the details displayed in the DED. These never change throughout six pattern runs.

Climb out and over the mountains make a right turn to get into the bombing pattern and up to altitude.

Downwind, base and the DED still displays the target as designated above.

Roll in and no diamond on my HUD for the designated WP. I knew where I was to bomb on this mission so did it by the Mark One Eyeball. Completed five more runs with no tag on the target circle, WP15 called up in the DED and the correct Lat and Long/Elevation.

This never happened with the Cougar so obviously I’m missing something basic (I hope).

Any thoughts on how to resolve would be welcomed.

Thanks in advance,
Duke

My TM Cougar w FSSB gave up the ghost last week and I’ve ordered a Warthog.
I’d like to use my rudder pedals and need a RUSBA, the only place I know to look is the Real Simulator site and they are out of stock.
Open to any other thoughts or places to look.
Thanks in advance,

Duke

Before you go into the cockpit are you opening the briefing page and then the COMM tab in the data cartridge to ensure correct freqs from the briefing page are reflected in the cartridge? I’ve sometimes forgot this step and took off with the incorrect freqs so no comms from wingmen or AWACS…

Thank you!

@airtex2019
This was me thinking of the Alternative Launcher as the Launcher in the main Falcon directory. A momentary lapse of reason as someone once said…