arneh

As I came back to the ship on mission 14, another Tomcat crashed during landing as I was entering the pattern. I assume this was scripted? But there was no reaction to this event, and no update as to what to do next. The carrier was burning, so landing there seemed out of the question. But I had limited fuel left, and no tanker aircraft I knew about. So I was left wondering what should have happened next? Is there some trigger which failed, which should have reacted to the crash? Or was the crash not scripted, and it was just the DCS AI being stupid?

Works if I don't change my TACAN, then Jester will set his to the correct channel. That said, if I command Jester to through the Jester menu to set correct channel he does it, even if I have set mine in the front cockpit. Not used to have Jester set TACAN for me, so I always used to set it myself before takeoff, particularly at night, where I really need it Thanks, good to know if Jester start selecting wrong channel again.

I tried now to jump into the rear seat, just before launch, and after I lost my TACAN homing. It seems his TACAN is set to channel 59: Don't know if this is the right way to check though, or does me jumping into the rear seat change anything by itself? Or maybe me setting TACAN in front cockpit prevents him from changing his in some way?

Sure, but that's one turn, at a different speed. It's very hard to know how exeactly hard to pull later on when you need to make a max performance turn. Of course I learn after I while, but that was after getting several unsats first I don't think it's the hard bank which is hard, but the sudden very fast change of bank. I don't think they do it that fast in real life with a wingman this close. But I understand it's a limitation of DCS AI that you can't adjust how quickly they enter and exit turns. Sure you learn after a lot of trial and error, but could be good to get a bit more instruction during the briefing how to best achieve the correct distance. And to be clear I'm talking about the turn from spacer pass to downwind pass when doing the ground attack circuits. Of course I learn after a couple of unsats how hard I need to turn, and trying to guess if I was too close or too far away (it just says wrong distance, not if it was too close or too far). But just some constructive suggestion to add a bit more instructions for how best to achive the correct turn to put you the correct distance away so players don't have to go through so much trial and error to get it right.

No, I don't dare to use any mods anymore Is Jester able to override the TACAN station I set in the front seat? Because, as mentioned, it does work initially, when I set it myself.

My grades. Not all of them are from first time, I did refly some unsats I got for mostly over-G during the BFM. One of them ask you to do 6.5 G, but give you an unsat if you're even slightly above. That's brutally hard to do with the G-meter hidden down in the bottom of the cockpit, while trying to keep eyes on the bandit. Also struggled a bit the first time in the AG-missions to get correct distance to target on the downwind legs. Would help if the instructions gave some indication of how hard my turn needed to be to line me up the correct distance away (something like do a 60 degree 2G turn, or whatever is necessary). Took some attempts before I managed to get an acceptable distance. Oh, and following the AI in close parade formation when entering and exiting turns I just found incredibly hard, so my unsat from there stands.

In mission 10 (night CQ), I dial in the correct TACAN channel from the kneeboard before taking off, and I can see I have distance and bearing infomation. However, just before takeoff this dissapears, even if I still have the same correct channel tuned. What i figured out I needed to do was use the Jester menu to ask Jester to tune TACAN to the carrier channel, then I got it back. Is something causing Jester to retune TACAN just before takeoff, which overrides the channel I have selected? And he tunes the wrong channel?

Tried mission 8 now, and encountered a couple of problems. 1) Almost as soon as I reached the target area, my wingman reported bingo fuel, RTB, soon followed by ejecting. 2) Warrior gave me the target rundown, and was told to press spacebar to get attack briefing. But upon doing so warrior didn't say anything more. I attacked the targets on my own, and upon all air defenses destroyed he finally talked again (confirming all targets destroyed and contact JTAC for bunkers). The bunker attach was unsuccessful, since I used two GBUs for the SA-9 and grouse earlier, and of the remaining two, one missed, and one had an "aborted" status and would not release. And since my wingman already ejected I had no usable high explosives remaining to complete the mission.

Same thing happened to me now.

