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 updated 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.
Nvidia: Water missing on terras, clouds are below the surface
This is becasue of Nvidia driver update. Revert back to 365.19.
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
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
ATI/AMD: Crash on Startup on Windows 10
Open the system folder in your SpaceEngine directory and delete the file atioglxx.dll.
Intel HD: Glitchy landscape and textures on planets
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"
To fix that, 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
SpaceEngine needs a modern "gaming" graphics card to run. Weak cards like Intel Graphics (many laptops have it) or 10 year old devices like GeForce 5700 will not run SpaceEngine. There is no way but to update your hardware. 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 etc). The goo performance will be only with a dedicated video card with 1024+ MB of onboard memory. Almost all modern $100+ devices can run SE smoothly. CPU power is not so important for SE, but having many cores could improve performance on fast interstellar and intergalactic flight. CPU does not significantly affect the landscape generation speed because it is done completely on the video card.
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 the "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 find a 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 it is a full version, not a patch!). If you install a new version overwriting the old one, you may get many bugs and glitches.
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.). The video memory is the most important resource for SpaceEngine. 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
This is not a bug. The current version does not yet have a completed spaceship rendering system - they cannot be rendered if there are no stars or planets in the renderlist. Just imagine that the ship is in hyperspace, so cannot be seen :)
7) Blurry textures on Solar system planets
This is not a bug. Our Solar system planets and its satellites have no procedural textures, they use real ones with limited level-of-detail. You can download addons with high resolution textures to increase the level of detail of real planets. But don't expect 1 cm level of detail; these addons also have limited size, and thus limited resolution (up to 150 meters per pixel for some bodies).
8) 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.
9) Problems in Windows 10 + AMD/ATI
Delete the file system/atioglxx.dll
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" look 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 - 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) - 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:
- Cloud cyclones have cut edges sometimes - Lines or junctures are visible on planetary surface - 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) - 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) - Level horizon command (End key) doesn't work properly on oblate objects - Weird behavior of movement keys in tracking mode (T) and after releasing it - 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 - Problems when releasing Left + Right click - Music player will unpause when SE window is minimized and restored, or when entering and exiting the main menu - Switching to fullscreen doesn't work sometimes - 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 - 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 - "Sky lighting shadow" in the subsolar region of atmospheres - Problems with the skybox export interface, and with the planetarium after using it, for some users - 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 - VSync doesn't work after usage of Oculus Rift in the Direct mode, sometimes it doesn't work at startup when Oculus Rift is connected.
I've found what seems to be a lighting bug in a close binary star system. It occurs when one of the stars eclipses the other relative to the planet:
The planet darkens considerably, which seems normal because technically the amount of light is cut roughly in half, but I'm not sure. The real issue is the "flickering" seen in the GIF above. I found that the flickering will go away if time is sped up and the stars are no longer overlapping/eclipsing each other.
I haven't seen anything similar to this before. I'm not sure if it's because I haven't examined a close binary with planets in this configuration, or if because something has happened to my system to cause this graphical glitch. One thing I did notice is that the stars are exceptionally bright, which may or may not have something to do with the light glitch.
I made a video of the phenomenon acted out and you may find it more helpful than the GIF:
Edit:My apologies, as JackDole pointed out this was most likely already listed as the "Eclipse bug". It appears I was more excited about being able to upload a youtube video and make a GIF than to actually take a proper look and see if the issue was already known. Oops!
I don't think this is a bug, but its something I'm having trouble figuring out the cause of.
I've been extensively modifying my palette file using the palettes from the page on the mods and add-on portion of the forum, and so far I've seen them and they look great. But the problem is, every single gas giant I come across, no matter how cold they are, they're still brown-ish instead of blue. I even came across a -250 degree celsius gas giant, and it was using the Saturn colors instead of the blue-white colors.
Have I entered the values for probability of appearing wrong? Am I reading how the game differentiates the colors of gas giants by their temperature wrong? I have some gorgeous blue palettes in my palette file that I was hoping would show up but just never have.
Palette itself is in this post. If anyone could tell me what's going on with this, it would be great.
And yes, I've been looking at white main sequence star systems when I was searching for a frozen blue gas giant. The -250 celsius one was found orbiting a white main sequence star.
Anybody got any ideas about what's causing my issue?
your computer work with an intel hd2000/3000/4000 graficengine?
Win 7 64bit, Intel i5, 3GHz, 4GB RAM, HD2500 Onboard. 0.974_RC3 works very good Win 7 64bit, AMD X4 955, 3,4GHz, 8 GB RAM, ASUS STRIX GTX960 DC2OC. 0.974_RC3 works very good
Sorry that I took a day to replay but I have fix the problem , I just clean installed windows 10 ( was using win 7 before) now I have win 10 64 bit version, ofcourse I kept my personal files I guess the problem was in the DLL files (as I found while googleing this problem).
BUT! this is the reality of life, one thing comes good other becomes bad ! I lag when I go to a star or planet by going near I mean trying to go to the surface. Do I need to just wait it off for the bodies and textures to render or do I have to do something ?
I have a Intel Core 2 duo E8400 @3.00 , 2.99 GHz, 6 gb of ram and windows 10 64 bit as mentioned above. Now about my gpu , umm, its not the best but here it is , ATI Radeon HD 2400 PRO , long story short , It has 256 MB of memory. Now, I am completely aware that you need atleast 512 MB to run SE but believe me it works with a 256 mb card( I just used the program) but then again I get soo much lag when going near a star ,I mostly get 60 + frames but when I go newa a star or planet (so near that its TEXTURES start to show ) the frames drop to 11 frames persecond and upon going closer it lags even more and gets to 3 FPS .
I have turned procedural STARS on , all the rest of bodies and unchecked from procedural. A bit of help will be appricated, thanks for making that amazing piece of software , Space Engineer.
I mostly get 60 + frames but when I go newa a star or planet (so near that its TEXTURES start to show ) the frames drop to 11 frames persecond and upon going closer it lags even more and gets to 3 FPS .
This is why system requirements said "GPU with 512 Mb". This limits not only video memory, but also generation of graphics cards. 256 Mb must be very old and therefore slow GPU. It's impossible to help here.
Hello. I've been toying around Space Engine for over a month with little to no issues, up until today.
I've noticed that Space Engine is working as if my keyboard had a different language configuration than the one I have. My keyboard is a spanish keyboard, but no problems had arisen from this previously, but now, for example, if I want to press the key for increasing the magnitude limit (the one I've been using for over a month), which is "]", it registers it as an "¿".
I've gone as far as reinstalling SE, but the problem still persists.
Anybody know what could be causing it/how could it be solved?
Edited by Elitecomentaris - Tuesday, 03.11.2015, 03:04
It's been 7 months since my first help request on this and 2 months exactly to the day since my last request so I am reposting the following in hopes I might be able to finally run 0.9.7.3 before the end of 2015.
I've been following this thread for months in hopes that a solution would work.
I posted back on page 4 the following:
Quote
Help needed.....
The new version is crashing upon launch for me. Meanwhile an installation of 0.9.7.2 runs just fine.
My video card is an AMD R9 270X.
My se.log file is attached.
The solution offered was:
QuoteHarbingerDawn ()
Quote Jadestar () The new version is crashing upon launch for me.
Try deleting atioglxx.dll from the system folder.
I've tried this but still haven't been able to get past the crash at startup. (see screenshot)
Before deleting atioglxx.dl:
AFTER deleting atioglxx.dl:
As you can see, there is no change. :(
Has anyone else with an ATI card had this problem persist after deleting atioglxx.dll? Did you eventually solve it?
I have no problems running .0.9.7.2 but 0.9.7.3 and higher all crash on startup.
I've done several clean installs of 0.9.7.2 + the 0.9.7.3 patch without any success at all. I really hope I am not going to be stuck with 0.9.7.2. That would be incredibly sad. :(
I love Space Engine, I've even donated. I don't want to get left behind.
ENG
New site
Russian Federation 
United States 
Germany 
Pirate 
Pakistan 
Mexico 
Brazil 
