Talonx1

It will work with dcs if you save the file in .txt format in tacview. Wire number is estimate and very inaccurate and I’ve found approach paths to be a little wonky. As mentioned it wasnt designed with dcs in mind.

Incorrect. When bug is present radios will not work even with volumes turned up. Ppl with this issue are fully aware of the need to turn knobs up to turn radio on. (At least the ones I’ve spoken to)

Using trackIR? If so sitting back a bit while recentering the trackIR. Default is f12 I believe.

Turn up tacan volume (left hand side, towards the rear) and tacan data will display properly. Once its up you can turn it back down again if you wish.

All you do is turn volume knobs clockwise (up).

Are you talking single player or were you on a server?

You can skip the fire tests and as a result the bleed air cycle as well to shorten it up a bit more.

Bug is not from that. I had the same problem and no amount of time on the enter button could fix it. The freq doesnt blink and become solid it flashes once and returns to previous freq. I assure you he’s tried holding ent down. For me the setting did the same thing (intermitent) and the AM:FM selection blinked back and forth on its own. On my end problem went away after unmapping comm volume controls from rotary knobs. He doesnt even have them mapped. Same problem for many people and different things end up fixing it. There’s some broken code in there somewhere getting triggered by different issues. Even hopping out of one jet on a server and into another one often lead to a change in symtoms.

Let me rephrase that “trying to help the original poster,” which includes making sure he/she has accurate information.

Above you say that you are starting to hold trim as soon as you start your break. Is that correct? If so what speed are you starting your break? If youre at 350kts as typically prescribed then you cant possible be gear down and full flaps when you start applying trim as the gear and flaps wont drop till 250. No need to get defensive either. Just trying to help.

Holding trim hat for 12 seconds just makes no sense if flaps are at full and gear is down. If it takes that long something is wrong. Most likely flaps arent set to full.

When I pass the boat at 350 kts and 800 ft I extend out to 1-1.5 nm. I then cut throttle to idle, deploy speed brake and gently roll into a 2 g turn. I keep the brake out till 300 kts then pull it in and wait for 250kts to deploy full flaps and gear. Once gear and flaps are down it takes 2-3 seconds of pitch trim (while still in the turn) and I end up wings level around @ 150-160 knots, 1.1-1.3 nm from boat on the beam and roughly trimmed up for on speed aoa. Then its just a matter of making minor trim adjustments and flying thrust for altitude till the final turn. Once trimmed for on speed aoa you really shouldnt be using stick for pitch at all. It will massively exaggerate effects on your aoa. Highly recommend turning on the control input display so you can see your trim adjustments, how fast its adjusting and roughly where it needs to be for on speed aoa flight. You can also throw your fcs display up on a ddi and watch your stab trim numbers if you want more realism.

With full flaps and gear down it should only take 2-3 seconds of holding the trim hat to reach proper on speed aoa trim. Trim responds differently depending on configuration. With flaps and gear down 12 seconds would be more than enough time to completely max out trim.

Just as an update, I removed the keybinds I had setup for comm volume controls and reloaded and the problem has vanished. I was previously using 2 knobs on my hotas to control volume. Now I have nothing assigned to them and have no problem. Others with the same problem that already dont have anything bound to those volume controls still have the problem though.

You mentioned that you turn up the volume, what level do they start at when you load up? For me disabling my controller mapping of the volume knobs and just not touching them at all solved the problem. For me (now with controller mapping disabled) they start at about 75%. Maybe try loading up and not touching those if you dont have to. Edit: Well I dont know. I tried loading up a server and adjusted the volume before trying to set channels and it still worked. I have no idea why I had the same problem and it went away after removing keybinds to the volume controls and even though you dont have any keybinds you're experiencing the same thing. Out of ideas other than maybe add something as a keybind then remove it. Maybe something in the keybinds is corrupted and needs to be overwritten. Edit: Also forgot to mention I dont even bother switching to M channel any more. It will program over whatever channel is currently selected anyway. Just tried programming them to M channel though and had no problems.

