RogueSqdn

Well if it’s a VKB tool, I’ll just stick with what I came up with last night: an AutoHotkey script that positions the cursor in the center bottom third of the screen, triggered by a button on the CM2 grip. Sent from my iPhone using Tapatalk

Curious what program you're using there. I just got my VPC gear last week and while I know my way around TARGET, I'm trying to get by with Joystick Gremlin. For putting the mouse in a specific spot, you have to move it a corner and then move it to your spot, which is not always ideal. I'm open for other options.

New order Mine was ordered on 4/21, shipped on 5/2, and arrived in NC today. I’ll open it when I get home but my wife sent me this picture. Ordered the WarBRD, CM2 grip, and T50 throttle. Sent from my iPhone using Tapatalk

Unfortunately I've hit a brick wall on the lighting. I'd have to have someone that knows a lot more about the subject than I do to figure it out. That said, when I was trying to get it recognized in TARGET, I did a bunch of googling and saw where people had tried and failed to get it going, but took their failure points and figured out the rest of it. I'm not trying to brag on myself, just saying that perhaps someone can take what I figured out and find the next step that's necessary.

I have two of them (bought one for my PC, one for my Mac) and aren't even using them right now... maybe I should hit eBay. ;)

I ordered the CM2 grip, WarBRD base, and T-50 throttle this weekend and got an email confirmation at the same time as the Paypal confirmation. I plan to use my WH grip when flying the A-10 and the CM2 for the Hornet and Tomcat (at least until the Tomcat grip comes out).

Doing some more fiddling around, and I can't seem to control the lights on the CMFD. I'll keep looking around, but if anyone has a suggestion, please let me know.

I've done some searching around lately, and after digging through a few files, I have managed to get a third MFD added and working in TARGET. There are three files involved (four if you're using the 120 DX button addon): 1) TARGET.tmh (C:\Program Files (x86)\Thrustmaster\TARGET\scripts) The first thing is to add the CMFD as a an alias at the top of the file: alias Throttle = "VID_044F&PID_0404", Joystick = "VID_044F&PID_0402", LMFD = "VID_044F&PID_b351"; alias RMFD = "VID_044F&PID_b352", HCougar = "VID_044F&PID_0400", T16000 = "VID_044F&PID_B10A"; alias TWCSThrottle = "VID_044F&PID_B687", TFRPRudder = "VID_044F&PID_B679", T16000L = "VID_044F&PID_B10B"; alias TFRPHARudder = "VID_044F&PID_B68F", JoystickF18 = "VID_044F&PID_0403", CMFD = "VID_044F&PID_b353"; You will also need to add two lines. First, after the RMFD line in the GetIndexJoy section, add: &CMFD = GetIndexJoy(Select(&CMFD)); // expect a CMFD to be plugged on USB Third, you'll need to add the MFDMap line after the RMFD line: MapList(&CMFD, &MFDMap); 2) dx+.tmh (C:\Program Files (x86)\Thrustmaster\TARGET\scripts) If you're using the 120 button addon here, you'll need to add those GetIndexJoy and MapList lines to this file as well. 3) VID_044F&PID_B353.dev and VID_044F&PID_B353_MFD3.xaml (C:\Program Files (x86)\Thrustmaster\TARGET\DevCfg) You'll need to make copies of either the left or right MFD files here and edit the information in the .dev file: a) Edit line 3 to say <HWID>VID_044F&PID_B353</HWID> b) Edit line 4 to say <Name>MFD Cougar 3</Name> c) Edit line 54 to say <File>DevCfg\VID_044F&PID_B353_MFD3.xaml</File> I haven't tried it, but if you change the references and files to B354, I imagine a fourth MFD would work. I've included the four files needed in this zip. Copy everything to C:\Program Files (x86)\Thrustmaster\TARGET (you'll need to give admin approval) and it should work. I included the instructions in case you want to try this on your own. Good luck! CMFD.zip

Seconded

Sounds like it'll work well for DLC on the Tomcat.

Looks great! I only have three suggestions. One, you already mentioned, remove that Warthog stick plate. It'll allow you to get much closer and more comfortable. Two, I'd consider adding a third MFD and screen and possibly a programmable keypad (X-Keys, Genovation, etc) to act as a UFC. I'd go that route before getting something aircraft-specific since you could change the layout based on what you're flying. Three, I'd try to find a way to put that Keyboard on the left side. If you need to use it while flying, it'd be much easier to do so without taking your hand off the stick. Have fun with it!

