A planet in the Andromeda galaxy that's very similar to Earth and where you can live underwater.

I'm from Russia, so the screenshot is in Russian, sorry. 🥲

Hey folks!

The first regular update of the year is now out on the public branch! We've been chipping away at some tricky technical issues, which will be the focus in the patch notes below. The first issue we've resolved is the "function not implemented" issue NVIDIA graphics drivers ran into while trying to record. It ended up being less of a 'fix' and more of an overhaul to our video encoders.

SpaceEngine now offers multiple codecs to cover your hardware/needs: AV1, H.264, HEVC (H.265), and SVT/AOM Software AV1. Hardware encoders are divided into NVIDIA, AMD, and Intel. See the deep dive below for more.

The second under-the-hood issue resolved in this update is our file pathing. To bring SpaceEngine more in line with common industry standards (and resolve permissions issues with not doing so), we have made changes to how and where user and cache files are stored.

When you first launch SpaceEngine post-update, the program will move your user files from their previous places in the install folder to your user Documents folder (%USERPROFILE%\Documents\Cosmographic\SpaceEngine), and create the cache in your Local AppData folder (%LOCALAPPDATA%\Cosmographic\SpaceEngine). This migrates the data specific to your install to the same home most software uses.

If you have a niche setup, encounter errors, or otherwise need to stay in the old self-contained setup, you can enter the following argument into your Steam Launch Options to launch in Portable Mode: -paths=paths-port.cfg 
(In rare cases, when SpaceEngine fails to write on launch, it will automatically request to try this method). The deep dive on these changes is below as well.

Thank you for your patience while we worked internally on these changes. We hope to be back to regularly scheduled updates soon™~

Steam link with Catalog Additions: https://store.steampowered.com/news/app/314650/view/672867776636912283

Video Encoding Changes:

A recent update to NVIDIA graphics drivers dropped support for older NVENC SDK versions, causing many users to see a "Function not implemented" error when trying to record. To fix this and future-proof for other hardware, we've updated the version of FFMPEG used by SpaceEngine and added more options for users:

• The Video Capture tool (F9 by default) now holds a host of codecs and formats to fit nearly all machines. Not all codecs work with all graphics hardware; you'll have to experiment to find what works best for your setup and needs.
  • AV1: High-end codec with good performance/quality, but requires modern GPUs (NVIDIA RTX 4000 series, AMD RX 7000 series, Intel ARC series or newer, respectively). Used for high-quality, high-resolution production or streaming.
  • HEVC (H.265): A high-quality native encoder, similarly ideal for production, but on a wider range of GPUs. May have compatibility issues with playback on some media players/devices.
  • H.264: Default for the average user. This should work on most manufacturer-supported GPUs.
  • SVT/AOM Software AV1: Compatible with all machines, but they use the CPU to record. SVT prioritizes performance, while AOM prioritizes quality. These are often considered a last resort for those without hardware encoding support. Users who relied on VP9 may want to switch to this codec.
  • Hardware encoders further specify NVIDIA, AMD, and Intel Hardware options. If you attempt to record with an incompatible codec, SpaceEngine will output an error and fail to record.
• There are now two modes to choose from before capturing. You'll need to experiment to find what works best for your project:
  • Offline rendering (Fixed FPS): Enter a target frame rate, and SpaceEngine will throttle itself to guarantee that frame rate in the final output.
    • Added a new 'Asynchronous loading mode,' which will use the full multithreading capabilities of the engine to improve performance, but may show the loading/generation process in the final video.
  • Streaming (Real-Time): Captures the raw, real-time output of the SpaceEngine window. You can set a framerate limit with or without Vsync if desired. Output quality is heavily influenced by your bitrate preset and will ignore custom values.

File Path Changes:

To bring SpaceEngine in line with industry standards, we have made changes to how and where SpaceEngine stores user and cache files. This is a more technical deep dive; the quick-and-dirty of what you need to know is in the foreword above.

When you first launch post-update, SpaceEngine will detect and move or create files as follows. In the unlikely event SpaceEngine fails to write during this process, it will abort launch and request to launch with the old file paths (Portable mode).

• The cache (models, shaders, filesys) will be created at %LOCALAPPDATA%\Cosmographic\SpaceEngine. The existing cache in your install folder will be deleted.
  • If you swap to a pre-0.991.50 version or launch in Portable mode, the cache will be rebuilt in its old location, then deleted again when you return.
• Save data is now stored at %USERPROFILE%\Documents\Cosmographic\SpaceEngine. The save-user.cfg and places-user.cfg files go into a 'save' folder, while all other personal .cfg files (i.e., keybinds) go into the 'config' folder. On boot, if no save data is found in this filepath, SpaceEngine will search the Steam install for existing save data, moving any it finds to the new location. For any file it can't find, new files will be generated.
  • Default .cfg files, such as graphical presets, will stay in the Steam install folder. These are not meant to be edited by the user and are restored anytime SpaceEngine updates.
  • When you swap to a build older than 0.991.50 or launch in Portable mode, your save will appear to have been wiped, as it is reading from the Steam install config folder again. To restore it,  copy or move the .cfg files from the config and save folders in the new filepath back to the config folder in the Steam install. This will overwrite the blank save. Per the new boot logic, if you move the files, they will be moved back when you return to the new file pathing. If you copy them instead, you will effectively now have separate saves for either side of that breakpoint that do not interact. It is recommended that you make a backup of your SpaceEngine data before doing this.