Happened to me too

I ran into the same issue now, 8 months later. No reply from Warrior.

Ok, so my timing was off by a second. Interesting that the pedal damper makes a difference. But that is still very slow. Even when the damper is off, should it be that slow? Are the pilots unable to move the pedals faster than that in the real Hind?

Why would it be a feature that my joystick does not match the position of the in-game stick? Is there a huge damper or something that prevents the pilot from moving the stick faster in the real aircraft? Most of the time it's not a big problem, but e.g. for auto-rotations in helicopters when you quickly need to dump collective and make big adjustments on the other controls for that, it gets to be a big obstacle if it can take up to 4 seconds for the controls to get where you want them to be...

I have an issue where some of the axis (mostly the primary controls) in game controls have much slower movement than my actual stick. It's only for some aircraft, mostly helicopters. Worst I've noticed is the Hind where for the pedals the ingame pedals needs about 4 seconds to move from full one side to full the other side. Here is a video which shows it in the Apache. First the controls settings which does show the speed the axis is actually moving, and then in the cockpit where you can see the much slower speed of the stick there. https://youtu.be/mNGojrpdJnk Also included a track file. For the aircraft I have tested these are the ones which have slow controls: AH-64, A-10CII, KA-50 III, Mi-24 These ones have responsive controls: UH-1, F-14, F-16, F-18, Su-25T, Viggen, T-51. slow-joystick.trk

I was testing out Multi threading in the latest open beta, but for me DCS freezes immediately upon entering the cockpit (with only partly loaded textures), and I eventually have to kill the process. It works fine in single thread mode. Other aircraft I have tried work fine in MT. A quick look through the log file revealed numerous of these, which I don't get in single thread: 2023-03-11 07:10:44.730 ERROR_ONCE DX11BACKEND (22592): texture 'zil135l_spec_fall' not found. Asked from '' 2023-03-11 07:11:42.399 ERROR_ONCE DX11BACKEND (9380): texture '.' not found. Asked from '' 2023-03-11 07:11:42.498 ERROR_ONCE DX11BACKEND (9380): texture 'mirrors' not found. Asked from '' 2023-03-11 07:11:42.605 ERROR_ONCE DX11BACKEND (9380): Can't load 'Fonts/font_general_RU.dds' in texture array ''. 2023-03-11 07:11:42.680 ERROR_ONCE DX11BACKEND (9380): texture 'mfd0' not found. Asked from '' 2023-03-11 07:11:42.680 ERROR_ONCE DX11BACKEND (9380): texture 'mfd1' not found. Asked from '' 2023-03-11 07:11:42.680 ERROR_ONCE DX11BACKEND (9380): texture 'mfd2' not found. Asked from '' 2023-03-11 07:11:42.680 ERROR_ONCE DX11BACKEND (9380): texture 'mfd4' not found. Asked from '' 2023-03-11 07:11:42.813 ERROR_ONCE DX11BACKEND (9380): texture 'mfd3' not found. Asked from '' 2023-03-11 07:11:42.814 ERROR_ONCE DX11BACKEND (9380): texture 'MFD_LCD_AH64_LEFT_PLT' not found. Asked from '' 2023-03-11 07:11:42.814 ERROR_ONCE DX11BACKEND (9380): texture 'MFD_LCD_AH64_RIGHT_PLT' not found. Asked from '' 2023-03-11 07:11:42.814 ERROR_ONCE DX11BACKEND (9380): texture 'MFD_LCD_AH64_LEFT_CPG' not found. Asked from '' 2023-03-11 07:11:42.814 ERROR_ONCE DX11BACKEND (9380): texture 'MFD_LCD_AH64_RIGHT_CPG' not found. Asked from '' 2023-03-11 07:11:42.957 ERROR_ONCE DX11BACKEND (9380): texture 'TEDAC_LCD_AH64' not found. Asked from '' Attached log files from loading the same mission in single and multithread. dcs-mt.log dcs-st.log