Greyman

i had that too, the first time i did it, but for some reason, the shells landed on target on the re-run. i thought it must have been something to do with my dive angle maybe.

Seems odd, but good find,

Maybe a thread for custom daisy-chained profiles that other users might find useful? Good job and grats on the sub-forum @Hollywood_315 and @hornblower793. EDIT: oh and can one of the FAQs be a lesson in how to spell VAICOM? ;p

\o/\o/\o/\o/

It might be worth checking what Hollywood wants to do for himself, but I wouldn't think he would have a problem. A FAQ might be a good place to start, for things like deleting export.lua and ticking the OB box. An AIRIO and/or Chatter sub-forum might be useful too, if there is an option to create them.

A sub-forum \0/\0/

I'm not sure, as i don't use Target for my WH, but it might still be worth removing any mappings from the physical one that might interfere. It would only be one or two mappings that you'd need to remove, just to prove that they aren't interfering.

A wise man once told me that the only problem with communication, is the illusion that it has taken place.

You haven't been switched back to the actual TM throttle controller, instead of the virtual one created by Target have you?

You shouldn't, as you should know by now that it only serves to make you miserable.

That is currently being addressed, so i wouldn't worry about it not being on the list.

Do you have the sychronise controls check box set. Can't remember its exact name, but with that set, the module applies all of your controller switch settings to their corresponding in-cockpit control. If not, the aircraft will adopt all of the default control settings.

ah, then maybe search for another, unwanted mapping, to a switch that you leave in the same position. If RDR ALT or maybe toggle has been mapped, by the update process, to another one of your switches, then maybe that might explain why it won't move from that setting.

The 2-way switches on the WH throttle will not work for functions like the one you describe, unless you amend the lua code to add the 2-way functionality. For example, to use the RDR ALTM switch on the throttle to switch between BARO(NORM) and RDR(DIS) you would need to amend the lua code first, to provide a mapping for the button (switch 25) being on and another for that button being off. As you have previously had this working, it looks like you might have applied such an amendment in the past, but an update has reverted to the default lua file and therefore overwritten your changes. Maybe keep the amendments safe, in another file, so that you can copy paste them back in again, after each DCS update?

Out of interest, do you bother entering the target coordinates or do you just designate the waypoint as the target and use the "laser search" function on the hud, when flying towards that target? I fly in VR, so the former was a bit of a challenge, but i've now downloaded a text copy mod, so will probably try it again, to check it out.

Did you retune the radio to Finger's frequency, 144.000 IIRC? If so, i wonder if it might be that opening the JTACs up together might lead to some conflict. I had a similar experience the first time i ran the mission, thinking that it might save time to open them both up together, on different radios. I restarted the mission and waited until warrior told me there were no more targets before checking in with finger.

As for 1, there are a few things that need to be set up, before you can use countermeasures, so maybe check that you have all of that in place. It is going to be virtually impossible to get to where you can photograph Gori otherwise. Some things to check are:- Master Arm must be on The 3-position dispenser switch is not in the off position. if you want to use countermeasure programs, probably just chaff for this mission, then select the centre position and if you want to manually deploy the chaff, then set it to the top, bypass, position. So that you know when to throw out the chaff, make sure you have the AN/ALR-67 RWR switched on, and the EW display on one of your top 2 screens. You might also want to switch on ECM The latter 3 controls are behind the joystick, so you might want to hide that, and maybe the pilot body, to make them more accessible if using clickable controls.

That was a good read. Thanks for sharing.

Try saying "Chatter Toggle" or mapping chatter to an unused PTT button. You can also set chatter to autostart and link it to aircraft power in the EX tab of the Vaicom config window

https://youtu.be/Xso1mMo_1Mg, an excellent video by @Lex Talionis, will be worth watching, for a suggestion as to how to practise the on-speed base turn. It helped me enormously.

When I first got Vaicom, I went through all of the city names and added them, along with my, probably wrong, pronunciations of them, to the Windows Speech recognition dictionary. One example being Kutaisi, which i pronounce as "Cut-a-zee" rather than the "Cut-I-zee" which i suspect it should really be.

If you haven't already got it, maybe try Bankler's Case 1 recovery trainer, https://forums.eagle.ru/showthread.php?t=221412. It'll keep you occupied for hours and provides very useful feedback, inflight and via a summary at the end, on the various stages of the recovery.

Your settings are very similar to mine, with just a deadzone of 4 to help avoid my clumsiness accidentally selecting pitch, when i want roll and vice versa. the curves on the joystick are exactly the same, at 15, and i have a TM Wartog HOTAS. I've just been doing some AAR and it wasn't perfect, but i got it done with only a handful of disconnects. i hate to say it, but it doesn't look like it's your axes that are causing your issues. Practice, Practice, Practice might be the only solution. Perhaps concentrate on making only very minor adjustments to pitch and roll, as large adjustments will usually only have to be mainly reversed, probably causing the issues you are experiencing. The curves are to accommodate the fact that the joystick in a real F18 is probably longer than your controller's joystick, so to get to full deflection it would need to be moved further from its central position. The shallower bit of the curve therefore serves to make your shorter joystick behave more like the real thing. It will still give the maximum reading when you get to the outer limits of the movement, but its movements closer to the centre position will not generate as high values as it would do with a linear "curve". It is easy to see, by moving your joystick whilst in the axis tune window for one of the pitch/roll axes. If you have a WH HOTAS, the settings we almost share, must be pretty close, as i am sure that they are the ones that Wags suggested for that with the F18

https://forums.eagle.ru/showpost.php?p=4288414&postcount=290 was the post to which i think you are referring and if it is, then what she actually says is that they will consider releasing a single player version and not that they will actually release a single player version, after 2 weeks. From https://forums.eagle.ru/showpost.php?p=4288649&postcount=343, which appears to be another post that you might have also have misread or forgotten, it would appear that someone had already clarified this for you. From the tone of your OP, which you might also want to re-read/re-word, it would appear that you are trying to prepare the ground to accuse Kate/ED of breaking a promise that was never made. It may be that you genuinely forgot about the content of the two linked posts, but either way, it might be better to check the facts before making such posts in the future and perhaps avoid other members calling you out on it.

If said newbie has only one axis on their throttle, I'd have to agree. :)