General suggestions for SpaceEngine

29 Oct 2016 04:45

Here you can post your suggestions.

02 Nov 2016 17:52

(Repost from old website)
Ok, I've been thinking about this for a while, but have never actually said anything about it. It would be really cool to be able to take samples from a planet. When on a planet's surface, you can take a same of the ground. Then a window would pop-up similar to the Wiki and would have information about the same such as chemical composition, temperature, density, and conductivity just to name a few I would imagine planets with life would have more frequent organic compounds. You could also do this for atmospheric samples and if you're underwater, liquid samples. This could add a new layer of complexity to planets and would be a major step to making a space adventure/science game. Further down the road, you could have conditions in outer space based on simulated space weather.

Lucas0231 · 03 Nov 2016 04:34

I have a idea, the chemical composition of oceans

Ex :

    Ocean
    {
        Height          9
        Hapke           0
        SpotBright      2
        SpotWidth       0.20
        DayAmbient      2

             Composition
             {
             H2O       97
             NaCI      1

             }
    }

04 Nov 2016 23:29

I have 2 ideas:
Add MassMoon parameter for the moons, this is the mass of the object in Moon masses,
Add DistKm parameter for moons, this is the distance from its parent object in kilometers|DOT|
Example:

Moon "Name"
{
  MassMoon 1.3
  DistKm  140443
}

Quarior · 05 Nov 2016 08:07

MatsoftwareAtHereToo wrote:
I have 2 ideas:
Add MassMoon parameter for the moons, this is the mass of the object in Moon masses,
Add DistKm parameter for moons, this is the distance from its parent object in kilometers|DOT|
Example:
Code: Select all
Moon "Name"
{
  MassMoon 1.3
  DistKm  140443
}

Otherwise, instead of DistKm, I think that SemiMajorAxisKm it is best suited. After also do with MassJupiter, the mass of the object in Jupiter's mass and otherwise MassKg, the mass of the object in kilogram. Also can be done with the radius.
Example :

Planet "Jupya"
{
 ParentBody "Stellya"
 Class "GasGiant"
 MassJupiter 1.73
 RadJupiter 1.73 //or RadiusJupiter

 Orbit
 {
  SemiMajorAxis 0.74 //AU
 }
}

Moon "Jupya 1"
{
 ParentBody "Jupya"
 Class "Selena"
 MassMoon 4.27
 RadMoon  2.62 //or RadiusMoon

 Orbit
 {
  SemiMajorAxisKm 745213.22
 }
}

DwarfMoon "Jupya D1"
{
 ParentBody "Jupya"
 Class "Asteroid"
 MassKg   4.23e+17
 Radius   4.37

 Orbit
 {
  SemiMajorAxisKm 842629.69
 }
}

05 Nov 2016 10:35

Quarior wrote:
MatsoftwareAtHereToo wrote:
I have 2 ideas:
Add MassMoon parameter for the moons, this is the mass of the object in Moon masses,
Add DistKm parameter for moons, this is the distance from its parent object in kilometers|DOT|
Example:
Code: Select all
Moon "Name"
{
  MassMoon 1.3
  DistKm  140443
}
Otherwise, instead of DistKm, I think that SemiMajorAxisKm it is best suited. After also do with MassJupiter, the mass of the object in Jupiter's mass and otherwise MassKg, the mass of the object in kilogram. Also can be done with the radius.
Example :
Code: Select all
Planet "Jupya"
{
 ParentBody "Stellya"
 Class "GasGiant"
 MassJupiter 1.73
 RadJupiter 1.73 //or RadiusJupiter

 Orbit
 {
  SemiMajorAxis 0.74 //AU
 }
}

Moon "Jupya 1"
{
 ParentBody "Jupya"
 Class "Selena"
 MassMoon 4.27
 RadMoon  2.62 //or RadiusMoon

 Orbit
 {
  SemiMajorAxisKm 745213.22
 }
}

DwarfMoon "Jupya D1"
{
 ParentBody "Jupya"
 Class "Asteroid"
 MassKg   4.23e+17
 Radius   4.37

 Orbit
 {
  SemiMajorAxisKm 842629.69
 }
}

Okay, but SemiMajorAxisKm maybe too long, I think, the DistKm is better[DOT] What do you think about MassMoon?

05 Nov 2016 11:46

For the next patch, fixing the antennae galaxies would be nice.
Currently, they aren't actually connected.

But with the editor I was able to make them connected.

Hopefully, this can be a quick fix

Quarior · 05 Nov 2016 14:24

MatsoftwareAtHereToo wrote:
Quarior wrote:
MatsoftwareAtHereToo wrote:
I have 2 ideas:
Add MassMoon parameter for the moons, this is the mass of the object in Moon masses,
Add DistKm parameter for moons, this is the distance from its parent object in kilometers|DOT|
Example:
Code: Select all
Moon "Name"
{
  MassMoon 1.3
  DistKm  140443
}
Otherwise, instead of DistKm, I think that SemiMajorAxisKm it is best suited. After also do with MassJupiter, the mass of the object in Jupiter's mass and otherwise MassKg, the mass of the object in kilogram. Also can be done with the radius.
Example :
Code: Select all
Planet "Jupya"
{
 ParentBody "Stellya"
 Class "GasGiant"
 MassJupiter 1.73
 RadJupiter 1.73 //or RadiusJupiter

 Orbit
 {
  SemiMajorAxis 0.74 //AU
 }
}

