KungFu

Guys, this seems to be mission related, I created a new test mission and it works fine there however it does not on the missions i have that worked before the update and loading them up and saving them doesn't seem to fix it. So not sure what the deal is, something the new version no like in the mission I guess.

In my case neither the 7s or the 9s work properly, same issue.

If it is a bug, I would think it would be something related to something specific on our setup/systems because if it was widespread it would have been caught during testing and we'd see every hornet pilot reporting issues. The only mod I have on DCS is SRS, highly doubt that would cause this but being a systems engineer for 20 years I don't rule anything out.

Yeah I always clean out those before updating, but did again just to make sure and did a repair..... no change. Antennae elevation I have mapped to a 4 way hat switch and works as intended looks like Same behavior on several missions

Track file, excuse the sloppy cat lineup, not used to new behavior on deck. f18Radar.trk

Wanted to see if anyone else is getting this or if I'm doing something wrong (must be, because there is no way in the world this would make it through testing) before I put in a bug report: Locked up a target that was at my 12 co alt. Radar seems to lock fine, but the target designation on the HUD stays in one location, like at 8 o'clock. No amount of movement will bring it to center. Repeated this with several aircraft hostile and friendly.

A quick work around until it gets sorted is to add a txt file to your SRS directory with radio name and frequency as the content. For example I have this text file for use in the harrier: ARC-210 COM3.txt and the content is 257.80 This means you can communicate on 257.80 solely through SRS and not tune in the the jet so no AI calls are made. Of course if no human AWACS, you can tune in jet to get calls. I realize this kinda kills the radio immersion but my ADHD can't handle AI and human AWACS calls at the same time, especially some ya-hoo doing bogey dope calls every second.

With my warthog (stock, 1 year old) I have 0 dead zone, and it will register fine movement with just the slightest bit of pressure on a linear curve. I don't think I've ever done a calibration, it always been spot on. I think it is very important to have the proper mount for the stick for proper feel. I have mine on a obutto side mount and with no play in the mount itself. I've never used the default desk "plate" but I wonder if differing types of mounts induce a heavier hand due to ergonomics. Kinda of like Dooley says with the extension.

Anyone else getting complete freezes randomly on the server? When it happens I can go to the f10 map and then quickly back to cockpit and everything is good. However it's caused me to buy the farm a couple times last session. Never had this issue on this server until recently and I'm not seeing the issue on others or single player. One really odd thing is this happens over Kalba quite a bit, this time a freeze, quick f10 and then back....however Kalba was completely covered in water lol. Sounds like a graphics driver problem, but I've not updated it lately. (I've cleaned by cache with no change)

Yeah it's not a very fine trim, I find I have to adjust power to get a neutral FPM/VVI. I want to say it is like 6 or so trim presses per deg of trim. Whether or not it's like that in the real jet I couldn't tell ya.

I use DMT/JTAC/CCRP all the time. When the DMT finds the laser it slews to it and if you have GBUs selected / auto then you will see the CCRP fall line as soon as it picks up the laser. Easy peezy

I think some do not realize that you can pull up on the throttle and move it to shutoff position and it sends a button press. ( I know I didn't for about a month after getting it )

Not asking for ED to host/maintain servers, just that ED provide a stable MP experience for community run servers and their players by fixing their software.

I think it's worse after the latest hotfix for sure. Two of the servers I fly on are experiencing severe desync and crashes. These servers were stable before friday's hotfix.

What is the "official" freq for blue ground ops? Seems that 140 is now ATC in briefing, but banner says AFAC/JTAC is 140.

Those are designed for 2/3 position toggle switches where one position in a two position switch fires off a directx button press and the other sends nothing. Same with a 3 position, except the middle sends nothing and the two other positions each send a directx button press.

I have a Southern US accent and had to go through about 10 Windows voice recognition training sessions in order to get a reliable response. Each time you do it, it gets better. In a pain in the arse but worth it.

Or at minimum a setting on the kneeboard with WoW, kinda like what the mirage does for laser code.

I don't understand why these can't be put into the default lua. It doesn't seem like a huge amount of work to add them and it would be a huge help to non-technical folks. For us techie folks it's a simple copy/paste into the lua file after each update, easy but annoying.

Yeah, it does kinda throw a monkey wrench into it doing it this way. Me and Target do not get along and it's banned from use in my household. :music_whistling: That setting is for WOW for me, although a little bit of throttle with WOW isn't huge because it takes quite a bit more to move even slick f18

85% saturation on Y axis gets rid of the lower deadzone for me. Now how to figure out the curves to lessen the AB zone

Watch some of the good landing videos where the pilot is showing the control indicator in the bottom right, notice that the throttles never stop moving, sometimes from idle to full mil. I think 104 Maverick posted one recently. If you watch a real f18 pilot landing, you will see the same thing, throttles never stop moving. Personally, I wait till I'm a bit slower to drop flaps, because lower speeds reduce the rocket man response. Maybe go half for a bit then full. Not sure if it's the way the real plane behaves but for now it's what we have

I find it much much easier to control the speed in the harrier. And I believe it is partly because of this: That's the controls indication in the F18, see that the afterburner detent "area" is taking up about 20% of the usable throttle axis (in this case a warthog, but would be the same with any throttle.) Now imagine if your throttle is a lower resolution one, you lose 20% of your usable MIL power range, so the same movement with a non AB aircraft would more fine/precise edit: oh and you lose about 10% on the bottom end as well. (notice you can move the throttle quite a bit before the slider moves), so about 30% taken away from the MIL range for the 18 compared to harrier. I am working on some curves to reduce the effect, but just keep the above in mind.

In my experience so far, the engines will respond about 2 seconds after tiny throttle movements when properly on-speed, but if you deviate from on-speed with a high neg VSI (say in a turn that one does not compensate for with power beforehand), notice your speed increase. That increase is what makes you *think* that the engines are not responding quickly enough because you have to add even more throttle to bring it out of the dive, sometimes at full MIL. You can see the response easily by flying straight and level on-speed, move the throttle just a tiny bit and you will see it climb easily within 2 seconds.

Been awhile since I've been on the 104th with the baquette, but look on the radio (and I'm using the English cockpit so yours maybe different) for the PoL + G selection is what you are looking for I think: