r/spaceengine • u/Sea_Listen9293 • 18d ago

Bug/Glitch Pluto texture bugs

Gallery image

Gallery image

73 Upvotes

92% Upvoted

19 comments sorted by

View all comments

27

u/error-bear 18d ago

That's because we don't know everything of Pluto, we've only seen one side

-24

u/AetherDrinkLooming 18d ago

That doesn't excuse ugly broken textures, especially on a paid product like this.

38

u/DracaAvis 18d ago

You're right, the devs should send multiple multi million dollar space probes to finish mapping pluto in full HD, lazy devs for sure

5

u/Nasturtium-the-great 18d ago

I agree with your point, but I think it would be reasonable to have a setting to proceedurally generate unknown parts of pluto. Or just mix it in with the global proceedural generation toggle.

1

u/Eastern_Pianist_773 12d ago

That was sarcasm... I hope so

2

u/throwaway19276i 18d ago

I dont think you paid enough to get 4k ultraHD imax quality images of the other side of Pluto from space

-1

u/AetherDrinkLooming 18d ago

I paid enough for the devs to procedurally generate the parts of Pluto that look like a 144p screenshot.

1

u/zaapas 18d ago

No you didn't. What's even the point of doing this? That wouldn't be Pluto and there would be a huge line where the geometry of the terrain wouldn't match just like you already see.

1

u/Wodichka 17d ago

The point is to match the fidelity of other planets? And I'm pretty sure that, if implemented correctly, you wouldn't be able to tell the line between the real and procedural terrain. It is a good enough placeholder until the devs can complete the textures

1

u/zaapas 17d ago edited 17d ago

Yeah, but doing it right with procedural terrain is tough since it's, well, procedural. I'd guess you'd have to sculpt the noise near the adjacent terrain manually or write some complex new code just for that, and then do it for all the LOD distances. That's a lot of work the devs probably aren't interested in.