Seconded. Experienced this tonight and took a while to figure it out. By the time I did, the SA-15 got me. :(

Thanks! I’ll defin be getting that made. I have a Sahaj 100mm extension and it’s way too high to work well with my Obutto.

I'm more interested in your stick extension. How did you do that? EDIT: Found the part2 thread and the file. I don't have a 3d printer though, and after several minutes looking around, I don't see any web services that accept the F3D format. Know any?

Just a little word of warning. Every now and then, especially with an early access product like the Hornet, new commands will be added in an update. This week's update added at a minimum the depress function of the sensor control switch. When this happens, you'll need to create a new version of your mod from the updated default.lua.

I grew up on Top Gun, wore out a lot of VHS copies. Saw it in the theater when I was seven. March 15th is my 40th birthday. I wasn't looking forward to that, but now I'll have something to look forward to. Thanks, Cobra, and the Heatblur team, for all your hard work.

I'm having trouble with the Audio tab. I'm wanting external sounds through my speakers and comms through the Rift. What should I set Windows to, and what should I set the Audio tab to? I'm doing what I think the manual is saying, which is to select Rift Audio in the VAICOM audio tab, but should the Device in Windows be my speakers or the Rift? I think we need some more detailed instructions here. Thanks,

I can never get it to LOAD. Always hangs up on mission loading.

Wow, just ran across this. This looks great and far better than doing it manually in Powerpoint or Keynote like I used to do in the past. Might I suggest this become a sticky and be moved to the Thrustmaster forum?

I used Super Lube 21010 NLGI2. No issues so far. https://www.amazon.com/gp/product/B000BXKZQU/ref=oh_aui_search_asin_title?ie=UTF8&psc=1

A few weeks ago I flew a night strike into Iran in the Hornet, in the Rift. I was chased out by F-5s and had to turn around and engage. After making it through that, I got to the S-3 tanker with only 400 lbs of fuel. I connected and it only got me to ~4000 lbs before it ran out, but that was ok, the carrier was only about 45 miles further out. I made it and boltered on my first pass. I came back around and was down to about 2700 lbs when I called the ball. As I touch down, BOOOM! I couldn't see that there was a Tomcat sitting there in the wires. Please get the carrier ATC sorted! :)

I didn't even think about modifiers... :doh: I'd use an available joystick key as a modifier instead of a keyboard key, though.

Didn't know you wanted a momentary button... my code was meant for a toggle switch like on the Warthog, where it's only on in one position. I realized just now that you had the word TOGGLE in your post. :) LUA scripting is not going to work for this situation, I'm afraid (neither LUA or DCS allow you to assign two separate commands to one button). If you were using TARGET, it would be dead simple to do: MapKey(&Throttle, APENG, SEQ(Strobe_BRT, Strobe_OFF)); With Strobe_BRT and Strobe_OFF either defined in your macro file, or replaced with the keystroke or DX button commands you wish.

Give this a try and see if it works: {down = extlights_commands.Strobe, up = extlights_commands.Strobe, cockpit_device_id = devices.EXT_LIGHTS, value_down = 1.0, value_up = 0, name = _('STROBE Lights Switch - BRT else OFF'), category = {_('Mods'), _('Left Console'), _('Exterior Lights Panel')}}, {down = extlights_commands.Strobe, up = extlights_commands.Strobe, cockpit_device_id = devices.EXT_LIGHTS, value_down = -1.0, value_up = 0, name = _('STROBE Lights Switch - DIM else OFF'), category = {_('Mods'), _('Left Console'), _('Exterior Lights Panel')}}, The existing lines for this switch are: {down = extlights_commands.Strobe_EXT, cockpit_device_id = devices.EXT_LIGHTS, value_down = 1.0, name = _('STROBE Lights Switch - Up'), category = {_('Left Console'), _('Exterior Lights Panel')}}, {down = extlights_commands.Strobe_EXT, cockpit_device_id = devices.EXT_LIGHTS, value_down = -1.0, name = _('STROBE Lights Switch - Down'), category = {_('Left Console'), _('Exterior Lights Panel')}}, {down = extlights_commands.Strobe, cockpit_device_id = devices.EXT_LIGHTS, value_down = 1.0, name = _('STROBE Lights Switch - BRT'), category = {_('Left Console'), _('Exterior Lights Panel')}}, {down = extlights_commands.Strobe, cockpit_device_id = devices.EXT_LIGHTS, value_down = 0.0, name = _('STROBE Lights Switch - OFF'), category = {_('Left Console'), _('Exterior Lights Panel')}}, {down = extlights_commands.Strobe, cockpit_device_id = devices.EXT_LIGHTS, value_down = -1.0, name = _('STROBE Lights Switch - DIM'), category = {_('Left Console'), _('Exterior Lights Panel')}}, So you can see that BRT is value 1.0, OFF is 0, and DIM is -1.0. Using those values you can come up with the example I gave you.

One option that won't give you trouble when DCS updates is to make a copy of default.lua, named it "Throttle - HOTAS Warthog.lua," and add your modified commands to that. If the module you're using already contains a file for the Warthog throttle, this idea wouldn't work (The file would get overwritten during DCS updates). I use OvGME, and from tiem to time vary between using solely lua edits and using TARGET. I haven't settled on one method or the other. TARGET programming doesn't bother me at all, as I've been doing it since the early 90s with bother Thrustmaster and CH programming.