SgtPappy

I have been trying to practice missile kinetics by setting up a neutral, coalt merge with my F-4 vs a MiG-21. Even if I set the MiG-21 to avoid reacting to threats, even if I carry no weapons, it will 100% just break turn left while popping flares (even if I equip it with no flares AND tell it to not dispense any!) I have not found a workaround to this. It simply will not engage until past the merge. I will test other aircraft combinations when I find time.

I did try twice, it had no effect

I did try that once and could not find the file! It seems it gets deleted and at some point the updater tries to find it again or something. I'm not sure. Either way, there were several files that could not be found, this was just the first in a chain so I decided to reinstall. I have always had DCS as an exception, so unfortunately this did not work either. I fresh reinstall ended up doing the trick.

I did not quarantine any files and have only been using windows defender. I'll try to see if there's a Windows update that I'm missing since all other updates have run fine until now. EDIT: Updating windows and installing optional drivers did not work. Fully shut off PC several times. Will try reinstalling.

I tried repairing, then downloading. I tried multiple restarts. It takes me 9.5 hours to download this patch and I've been met with this twice now. I made sure to uninstall all mods and even liveries after repairing and then trying another update. I'll be trying a fresh install next, but is there anything that can be done about this? autoupdate_log2.txt

Not sure if this one is a bug related to the F-4, DCS or if it's by design. I would like to know how other people have been experiencing blackouts in the F-4, or even in general. In my video below, you'll notice that as the greying out starts to get a bit more intense, I suddenly black out (you'll hear the "thunk" of the FFB stick as the motors turn off). This is the very first time I've blacked out in the F-4 and it seemed very sudden as I am used to the older blackout visuals which really make almost the whole screen black before your virtual pilot loses consciousness. I am curious if this is the same amount of grey out others have experienced before blackout. If pilot fatigue is modeled here, is it also modeled in other jets based on your experiences? For context, I was turn fighting a few minutes before this point and was also flying up high for a few minutes so it isn't a G-warmup or oxygen problem.

Thank you! No rush though. I'll be doing some research too and forward you what I learn. Then I'll be away on vacation in October so I'll probably make the livery itself when im back.

If you don't mind, then yes please! Send me a PM if you want to discuss more. I prefer to have a slatted F-4E that he got some kills in during the YKW. It seems that the one you made (very well done model btw!) has no slats and maybe the art I have of it is incorrect or post-YKW.

Probably this one, but it depends what I find the most reference material for. If you have some, let me know. https://www.aviationgraphic.com/aviation-lithographs/2145-f-4e-kurnass-184-iaf-107-tayeset-jp-1735.html

At some point I hope to make a Karpada and/or Yiftach Spector's slatted F-4E since he flew slatted F-4E's without TISEO, just like what we have now.

I'll be sure to record it if it happens in SP. Or maybe even a small MP session with just me and my friends could be useful.

Has anyone experienced incorrect/corrupt sounds or sounds looping at odd times? I think I've had these on 3 separate occasions but have never found what triggers these kinds of bugs. Each video has different sounds looping and none of them could be solved by resetting Jester. For the first video, the sound starts quite but gets progressively louder over the 5 mins. Just fast forward near the end to hear it at the max volume. For the last video, there's a bonus bug - despite getting the radar damaged in combat, it comes back on when I land.

I'm starting to think that DCS itself is the issue since it's only MP, but I'll look into it. I've also noticed the voice commands sometimes "chop" and only in MP. Thanks!

@Zabuzard sorry to harp on this again but for sure this time, there seems to be a problem. I cannot reproduce it offline, I'll keep trying, but online Jester is seemingly just "focusing" over and over again. I have also used the long button press instead of voice attack to reduce the variables but he often refuses to lock. He just keeps "focusing" on my guy. In the video you'll hear me command via voice attack (which is supposed to translate the voice command to a 0.4 sec press on the Jester context button) and then I try it 2 more times. I try the long button press on my HOTAS one last time to which he says "Focusing on your guy" again. I immediately then try - and fail - to lock the bandit myself. Note that when I try to long press, I hold it for at least 0.5 seconds and he'll say "Focusing on your guy" before I even let go of the button. The next thing I will investigate is my controller itself. There's a chance that the button presses aren't registering well, although this doesn't explain why the voice command isn't working. Is anyone else having this problem?

Same. I get bad frames mainly when merging with anything in any aircraft. JOEM423, try emptying the fxo and metashaders2 folders in "saved games > DCS" after you load into a mission or server if you haven't tried already. My frames in general improved after I started doing this.

That's an interesting point, thank you for noticing. Now that I think about it, he says this sometimes but would lock other times. In the tracks, I use exactly the same voice command as in the videos where Voice Attack translates it into a button press of something like 0.4 seconds (i'm making up that number, I'd have to check when I'm home). He locks in the tracks but not in the videos so for sure I have the correct command bound. Do you think server latency, lag or dropped packets etc in conjunction with VA could have an effect on the button dwell time? I'll double check the VA bindings and see if perhaps it does not dwell on the button press for quite long enough to make the distinction. Perhaps I should ask VA to use 0.6 seconds to fight any of the aforementioned effects of MP servers.

