FalcoGer

I certainly didn't put it in wishlist. And if I did it was by accident.

Please elaborate. What is it supposed to be like?

Using the TADS sometimes gets really frustrating in FLIR as when even a sliver of sky is visible suddenly the whole brightness and gain level change ridiculously, then you zoom or you slew a bit and suddenly the sky is not in the picture anymore, you gotta twiddle the knobs again. If you want to see the ground and vehicles well you have to fiddle with the knobs all the time, in particular every time you switch zoom levels. I don't mind the sky being blindingly bright, on the video display, I want the ground to be the same image quality no matter what I do. It seems like the camera is trying to fot the range of temperatures onto the display that it can see, rather than assigning any particular temperature a pixel intensity and keeping it there (which would be my preference), no matter what other temperatures are in view. For example if you have a 40°C tank, 25°C ground and a 500°C fire on a burning tank, I want to tell the difference between the tank and the ground, not have it be the same because suddenly everything but the fire turns black on the display. Now the question is. Is that realistic? Is there an option I can make in some MFD menu to make it assign pixel intensity to temperatures and not care about the hottest/coldest spot in the image? The pilot has an AGC switch for the PNVS but it doesn't appear to do anything. That system has the same issues. I like to use it in daytime to look through the canopy frame, but whenever a sliver of sky is visible the ground just turns black (ie. transparent) in the HDU. I can adjust the brightness and gain knobs to see the ground (the sky turns opaque, but that's fine), but when I then look at the ground again without the sky in view, everything just turns white, which completely defeats the purpose. I want to see, not twiddle knobs all day long every time the sky gets in view or not.

We've been promised better ATC for years now. But there has been nothing to show for it. The best we got is a semi decent carrier approach control for the US Navy. I understand that this is complex with different terminology in different countries and in different times. But that's no excuse for apparently 0 progress over a decade and a half. Incremental updates are a thing. Implement one system, apply it to everything and then add the nuances later. Add the current world standard for terminology and procedures first, then add the special cases (Russia and WW2) later. I would like to know where the progress is regarding to this. It's always "It's WIP", but I really feel like we're being lied to and nothing at all is being done on this end. I remember being yelled at "Hold position" in a perpetual loop for no apparent reason when I first started with FC3 when each module required a game restart, and the same thing still happens today. What has actually changed? What is being done right this moment? What milestones have been reached this year? Or last year? I don't see the progress and anytime someone asks it's "It's complicated" and "It's WIP". It might be complicated but it's not like it should take years to put in some points for arrival on the maps and have some logic for spacing and giving people vectors and speeds and altitudes. Again this can be done incrementally. Do runway management by the tower first. Then ground ops. Then departure, which really doesn't need to be anything special because you have you either have your mission or fly QRF, then arrivals. Then perhaps expand to AWACS actually controlling things instead of spamming you with pointless contact reports that have no bearing on what you are doing. There is no point developing one monolithic solution and then dumping it in all at once, possibly in 15 different languages for 5 different time periods. Do one thing that's the most common and standardized (modern English ATC), then apply that to everything (including Russian airports in WW2), because that's still a big step up from what we have now, then add the special cases later.

aka in 2035?

Why? Just put a red jet in and fight it properly. Once they're blown up you just restart the mission, or set both jets to invulnerable. Or better yet, get a friend (I don't know what that is, but I've heard that 'friend' stuff is really useful) and do it with them.

Sometimes it is required for the CPG to take control of the aircraft, perhaps in DCS more so than in real life. There is a confirmation dialogue that the pilot has to approve if the CPG wants to take controls, which makes sense, but only in a setting where you are not already in communication. If you are already in communication, for example in SRS or the voice messaging service of your choice, then it would be much more convenient to just press the button and have control, confirming the handover over voice. The requirement for this arises primarily from 2 factors. 1. It's inconvenient. It's inconvenient to take your hands off your flight controls, grab your mouse and click the approve button when in reality all that is really needed to happen is: a) you trust your CPG, b) your CPG takes control. If you do not trust your CPG, then why are you flying together? If you want your CPG to take control for whatever reason, then why is there this hurdle in the way that makes it clunky? 2. DCS is still a piece of computer software rather than real life DCS has a framerate, and at times it drops to slideshow levels for various and sometimes inexplicable reasons. If this happens while you are flying, it would be safer to hand off your controls to your copilot who might not have a potato for a computer (like I do). Unfortunately the confirmation dialogue gets in the way. And if you are having a slideshow, you simply are unable to click that approve button and thus you are doomed in a perfectly good aircraft. If the CPG could simply force take the controls (presumably after a lot of cursing from the pilot and telling him to do so) everything would be well until DCS has resumed running at a normal pace after the upset, after which controls can be switched again. A second example happened to me today. The pilot was flying with VR and his VR software inexplicably popped up and tabbed him out of the game. I tried to take control while he sorted that out, but could not because he was unable to get DCS up again quickly to click the approve button. I understand the reason for the confirmation dialogue, and it makes sense in some circumstances the same way as not having that dialogue makes sense in others. If your CPG hits the take control button on accident, things may go south very quickly. If you fly with random people they might be malicious, but then again they can just drop the stores for you. This is why I advocate for a system that allows for each individual person to choose whether they have this control handoff confirmation or not in the special options. Set once for all missions and on all servers (ie. not in the mission editor). If the CPG needs to take control, it might be because it's urgent and/or because the pilot is unable to maintain control or even control the game. In such a case the confirmation is game breaking in that it makes you blow up because of software or computer troubles while it can be prevented if only you could turn it off. I think that most people flying together will have some sort of voice communication. As such forcing communication through a mouse driven menu is simply unnecessary, annoying at the best of times and frustrating at other times.

