Do we have a ETA on the cure for the beige plague?

There is so much overreaction on this thread.

True. I personally hate the beige planets and moons, but I (as a software engineer) I can understand the delay.

It's not a showstopper bug. It affects everyone, but it is a minor cosmetic issue. It's not like the game is crashing. It's an unintentional side-effect of a newly reworked subsystem. It's apparently hard to fix.

That puts it low on the todo list, regardless of the (loud) complaints of a portion of the players.

It sucks, but that's just how the software industry works.

My bigger fear is that assuming they keep to "pure science" the beige planets will just be replaced by mostly gray planets. (See the photos of the solar system moons I posted earlier in this thread.) Astronomers use color enhancements to bring out subtle details, of otherwise non-descript landscapes. Without some level of "exaggeration", the galaxy will be filled with boring planets and moons.

I don't want NMS, but as an explorer, I want interesting and picturesque stuff to explore.
 
Last edited:
Fix for planetary surfaces isn't coming anytime soon, see you in part 3. I wanted clarity in that regard, and I got something close to it. It'll do.

At least you are realistic. "something close to it". I would say "not even close" regarding proper communication, but all is good.
 
As my Avatar shouts it out in a very obvious way, I too find this a problem,a big one.

Having seen some of our responses,after FD's, I see why they shy away from threads like this. They are on a loser no matter what.
 
As for the thread title question, MBrookes should have answered in his usual style and much angst could have been averted:
OP: "Do we have a ETA on the cure for the beige plague?"
MB: "No."
 
Last edited:
Bring out everyone's favorite STRAWMAN!

This has NOTHING to do with the consoles. And the texture rendering before the beige issues did have issues. My top of the line CPU/GPU most definitely didn't like it.

Au contraire. We have discussed this problem in our squad and no one has had problems with the performance. Either your message is white-knighting par excellence or something really has gone wrong on your site.

And, if I remember it correctly, there was a statement from Michael Brookes stating that the colour change was caused by realistic colour values of the materials. So basically we are talking about colourization here. And there´s no - and I mean zero -reason not to change it back to 2.1, except the underlying engine was tuned for whatever reason and they don´t talk publicly about it. Until this is not proved wrong, my statement is: They tuned it down for performance reasons leading to the mess we have now.

It´s not affecting gameplay though. I wouldn´t care, but someone is not playing honest at the moment.
 
As for the thread title question, MBrookes should have answered in his usual style abd much angst could have been averted:
OP: "Do we have a ETA on the cure for the beige plague?"
MB: "No."

People would be angry then that FD didn't give detailed answer.

They can't win this round. People think it is easy to fix, something that was done for consoles, etc. They can't accept simple answer that developers wanted to make game better, screwed it up, and now have to design and plan completely new, better system to fix side effect they see.

That's a life of developer.
 
  • Like (+1)
Reactions: NW3
Au contraire. We have discussed this problem in our squad and no one has had problems with the performance. Either your message is white-knighting par excellence or something really has gone wrong on your site.

Sure, you didn't have problems, Other had plenty.

And, if I remember it correctly, there was a statement from Michael Brookes stating that the colour change was caused by realistic colour values of the materials. So basically we are talking about colourization here. And there´s no - and I mean zero -reason not to change it back to 2.1, except the underlying engine was tuned for whatever reason and they don´t talk publicly about it. Until this is not proved wrong, my statement is: They tuned it down for performance reasons leading to the mess we have now.

It´s not affecting gameplay though. I wouldn´t care, but someone is not playing honest at the moment.

Not really. Michael said yes, *One* of reasons why change appeared that before that planets were coloured by more primitive methods. They added more complex material system to rendering - this by the way made ships look way cooler than they were. However, there was snafu with color scheme. Way code was designed was to be effective, and thus fast (it is rendering after all). Turned out this method has side effect everybody complains on this thread. And turns out more visually better looking method might have impact on performance so much that it might require to remove DX10 support for example.

It is all speculations, but you really guys don't get how complex software is really and how dependencies in such game impact one element or another, thus making very hard to 'fix' anything that fundamental within one cycle of update. Talk about changing gears while driving a car.
 
