Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP - Terrain texturing #3453

Closed

Conversation

fluffyfreak
Copy link
Contributor

Well here's some updated and Textured Terrain to wet your appetites.

Things to do... many:

  • Determine the max terrain height, approximately anyway (currently mul'd 277.0f).
  • Fix the water and lava rendering somehow.
  • Generate the texture array for a planet.
  • Improve the input data used to lookup the texture.
  • Use a different Lookup texture for each planet type (generated?).
  • Get some better textures!
  • Make a better lookup texture!
  • Document it all.

This destroys the terrain colour noise stuff and replaces it with terrain texturing based on the slope and height of the terrain.

It currently uses a choice of 16 textures, which are actually sourced from just 4 originals and duplicated whilst I'm developing it.

Since we'll be texturing whole planets it seems silly to keep the detail texturing optional, so I'll also be removing that option and it will always be there.

Andy

@impaktor
Copy link
Member

Neat. Looking forward to this.

Regarding your question on IRC, JohnJ (creator of JJFFE) replied:

<JohnJ_> <FluffyFreak> I have a question, how can I guess at the maximum 
         height of the terrain for a planet?                    [01:58] 
<JohnJ_> If it's noise-based then you can do a probability maximum.

Also, for the RSS issue, I'd contact github support. Could it have something to do with you using windows? I'm not sure what else differentiates your setup with the rest of the devs.

@fluffyfreak
Copy link
Contributor Author

@impaktor if it were just noise that might be possible, but there's a lot of logic and some really stupidly bizarre other maths in there tied into it.
I think sampling of some form is going to be the most reliable way and hopefully won't be too expensive to process.

…nto terrain-texture-arrays

Conflicts:
	data/shaders/opengl/geosphere_terrain.frag
…nto terrain-texture-arrays

# Conflicts:
#	data/shaders/opengl/attributes.glsl
#	src/graphics/Types.h
#	src/graphics/VertexArray.cpp
#	src/graphics/VertexArray.h
#	src/graphics/opengl/RendererGL.cpp
#	src/graphics/opengl/VertexBufferGL.cpp
@fluffyfreak
Copy link
Contributor Author

Going to close this since i have plans for terrain stuff, might as well leaved it alone until they're done and supercede this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants