Talonx1

I have the new version. All the wires inside the throttle are very neat and tidy and theyve even put a magnet on them to try to reduce the interference problem. It still happens though. I’m not aware of any additional functions over the older model but I didnt have one so cant say for sure without looking it up. The first thing I tried is hooking up to a powered usb hub as is often touted as solving the ghost input issues but it didnt help. Putting distance between cables did. (Did a quick search, I believe the only change in controls was between the older (mil themed) x-55 and the (blue) x-56. There is no difference in controls between the grey (new logitech) and blue (old saitek) x56. They just altered the type of plastic used and improved the work quality (wiring and tolerances.) That and perhaps the ROM to make it compatible with logitech software. It still requires its own software though and doesnt work with logitechs software for mice, keyboard etc. )

As I said, there are multiple reported causes. It has been completely resolved for me (so far) by rerouting and keeping the cables clear.

Recently another thread on this that was moved out of bug section. A quick net search reveals common problems with x55/56 errant key commands due to a couple different issues. In some cases its reported as being due to underpower. Solved by using a powered usb hub. In others cases its due to cross cable interference. I had the latter. I was able to solve the problem by rerouting the joystick cables to keep them further away from cables from other devices like my trackir, headphones etc. (Wasnt moved, just marked as “cant reproduce.” Its a hardware issue not a dcs/hornet issue and is reported in other forums like elite dangerous. But then again you never suggested it was, just sharing :) )

I rely largly on the HSI for when to make my turn. Tacan boxed and watch for the ships tacan icon to pass about 10 deg past abeam and start my turn. Recommend starting with about 10 deg past beam then increase as needed. You dont want to go too far or you’ll end up too long in the groove and off glideslope and dont want to start as soon as youre abeam on hsi or you’ll be turning before you actually pass the round down and end up high and not enough time to lineup. I find the display more consistent than trying to eyeball it. You should also do an eye check and compare it to what you see on the hsi because you never know when youre gonna have to do it without tacan or some other problem.

As mentioned, the flat break isnt based on break angle its based on speed and G. Common practice is to pull G that equals 10% of your speed. I.e 300 kts = 3 G. I prefer to hit the airbrake, drop throttle and pull a steady 1.8-2G, letting off the brake and dropping gear and flaps as soon as I hit 250kts. Then apply some pitch trim while still in the turn and level off at or near on speed AoA for the down wind and fine tune trim and altitude as necessary. The final turn is angle based and works because you are (should be) on speed AoA. Also as mentioned there is no 20 deg mark and keep in mind that on the final turn 30 degrees is a guide. It will vary slightly based on wind speed, weight and drag so by the as you hit the 90 deg point on that turn you need to be ready to adjust bank angle to anjust the turn rate and hit your mark on the ball call.

Trim works very quickly once flaps are at full and gear is down. If you are not in proper landing configuration then trim is less sensitive because the FCS automatically takes care of pitch trim.

Dont know how real it is but have also found that I’ve taken hits, sometimes with apparent system/flight control damage and sometimes not but dont get any kind of audio feedback to know anything has happened. In one fight I took damage while at slow speed high aoa and went into a spin, thought I was still in control and had no idea what happened. Spent the next 30 seconds or minute trying to recover only to findout when viewing the acmi that I was hit my a missile and immediately listed as destroyed the entire time. Another time took gun rounds to the cockpit and my plane just continued on in a turn till it ran out of fuel. Again not so much as a clunkclunk sounds as cannon rounds pelted my plane.

Bug, turn tacan off and on again and it will return to tracking properly.

Release or beta? Are you over turning when using nws hi? If you do the wheel will crank over too far and it will push forward sliding the wheel instead of turning. Think of trying to ride a bicycle and cranking the handlebars all the way over suddenly. And are you sure you sure you are following hookup procedure properly? Extending launch bar thempressing “u” to hookup? I’ve never had a single problem hooking up on or offline that wasnt because I was out of position. I’ve only ever had a launch problem one time when the blast shield was up but cat didnt launch. I’ve seen bouncing planes but its ussually online and happens when trying to land on field after trapping and relaunching from carrier.

Its not blowing into your canopy at 6kts. Its blowing at 6 kts plus ships speed. :smartass:

Just seems odd that others dont see it. 13 kts online or offline?

