[FIXED INTERNALLY] F5 HUD dark green?

[Quekel]

Hi All,

 

On the new update my F5 HUD is dark green, anyone else having the same issue?

[Knock-Knock]

Same here.

Tried deleting metashaders and fxo folders, plus running a cleanup and repair. Happens for both default and chinese cockpit.

Looks like its calling for a texture that doesnt exist, so we get that dark green missing texture slapped across the HUD.

[Quekel]

Glad to see i'm not alone, I also notice a FPS drop when on outside view and looking at the exhaust smoke from the engines. Could you check the same?

[PSV_Tango]

The Amount of issue with the module are ridiculous, the feeling that the module is completely abandonned, it's really annoying.

 

Radar and Hud issue, but mostly a total mess with all the plane textures since the last update in August 2018.

[ThorBrasil]

The Amount of issue with the module are ridiculous, the feeling that the module is completely abandonned, it's really annoying.

 

Radar and Hud issue, but mostly a total mess with all the plane textures since the last update in August 2018.

 

I've never doubted that the F5 was abandoned.

[imacken]

Hi All,

 

On the new update my F5 HUD is dark green, anyone else having the same issue?

 

Yes, and the radar - see attached. What are those white dots everywhere?

[DrGarantia]

Exact same problem, hud was OK before patch, now it is almost opaque with this green tint.

[Strikeeagle345]

how does this even happen? The F-5 wasnt touched....

[Sauerkraut]

It's not a bug, it's a feature. :)

 

See it as protection against glare.

 

In some Russian machines you can also dim the HUD.

 

It is sad that all the energy in new features of the F-18 is plugged and most other aircraft are increasingly neglected.

Edited March 1, 2019 by Sauerkraut
for imacken

[imacken]

It's not a bug, it's a feature.

 

See it as protection against glare.

 

I assume you are joking!

[Charly_Owl]

Running into the same issue... I hope it's fixed quickly... because it's super annoying. :(

[Lucas_From_Hell]

It's making approaches really hard because the runway basically disappears unless it's noon in good weather.

[Reckoner]

Rather than fixing current bugs they are adding new ones. Ways to treat was is supposed to be a released module.

 

Same issue here if wasn't clear.

[Dirty Rotten Flieger]

Well God Dam. The very day the Mig 19 comes out and they break it's obvious opponent, the Tiger.

 

I'm actually relieved to realize it is a bug and not the devs idea of glare proofing that only looks so bad on my combination of hardware. For a horrifying moment I at first thought this is a feature and just how the tiger HUD will look from now on OH GOD PLEASE NOOOO!!!!!!!

 

It's unplayable in this state.

[Nealius]

Same problem here. I went through the cockpit texture files and .luas but didn't see any glaring issues. I was hoping to cruise around in the F-5 but I guess not :(

[Vitormouraa]

Looks like I won't be flying the F-5 on Cold War...

[RustBelt]

The Amount of issue with the module are ridiculous, the feeling that the module is completely abandonned, it's really annoying.

 

I guess I don't understand, the F-5 is a Finished module. Are the makers supposed to update it in perpetuity to fix every bonehead thing ED does to fiddle with their Jenga Tower of a game engine? Once a module is out of Beta shouldn't ED be the ones responsible for keeping it working as developed while they unceasingly futz with the game?

[Schmidtfire]

I guess I don't understand, the F-5 is a Finished module. Are the makers supposed to update it in perpetuity to fix every bonehead thing ED does to fiddle with their Jenga Tower of a game engine? Once a module is out of Beta shouldn't ED be the ones responsible for keeping it working as developed while they unceasingly futz with the game?

 

The makers for F-5 are ED (former Belsimtek). But yes, the whole Jenga-thing is very frustrating. And rather expensive. Just imagine all the resources and manpower it takes ED and other devs to fix bugs on old and released products! And all the upset players.

 

I have played PC games and sims for 26 years and this is the only title where updates likely will break stuff that is working. Something is very wrong under the hood, just hoping that ED would figure out how to avoid it from happening. They are smart people.

 

Back to the F-5. A 59.99$ completed module that gets more broken every update. What if a newcomer to DCS or simply someone who does not engage on the forums see this module in the store. How could he/she ever know what state the module is in? It looks fine on the storepage right?

 

I love DCS and I like ED. But this is so F R U S T R A T I N G to go through with almost every single update :mad:

Edited March 2, 2019 by Schmidtfire

[Nealius]

Judging by how long it took to get the Spitfire's cockpit issues acknowledged and fixed, as well as the Yak's issues (which are only acknowledged, not fixed), it might be a while before we get an official response or fix on this one :(

[some1]

I guess I don't understand, the F-5 is a Finished module. Are the makers supposed to update it in perpetuity to fix every bonehead thing ED does to fiddle with their Jenga Tower of a game engine? Once a module is out of Beta shouldn't ED be the ones responsible for keeping it working as developed while they unceasingly futz with the game?

 

Actually, the stuff breaks because there are some changes to the module being made recently. It looks like F-5 textures are slowly being updated to PBR, but sadly, it looks like no one controls what's being pushed to the public and we get some half working WIP stuff.

[gulredrel]

Actually, the stuff breaks because there are some changes to the module being made recently. It looks like F-5 textures are slowly being updated to PBR, but sadly, it looks like no one controls what's being pushed to the public and we get some half working WIP stuff.

 

I also found this a bit frustrating. Working myself in a software QA department, I think they are missing a proper regression test strategy for the numerous addons out there.

I hope, this will improve in the future.

 

Having small bugs on MERs or whatever which are not obvious at first can slip through into open beta. But such obvious things should have been detected if only one single person would start instant action in every single module.

[Wags]

Thanks guys. The issue has been reported and we'll try to fix ASAP.

[imacken]

Thanks guys. The issue has been reported and we'll try to fix ASAP.

 

Excellent news! Thanks, Wags.

[grunf]

Thanks guys. The issue has been reported and we'll try to fix ASAP.

Thank you!

[Vitormouraa]

Actually, the stuff breaks because there are some changes to the module being made recently. It looks like F-5 textures are slowly being updated to PBR, but sadly, it looks like no one controls what's being pushed to the public and we get some half working WIP stuff.

 

If that's true, why did we see this bug before?

 

Thanks guys. The issue has been reported and we'll try to fix ASAP.

 

Fantastic. Thanks!