Bad Karma

So it looks like your squad files F-16, F-18. and the AH-64. Are there any other planes that your squad flies?

Are you still looking for pilots? Primary plane is A-10

I have both Normandy 1944 and The Channel map in my library on Steam. I see the upgrade on Steam but it only lists this for the 14.99 and not the 10.00 price if you own both of the terrains. Is anyone else having this issue?

Well I did have some odd Track IR behavior recently. I would start the Track IR software and the program would freeze up in a white window saying Not Responding. Or else it would start normally and freeze when selecting a profile. I contacted tech support and did the full uninstall and reinstall of the Track IR software and they even had me do a reinstall of the C++ library. My problem seems that Track IR does not like to be closed on a second monitor. I run the program on my second monitor and just drag it back to my primary when I close it and it works fine. Track IR even admitted that running the program on a second monitor can cause an issue. If I close the program on m second monitor all I need to to do delete the ProfileMap.dat file in the NaturalPoint AppData folder and that will fix it. If it is being stubborn deleting the settings. xml file will do the trick. This is easier than reinstalling the driver. Maybe this will help someone.

I appreciate you taking a look. I was able to get the radio check ins working on that mission. This was my second play through on the campaign and I hope you make a part two.

This is in the latest beta version. I start the mission and fire up the APU and tune the radio to 33.3 as the mission prompt box says but I am unable to get a check in. I tried everything I could think of different frequencies etc. to see if I could get the mission tor proceed. I went back to mission 04 and ran though the mission prompts and it worked just fine. If you could look into this I would appreciate it.

Here is a post I found on Reddit in the DIY HOTAS sub. It has link with PDF showing 2D drawings of the TEDAC grips. You could use those drawings and model around the views to create your TEDAC grips. https://www.reddit.com/r/HotasDIY/comments/abydz7/mason_controls_blue_prints_stick_grips_throttles/. It has some other grips and throttles there as well that may come in handy to anyone starting a project.

I guess I need to make up for my previous blunder so here it is. This is a function LULA command to get the Thustmaster Warthog Throttle Boat Switch to act as a video mode switch for the TADS. It will switch from FLIR, TV, and DVO. Put the commands in the Joystick Lula file and then go to the keybindings and under custom you will see the new command. Set the forward switch on the Boat Switch to one and the rear switch position to the other command. The devices.TEDAC, tedac_commands.LHG_TADS_SENSOR_SELECT_SW command was found in the DECSWorld\Monds\Aircraft\AH-64D\Cockpit\Scripts\clickabledata.lula file { down = tedac_commands.LHG_TADS_SENSOR_SELECT_SW, up = tedac_commands.LHG_TADS_SENSOR_SELECT_SW, cockpit_device_id = devices.TEDAC, tedac_commands.LHG_TADS_SENSOR_SELECT_SW, value_down = 1.0, value_up = 0.0, name = _('LHG_TADS_SENSOR_SELECT_SW UP'), category = {_('TEDAC'), _('Custom')}}, { down = tedac_commands.LHG_TADS_SENSOR_SELECT_SW, up = tedac_commands.LHG_TADS_SENSOR_SELECT_SW, cockpit_device_id = devices.TEDAC, tedac_commands.LHG_TADS_SENSOR_SELECT_SW, value_down = -1.0, value_up = 0.0, name = _('LHG_TADS_SENSOR_SELECT_SW DOWN'), category = {_('TEDAC'), _('Custom')}},

