Zabuzard

Can you check your mission debrief log? Would be interesting to see how many failures you got, even if your wing is still attached. A track file would indeed be very helpful

Ive put it on the list, cheers. In the meantime, you can quickly hop in the backseat or disable Jester and then lock the return yourself, then reactivate Jester. He should be able to work with the track then.

Tracked issue, thanks

Potentially fixed with the upcoming patch, thanks. If not, please callback

It is definitely complaining about that a bunch of times in your log. Ultimately it crashed within DCS weapon code though. Hard to say what exactly caused it.

Oof, good spot. Fixed.

They are being worked on. Cant comment on when they will be done though. But rest assured, its in the backlog

Could you actually share one of the broken replays please? Then we can have a look and see whats going on

Fun fact, IRL the antenna stick itself isnt even spring-centered or similar. It stays where you put it to. Quite annoying IRL, as it had no deadzones.

Regarding target spotting, it might be worth mentioning that Jester is now, with the Phantom, following an algorithm dictacting his actual vision cone. If he is operating the radar, he is looking at the radar and not outside for example. Same when he needs to read his instruments and gauges to update his knowledge of the aircraft state, such as reading current airspeed. He will of course interrupt that every now and then to also look outside, but if you ask him for example to lock someone, he cannot at the same time spot someone outside the cockpit... You can also easily G-lock him when you pull hard turns and then he cant do much at all momentarily while his head is being pressed into for example the radar boot. Like with real Phantom WSOs, his general preference where to look when looking outside is your six. So him not spotting a target in front of you can sometimes also simply be because he is currently looking behind, while it is your job to check the front aspect. In a similar way, you cant expect him to operate the radar and do a "regular search", moving the antenna around etc, while you are in a heated dogfight. His eyes will be outside the cockpit, watching your six instead. There are a lot of factors to consider and we certainly will improve him further. If you encounter any specific odd situation, please just hand in a working track. That allows us to spot whats going on, tell you what happened and use that to possibly improve Jester or even fix bugs

Are you looking at a Phantom AI or player controlled aircraft? Are you looking at someone elses Phantom or your own (but as WSO)?

Unlike in the Tomcat, where click-tasks will delay voice-tasks since he only has a single action queue and hence the issue is more severe, Jesters voice phrases in the Phantom are delivered within milliseconds, as he now has multiple independent action lanes and a better task scheduling system that also includes priorities. The reason you might still get "outdated information" is due to the length of the voice phrase itself. For example, if he sees a target at 1 o clock, he will decide within milliseconds and start talking for example "enemy fishbed at one oclock". At the time of him arriving at the "one oclock" in his sentence, the target might already be elsewhere. But it was there the moment he started talking that sentence. In the Tomcat this can be much severe, as click tasks and other things can block him from starting to talk, after already deciding on the sentence. We are of course planning to further improve this throughout the early access period to get rid of the issue entirely by splitting up sentences into the words and enabling him to dynamically choose some words, such as the exact target direction, at the moment this specific word will be spoken in the sentence.

No news since my last message on this topic yet. If something changes, you will see it in the changelog, cheers :)

Because most of them work differently and have a different set of features. Afaik there are modules that run into the same issue, just not many.

Yeah because if you have the FFB checkbox checked and have a FFB stick like you say, the aircraft thinks you are using FFB and will work differently. You should not have this checkbox checked if you are not actually using FFB. I understand the tricky situation, given that you swap sticks with the aircraft you fly. I dont see any easy way to "fix" your experience and there will be some other aircraft running into similar issues as well, not just the Phantom. Probably something that has to be tackled higher up by ED, perhaps by introducing setting-profiles.

The music folder contains the METEOR soundtracks in high quality. If you want to listen to it outside of DCS. Regarding song naming, the code doesnt care. It literally just takes any files in that directory in alphabetical order. As long as your song name matches the path defined in the sdef file, it should find it.

There are no plans for the earlier RWR, no. Afaik, historically, that would even be pre-DSCG (but don't quote me on that). The newer RWR can technically be installed in the housing of the older RWR, as the screen and knob both support the new interface and are compatible. We didn't intend to have this confusion though, it is classified as bug in the 3D model which will eventually be addressed.

If you don't like him, note that you can disable him completely. You can then operate both pits yourself if you want. Some users prefer doing that. The Phantom, and especially Jester will continue to be improved significantly throughout the Early Access period :)

You mean when you have the checkbox enabled despite not having an actual force feedback stick? If not, please elaborate, thanks.

Yes, it is meant to follow the setting in your DCS settings, but that currently doesnt work.

Looks good. If it doesnt work, export the music as OGG, not WAV :)

DCS, during startup, reads the folder where the sdefs for the TapePlayer are located in. The sdefs tell DCS where the corresponding sound file can be found (open one in a text editor and you see where it defines the path). Our code will load all sounds from that folder in alphabetical order, provided DCS found and supports them (use OGG, not WAV, not MP3,...). So you would open the directory with the TapePlayer SDEFs, copy one of the existing and rename it as you like. Then open it in a text editor and adjust the path in it accordingly. Then you would open the directory of the existing TapePlayer sound files and put your OGG file next to them, with the name you used in your SDEF. Just mimic how the existing sounds are setup. Restart DCS and you should now have 11 sounds instead of 10 on your player.

Are you sure you actually fully refueled them? It can take up to 10-15 minutes depending on the situation. Might want to share a track, then I can tell you the fuel state in all individual tanks directly :)

It is expected behavior that he turns on the radar after getting airborne. Otherwise you would be lost in a mission where your base is under attack for example. The reason he might turn it on during AAR is that you probably closed the refueling door - likely to reset it, in which case Jester thinks you are done with the AAR, so he turns the radar back on. It is difficult for Jester to understand whether you want to refuel or perhaps just escort a tanker (with radar engaged ofc), so his current set of conditions is very carefully chosen to make sure you don't end up in a situation without radar when you actually need it. Needs more fine tuning of course. The current radar on/off commands in the wheel are only momentarily and get overriden whenever Jester reaches a triggerpoint in his logic that would tell him to turn it on/off, hence you are seeing this behavior. It is planned to add a permanent radar on/off command for the case where you really want to go silent until you tell him otherwise. But this command is then supposed to turn off more than just the radar, also the jammer and similar emitting equipment.

They are just text files. You can create and edit them with Notepad or similar. The manual tells you where to put them and if you follow the link, it explains how to make them as well. I would suggest just copying one of the existing and simply editing the path/name of the sound file listed in it.