Last edited:
[...]My bigger fear is that assuming they keep to "pure science" the beige planets will just be replaced by mostly gray planets. (See the photos of the solar system moons I posted earlier in this thread.) Astronomers use color enhancements to bring out subtle details, of otherwise non-descript landscapes. Without some level of "exaggeration", the galaxy will be filled with boring planets and moons.

I don't want NMS, but as an explorer, I want interesting and picturesque stuff to explore.

If they really do stick to the science then grey planets and moons might be less of a problem then you'd expect. :) We're just living in the neighborhood of a G type star that happens to mostly emit light in the white spectrum. That same grey planet will look gorgeously different near a red giant or a Wolf-Rayet type star.

The more real the better in my book. :)

(but then, I'm all about hard sci-fi and realism, so there...)
 
If they really do stick to the science then grey planets and moons might be less of a problem then you'd expect. :) We're just living in the neighborhood of a G type star that happens to mostly emit light in the white spectrum. That same grey planet will look gorgeously different near a red giant or a Wolf-Rayet type star.

The more real the better in my book. :)

(but then, I'm all about hard sci-fi and realism, so there...)

^^^^
That exactly. And we also know that the star lighting will be updated as well, soon (TM). AFAIK Carbon stars have greensish light in withcspace tunnel and in the system map, but not when we properly arrive.
 
^^^^
That exactly. And we also know that the star lighting will be updated as well, soon (TM). AFAIK Carbon stars have greensish light in withcspace tunnel and in the system map, but not when we properly arrive.

Yeah.

For me it is truly a bummer that FD won't roll these updates any time soon - because of way their development works which I will admit appears slow to me and might cause some disappointment, although I have luxury of understanding complexities behind all it - but yeah, when next galaxy visual update comes, it will be feast for eyes.
 

verminstar

Banned
So after an evening to reflect on what I now know, any potential fix is literally years away, and there is some apparent confusion in the 3 or 4 answers, as in they don't appear to match up. We told just last week it's in the hands of QA, only to find out yesterday it's been discussed? It would be easy to admit some confusion here...but I suspect I already know why there's confusion here, but I won't write it down as they will ban me fer it.

So to tie this off completely...exploration is dead to me in its current state. The thing that broke exploration ain't gonna get fixed anytime soon if ever, and the devs have all the communication skills of North Korea.

All but done with the forum and all but done with the game in its current state...it's a result of nothing else ^
 
So after an evening to reflect on what I now know, any potential fix is literally years away, and there is some apparent confusion in the 3 or 4 answers, as in they don't appear to match up. We told just last week it's in the hands of QA, only to find out yesterday it's been discussed? It would be easy to admit some confusion here...but I suspect I already know why there's confusion here, but I won't write it down as they will ban me fer it.

So to tie this off completely...exploration is dead to me in its current state. The thing that broke exploration ain't gonna get fixed anytime soon if ever, and the devs have all the communication skills of North Korea.

All but done with the forum and all but done with the game in its current state...it's a result of nothing else ^

Issue has been talked about for months. Of course it is not in QA anymore. FD has ack it long time ago.

Also yeah, just stop. Bye.
 
Hi guys,

... but unfortunately it will not be in the short-term.

Oh well. So long Elite, it was nice knowing you. Maybe I'll check back in again in a couple of years, and see what my lifetime expansion pass entitles me to.

Perhaps my then FD will have added DLC options for planets: DLC 1: green planets. DLC 2: red planets. Etc...


The problem for me is not the beige. It's the monotony. It's not the fact that the planets are beige, its that they are unrelentingly beige. You'd expect variation in colour and shade an texture, but there is very little. Everything is almost the same shade. Go to a desert and you'll be amazed at the variety of colour you can see - but you'd probably sum up the overall colour as beige.

I guess it's a bit of a metaphor for the game as a whole. There are moments of brilliance and joy and pleasure. But, seen from a distance I'm afraid it averages out to dull, monotonous and monochrome.

What a pity.
 
So after an evening to reflect on what I now know, any potential fix is literally years away, and there is some apparent confusion in the 3 or 4 answers, as in they don't appear to match up. We told just last week it's in the hands of QA, only to find out yesterday it's been discussed? It would be easy to admit some confusion here...but I suspect I already know why there's confusion here, but I won't write it down as they will ban me fer it.

So to tie this off completely...exploration is dead to me in its current state. The thing that broke exploration ain't gonna get fixed anytime soon if ever, and the devs have all the communication skills of North Korea.

All but done with the forum and all but done with the game in its current state...it's a result of nothing else ^

I think the reason they don't like to communicate with you is because you take everything they say literally and then make up your own conclusions.

PS
Which is only fair because they are not very clear in their communication, however it's not strange to get 4 different answers when you ask 4 different people.
 
Last edited:

verminstar

Banned
I think the reason they don't like to communicate with you is because you take everything they say literally and then make up your own conclusions.

PS
Which is only fair because they are not very clear in their communication, however it's not strange to get 4 different answers when you ask 4 different people.

Whatever the case or truth is, this aint gonna get fixed anytime soon if ever...thats not 3 or 4 different answers at all. Thats one answer and its the exact thing I suspected it would be after bretts little comment about it being in the hands of QA last week. Theres literally nothing to talk about but they cant just say that outright, so they say as little as possible in the hope it just gets forgotten about.

Think back to MB post about it being worked on with no planned fix in 2.3, till last week and bretts off the cuff remark about it being in the hands of QA, only now to find out its certainly been discussed but no time soon. The usual spammed excuse, no eta no guarantee.

So no...the answer has actually become quite clear and one is much less confused now. Fear not however in that Im not gonna go off into a salt crusade on every salty thread I can find...quite the opposite actually. Think along the lines of just accepting it and moving on.

That should keep eagleboy happy if nothing else ^
 
Last edited:
There is so much overreaction on this thread.

One reason for that is the large amount of love for the Elite franchise in this thread too. Many players who have been here since day one, even before day one, who love exploration and really want to play the game, but just can't enjoy it anymore due to this issue. I know several posters in this thread can't fathom how that can be true, but it is. It's the reality of quite a bit of the community's feelings. While this might seem like a small issue to those who don't care much about it, it is not a small issue. No matter how much you want it to be, no matter how much Frontier might think it is, it is not.

Players are leaving the game or playing much less due to this, it is driving customers away. That translates into something that really should be a higher priority than it currently seems to be at Frontier. A lot more than "discussions on how to address this" should be happening one year after the fact. They broke it, and from the sounds of it a fix is nowhere near any kind of implementation, an entire year later. So yeah, there is some overreactions going on, but in all honesty, it's greatly justified considering how monumentally game impacting this has been for players who love to explore.
 
Whatever the case or truth is, this aint gonna get fixed anytime soon if ever...thats not 3 or 4 different answers at all. Thats one answer and its the exact thing I suspected it would be after bretts little comment about it being in the hands of QA last week. Theres literally nothing to talk about but they cant just say that outright, so they say as little as possible in the hope it just gets forgotten about.

Think back to MB post about it being worked on with no planned fix in 2.3, till last week and bretts off the cuff remark about it being in the hands of QA, only now to find out its certainly been discussed but no time soon. The usual spammed excuse, no eta no guarantee.

So no...the answer has actually become quite clear and one is much less confused now. Fear not however in that Im not gonna go off into a salt crusade on every salty thread I can find...quite the opposite actually. Think along the lines of just accepting it and moving on.

That should keep eagleboy happy if nothing else ^

The thing is, not anytime soon could mean not next week, not next month or not this year. Personally I expect the fix either with 2.4 or 3.0. You think it's years away. Both our guesses are based on absolutely nothing. There is no comment from FDEV saying it's years away and they are not saying it will be in the next update either. And yet you are almost 100% convinced that it'll be a few years until it's fixed. Based on what?!
 
  • Like (+1)
Reactions: NW3
The thing is, not anytime soon could mean not next week, not next month or not this year.
Well, with the timescales usually involved I think we can safely rule out next week and month. If it had been a candidate for the 2.4 update, it would probably be lined up for testing right now or at least be in the process of being concluded and included in some sort of roll-out scheme. Especially considering the scale and complexity, this isn't something they will cobble up in a month just before a release date. For me it makes it pretty clear we won't see the fix in the September 2.4 update. Or one close to that.

So I've interpreted Dale's post as meaning: not this year, probably part 3 at the soonest.
 
  • Like (+1)
Reactions: NW3
Back
Top Bottom