Zabuzard

Already fixed internally [emoji106]

No, its unrelated. We are aware of the radar issues with the current update.

Thanks, this is happening occasionally since release but no one was able to pin it on a working (short SP) track.

Thanks for the investigation :)

Yeah. Thats because the ground cart isnt present in those LODs, a necessary performance optimization :)

AI or player aircraft? Does it also happen when you load the Spike fresh on the ground instead of spawning with it from the mission editor?

Yes, that is to be expected. It is because in Multicrew the Mavericks are simulated on the Pilots machine (same for the planes FM). While the TGP is simulated on the WSOs computer. The lag you experience is the time it takes for your command to travel to the server (your ping), then from the server to your Pilot (their ping), and then the same route back with the results. If you for example selfhost and play with a friend in the same house, you wont really have lag. There is no simple way around this, unfortunately. Its possible to transfer the simulation around and we will work on that eventually, but it's not trivial. Cheers

Yes, Jester polls the list of airfields from the map-data. And helipads are also categorized as airfields (just with some different attribute). It only happens with map-built-in pads.

You can just delete the variations you dont like. He has about 20 for each and ~5-10 of them are in the style you are asking for already. Delete the others, then he will only say it in this style. Mods\aircraft\F-4E\Sounds\Jester\refueling Mods\aircraft\F-4E\Sounds\sdef\Jester\refueling If you are having an issue with other non-AAR calls, please be specific and tell us which calls you do not like. Otherwise your feedback cant really be used, cheers.

Perfect, thank you for the mission. Can confirm its fixed The fix will be in the update after the upcoming, cheers.

Since you mention the price, Id like to remind you about two things: - You purchased an early access product. Experience can thus be rough for a minority of users. Id wish it wouldnt be like that, but thats how development goes. - We have a no-questions-asked refund policy. So if you cant get the issue resolved, you can just refund, get your money back and perhaps try again in a few years or once the product is out of EA Fingers crossed on getting these nasty issues resolved [emoji106]

Not yet, but this is on the list of things we want to do already.

Could you send us a mission where this happens? No matter what I try in the ME, I cant get those pads to appear in the list. I know how to fix the issue, but would like to be able to verify the fix before submitting it

I just checked it ingame. The presence of the R symbol already indicates you are being tracked and under attack. Shortly after you see the R appear, a missile will come your way. If you want to detect its search-radar, hit the SEARCH mode. You will then see the vehicle used for searching targets appear on your screen before you are being locked: Dont forget that you can also click the HANDOFF mode in order to hear the high pitched tone as soon as the R appears, then its hard to miss that you are under attack

Your query may sound trivial to you, but it is a lot of work actually. If you just flip the knob manually, Jester will do mistakes and mess up your locks and similar, as he actively interprets the number displayed as Vc. If you change the knob, he takes the other number and thinks thats the Vc and then messes up everything. Vc is a mandatory component to his logic and if you would tell him to flip the knob around, that would mean he has to pause all his radar logic until you are done with that stuff. Well, not sure what to respond to that. I guess you need to wait for Jester customization then, so the Community can give you Pilot<->Wso interactions/options that we think are unrealistic. The "where is the target" feature would include that as well. It is essentially a request to the WSO to move the knob around briefly in order to give you all info he has on the target. And it would be context sensitive, doing different stuff in other situations (dogfight, A2G, ...), so that the interaction can be reused and people dont have to bind a million things but remain being able to control entire Jester with just 2 binds if desired.

Id suggest to first tell us such things, so that we can remove it for everyone This one specifically wasnt known to us yet Cheers

Essentially, you are trying to play WSO here, despite being the pilot. We believe a better, and more realistic crew interaction would be something like "hey Jester, where is the target?", "uhm, 20° right, 25nm, 17k ft". So that is what we will do instead. Also because this flow integrates very well into other aspects, such as losing the target during a dogfight or when needing assistance to find a ground target etc. To your specific use case, you can deduct that from the screen via the antenna indicator on the right plus the range. All crew, pilots and WSOs were able to guesstimate target altitude within a second by just looking at these two parameters and hence never desired to flip the knob around to sacrifice Vc. Jester moving the knob around outside of lock validation or no-lock shots wouldnt be proper behavior. And allowing the pilot to mess around with it in any way would mean significant extra work to let Jester understand that he currently can't do his job anymore because he is missing Vc, which is integral to his workflow. Its less work to do the "Wheres the target?" feature than that. Hope that clarifies things, cheers.

Yes. Also note that for some SAM systems the presence of the symbol on your display already means a missile is coming your way. This is especially the case for systems that have separate search and tracking radar emitters. You have to interprete the symbology and indications depending on how the target system works. The manual will in the future have a detailed list of each common platform and how the various stages are indicated on your RWR.

Jester does operate the knob, also outside of Boresight. So if you start messing with it, you will confuse Jester and he will also eventually set it back to another setting. The correct procedure for a WSO, outside of Boresight modes, is to always put the knob into a setting that allows to read Vc, the single most important value. Based on Vc, you can easily deduct target altitude, aspect and of course the closure rate itself is given as well. Heading and distance is shown on the screen by the placement abd movement of the return already. Jester assumes the knob to be in Vc, if you force-move it, he will incorrectly interpret the number on the display and mess up. Aside from Boresight no-lock shots, the only time when the knob should be moved is shortly after obtaining a lock to validate lock quality. Jester cycles the knob through all settings after locking in order to do that (he doesn't really validate much yet though). Then, back to Vc. That said, we are planning to add some form of "where is the bandit" command where Jester would give you a BRA callout or similar again.

Its possible that a default loadout is too old and contains invalid definitions. @IronMike FYI

Yup, thank you. We have added it to our backlog and will fix it eventually

Yeah, known issue. It had problems since release already.

Huhu, is the track working and reproducing the issue for you? It seems its almost 2h long and it seems to bork after like 10-15min. Long tracks unfortunately have poor stability, try to replay it yourself to check. Ideally tracks are 5-15min only (Singleplayer and on Caucasus). Thanks for trying though, highly appreciated :)

This is a known bug that has already been fixed for the upcoming patch, cheers.

Things are never final and will always be refined until we and you are happy. The recent engine sound update in particular had some bugs and will be temporarily reverted in the upcoming patch. It will then come back later once the issues are fixed.