Please post here all of your reports about bugs or crashes in SpaceEngine. Before you post any bugs, please follow these steps:
First of all, make sure you make a clean install of SpaceEngine and update your video card drivers. This may solve 99% of all isues.
Read the Fixing common issues section below. It is possible that your problem can be solved there.
Read the List of known issues section below and make sure that your bugs are not on in it. You can use your browser's word finder to help search the list.
If the bug is not on the list then please post it in this thread. Attach to your message a screenshot (if possible) and a log file (it's called the se.log and is located in the SpaceEngine/system/ directory). Only the log file will help us to understand your problem and find a solution!
Fixing videocard-specific issues
If you do not know which videocard do you have, open the system/se.log file in the text editor and read the Vendor information in the beginning:
INITIALIZING OPENGL [MT] Vendor: ATI Technologies Inc.
Then look for a solution for you:
Nvidia: Major lag spikes
To prevent major lags with Nvidia, go into Nvidia control panel, and in SpaceEngine's profile set Threaded optimization to off.
ATI/AMD: Transparent or invisible planets, no landscape
ATI/AMD: Crash on approaching to the black hole, neutron star or white dwarf, on using ship's hyperdrive, or when enabling the Oculus Rift mode or the Fish Eye mode
First, try the solution in in the previous paragraph. If this didn't help, open config/user.cfg and change this parameter value to false, so that it looks like this:
EnableMipmapsWarp false // use mipmapping for warp effects rendering
If crashes on enabling the Oculus Rift mode or the Fish Eye mode still remains, change these two parameters to false as well:
EnableMipmapsGUI false // use mipmapping for GUI FBO EnableMipmapsFrame false // use mipmapping for scene FBO
Intel HD: Glitchy landscape and textures on planets
Open config/main.cfg and change this parameter to 13:
PlanetHeightmapFormat 13 // format of the terrain heightmap textures: 13 - R32F, 16 - RGBA32F
If this didn't help, open config/user.cfg and change this parameter to true:
- "Error loading surface generator shaders. Press YES to run program with procedural planets disabled. Press NO to exit"
Download and install latest drivers for your video card. If you still get this message, it could be that you have an incompatible video card (see next paragraph).
But you still can try and run SpaceEngine by disabling checking of critical errors at startup. Open main.cfg and change value of this parameter to 'true':
IgnoreCriticalCheck true // ignore checking of OpenGL version and critical extensions supporting
NOTE: I can give no guaranties that SpaceEngine will be stable and work correctly if you do make this change.
If you have an "Error loading surface generator shaders" error and press Yes, SpaceEngine can run, but it will not be able to render procedural planetary landscapes.
After updating or rollback of the drivers, you must delete the cache folder in the SpaceEngine directory.
2) Weak system
Most of the forum posts I receive are from users that report an inability to start SpaceEngine, This is because those users have inbuilt Intel graphics card, or some old GeForce 5700 series, or not a proper "gaming" laptop. There is no way but to update your hardware system. There are no plans to make a second version of the engine for weaker systems with simplified graphics, CPU texture generation, etc. It would be like coding another engine from scratch. Once again, I would remind everyone that the minimum system requirements can be found on the Home page, but I will mention it here as well:
CPU 2.0 GHz RAM 2 GB Video GeForce 8600, Radeon HD 2600 VRAM 512 MB
I stress the special role played by videocard onboard memory (VRAM). 512 MB is the absolute minimum. The engine uses a large amount of data that must be in video memory (textures, meshes, vbo, etc). If your system meets the recommended requirements, the engine will work, because its development is made for this hardware:
CPU 3.0 GHz RAM 4 GB Video GeForce 9800 GTX, ATI Mobility HD 5730 VRAM 1024 MB
If you have a Intel HD graphics card, it is better to disable asynchronous loading in the main.cfg as well:
3) System with hybrid graphics (NVidia/ATI + Intel HD)
If you're running SE on a laptop with dual graphics, make sure SE runs on NVidia or ATI chip instead of Intel HD. You may see it in the beginning of "SpaceEngine/system/se.log" file. If it says: Vendor: Intel Renderer: Intel® HD Graphics 4000
then you should open Nvidia Control Panel or ATI Catalyst and force SpaceEngine.exe run on NVidia/ATI graphics card. If you do not found SpaceEngine profile there, create a new one.
4) Artifacts on procedural planets
If you get missing landscape blocks, blurry or blinking textures, random spikes sticking out of surface, check out these recommendations here:
a) If you have a laptop with hybrid graphics, read item #3.
b) Make sure that you make a "clean" installation of SE. If you install a new version overwriting the old one, you may get many bugs and glitches. If you get some glitches after the patch is installed, remove the folder called cache from SpaceEngine's directory.
5) Frequent crashing while generating planetary surface
If you have frequent crashes on planets, or get an "OUT OF MEMORY" message on screen, or "Unexpected deleting of child node" in the log file, try taking these steps first:
- Close any other programs that can consume the video memory (games, video players, graphics editors, etc.). SpaceEngine is not a small flash type game, video memory is the most important resource for it. It may help to disable the Windows Aero theme too, as it consumes a lot of video memory. - Disable "3D water" in Graphics settings (Ctrl-F4) - Reduce "Landscape LOD" to -2 in Graphics settings (Ctrl+F4) - Set up the amount of video memory in the main.cfg file:
VideoMemorySize 2048 // video card onboard memory (VRAM) in megabytes
The value must not be less than 1024, but not more than the total amount of physical video memory plus amount of RAM. For example, if you have a graphics card with 1024 MB of video memory, and more than 2 GB of RAM, you can increase VideoMemorySize to 2048.
6) Spaceship disappears when far from a star
It is not a bug. Current version have not yet completed spaceships rendering system - they cannot be rendered if there is no stars or planets in the renderlist. Just imagine that ship becomes invisible in interstellar flight
7) Blurry textures on Solar system planets
It is not a bug. Our Solar system planets (Mercury, Venus, Earth, Moon, Mars, Jupiter, Saturn, Uranus, Neptune and its satellites) have no procedural textures, only real ones with limited level-of-detail. You can download addons with high resolution textures to increase level of detail of real planets.
8) Crash on entering the Display menu
If you experience a crash when trying to open the Display menu, open config/main.cfg and change the Maximized parameter value to true, so that it looks like this:
Maximized true // start with a maximized window
9) Problems with very high resolution displays
If you're using a very high display resolution and have problems selecting things with the cursor, or your screenshots are being output at a lower resolution than you're using, try the following:
1) Open Windows Control Panel, navigate to Display, and set the DPI scaling to "Smaller - 100% (default)" - it should look like this.
2) If you want to adjust the DPI scaling, click on "Set custom text size (DPI)" in the sidebar and change its value to suit your preference.
List of known issues
Green items have been fixed for the next release
Not real bugs, but effects caused by limitations in the engine:
- Star mode "points" and "sprites" looks the same. This is right! This switch changes the rendering technology, not the visual appearance. - Ships do not render in interstellar space - Star catalog has many errors in star classification, so there are many "giant dwarfs" and "dwarf giants" - Many real binary stars rendered as single, and many single rendered as binary - SE simply have incomplete catalog of binary stars - Comet nucleus star-sprite will shine through planets [example]. - Galaxy/nebula sprites will rotate when seen from certain angles - Skybox edges are visible when near the center of galaxy - Auroras, comet tails and rings can be rendered in front of ships/moons sometimes - Lens flares are distorted by gravitational lensing (black holes and ship warp drive effect) - Text editor for Wiki descriptions is not working - it is not implemented yet - Solar system moons don't have extremely accurate orbits (requires implementation of custom orbit models, e.g. VSOP-87) - Sunspot distribution is not always realistic - Ocean tag not yet implemented in planet editor - Rounding errors (e.g. 30° in catalog rounds to 29°59'59.99" displayed on HUD) - "Normal" autoexposure mode is unfinished - Bloom effects from the bottom of the screen are replicated at the top of the screen in anaglyph mode - Many HIP and HD stars do not appear in the search menu
Real bugs:
- Inaccurate tidal heating calculations, makes some moons too hot (e.g. asteroid Dactyl) - Crash when entering the Display menu for users with single-monitor setups - Does not work in Windows XP - Menu button sound doesn't work - Lens flare color in Normal or Super diffraction spike mode is inaccurate when close to a star - Changing "modes" between simulation and orbital when piloting ships can cause glitches - Few issues with asynchronous loading (stars don't always generate properly, especially when flying to new galaxies) - Flashing landscape LOD on a planet when Wiki for it is displayed - GUI response issues with some users (interface items glitchy or not respond easily) - GUI toolbars may completely disappear when pressing pin button while half-hidden - Flickering flare color in close binary systems [example] - Auto-exposure does not react when a sun is blocked while diffraction spikes are set to normal or super - "Eclipse bug" on distant planets (weird dark shimmering on outer planet caused by inner planet crossing the sun or two suns eclipsing) - Cloud cyclones have cut edges sometimes - Level horizon command (End key) doesn't work properly on oblate objects - Problems when releasing Left + Right click - Lines or junctures are visible on planetary surface - Switching to fullscreen doesn't work sometimes - Weird behavior of movement keys in tracking mode (T) and after releasing it - Automatic reference object setting with spacecraft doesn't always choose the best object (for example, when near dwarf moons or debris asteroids close to a planet you are trying to orbit) - 3D water fog sometimes starts above the water surface - Problems with the skybox export interface, and with the planetarium after using it, for some users - Music player will unpause when SE window is minimized and restored, or when entering and exiting the main menu - If a galaxy model is selected, the camera is not following any object, and the program is in Edit Mode, closing and restarting the program will cause the WASDRF movement keys to behave incorrectly until the camera is set to follow an object - Visual atmosphere heights are inconsistently and unrealistically generated - Physical atmosphere properties are inconsistently and unrealistically generated, and are not tied to the visual models - Cyclones are not generated in the southern hemispheres of gas giants - Shimmering bloom splotch when very close to the surface of a planet [example] - Lighting errors in system browser when viewing from outside the system - "Opacity spot" in the subsolar region of atmospheres - Strange behavior of fish eye and cube map views when near planets (only when a planetary object is in the neg_z face) - Only one planetary nebula model is used per galaxy - Camera will be set to 90° FOV when returning from fisheye or cubemap view sometimes - If spacecraft .sss Length is very different from its .cfg length, there may be rendering glitches - Eclipse shadows on atmosphere not occluded by planet [example]
I have just had Windows 7 Professional 64 bit installed on a Dell Precision T3500 with 21GB of RAM, W3530 Xeon 3GHz quad core processor, with an NVIDIA FX 4800 graphics card. I am using a 1028*768 screen mode.
I have installed the latest drivers from the NVIDIA site, well one of the many drivers possible, and I have just installed space engine 0.9.7.2 and it didn't even start and Windows reported that it "had stopped working" with the following error info
Problem signature: Problem Event Name: BEX Application Name: SpaceEngine.exe Application Version: 0.9.7.2 Application Timestamp: 549da900 Fault Module Name: SpaceEngine.exe Fault Module Version: 0.9.7.2 Fault Module Timestamp: 549da900 Exception Offset: 000abcc2 Exception Code: c0000417 Exception Data: 00000000 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 2057 Additional Information 1: 3cc3 Additional Information 2: 3cc3e5e140f18763c6f3bd3e34639414 Additional Information 3: b7d9 Additional Information 4: b7d9da6ecd26bf9014f7664e01e55a0a
There doesn't seem to be an se.log file in my spaceengine/system directory
I am new to Windows 7 so I may not be familiar with all of the security/admin issues.
Having installed version 0.9.7.2, the only problem I have is textures for planets, moons, and stars not rendering at all, or rendering incorrectly. (transparent, surface glitches) Link: http://imgur.com/a/cCqPU.
Afterwards, I put the atioglxx.dll file into the system folder, just as the videocard issues page said to do with ATI graphics. Only when I booted up the game after that, Windows told me it stopped working. Link: http://imgur.com/Swndwa9
I also can't seem to find a log file in my system directory.
I eagerly await your reply and method for fixing both these issues.
Added (28.11.2015, 05:00) --------------------------------------------- Here is a better link for my texture errors: http://imgur.com/gallery/nopM9/new
My specs: AMD Athlon II X4 640 Processor: 3.00 GHZ. 6.00 GB of RAM(5.75 usable) OpenGL: 3.3 Graphic card/driver: ATI Radeon HD 4200, Total Memory; 2943 MB. Dedicated Video Memory: 256 MB OS: Windows 7 Home Premium(64 bit)
I installed version 0.9.7.2 to my desktop. Having done some troubleshooting on my own, I removed the atioglxx file from my system directory and the game loaded just fine.
All I have to fix now are the planet, moon, and star shaders. Another link: http://imgur.com/wSzUqQx
Keep in mind, these specs could play 0.9.7.1 with no problems other than lag which could be managed. I wanted to update so I could have lava flows and better star rendering.
I have a problem with textures in the game, loaded all the files from the Addons Earth - Earth (11.5 Gb) and placed in the directory SpaceEngine / textures / planet / Earth. Play game and on Earth my textures look weak and are very blurry, like in the pictures.(The same problem is with version 0.9.7.2, 0.9.7.3 My computer is good Phenom 4 core 3.5 GHz, 12 GB RAM, GTX 660 (3 GB VRAM) Please help my why teddy bear going on in the game :( Regards
There he writes that you can download HD textures, textures downloaded and I still have such a poor image in the game. My photos are uploading HD textures (Earth 11.5 gb)
And whether a change to an older version can help and textures then upload to game ? What could be the reason that the texture does not want me to work in the game...
Hello there :3 So recently I have updated my GPU drivers, and now Space Engine is pretty much unplayable. Let me describe the issue in more detail: I have an HD6850 GPU with 1 gig VRAM, and couple months ago I had Catalyst 14.4 and was playing Space Engine on LOD 2 just fine. Planets took about 30 sec to load, but that's fine for taking screenshots and such. Now I have Catalyst 15.7 (driver version 15.2) and I have a good ol' infinite loading and a crash after staying on a planet for 5 minutes or so. Rest of my PC specs are as follows: Phenom X3 2.3GHz Windows 8 8 gigs of RAM (4 physical, 4 pagefile). Pretty much only things that have changed since I had no issues with SE are: driver version (from 14.4 to 15.7) and pagefile size (from 2 gigs to 4 gigs). That's it. Now, as I mentioned before, everything was working fine praviously, but I'm not exactly keen on needing to go back to previous driver version, if you know what I mean. Log file doesn't seem to have anything abnormal, aside from "Available VRAM: UNSUPPORTED", but I have attached it regardless. Thank you :3
HarbingerDawn, I see. Thought as much. Expected it to be the driver issue from the start, knowing SE's relations with AMD drivers. Well then, I guess I'll revert to 14.4 at some point, if no other solution will be found. Thanks :3
Edited by nightquaker - Tuesday, 15.12.2015, 15:42
ENG
New site
United States 
It looks like (null) 2.1 (null).
Pirate 
Poland 
Russian Federation 
United Kingdom