MrReynolds

************************************************************************ Too Long Won't Read: Throttle died - replaced within a week. ************************************************************************ I'm a typical forumite - quick to moan and complain but rather quiet on the positive. So let's be a bit positive for once! We all know the X-56 throttle is rather stiff. I guess mine's stiffer than most! Slowing down after entering the groove and .........POP - something snapped. I thought at first it was just the button holding the two halves of the throttle together but no. Shall we call it a rather catastrophic failure? No worries - I've got a Warthog throttle hanging around. I'll use that for now. Let's contact support. This was a Friday night. I PM'd LOGIRich, and then messaged Logitech. Over the weekend Rich had replied - offering to help out if possible. This was a relief as I'm sure we've all been on the long end of poor customer support. By Tuesday evening Logitech themselves had replied - saying the RMA had been okay'd. Friday evening - Boom. I've missed the UPS delivery but all's well. Just picked it up and everything's up and running. EVEN GOT A COMPLETE SET REPLACEMENT....not just the throttle. So. Thoughts on the X-56 after going back to Warthog for a week: - Jeez the plastic is SO poor compared to the Warthog. Honestly. Logitech make a premium product and I'll buy it. - Oooh, the warthog throttle action is so smooth (refueling was 100x easier) - Ah....the mode switch is better on the Warthog (a thumb button as opposed to having to flick the switch on the box. Yeah, first World problems)! - The switches are switches, not buttons + mmmmmmm. I miss the rotaries. +mmmmmmmmmm actually I prefer the layout of the X-56! (I still use the Warthog for elite - the middle nipple as opposed to thumb seems better for lateral thrusters) Back to being sensible! + The cursor stick is WAY more responsive on the X-56 + The programming software, although not as good as I would like, saves your key commands. Being able to press the button on the stick which takes you to the command and then being able to choose from a list is rather good. I still haven't remembered the warthog button names. I used and loved Foxxy back in the day, but TARGET is pretty basic and I never did bother learning scripting. - Talking about programs, sequences work better with TARGET. On the whole - I would take the 56's throttle. Warthog vs X-56 system? Depends if you're willing to save those "few" more pennies. Probably Warthog for the materials and smoothness. The new throttle is still REALLY stiff. REALLY. Yep. Really. Yes I've dialled the tightness up and down. I thought maybe the one that went Badda Boom was a particularly stiff bugger. Nope. The new one is just as stiff. So. Anyone perusing the forums I can vouch thoroughly for Logitech's support. Bravo to them and thanks. :joystick:

Well here's a good one. I had this same issue - the "c" not working to uncage. Believe me, I've done everything right. Added an extra bind: Shift+c and ...... everything works fine. C pops up in the command list (key press or joystick press). Just doesn't work in game. The only thing for me is that I'm currently running a hybrid system of Wathog throttle and x56 stick (don't ask, pictures to come if and when I don't get support fgrom Logitech) so there could be some kind of ghost conflict.

How long's a piece of string? How long is early access? I too am growing imaptient with the slow progress. We know it's early access, but it's been almost a year now since "release" and still no targeting pod. Forget about A-G radar in the foreseeable!

Thanks for the help, but no joy. Stationary artillary as well as other "test subjects". Same mission: AGM65E = GOOD. Ordered Mavs and gave reference and laser spot. AGM65F = Cannon only. As I said same mission - just a loadout change between saves so it "can't" be the JTAC coding....

Thanks for the input. @work, but pretty sure I've tried all variables for these. Will try when I get home and feed back.

Right. I know I'm doing just one little thing wrong, but I can't get JTAC to issue an attack with '65 command. JTAC WILL give coords if carrying bombs. If I have cannon it'll also tell me to attack with that. If I'm carrying AGM 65 only (and no cannon rounds) it'll just tell me to leave the area becasue the job's done! Any ideas what I could be doing wrong? The JTAC script is fine for other weapons - just AGM-65s. Thanks, Mr R. EDIT: He'll order up AGM-65E with the laser, so it's the infra red mavs I'm having issues with at the moment.... EDIT 2: With MK82s it's a no go as well. CBUs get asked for however.

I've just spent 2 hours with AFAC - and I think with the Hornet, JTAC doesn't like Mavs or even dumb bombs. I'm not there yet, but if I have CBUs I get asked to use them or guns. Take ammo from the guns and use MAV or Mk82s I just get sent away by the JTAC........ TOTALY weird and took me ages as I had one JTAC mission working, and another with the same variables for the JTAC NOT working. Changed loadout and voila!! Hope you got this fixed - found the post whilst searching for any answers for me.