This is for my fellow Thrustmaster Warthog HOTAS owners. I want to get as much functionality on my HOTAS as I can so I matched the throttle behaviour on the A-10C and A-10C II. So lifting up the throttles will move the engine power levels from off to idle for start up and idle to off again at shutdown . After that it switches back to the normal collective functionality. This was almost a direct copy paste from the A-10C II LULA file with some minor edits. If you own the A-10 module and the Trhustmaster Warthog HOTA looking at the LULA file for the Throttle HOTAS Warthog LULA file can give you some ideas.. {combos = {{key = 'JOY_BTN30'}} ,down = iCommandLeftEngineStop , up = iCommandLeftEngineStart, name = _('Power Lever (Left) - OFF/IDLE') , category = {_("Special For Joystick"), _('Systems')}}, {combos = {{key = 'JOY_BTN29'}} ,down = iCommandRightEngineStop, up = iCommandRightEngineStart, name = _('Power Lever (Right) - OFF/IDLE'), category = {_("Special For Joystick"), _('Systems')}}, --{ down = iCommandLeftEngineStop, up = iCommandLeftEngineStart, value_down = 1.0, value_up = 1.0, name = _('Power Lever (Left) - OFF/IDLE'), category = {_('Power Lever Quadrant')}}, --{ down = iCommandRightEngineStop, up = iCommandRightEngineStart, value_down = 1.0, value_up = 1.0, name = _('Power Lever (Right) - OFF/IDLE'), category = {_('Power Lever Quadrant')}}, I top two lines of code were my additions to my LULA file. The bottom two lines were the original lines commented out for testing. I am just showing them so the original lines of code to make them easier to find in the file. My next edit might be to make the Boat Stitch change the video mode on the TDEAC from video to flir etc. EDIT: Well I double checked the keybinds for Off/Idle and they do actually work when raising the throttle levers on the Warthog Throttle. No need to edit the LULA file to do this one. Now I guess I can play around with it and see if I can get some other buttons to work the way I want them to.

Thanks to the few others for posting up here so I know I am not crazy. Thanks Catweedle for posting a track I guess I should get used to doing that. I did have another thought about this issue late last night. I am using a Thrustmaster Warthog HOTAS and it does work great with the A-10 modules but can have some unexpected results with others. By default the two stage trigger used in the A-10 as a hold on the first detent even while the second detent is getting pressed. This is to activate the A-10 Gun PAC (Precision Attitude Control) system on the first trigger detent and having it active while the gun is firing. When the trigger is released the PAC system turns off. So I went into the Windows Joystick Control Panel and checked the default button mapping. On pressing the first stage of the trigger one button activated and hitting the second detent the sets both trigger detent buttons to on. So this whole thing might really be more of a controller issue vs a programming glitch. I am going to have to lean some Thrustmaster Target Scripting and hopefully get the trigger to function as I desire. This might just have to do with playing JD Longbow as s teenager. Maybe we can see if other users of the Thrustmaster Warthog HOTAS are having the same issue? I also included a track file of what I am seeing. Laser Range Finder Reads 9999 On First Dentent Pull.trk

There is a setting that might help you out. At the start screen go the options menu and go to the special category. There should be a list of your installed modules on the left so select the AH-64. Now in that option screen there is one that will allow you to click through all guards and make them totally unneeded. No need to bind a key just hit the trigger and you are firing. Not "Realistic" but it does simplify things.

Sorry about that I guess YouTube made some changes since I used it last. It should be working now. I actually made a new video since the last one was a little hard to see. This one is a zoomed in view on the TADS display. TADS View First Detent Reads 9999

Started in version DCS 2.7.11.22041 Open Beta and continuing in version DCS 2.7.11.22211 Open Beta As CPG and using TADS system with 30MM cannon armed I use the first detent to establish range to target. The range displays as 9999 and shows the BAL LIMIT error. I use the second trigger pull and the laser displays the correct range. I can than fire the cannon accurately without any error. I am in hover while doing this as per the Quick User Guide. I read through the AH-64 Quick User Guide on weapon implementation on use of the cannon just to confirm I was using the system correctly. "8. If laser ranging is desired, begin lasing the target with the laser trigger on the RHG. If both the target and the aircraft are stationary, first detent ranging may be used. If either the target or the aircraft are moving, the second detent designation should be used." I have a Thrustmaster Warthog Stick I am using as a controller. I have the first stage of the trigger mapped to LRF First Detent and the second stage of the trigger to fire weapons. I did change the controller mapping to see if that would change things, but it didn't affect the results. There is some odd behavior using this setup as well I can range with the second detent, but the range will bounce back to 9999 pulling through the first detent. If I hold down the button assigned to the second LRF detent I can hold the correct range to target. I made a video of the issue; I apologize for the quality I am by far a YouTube expert. DCS World AH-64 LRF 9999 Bug

We have a winner. Thanks Baldrick33, that did the trick. For that I will give you some beans or a triangle for you when you play in the band. Black Adder was a great show.

I gave it a try Ghostraider. I was able to WAS up the gun, release the trigger guard and fire a few rounds off but the mission was still stuck on "WAS Up The Gun".