#Height of cloud layers are forced to be the same the moment you edit clouds

17 messages · Page 1 of 1 (latest)

hidden moon
#

Almost self explanatory. All bodies have this issue. Here's one: RS 0-3-397-1581-12594-2-32-271 2

This is a huge issue. You cannot edit any cloud parameters in-game without the heights of clouds all being forced to the same height. I remember reporting this back then and IIRC it's because one function call was changed in the GUI code, but I know nothing more.

timid relicBOT
#

Thank you for posting in the bug forums, centri.t4t!

Please Follow These Guidelines while reporting Bugs:

  1. Official Releases Only: Bug reports must be from the official public or Beta branch of SpaceEngine on Steam. Reports from modded or unofficial versions will not be considered. This includes 0.980
  2. Update to the Latest Version: Ensure you are using the latest version of SpaceEngine from the public branch. Update your game if necessary before reporting.
  3. Detailed Information Required:
    • Logs: Please include your se.log file located at <Steamapps>/common/SpaceEngine/system/se.log
    • Steps to Reproduce: Describe in detail the steps to reproduce the bug. Include all necessary steps to allow us to replicate the issue.
    • Screenshots: If applicable, attach screenshots or images that illustrate the problem.
  4. Hardware and Software Details: Provide your CPU, GPU, RAM, and operating system details.
  5. Check for Duplicates: Avoid submitting duplicate reports. If the issue has been reported, add to the existing thread!!!!
    Is This a request for help modding? the correct place for mod help is https://discord.com/channels/148933808811409408/1164988630671044638

Bug Report Template:

   Summary: Example issue
   Description: What is going wrong?
   Steps to Reproduce: What steps did you follow?
   Actual Result: What did you observe?
   Expected Result: What was expected?
   Reproducible: Yes/No/Intermittent
   GPU: Your GPU model
   GPU Driver: Your GPU driver version
   Version: SpaceEngine version
   Modded: Y/N 

Failure to adhere to these guidelines will result in your post being removed without warning.

hidden moon
#

this also makes haze layers on gas giants useless. please fix in this beta, it should be a 1 line change

ancient jungle
#

Thanks for reporting this. I complained about this a while ago, hoping it'd be fixed automatically with the following updates.

#

I'd like to complement the report with the fact that coverage fractions don't seem to be working for giant classes either. In other words, you cannot really create a cloudless jupiter/neptune or a one that would have some gaps between the cloud bands.

hidden moon
#

yeah that's intended, in the shader it's forced to 1 opacity

#

neat idea though, I'll check out how it looks later

hidden moon
#

doesn't work lol

ancient jungle
#

That's kind of silly, if you ask me. According to the Sudarsky classification as well as various early class brown dwarf observations, cloud coverage may not be complete. Instead it can be patchy, which is something that hasn't been emulated by any of the SE versions.

hidden moon
#

well SE assumes that the palette of the clouds will match the atmosphere in those cases

#

it doesn't make much of a difference theoretically, though in-game they'll look too dark if you try this because the default color is black instead of w/e the fog of the atmosphere would create

candid knot
#

I've logged this internally. Are there any parameters outside of just Clouds that cause this issue?

ancient jungle
#

It's just located within the Clouds tag. No matter what Height you input, the layers are still at the same altitude in the game itself.

#

Something must be up within the input-output procedure itself.

candid knot
#

(Showing my work)
From my own poking around, it appears that all these parameters cause the issue (top layer of the example planet disappears even after returning to the original value, requiring a planet restore).

ancient jungle
#

Looks like a lot...

frozen radish
#

To add onto this, the coverage of multiple layers will be locked to the last layer, even without any fiddling in the GUI