I believe it was working fine below 20kts to begin with? No idea if its in or not. I think the cv on our server (at least one of them) is running under 20kts anyway and I havent been having any problems. What I dont get is if it causing so many problems why not just slow down your carriers? Sure it still needs to be addressed if it hasnt already but why should anyone be running 27 kt carriers anyway? All you need is like 25 kts total wod right? Set speed to 19 and winds at 6 and done. 6 kts is hardly gale force. If thats too much wind for you to handle you should probably practice a little more.

He didnt. Overzealos mods moved his post here from general.

Only time I’ve seen slippage since patch was during latency spikes. Bound to happen at times when you get a little lag and dont think at that extent it will ever be possible to completely get rid if it. You have an object moving and sending its position to server parked on top of an object moving on the server. Any little discrepency in timing/position data and its gonna “slide” no matter how sticky the tires are.

Ath the base of the right hand side of the front console you’ll find the radar altimiter dial where you set your low altitude warning. Rotate the knob to move the bug and then the radar altimeter will work when you select it on the front panel.

Most commonly (for me) it comes from whatever is assigned to the 3 toggle switches across the bottom of the throttle. Its stopped doing it now for the most part but had my hook drop on its own once again tonight. First time in days its done it. In any case (imo) its pretty safe to say its a control issue and not a hornet or dcs bug.

I drop gear and flaps at the same time as soon as I hit 250 kts. Do it during the turn and you dont notice a pitch reaction so much.

Had similar problems with x56. Throttle was sending random signals. I rerouted the wires for the hotas keeping them away from other things hooked up to usb and it went away. The x55/56 seems extremely vulnerable to cross cable interference. This wasnt something I take credit for finding. A thorough web search returned lots of people with the same problem.

Latest update broke Simple radio for open beta build. There's a .lua file available to fix it (only for open beta build) so if you're using SRS you'll need that sorted before you can use it.

Setup a short intercept against a couple migs to practice with the aim-7 and simple intercepts in general. Sometimes (most of the time) I get a sort of generic range ring. Nothing counts down, there seems to be a max/min range mark but not the proper rmax, rmin, no escape marks that should be there. It almost looks like a place holder graphic imo. It was staying till I got within 10km then it would change to the proper range ring. (EDIT: Dont think its a bug, need to pay more attention to the ranges at which it happens but I think its just a different ring you get at longer ranges that I havent been able to find any documentation for. As for the spinning range marker on the 9'ms I'll have to watch for that again as well as the incorrect heading arrow and will try to save the track next time I see it.)

Have been experiencing similar. In a2a engagement against AI there is sometimes no range ring indicator for the aim 7 and last time I had it happen when I switched to 9m’s the indicator was just spinning round and round. I’ll try to remember a track file next time it happens.

/ works for general comms on the ground. Once you are airborne you have to use the radio ptt buttons (whatever they are mapped too) for comm 1 and comm 2.

So I guess this isnt considered a hornet problem? Mods need some PR training.

Dont know if this is a gulf map issue or a hornet issue, maybe to do with the canopy rendering. Over water and higher than around 10k ft I get a line across the middle of my screen. Above it the water renders darker and below it lighter. It's only visible in front of water. Have tried various resolutions and visual settings and its always there. Quality isnt great, most easily seen in full screen.

With a curve of 25 you should be getting very fine movements in close but once you approach 25-30% its gonna pick up really fast and be hard to make medium throw movements. It sounds way too high to me. Any time you have a nonlinear response the output from your stick is gonna increase over distance and it can be very hard to predict especially in situations where you may need to make sudden changes of direction. A slight over movement can have much more dramatic repurcussions than if you are using linear inputs. That said it can be hard to make the kind of fine adjustments necessary for AA refueling and close formation flying if you dont desensitize the center a little. For me, I like to keep things as close to linear as possible to maintain natural response and predictability so I wont fly with anything more than 5-10 on curve. I think 5 is what I’ve finally settled on. Same for throttle. I’m using a curve of 5 now to sacrifice a little precision at min and max in order to achieve a little more precise control in the midrange for landings, fueling and formation flying. For my flight stick curve one thing I did was do snap rolls. Try to roll as quickly as possible 90 deg. and try to stop it perfectly. With a big curve getting a feel for controlling the roll is much harder than if its linear. So I experiemented with small amounts till I found a setting that maintained a satisfactory level of rapid control while improving low level precision.