PawlaczGMD

The evidence is presented in the thread of the mod I have posted. You just choose to troll with "I like it the way it is" instead of reading it.

Yup, I'm in VR. So I guess they've already figured this out, but it's not yet implemented in VR for whatever reason.

To give ED some feedback - IMHO the new dots are better than the old ones, where I couldn't really see them. However, they are significantly overdone. The visibility it gives you is insane. Frequently when objects approach closer, they become harder to spot! That's really backwards. I think it boils down to the fact that when the actual model is rendered, it blends in better, whereas the black dot is very high contrast and artificial. I think an improvement would be to sample some colors from the actual object and render them instead of just black. The size is also too large at big distances. Currently, I can see everything for let's say 20 nm against a clear sky. I think 10 nm would be more reasonable. Especially in MP, I feel like this system takes away a lot of skill, as with BRAA calls, people will pretty much always spot each other from BVR. In Cold War era and before, this will impact almost every fight, for the worse.

I have noticed the same behavior erratically, recently in the F-5. Easy comms off, correct radio bound (not the default Comms button), radio turned on and tuned. With the same controls and options, sometimes radio will just not work seemingly randomly. I can get the comms menu to open, but I do not get any responses, and AI does not react to my commands. Then I will restart the mission with the same setup, and it will work fine. I'll provide a track when it happens again. Additionally, the ATC replies are sometimes bugged, it will show subtitles, but no audio. This is independent from the above.

Nobody cares what you think about it though. It's overwhelmingly probable that the developers have misinterpreted the RWR manual, and implemented it incorrectly. It's thus wrong and unrealistic. The mod makes it work closer to how it should. Ideally the Search button would be fixed by the devs to work in a way that's correct.

Isn't normal alignment 20 mins, and precision one 40 something? For reasons above, I basically never do them, so I'm not even sure, you might be right. I was referencing the precision alignment just FYI. It might be overkill.

+1, most high-end HOTAS have this in their software. But the software doesn't know which plane you're in, so you have to tab out and change the profile. All we need is an AB variable in the thrust axis tuning, that maps the X % throttle input to Y % where AB kicks in. You can do it with the current user curve, but it's a huge pain, and it's impossible to get linear response in both MIL and AB regions. A basic feature, really.

Same, the sun square thing is annoying.

I don't think it's a question of realism, but rather abstraction of ground crew procedures, and understanding of practicality in what is a computer game at the end of the day. I believe that the real navigation system needs 40 mins to align. However, it is certainly something that the ground crew would set up, and would be done by the planned take-off time. The best solution would be to give players an alignment "cheat" in Special options tab. This is not unprecedented, as many aircraft have things like simplified crosshair, take-off, nosewheel, etc. If the Realism cheat is not set up on the server, the navigation system is simply unusable for any precise task, and I think it's less realistic than starting pre-aligned. I imagine the only time when a real pilot would take off without proper alignment is an emergency scramble. Any normal mission, the ground crew would set up the helicopter for planned take-off time. In, particular, none of the Single Player campaigns that I've played have this enabled. They also plan the take-off time to be immediate. So in practice you just always have extremely poor nav precision. I strongly believe this is way less realistic than having your machine aligned when you load into a mission. I personally actually enjoy playing with the weakness of the system, and needing to do fixtaking - however, this does no good if you lose alignment in a few minutes after anyway. What I don't enjoy is being expected to wait 20-40 mins before I start the Ka50 up to be able to meaningfully use the system. Additionally, this is a video game, and you cannot expect people to wait this long. As someone above pointed out, refuel and rearm takes 2 minutes instead of dozens, and you can do it at any position in the airfield vicinity, so a departure from literal realism is not unprecedented here. Having the option to simplify this behavior is reasonable. I would see this as an abstraction of ground procedure.

Here's the issue that you don't seem to get: When you get locked, the RWR will only give you an audio warning and not show you any visual cue! You have to toggle the search button. It should be obvious why this is a very bad idea. How it should work: turning off Search removes long-range radars that are not locking you, decluttering the display. But you should never ever have to press a button to be able to see the radar locking you. At worst, the Search mode as it currently is should automatically switch off when you're locked. The way it works currently is completely unbelievable to many people.

As per the title. In VR, sometimes, going to the map and back causes the overall brightness to increase significantly for a few seconds - very uncomfortable. I only experience this in Ka50, on both Pico 4 and Pimax Crystal headsets.

I recommend a high-res cockpit mod on here - It has a clear canopy. Yeah, this is insufferable in VR.

The RWR is almost certainly bugged. It more or less displays all radars NOT locking you in Search mode, and ONLY radars locking you in non-Search mode. This is an insane way for an RWR to work, as it makes it almost useless. Yeah, I'm going to fiddle with this tiny button when I pick up a lock tone - I don't think so. Install this mode that makes it show everything:

I've found that it doesn't if you do autopilot reset instead of disengage... what is supposed to be the difference anyway?

Noticed that, in the stock campaign, when my flight has 4 members, nr 2 will listen to orders and engage when asked, but 3 and 4 just hang back behind me and refuse attack orders, being general wastes of space. They only really do something after I engage myself, but as you can guess I would rather send them in first or at least at the same time, but no, they always hang back behind. Anyone notice it? Is this a bug?

I noticed the autopilot on the SU-27 goes into heavy shaking/oscillation after a few seconds, making it useless or at least silly and immersion breaking. Also, when disengaging AP with the same key you switch it on (say "A"), weird things happen to my bank trim,violently banking to one side, only to be fixed by trim reset. Resetting AP with alt-9 seems to switch it off fine. Are these bugs or am I doing something wrong here?

Similar problem, specifically when editing controls, sometimes button press doesn't register many times, and when editing loadouts pre-mission the game can hang for 10-15 seconds randomly. I also noticed this in Multiplayer server browser, it will often hang, or at least won't update server info when you click into a different one.