bit late but what is SHF?

is that IC safe?

If a missile is detected, the warning should be played. If you don't have any other information, the most reasonable guess would be that the missile warning is played before the missile hits you, not afterwards. Who in their right mind would engineer a system that delays such information?

The missile warning comes up right away as the flashing arrow on the CMWS bolt on. If in auto the flares launch right away. But the missile warning is often delayed by up to 3 seconds, by which time a missile had plenty of time to blow you up or get someplace where flares won't do much anymore. This is especially troublesome if you are currently engaging and are on bypass since you don't want to spend your flares for friendly missile launches. In the attached track you can see the flares launching and the missile warning flashing but the audio warning comes way later (way later being relative to a short range missile heading your way from 1500m). By the time you hear the warning, the missile has already covered 2/3rds of the way, even though the launch was detected right away. Unrelated: George just doesn't want to shoot the gun. Late_Missile_Warning.trk

Even when stationary and with no wind, gun rounds land right of your aiming point when shooting the gun to the left and they land left of the aiming point when shooting the gun to the right. The gun should be aiming where the cross is if everything is stationary. On top of that gun rounds do not impact at all if you shoot beyond a certain range, which is about 2900m. I don't care about effective range of the gun, the bullets are still physical objects that don't de-materialize spontaneously after crossing a magic border. And on top of all of that, the gun should be tracking the TADS and a ballistic computer should calculate a solution using the bearing and range change over time, current range, time of flight for the projectile (not sure if muzzle velocity change due to temperature/humidity is calculated into this), bullet trajectory (not sure if wind is calculated into this) and the helicopter's own movement. In short if you are tracking a moving target, it should hit that target, not the spot where you pulled the trigger. Unrelated: Airshow cones have no collision. Also Unrelated: That's a really sturdy landing gear. Gun_Tracking_Mismatch.trk

no. i set agl 0 and it switches to some value greater than that.

When you do that it immediately snaps back to like 70ft.

When placing waypoints down, they are always forced some distance above the ground. That is annoying, I want to place my waypoints on the ground, at 0ft. I would like that to be an option.

So you are fine with a depiction of warfare and death but not blood? I think it would be a good visual indicator that you need to return george for an oil change. If you're not fine with that then turn it off. I don't see the issue. Besides what do you think happens when someone gets shot in the face with a couple of 30mm HE round? He takes a nap? Granted, I don't want body parts flying around, I don't even care for blood on the ground or clothing or anything like that. I just want to know when my copilot is shot. Adding a decal to the partitioning window is like 10 lines of code and 5 minutes of texture work. Besides that, real apache pilots didn't seem to care much about how they (that is their enemies at the time) had to scrape the intestines off the ground to have a funeral, judging from what guncam footage with voice is available. "It's their fault for bringing children into the battlefield" and whatnot. I think a little blood is harmless in comparison.

Yeah, the second one is a bit weird. Maybe it has to do with the buttons. Sometimes it shows, sometimes it does not.

This issue is only present when starting from cold. When selecting the radio with the RTS rocker switch, it uses one state, when selecting the radio with the radio transmit select on the cyclic it uses a different state. For example when you select with RTS rocker switch from VHF to FM1 and then press the PTT depress, it behaves as though the last radio was the one selected using that method and switch to the next one after that. Also in multicrew (multiplayer with 2 people), the radio selected by the opposite crewmember doesn't show correctly and is always VHF. RTS_missmatch.trk

When an item on the MFD is active for KU entry it should be boxed. This is not the case for the manual radio frequency entry. 1. Go to COM 2. Got to MAN 3. Select VHF Expected behavior: current frequency is boxed. Actual behavior: nothing changes on the MFD, only the KU comes alive to indicate entry. Same for ECS cockpit temperature. no_boxy.trk

And it still does jack against bunkers.

No apologies after all.

What's the point in carrying fuel that's not being used? If you wanna carry fuel around it's probably cheaper to load it into a fuel truck and drive it over.

Predicted hover torque was from Performance page Robbie tank has to be commanded on yes, but that is part of the startup procedure Chaff is armed on the ground, so that's wrong in any case.

I'd like a little compass rose that's rotating with the external views. The infobar shows the heading only when in free cam or the heading of the object you are viewing. But often it's nice to know which direction you are looking in instead. I propose a little compass rose somewhere on the screen that's always relative to the direction you're looking in. Example from dangerous waters.

Alternatively, some integration with the kneeboard. Every time you press a button you add a line to some kneeboard page that's always present. maybe a little X next to each line that you can click to make it disappear. Even one page per button press would be okay. Have a little picture of the map where the key was pressed to fill the empty space, have all the coordinate formats on there and a button to delete the page. Anything to make it easier to copy F10 coordinates into the cockpit without using pen and paper.