I've been doing this from time to time as well, knowing that STT locks from beyond visual range are more of a rarity on this age of combat. That said, I would like to get proficient at both. The more I can put the bandit on the defensive from longer range the better. By the way, do you know if Jester puts the aspect switch to "nose" by default when you ask for boresight or go into cage? I've been asking him to do it everytime.

I decided to revisit this. The couple past sessions on the Cold War server, I've been flying high to get better contrast on the radar. Things go pretty well initially - Jester will see the contact and even I can see it easily on the repeater (yay!) at around 9 nm. He focuses on it and I tell him to lock it up via Voice Attack and he immediately confirms the request. 5 seconds pass as he changes some scope settings. 5 more seconds pass as the bandit gets closer. Perhaps another 5 seconds, and we've merged. See video below (sorry for the very quiet sound): The second time this happens (see below), you can see once again that Jester and I both have a clear view of the contact but after confirming my command, he does not lock instantly - 3 or 4 seconds pass until I decide to lock it with my own controls and then turn off Jester so he does not decide to take control and unlock it. It would be great if he reacted faster to this very easily-visible target. In the interim, can we have Jester not unlock a target unless we request him to? It can be a little frustrating to wait for him to lock something such that I need to lock the bandit myself and then not forget to turn him off in fear that he'll unlock while I'm guiding a missile. Finally, please see the attached tracks. I was unable to reproduce the very very long amount of time Jester takes to lock in the previous videos, but it does seem to take him longer when you ask him to lock while he is in his "focus" loop, and even longer when there is clutter around. I think that makes sense except for the fact that in the videos I posted, the target is extremely obvious with no clutter close enough to it to lock. IMO, Jester should have no problem locking this kind of constant near-instantly. Jester is way better than me at finding/seeing targets in clutter and his scans often find something which is great for an old radar that's not really meant to search. So I think Jester would be even better if this could be resolved or improved. Jester takes time to lock bandit 2.trk Jester takes time to lock bandit.trk

No, you would tell Jester to return to search. You can do this by double tapping the context button.

Being able to command boresight and aspect is way more immersive than commanding it all myself. Thanks for improving Jester bit by bit every patch. But this also made me notice it's hard to see targets with the 25 nm scale because of my crappy eyes lol. Can I request another thing in addition to the gain change with IFF check? It would be great to have Jester choose the 10 nm scale for boresight by default or maybe have the ability to ask him to set a range scale.

So does this imply we will never have the ability to be warned in the F-4 that we've been launched on by another aircraft's SARH missile (assuming that plane is using CW as opposed to HPRF like the F-15's STT shot)?

Well you truly learn something every day. Thanks for the language lesson

Ah I see at least one of you guys probably read the same book I did. Awesome news, super excited.

Pretty sure they're working on a 1973 Yom Kippur War set of missions/campaign that includes a few custom assets.

Ok I'll see if we can reproduce it in SP in the meantime.