Trying to explain SFS's planet data parameters

[Altaïr]

Yeah, that's an error of my part haha... Altaïr Mind changing that R to 2πR cause i keep failing geometry classes?

Sure. It's done.

 

[Axiom]

Another Weird Question, but is it possible to view text heightmaps as images?

 

[Altaïr]

Another Weird Question, but is it possible to view text heightmaps as images?

You can, using a spreadsheet, copying the data in it, and plotting a graph from it. That's what I used sometimes.

 

[Axiom]

ok, thanks!

Edit: New problem, when I try to make a graph out of the crater edge heightmap in sfs, it gives me this instead if anything resembling a graph:

Edit 2: it was because of the commas making excel read it as text

 

[Axiom]

So what are these heightmaps used for? Like these don't look like terrain (like at all).

These are recreations of the terrain in Excel

 

[mariohobbs]

So what are these heightmaps used for? Like these don't look like terrain (like at all).
These are recreations of the terrain in Excel

Its most likely from the scale of your x-axis, since the X and Y don't seem to be the same as in game.

 

[Axiom]

So There's 2 types of these mystery heightmaps:
Theres the plains one which always has a displacement of one. And then theres the 'Curve' Family of heightmaps which appears later in the heightmap code.

I think that the former is used to only have certain heightmaps in certain places. And the latter is used to modify the heightmap (how this works is still a mystery.

This is Deimos, this has the Curve6 and Curve7 heightmap modifiers

This is Europa, this has the Pow3 modifier

This Ganymede, this has the Curve8 modifier. The whole reason why I think these are modifiers as the terrain on Ganymede is more pointy than the perlin heightmap would suggest

This has the Mercury_Plains heightmap. I think that it sets which parts have the heightmaps and which parts don't as:

1. It is the size of the entire planet
2. The heightmap itself is all ones apart from 2 sections which are zeros. I think the heightmap is making it so the other heightmaps don't apply in Mercury's landmarks
3. It starts with the phrase 'PLAINS' rather than output, and one of the other parameters in the other heightmaps is PLAINS

This is the Moon, has the same Plains Heightmap

This is Phobos, it has the Curve4 modifier

This is Mars, has the plain heightmap

This is Venus, It has the Venus_Plains thing and also has the Curve1 modifier. This is further evidence to for my theory that it's some sort of modifier as there aren't any heightmaps that make Venus' volcanoes

I might take this to the discord to be honest

Edit: According to discord I'm right:

This will be really useful actually

 

[zTallsRobot]

I wonder why terrain textures in realistic mode (Mars and earth for example) are buggy as hell. Because they look so stretched at the point they look pixelated, and you can't even land on some parts on Maxwell montes's top, because it doesn't collide with the surface. How do I fix it??

 

[Axiom]

I don't know for sure, for your first issue maybe just make new, more detailed surface textures? (or just change the X of the surface texture to be smaller). For issue 2 maybe remake the heightmap witha different Maxwell Montes?

 

[floatingfuel]

Let me jump the topic for a moment, which parameters can be scaled by difficulty?

Also, to apply scaling to a parameter, should one just add <parameter's name>scaleDifficulty;{......}?

 

[Axiom]

which parameters can be scaled by difficulty?

So SMA and stuff to do with the atmosphere

Also, to apply scaling to a parameter, should one just add <parameter's name>scaleDifficulty;{......}?

You do this:

This is a segment from TTSS from Flight Russian Man

Edit: to change topic again can anyone explain why the planet below doesn't work?

Edit 2: I now know what was happening, it was because ZArchiver was creating a random string of curly brackets at the end of the file whenever I saved it, do you guys know any good file editing software for Android? I use quickedit but it can't view images