[FIXED INTERNALLY] Strange sun

[352ndDeacon]

They don't get $$$$$$ for taking care of it. Only for selling you another bugged module.

[grafspee]

I think they just treat us lightly. I do not see any other explanation. I do not think that this is an unresolvable problem, rather very easy, only nobody wants to take care of it.

 

i think that's not true i think they got lots of work right now, they announced so many things recently. i think that this thing is just priority and i have feeling that sun fix for spitfire is long way from now :P

[philstyle]

Hey, guess what . . .

[Nealius]

It should be an easy fix. Razbam had the same issue with the M2000 and Harrier a while back, and they fixed it in a fraction of the time that it's taken ED to even report this issue in the Spit...

[Sulaco]

Does anyone know if this is planned to be fixed in tomorrow's update?

[philstyle]

Does anyone know if this is planned to be fixed in tomorrow's update?

 

 

Nobody knows

I expect it will not be fixed.

[finch]

seems the fixes and updates are only focused on the F-18, the other modules are in standby

 

 

Edited May 8, 2019 by finch

[philstyle]

seems the fixes and updates are only focused on the F-18, the other modules are in standby

 

 

 

 

 

I dared to suggest this more than a year ago, and was given a hearty reprimand (hence the "warning" on my profile).

 

 

.

[kontiuka]

I dared to suggest this more than a year ago, and was given a hearty reprimand (hence the "warning" on my profile).

 

 

.

Respectfully, how many times did you suggest it? You usually don't get a warning for just a one-off remark unless it's really bad.

[schurem]

Alas, bug still present in current beta 2.5.4.30386

[petsild]

Please NineLine if you would inform us, thank you.

[Robin885]

In 3 weeks it will be a year that this bug is present, it can't be such a nightmare to fix, Razbam fixed it on their modules in a single day... Why isn't it being watched?

[NineLine]

I dared to suggest this more than a year ago, and was given a hearty reprimand (hence the "warning" on my profile).

 

 

.

 

You were not warned for anything related to this issue, also no one can see your warning but you and moderators, as well, this is not really a discussion to have here, its heavily off topic, and also against the rules.

[grafspee]

my question is why it was taged as reported just recently, why pretending that there is no problem here for such long time.

it should be taged as queued for fix long time ago it would spare lots of ppl unsleeped nights.

i can totaly understand that fix is hard, ppl resources are focused on something else right now ok i get it

[NineLine]

my question is why it was taged as reported just recently, why pretending that there is no problem here for such long time.

it should be taged as queued for fix long time ago it would spare lots of ppl unsleeped nights.

i can totaly understand that fix is hard, ppl resources are focused on something else right now ok i get it

 

Lots of things are reported and not tagged, the issue was reported internally before anyone saw this thread. Being tagged reported doesn't mean it will be fixed tomorrow as much as I wish that were the case.

[grafspee]

Lots of things are reported and not tagged, the issue was reported internally before anyone saw this thread. Being tagged reported doesn't mean it will be fixed tomorrow as much as I wish that were the case.

 

i dont expect to be fixed when it gets tag reported, at least its officialy reported now, im much happier now

[NineLine]

The bug is finally seeing some activity internally after some more poking, so I will keep you updated when a fix is in, or watch the upcoming changelogs.

[NineLine]

This is now fixed internally, my hopes it will make it through the build process for this Wednesday's open beta.