Another bug report. I AM changing loadouts, and adding more SAMs to the missions. Probably what's causing the troubles.

Give me the flight path tracker for carrier landing like the f14 and I'll take it :-) Oh, and really detailed comms. Thanks :-)

IGNORE: Think something got corrupted. All's cool now. Kept logs "just in case"..... Crash report: pre-error?

Thanks for the help. Already done the pinky setting in DCS thanks. I have 3 settings: up = landing, middle = A-A/nav, lower = A-G. Everything is fine for single keystrokes, but if I have a macro programmed in the software when I use the pinky modifier in DCS obviously the joystick runs the macro so it's a no-go until the newer software's released. Thanks anyway :thumbup:

As always MUCH appreciated. This must be one hell of a labour of love for you :-) THANKS. EDIT: Great job by the way ;-)

More columns in LOGIRich my good fellow. I'm using the Logitech software for macros etc. BUT - I only have 3 columns to program (1 for each switch position) Can you ask the programmers to add the functionality to create more columns (I'm thinking pinky switch integration here). I think an old version of the software had the option to add columns - and a developer somewhere replied to me asking WHY I would want more. There you are, 3 switches, and a pinky + switch would be useful. At present in DCS if I have a macro used I can't then use that button in game as a separate one. Thanks, MrR.

Coolio. Many thanks :-)

Having a blast with this - so many thanks to you. However, this is my second play through and each time I get to a certain point I get this error: It's only on a base attack, and I've already taken a few bases in the campaign. Have tried a different variety of planes / variables. ******* With further looking, attacking with ARMOUR from Sukhumi TO Gudauta gives the crash. NO armour = fine. Attacking from Senaki to Kobuleti is fine - with or without armour. https://photos.app.goo.gl/6jc8nnPhxJ39eKkP6 Bizare, and keep up the good work. Oh yeah, a plus one. In an update soon how easy would it be to reverse the campaigns? Have the West start in the top left for example.

Pah! Sorry indeed. Thanks for keeping things going :-)

I agree we're slowly getting there. My dream scenario: Fight through a flight of Migs Clear longer range SAMs with MAVs using coordinates given to us by JTAC Use the HMD to mark a short range SAM launch position and pass to an auto bombing solution whilst another flight swoop in and take out the enemy base. Get an emergency JTAC call about TIC and take THOSE buggers out too! Land back at the carrier using ICLS and have tea and biscuits! Oh. And ALL in a dynamic campaign....... Give it another 2 weeks :music_whistling:

I was going to add that bit - but thought I would be greedy asking for TWO new things :pilotfly:

Okay - can't resist. The "Fleet Defender" has her targeting pod. When are we getting ours?? :( Just want my JTAC fix of entering coordinates, using the pod to hand off to MAVs then BOOM!

Sorry to be a pleb, but I can't get this working. I DID....... Now it doesn't and I can't remember how I installed it! Very frustratuing with the FA-18 and not being able to plug in coordinates. Any install guide would be peechy. Thanks.

Ah. Just about to post this as I need to delete a load of templates that I no longer want! Thanks.

Lancerr - I'm finding I'm taking a good 5-10 minutes per mission in the editor tweaking. CAS is one of the missions I add an "engage targets" enroute task. But - rather do that to these missions than have to make my own!! (not a moan) ;-)

Any news on these bad boys? Loved using them in the A-10 by marking various threats and rippling off Mavs using a macro (yes - very unrealistic)! Without the targeting pod how does the Hornet do this? (lol - I bet there's a 15 point procedure there)! HUD cursor then set mark point? Mav sensor? Helmet site would be TOP BANANA! Then of course in 2 weeks time when we get the A-G radar...... On a side note I enjoyed playing "dumb" Wild Weasel yesterday where I programmed an AI bombing flight to track near a SAM site for me to visually acquire the launch and take out with the maverick. Rest assured no pilots or equipment were harmed in planning of the run :thumbup:

Viper pilot. Just bought. Thanks

shdwp my good fellow. SO many thanks for this. I'm one of those that keep banging on about Falcon 4's campaign and DCSs lack of one. This is making life so much more fun for me. Now, a REALLY cheaky request. Is there a way you could possibly expand the missions to include 3 or 4 missions in one? Maybe programming each mission for a given airbase, or having each airbase spawning a mission. I'm loading up each mission and adding more and more features before I fly. Keep up the good work dude, really appreciate it :-)