Davee

I'll take a second look at this.

Wonder if it will work with the hat clip?

They were going to use the CF-105 as a refueler for them but things got broken. :)

It would be really great if the VKB device configurator would recognize TM equipment like VPC configuration device does. See this link: I sure would like to combine different devices like many of us have. I have a TM WH Throttle and VKB MCG II. Cheers, Cats . . .

Yes, that is what I want also. I use Target script for all the things you mentioned. At this time VKB does not recognize TM like VPC does.

Hi Avantar, For WH products the Target Script Editor will accomplish what you are doing. Most use just basic Target which is just that . . . basic. :) But . . . . I have a TM Throttle and a VKB stick. My issue is that I would like both sticks to recognize when a modifier key is pressed to change modes between devices. A program that will serve the same function or better than the Target Script Editor which only works on the WH. Thanks for a superb program. Cats . . . .

I used to just remark out the folder for Russian in the language files and it will automatically choose English as default.

Go to the Nellis map and land in area 51 and look into one of the hangars and you will find a hidden undocumented surprise that has been there since the map was released. That doesn't appear to be a problem for you? :)

Can this be done if each drive is a different size?

Yes they did a while back but a search will be required to locate the information.. As I understand it, it is a fully fleshed out carrier compared to the free one. Think elevators and such.

It helps to allow it to move with a crosswind on final. It compensates the correct amount if you place the flight-path marker where you want to land when compensating for the wind. Otherwise, I cage it.

Have you taken off before with no problem? I have not had this happen to me but I thought that I would post some links in case you see something missing. https://www.youtube.com/channel/UC1Rsn65d8Qzy4T9A8435sYw

This should work if I recall. MapKey(&xxxMFDxxx, xxxbuttonnamexxx, CHAIN(a, L_CTL+'3', L_CTL+'5')); I don't have an MFD so you will know better the name where I put xxxMFDxxx.

Thanks Sokol1, This is quite the find. It might make all the difference for me. Two things come to mind. I see that the standard target program is being used in the example. I use the TARGET SCRIPT EDITOR. Quite different. From the information, it seems to imply that the VKB Stick shows up in TARGET and therefore I assume that it still uses TARGET to program the buttons. If this is so, then I should be able to utilize TARGET SCRIPT EDITOR which is a very powerful tool and not subject to the whims of DCS changing the .lua file. Even the .lua files can't do what the SCRIPT EDITOR does. So my preference is for a number of reasons beyond what is discussed here and it certainly qualifies me as a TARGET SCRIPT Addict. :) Thanks for this, I will investigate further this afternoon and hope that I will be able to pair up my systems. I think that the VKB stick is physically superior in many ways to the WH Stick but the WH "System" is of greater value to me as a matched pair inter-programmable with modal buttons or switches. Cheers.

Agreed . . . . we are comparing - er, really contrasting two different generation jets with different avionics. But I think it depends on the circumstances of the fight that should be extrapolated in detail because, one jet will not always beat the other. :) The term "better" IMHO, can be a charged and subjective word that if expressed without qualifications, gets some folks hyped up because they assume their favourite jet is being dissed. I took the term "better" for what I think you meant. (The art of reading comprehension.) No issue for me. So guys, let's not let this thread get off the rails! The original poster has a good question and outside of more flying time on each module, there are many other possiblilities. Looking forward to some factual technical input on tactics and capabilities and numbers in the air, experience and conditions of the missions. In response to the OP please! Cheers guys!

I did the same but for me having the WH HOTAS for many years, I've grown very comfortable with TARGET script. I am however, having difficulty figuring out simple changes to the VKB Gunfighter stick. So many options to choose from and the manual is not (to me) user friendly. I'm about to give up and sell the VKB and seriously will consider the F18 stick and base when it becomes available. I have, in the last couple of days, reconnected my TM Stick and having a much easier time configuring the options for IO/UMD/CHAIN/SEQUENCE commands. It really opens up the options with a matched set. The only thing I have against the TM Stick is the heavy spring and outdated gimbal system. They need to move fast to change the base. But . . . . hey, that's me. Cheers :) ps: For clarification as it seems that many assume TARGET use means the basic TARGET program. Please note it is the TARGET SCRIPT EDITOR that I use.

I think it's changing the laser code pulse transmittion from the aircraft only, not the bomb code which is pre-set? The bomb code does not change but the pilot can change the laser pulse code to match the bomb code on board of another aircraft for buddy lasing?

If I recall from Marketing 101, that according to the Antitrust Laws and the Combines Act, a new product being introduced to the market cannot be on sale or at a reduced price. After initial release (can't remember the duration) then it is OK. This is to avoid undue competitive advantage on an untried product.

If you have a lamp behind you that is in the soft white or 3,000 degrees Kelvin, it will project some Infra Red and affect the TIR sensors also.

My understanding of the AIM-54 was that it was designed for downing (then) Soviet bombers at long distance. Big aircraft incoming. I've never heard of it being utilized against fighter sized aircraft. Seems to be a misuse of the intended design to me. For me, this is a negative to the suspension of reality.

It came back again for me and this is what I see: If you start the sim without having Target loaded it will select the JS that way and show that only in the SIM controls menu. If you then load target later, both will show in the SIM controls menu. You will then have to load target and then replug the USB plug. That will get rid of the non-target control info. From then on, it will load Target just fine until . . . . . wait for it . . . . you decide to load the SIM again WITHOUT the target profile loaded and whoa, you're back to unplugging and loading target again. Pain in the butt.

There is no trim re-set in the Hornet. Just some thoughts: Have you followed the trim setting procedures at startup? Are your rudder pedals centred correctly? Are both engines putting out the same power?

+1

This!

OK, I'm not familiar with that program. However, I'm pretty sure that a script profile is in there somewhere. To my knowledge, it is alway there - even in the background somewhere. Hope you find it. Still working fine for me.