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 can't export any textures larger than 3999 x 1999 without crashing immediately and it only takes about exporting 5 textures at 3500 x 1750 to crash... Does anyone know why this might be??
Living among the stars, I find my way. I grow in strength through knowledge of the space I occupy, until I become the ruler of my own interstellar empire of sorts. Though The world was made for the day, I was made for the night, and thus, the universe itself is within my destiny.
Allrighty, SpaceEngine seems to be running smoothly, and pretty much like a charm for me. However, while navigating around the systems I've created, I did come across a couple of oddities that seem to be the result of unpolished features (hence no logs, but I'll get them if these are really bugs and they're needed).
Here's one of them:
What you see here (although you may have to blow the image up to actually see it) is what seems to be dunes climbing the mountains up until they get almost vertical.
The other images are of a desert moon that is crawling with pretty weird emissive features. I put thermal emission to the max and took a few screenshots of a number of them, from orbit down to the floor. Here they are (distant orbital shots need blowing up):
(by the way, I still haven't found those weird cliffs that were relatively common a couple of versions back; that issue seems to have been solved)
Those are lava flows, they existed in 0.972 as well.
Yeah, I know, but those are lava flows 1. without a geographical structure that might be seen as their point of origin (no visible volcanos in any of these), 2. much more linear than anything natural should be, and 3. that totally disregard underlying orography (in the second image, you can see one of them climbing the walls of a pretty large crater, instead of pooling next to it as it should be; something of the sort is also seen in the last image, with those "lava-flowy mountains" both in the left and in the right).
For some reason, 0.9.7.3 crashes after I hit "Planetarium". 0.9.7.2 worked fine (if I didn't visit too many planets in one go). Would a driver update fix this problem? If not, how do I get it to work on my HD 4000 GPU? I've attached my SE.log file.
Is anyone else having any issues with their custom catalog systems?
For some reason, when I press F2, a random Jovian is designated as the system's "Primary" body, but the HUD shows glitchy temperature data, incorrect distance sorting, and a glitchy appearance for the barycenter in binary systems. A similar situation exists with my single stars. At first I attributed it to the inflated radii I set for these Jovians, but changing it did nothing to fix it.
Specs: Dell Inspiron 5547 (Laptop); 8 gigabytes of RAM; Processor: Intel® Core™ i5-4210U CPU @ 1.70GHz (4 CPUs), ~2.4GHz; Operating System: Windows 7 Home Premium 64-bit; Graphics: Intel® HD Graphics 4400 (That's all there is :( )
Yeah, I know, but those are lava flows 1. without a geographical structure that might be seen as their point of origin (no visible volcanos in any of these),
This is a bug.
QuoteJCandeias ()
2. much more linear than anything natural should be, and 3. that totally disregard underlying orography (in the second image, you can see one of them climbing the walls of a pretty large crater, instead of pooling next to it as it should be; something of the sort is also seen in the last image, with those "lava-flowy mountains" both in the left and in the right).
Realistic flooding is impossible to implement in one-pass procedural generator. Actual liquid dynamics must be simulated.
QuoteStargate38 ()
For some reason, 0.9.7.3 crashes after I hit "Planetarium". 0.9.7.2 worked fine (if I didn't visit too many planets in one go). Would a driver update fix this problem? If not, how do I get it to work on my HD 4000 GPU? I've attached my SE.log file.
Did you tried fixes for Intel HD posted in the OP?
QuoteAlabeo ()
Why is this so blurry? 0.9.7.2 wasn't as blurry as this is. http://prntscr.com/6yym3p Look at the planet edges. Same goes to pretty much everything else, including landscapes.
It looks like broken FXAA shader. Try to disable FXAA in the Graphics settings.
QuotePlutonianEmpire ()
Is anyone else having any issues with their custom catalog systems? For some reason, when I press F2, a random Jovian is designated as the system's "Primary" body, but the HUD shows glitchy temperature data, incorrect distance sorting, and a glitchy appearance for the barycenter in binary systems. A similar situation exists with my single stars. At first I attributed it to the inflated radii I set for these Jovians, but changing it did nothing to fix it.
Very strange issue. Are you sure you made a correct hierarchy in the system? Also, object Hadeus seems have something wrong with radius. If it is a star, you must check carefully its spectral class (SE allowed only classes, described in the creating a planet tutorial).
QuoteRicardo ()
cant capture in AVI, is there a problem with this version? is there any other compression video tools i can use?
Which codec did you choose? Are you installed some additional encoders?
Very strange issue. Are you sure you made a correct hierarchy in the system? Also, object Hadeus seems have something wrong with radius. If it is a star, you must check carefully its spectral class (SE allowed only classes, described in the creating a planet tutorial).
Were you able to check the zip file I attached to that post? It contains the catalog scripts for "Hadeus" and an additional system that I was seeing the issue in. Regardless, I will double check the tutorials to see if I missed anything on my end.
EDIT: Indeed it was. For "Hadeus", the Hierarchy was fine, but for the masses of the stars, I was using "Mass" instead of "MassSol" in the planet catalog version, so the game was assuming I meant Earth masses instead of Sol masses. And for my singular star I had elsewhere that also had this issue, placing the additional star parameters was superfluous. After checking the catalogs inside the .pak files looking for examples, I realized I didn't need to define the star's body in the planets catalog, since it was a singular star instead of a multiple. So I corrected my issues and they render normally now.
Specs: Dell Inspiron 5547 (Laptop); 8 gigabytes of RAM; Processor: Intel® Core™ i5-4210U CPU @ 1.70GHz (4 CPUs), ~2.4GHz; Operating System: Windows 7 Home Premium 64-bit; Graphics: Intel® HD Graphics 4400 (That's all there is :( )
Edited by PlutonianEmpire - Tuesday, 28.04.2015, 21:52
Yep, and I do thank you for all your efforts here!
Specs: Dell Inspiron 5547 (Laptop); 8 gigabytes of RAM; Processor: Intel® Core™ i5-4210U CPU @ 1.70GHz (4 CPUs), ~2.4GHz; Operating System: Windows 7 Home Premium 64-bit; Graphics: Intel® HD Graphics 4400 (That's all there is :( )
Edited by PlutonianEmpire - Tuesday, 28.04.2015, 22:44
Realistic flooding is impossible to implement in one-pass procedural generator. Actual liquid dynamics must be simulated.
Ideed.
Say, it just occurred me: would it be possible to limit lava flows to regions with heights lower or equal to their points of origin? It would still not be realistic, and would probably result in a series of lava lakes, in some cases, but at least such long, linear and height independent features would be avoided.
Just an idea for a quick hack until actual liquid dynamics is implemented.
QuoteSpaceEngineer ()
This is a bug.
Is it a known one, or do you need a log to figure out what's happening?
ENG
New site
Russian Federation 
United States 
Portugal 
Poland 
Regardless, I will double check the tutorials to see if I missed anything on my end. 