• All future exports, logs, screenshots, and videos will appear in the %USERPROFILE% filepath in corresponding subfolders. Existing media files (or any media files generated in older versions) will remain in their original places.
  • Logs, such as your se.log, now generate in their own 'logs' folder.
  • All forms of screenshots, videos, and exports populate to similarly named folders.
  • For PRO users, the Camera Path Editor now opens %USERPROFILE%\Documents\Cosmographic\SpaceEngine\addons\scripts by default when you try to Save or Load a spline path. For old path files, you will need to manually navigate to the old folder in the SpaceEngine Steam folder each time, or move old content to the new location.
• Scripts, catalogs, textures, pak files, and other addon files can now be searched for at three locations: The original locations of SpaceEngine\data and SpaceEngine\addons in the SpaceEngine Steam folder, as well as %USERPROFILE%\Documents\Cosmographic\SpaceEngine\addons. It is recommended to use the third location for ease of use.
• If you are a mod/addon maker, you must manually move SpaceEngine\workshop\projects to %USERPROFILE%\Documents\Cosmographic\SpaceEngine\workshop\projects for your projects to appear in the Workshop Config tool after this update. Content paths can stay as-is, but if you change them to accommodate the modified workflow (i.e., you store your content in the workshop folder), remember to update the filepath in the tool as well.
  • If you choose to operate in Portable mode, the tool will read from the original projects location.

To facilitate both the new file paths and the Portable mode failsafe, SE now has two sets of ‘folders.cfg’, called paths-def.cfg and paths-port.cfg.These live in the same location of the system folder in your install.

• The paths-def config holds all the file paths defined above, while paths-port holds the old ones that kept everything in the install folder, identical to previous versions of SpaceEngine.
• When SE launches, it will always try to write according to paths-def first. If it encounters issues at any point in the launch process (fails to create a folder/file), it will abort the process, post an error, and then request to re-launch itself using paths-port.cfg.
  • If you have a strong preference for the old file format (or low space in your default user location), you can opt to use paths-port.cfg first by inserting the following argument into your Steam launch options: -paths=paths-port.cfg.
    • Access this by right-clicking SpaceEngine in your Steam library, clicking 'Properties', and entering the argument in the text field under 'Selected Launch Option'.
    • If you already have save/config data moved to the default user location, it may not migrate back on its own. You will need to visit %USERPROFILE%\Documents\Cosmographic\SpaceEngine and move your config/save files back to your Steam install’s config folder (you can open a Support ticket if you need help; we will be happy to assist!).
  • For advanced users, you can make your own file path config by copying either config file, giving it a new name, and using the above launch argument with that new file name in place of ‘paths-port.cfg’.
    • While you can edit either default config directly, it is not recommended, as they may be overwritten and returned to default in a future patch
    • By using a custom file path config, there is a risk of errors and instability. Only do this if you are confident in working with Windows file paths. A separate guide will be made to cover the nuances of file pathing.

Changelog:

• Pressing the Screenshot button on the magnitudes toolbar no longer opens the screenshot folder. You must now shift + click to do so (the tutorial has been updated to reflect this)
• Disabled the normal functions of edit mode keys while in edit mode, so you can focus on editing
• Added new splash screen images and quotes
• Added new Featured Locations from the 0.991 Featured Locations Contest
  • Note: Due to catalog updates, some Locations were altered or removed during implementation. All original submissions can be found in the contest-07-archive channel in our Discord
• Added Tarantula Nebula with custom model
• Added VFTS 234 (binary system with quiet black hole)
• Added 16 new LMC globular clusters
• Added LMC open clusters NGC 1850A and H88 301
• Added globular cluster NGC 1049
• Added Wolf-Rayet binary R145
• Added 42 new ultra-cool dwarfs with rotation periods, added another 24 rotation periods to existing ultra-cool dwarfs
• Updated the exoplanet catalogs with 66 new host stars and 93 new planets, six brown dwarf candidates
• Added one new small moon of Uranus (S|2025 U 1)
• Added 11 new moons of Saturn
• Added triple quasar system LBQS 1429-0053A/B/C
• Added 25 new binary asteroids and one satellite of Quaoar
• Added Betelgeuse companion star, Siwarha (While Siwarha is still somewhat contested, recent evidence heavily favors its existence)
• Added RR Lyrae name to HIP 95497 and updated its spectral type
• Added Gaia designations for 107,567 stars
• Fixed dozens of galaxies in the Virgo and Fornax clusters
• Improved orientation of all Messier galaxies
• Improved several Local Group galaxies
• Improved rendering of elliptical galaxies
• Fixed parent galaxy of Fornax A*
• Updated the distance and spectral type of x Carinae
• Updated orbital information for asteroids Salacia and Actaea
• Updated the spectral type and other parameters of WOH G64
• Improved position/size/orientation of LMC
• Improved the HIP 81208 system
• Removed refuted planets Fomalhaut b and 42 Dra b
• Removed duplicate of planet CFHTWIR-Oph 98 A b
• Fixed an issue where planets 55 Cancri B b and 55 Cancri B c orbited the planet 55 Cancri A b instead of the star 55 Cancri B
• Fixed a bug where planet temperatures displayed in the Solar System Browser changed when entering Chart Mode
• Fixed Location thumbnail fitting method on ultra-wide displays (shown on-screen during pre-loading)
• Unlinked scrollbars in the Locations menu; this fixes an issue where one tab could appear empty after scrolling too far on the other
• Improved the Planetarium Tutorials with updated language and fixed multiple progression stops
• Wireframe in the nebula editor now works outside of debug mode
• Replaced ‘folders.cfg’ with two file path configs: paths-def.cfg for the new file paths and paths-port.cfg for the old ones
  • In rare cases, when SE fails to launch with the new file paths, it will request to use the old ones (paths-port.cfg) as a failsafe
• Added a new launch argument, ‘-paths=’ to support opting in to paths-port.cfg if desired