Have only had it not work at all once. That was on a MP server just a few minutes before the cv despawned. (May have been damaged as well)

Debatable whether or not its been "fixed." Guess we'll see whenever the next update comes out. Which is hopefully soon because my radio is pretty much useless.

https://forums.eagle.ru/showthread.php?t=213659

Ppl have produced custom textures for the carrier deck. It would be nice if someone added a custom texture with some visual cues for lineup. Realistic? No, but neither is liking up a jet by yourself without any help from deck crew.

Hoping you're correct. There was a "fix" for comm channels in a recent patch so just afraid someone assumed this was that and that it was already taken care of.

NOT FIXED, not sure why this post was marked fixed. This video was made about 30 minutes ago on the current build. Unless by fixed you mean it WILL be in the next upcoming build?

confirm same, after last update I no longer get the 3 digit identifier in hud or mfd. I still get a bearing and distance but no ID or time to go.

Specifically, 1. AM/FM selector flicking back and forth on its own after its been pressed once. Any time it changes on its own it interrupts any attempt at inputting a frequency. Some times pressing a different UFC selection button makes it stop, sometimes it doesn't. Sometimes changing to a different preset and back again makes it stop. 2. Manual frequency input not working sometimes. Was supposedly fixed in a recent patch but I went from it working fine to working sporadically as a result of that patch. In the attached video it only fails to accept the input a couple of times but sometimes I can sit there for half an hour and it will never work. 3. Once a manual frequency IS accepted it takes over every pre-set channel. As I change to presets it briefly shows the preset then switches to display the manual channel. Probably a few other things I'm forgetting but video is attached. I recorded from cold start to include everything up to that point that I did. Jump to time 2:10 to go straight to comm controls. In the video... (The cursor didnt record so I'll explain a few things as they happen) -Aware that at first I try to program a freq to channel 1 on comm one which obviously doesnt work. I meant to pull the comm 2 knob before input but it didnt take. You cant see the cursor but you can see the tool tip show up over the comm 2 knob just before I input the number. -I then input a manual freq on comm 2 which works and hit the AM/FM button. You can see it starts changing back and forth and if I attempt to go to comm 1 it reverts back to comm 2. -I then press GRCV (3:39) and AM/FM stops flicking back and forth and I'm able to change to comm 1. -I'm then able to program a channel to manual on comm 1 and even press the AM/FM button a couple of times without it getting possessed. -I then go back to comm 2 and the AM/FM button is going wacky again. I try hitting other UFC select buttons but nothing works this time until I change to a preset that has a blank field for AM/FM (4:42) then when I go back to M the AM/FM selection has stabilized until I hit UFC Selection 4 again then it once again starts flicking back and forth. -I switch through channels and back again and it stops which is when I then notice that the manual freq is showing up for every preset. -I then change the manual freq just to see if it then puts that freq over all the other channels and it does. Just to be clear this is just an example. Each time I load it may behave slightly differently. In this video for example I'm able to program freq's successfully but other times it wont work at all. Sometimes pressing a different UFC selection will stop the AM/FM flickering every time and sometimes it wont. Often times even though I have the proper frequency programmed I still cannot contact the tower (grayed out comms selections and no response.) Sometimes it will work if the freq is programmed into comm 2 but not in comm 1 and it makes no difference whether I initiate the comms with the hotkey for comm 1 or comm 2. Sometimes the tower will respond on the first try and sometimes I can try 10 times even when it's lit up (not greyed out) and it wont work till the 10th try and sometimes never. Comms in general are extremely erratic. Edit: Forgot to mention, DCS is up to date, I've tried performing a repair and I've tried removing the f-18 module and reinstalling it again. High res still processing, HD should be available shortly.

Settings maxed. All of the gulf seems green. I can see the desire to have it green at shallower depths but the scale should be reduced so that it has to be significantly more shallow to be green. Maybe the depth maps lack sufficient detail?

I’ve never had to touch trim other than during carrier approach and trimmin for on speed aoa. The only time I have thought I needed to it was my joystick. Easily proven by adding a small dead zone and the plane was no longer leaving level flight.