Moon "Jupya 1"
{
 ParentBody "Jupya"
 Class "Selena"
 MassMoon 4.27
 RadMoon  2.62 //or RadiusMoon

 Orbit
 {
  SemiMajorAxisKm 745213.22
 }
}

DwarfMoon "Jupya D1"
{
 ParentBody "Jupya"
 Class "Asteroid"
 MassKg   4.23e+17
 Radius   4.37

 Orbit
 {
  SemiMajorAxisKm 842629.69
 }
}
Okay, but SemiMajorAxisKm maybe too long, I think, the DistKm is better[DOT] What do you think about MassMoon?

Else, SemiMajorAxis in "faster" SMA and for SemiMajorAxisKm SMAKm and you idea about MassMoon is good and I have use in my example.

05 Nov 2016 14:47

MatsoftwareAtHereToo wrote:
I have 2 ideas:
Add MassMoon parameter for the moons, this is the mass of the object in Moon masses,
Add DistKm parameter for moons, this is the distance from its parent object in kilometers|DOT|
Example:
Code: Select all
Moon "Name"
{
  MassMoon 1.3
  DistKm  140443
}

I'm inclined to think it would even be called Lunar Mass ("LunarMass"). No?

Juxlos · 05 Nov 2016 16:07

Maybe MassLuna then?

Moon "Name"
{
  MassLuna 1.3
  SemiMajorAxis  140443
}

since that's how it's already been written and I don't see why satellites should get special treatment in orbit.

I'm thinking geological factors like plate tectonics would be nice, although I'm pretty sure it'll be quite tricky to implement and it probably doesn't do much visually.

05 Nov 2016 23:31

Proteus wrote:
MatsoftwareAtHereToo wrote:
I have 2 ideas:
Add MassMoon parameter for the moons, this is the mass of the object in Moon masses,
Add DistKm parameter for moons, this is the distance from its parent object in kilometers|DOT|
Example:
Code: Select all
Moon "Name"
{
  MassMoon 1.3
  DistKm  140443
}
I'm inclined to think it would even be called Lunar Mass ("LunarMass"). No?

MassMoon is better[DOT] I want that my ideas for SE be in SE

05 Nov 2016 23:37

Juxlos wrote:
Maybe MassLuna then?
Code: Select all
Moon "Name"
{
  MassMoon 1.3
  SemiMajorAxis  140443
}
since that's how it's already been written and I don't see why satellites should get special treatment in orbit.

I'm thinking geological factors like plate tectonics would be nice, although I'm pretty sure it'll be quite tricky to implement and it probably doesn't do much visually.

I want MassMoon, I think it is better

05 Nov 2016 23:43

Quarior wrote:
MatsoftwareAtHereToo wrote:
Quarior wrote:
Otherwise, instead of DistKm, I think that SemiMajorAxisKm it is best suited. After also do with MassJupiter, the mass of the object in Jupiter's mass and otherwise MassKg, the mass of the object in kilogram. Also can be done with the radius.
Example :
Code: Select all
Planet "Jupya"
{
 ParentBody "Stellya"
 Class "GasGiant"
 MassJupiter 1.73
 RadJupiter 1.73 //or RadiusJupiter

 Orbit
 {
  SemiMajorAxis 0.74 //AU
 }
}

Moon "Jupya 1"
{
 ParentBody "Jupya"
 Class "Selena"
 MassMoon 4.27
 RadMoon  2.62 //or RadiusMoon

 Orbit
 {
  SemiMajorAxisKm 745213.22
 }
}

DwarfMoon "Jupya D1"
{
 ParentBody "Jupya"
 Class "Asteroid"
 MassKg   4.23e+17
 Radius   4.37

 Orbit
 {
  SemiMajorAxisKm 842629.69
 }
}
Okay, but SemiMajorAxisKm maybe too long, I think, the DistKm is better[DOT] What do you think about MassMoon?
Else, SemiMajorAxis in "faster" SMA and for SemiMajorAxisKm SMAKm and you idea about MassMoon is good and I have use in my example.

Ok, SMAKm can be used, RadMoon parameter is also good

06 Nov 2016 19:24

Suggestion: If I'm in normal camera mode and travelling at whatever speed I am, if I switch to modes 2 or 3 while moving, it should switch seamlessly without stopping, so that it's still going and when I let off of the movement button(s), it continues going at that speed but now goes by the camera's inertial rules of that mode. I'm also thinking that optionally, if I switch back to mode 1 while holding direction, that it does the same until I let off the directional keys. With this kind of seamless mode change, it would give a great deal more control over movement between instant and smooth/cinematic.

10 Nov 2016 11:59

Another suggestion: An option (able to be toggled on or off), for automatic dynamic speed adjustment according to how close/far from a surface you are. The threshold of distance before it kicks in, as well as the minimal speed reached, could be changed with a slider or numerical value. This way, we can have fine control over when we wish to manually fly down into an atmosphere with the camera and won't have to worry about slamming violently into the surface but have a nice fluent movement over its surfaces.