Dawgboy

@silverdevilwhen live, it corresponds with the screen showing a darker image in the video, but I see flashes of weird objects and it might darken a bit. It shows whenever there's a text menu displayed or closed within the sim. I tried it in the South Atlantic and Syrian map missions, and both do the same thing. I wish the video caught exactly what I see, but it doesn't. Just note the video darkening corresponds with the flashing of weird objects.

Regardless of theater, and only when I toggle the UHF or VHF comms menu as a Viper driver, the screen flickers with various objects, without a discernable pattern. It doesn't do this for any other keybindings or keyboard input. I will post a video of this, in which the actual flickering is there, but exaggerated in length...the flickers are much shorter, but completely bothersome. The introduction of the menu in the top right corner, or removing it, seems to cause this flickering. Screen Flickering This started two Open Beta updates ago. I was hoping the latest update would fix it, but no joy. Anybody else see this issue? I'm on DCS 2.8.2.35759 Open Beta. TIA

Thanks @Flappie

Barely visible taxiway/runway/etc. airfield lighting on various maps w/fog, and even when next to the taxiway lights, you can barely see them, even though aircraft lights are visible. Known issue?

What's the point? I made my point already, and you disagree, which is fine. However, you're bolstering my point in a round-about way...if they don't have the dollars coming in from new modules, there will be no more bug fixes, OR, they will take even longer. This is the difference between the freeware non-profit model and the for-profit model. Running it for-profit is always a delicate balance, full of tough staffing vs priority decisions, especially with Early Access aircraft. With the freeware, non-profit approach, you wait forever for both fixes AND new functionality. Your desires are completely controlled by what the devs can do within their volunteer time. I am amazed at how fast ED introduced some of the new Viper functionality, while being frustrated with the bugs. I even took a break from DCS because of it. MSFS2020 came at a good time for me, since I only fly the Viper. Now, if something's already out of Early Access, I think it's an "all-hands-on-deck" situation. I don't fly any helos, so I can't speak to the Hip issue you cited, but I'd be pissed if the Hip was already fully released and out of Early Access. When you buy an Early Access module, you sign up for the reality that comes with that module until it's fully released...

I understand the logic in this post. I think, though, there are two major groups...yours and the folks that want the jet to be more complete. I see advantages to both; however, I favor the fuller feature approach, mainly because you can test the entire mission flow and find bugs you might not have if you were "handicapped" into a comprehensive testing cycle for each sub-module. As soon as you add more subsystems, these integration bugs will show themselves. I find a more compelling argument in finishing a module's functionality, before starting another aircraft, leaving some bug-fixing teams in place at the end. But that isn't the way things work in this business; to keep the revenue flowing to support the business model and employees, you need to keep introducing new paid modules with a good strategic roadmap. To be sure, there will always be an unhappy contingent. For all the euphoria of the Apache release, as was with the Hornet, Viper, Tomcat, etc., each camp's fans will start the inevitable cycle that caused this post and other similar posts...frustration with bugs, as well as incomplete feature sets that come with Early Access and a lack of qualified experts that dance around ITAR/classified information.

I have seen this same issue, but the track file was too huge. I was in single-player mode.

This is an interesting mod, similar subject:

@razo+r @Northstar98 @Tholozor @norman99 Thank you for your tips. Followed the fusion of them, and connected the first time. Now to practice...

@norman99including turning off the HMCS?

And for some of us, live long enough.

"Move along, sir. Nothing to see here. Keep moving..."

By the authority vested in me, APPROVED!! Now, back to reality...

That's an outstanding compromise, and again, I'd buy it. Q: Doesn't the AIM-120D require a Viper radar replacement?

True. There're bigger challenges to the F-35 than just the radar, tho.

Ha! Point taken. Yeah...both may be a bridge too far, but the V Viper could be easier.

608 USAF Vipers to Upgrade to V Variant I'd be willing to pay for this as a full module, if DCS took it on. I realize it comes with challenges, being "current" technology, etc. But a sim pilot can dream, right?

I saw this in single player mode, which is mostly what I've playing as of late. I will replay the MIZ where it showed and report back.

Good point. In the other Viper sim, we'd watch the AI cuz they'd know all. I wonder what the fog-of-war factor is on AI. I don't have enough experience with DCS to say.

BLUF: There's still some quirkiness in the VIper radar. @NuggetzSame here, but I wasn't carrying an ECM pod...just loaded A2A w/centerline bag, co-altitude at ~angels 22, targets 300-350kts. I get explanations about the radar not being able to break out 4 Blackjack in tight formation, seeing them as one. Even when the 4 Blackjack are spread visibly huge across my 10-2 line, the radar still doesn't see them as 4 targets. Antenna elevation was good, scan volume was good, slow conversion to the rear, etc.; there was ample time for the radar to see all of them. My live Hornet wingman never saw a single target in the formation, even though he had antenna elevation optimized, etc. We flew it multiple times, and the same results each time. Granted this was before the change to allow 4 Blackjack in a single group; however, 4 Blackjack should be 4 Blackjack to the radar, regardless of group setup in the Mission Editor. In a flight of 4 Fencer nearby in the same mission, I was able to break them out, although folks pointed out they were in a wider/loose formation compared with the Blackjack. I think I would agree with the explanation, EXCEPT, I had the Blackjack visual, clearly spread apart on my 10-2 line, me converting to a stern attack, and the radar still didn't see all four. It was the same in MP and SP missions.

All maps or? I had this issue in Marianas, even with AWACS, which I reported.

Thanks, good rundown. I really like the Viper's stick on the right, versus the center. I've flown both in my physical cockpit, which you can configure either way, regardless of the DCS module you're flying. I just like the stick on the right better, although this, too, is a matter of preference...there's no right or wrong.

Viper.