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 issues.
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 graphics card-specific issues
If you do not know which graphics card (chip) 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.
Intel HD: Glitchy landscape and textures on planets
Open config/main-user.cfg and change this parameter to true:
Note that this is an experimental feuture and may cause glitches; collision detection also works incorrectly in this mode. Also, read Fixing common issues #3.
Intel HD: Red clouds on Earth
Install the latest driver for Intel HD.
Intel HD: Black screen
Disable comet tails. Go to the main menu, then Settings -> View, and uncheck "comet tails". If you even don't see the main menu, close SE, delete the file config/main-user.cfg, and try again.
Fixing common issues
1) Obsolete or incompatible drivers
These are the most frequent errors found in SE. You will get a popup window with one of these following messages:
- "You have old OpenGL version (2.1.1). Update your graphics card driver or install compatible hardware"
- "You have old GLSL version (1.2). Update your graphics card driver or install compatible hardware"
- "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-user.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 or Radeon with at least 1 GB of dedicated video memory
I stress the special role played by graphics card's onboard memory (VRAM), and 1 GB is the absolute minimum. The engine uses a large amount of data that must be in video memory (textures, meshes etc). The good 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 flights. CPU does not significantly affect the landscape generation speed because it is done completely on the graphics chip.
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 chip. If you can't 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.
c) Just restart SE. It helps in 99% of cases.
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. - Reduce "Landscape LOD" to -2 in Graphics settings (Ctrl+F4) - Set up the amount of video memory in the config/main-user.cfg file:
VideoMemorySize 2048 // graphics 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) 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).
7) 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:
a) Open Windows Control Panel, navigate to Display, and set the DPI scaling to "Smaller - 100% (default)" - it should look like this.
b) 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" look the same. This is right! This switch changes the rendering technology, not the visual appearance - 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 - Galaxy/nebula sprites will rotate when seen from certain angles - Lens flares are distorted by gravitational lensing (black holes and ship warp drive effect) - Solar system moons don't have extremely accurate orbits (requires implementation of custom orbit models, e.g. VSOP-87) - Solar eclipses on Earth, Moon, Jupiter and other real planets are inaccurate (the same as above) - 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) - Many HIP and HD stars do not appear in the search menu, as well as procedural objects (RS xxxx) - Camera sometimes falling through the surface - Collisions detection between ships is not implemented yet; and between ship and planet is inaccurate
Real bugs:
- Lines or junctures are visible on planetary surface of real planets - 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 - 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 - 3D water fog sometimes starts above or below 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 - 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.
edit: I reposted this in the troubleshooting thread.
Greetings!
I am new to SE and installed it today - very excited. It's installed and seems to work fine at first sight, no error message, I can go to objects etc, however I am unable to see any space objects at all, even though their viewing is enabled. I have attached a screenshot along with my SE log file. I suspect that it's not a bug but a spec issue? I did upgrade my graphic driver earlier today however it didn't resolve the issue. What do you think? I'm hoping there is something I can do to fix this, besides dumping my laptop for a new one!
An update on the bug I mentioned earlier. Apparently It does not have to do with atmospheres. Suns appear oddly small and dim from planetary/moon surfaces if auto exposure is turned on.
I think that one was just a temporary work around for the bug that causes the 3d water "fog" to appear above the 3d water layer sometimes.
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 :( )
SpaceEngineer, Hi, i have a very annoying problem, i don´t know if it´s normal o already been fixed, if yes, please tell me where i can find a solution. Problem: When i´m editing a spaceship in the spaceship editor inside Space Engine, i can´t edit the thrusters correctrly, weeks later i did it perfectly, but i don´t know what´s happening right now. I can´t see the guide line for thrusters, only when i´m using them. And when I try to delete one Space Engine crash.
That don´t happen with the docking ports, only with thrusters, doesn´t matter what spacecraft is, i try with space engine´s default ones and the same thing.
PD: Sorry if my english is not so good but it´s not my native lenguage xD
I've noticed in the latest 9.8 that some info of known objects is wrong. Sagittarius A for example age says something like 1.7... X 10^6 that's just under 2 million years, I checked an older version 9.7.3 and it's correct on that one.
Also Alnilam has its mass listed as 65 Solar masses in the new version and most Orion OB1 association Stars have an age listed as just over 1 million years. The older version has them as correct so I'm not sure what's happened here.
Edited by Organised_Chaos - Saturday, 17.09.2016, 13:49
Organised_Chaos, I think that has to do with the so-called star solver.
QuoteSpaceEngineer ()
The star solver
The star solver is a code what tries to compute or generate missing data for a star based on the provided data. It's often situation in astronomy when some data is provided in catalogs, but some does not. SpaceEngine requires at these parameters to correctly render a star (star system):
This algorithm attempts to extrapolate nonexistent data from existing data. For example, the size and mass of a star can be extrapolated from spectral class, apparent magnitude and distance. I think this algorithm has become more complicated, in the new version of SpaceEngine. Therefore, the calculated values differ probably somewhat from previous SE versions.
O and B stars exist only a few million years. If neither the age, size, mass or temperature are specified in the catalog, SE can not determine whether such a star is a million years old, or 10 million years.
But everyone is invited to fill in the missing data in the catalogs. Especially in the Hipparcos.csv file. There are missing some details on radius, mass and temperature of the stars.
The trouble is even some of the most famous Stars, Betelgeuse for example has most info already provided....The class, diameter and mass are all present and correct and yet its age is listed at just over 1 million years. Same thing with Alnitak, class, diameter and mass all correct yet the age is again, just over 1 million years. Lastly surely the algorithm couldn't think a Super massive Black Hole in the centre of a Galaxy is less than 2 million years old? (Then again I know nothing about programming so could be wrong)
Thanks, I'll look into that Hipparcos.csv file and add some info.
There are two things I can do that will always cause SE to crash. One is exporting textures for a planet at a resolution higher than 3000 pixels. A logfile that I saved is the first attachment.
The other thing I've found that always makes SE crash is approaching the central black hole of galaxy RG 0-0-0-0. The logfile when doing that is the second attachment. My computer is a MacBook Pro booting into Windows 8.1, Core i7 2.3 GHz quad, 16 GB RAM, NVIDIA GeForce GT 750M with 2 GB VRAM.
A more minor annoyance I've noticed is that the options in the "Models lighting" section of the Magnitude/brightness settings panel don't get saved in main-user.cfg. I like to set galaxy lighting to around 2.8 or 2.7 (because the Milky Way isn't that bright when you see it from Earth, even in an area with no light pollution), but the setting gets reset to 4 every time I restart SE.
I'm having an issue where the target computer, when selecting warp mode > then the target body keeps switching back to the previous/last target , sometimes lightyears away! I'm not using it incorrectly, and can navigate really far however the bug keep cropping up (about 40%) after I choose a new desination.
I believe Sag A*'s age is incorrect because SE assigns the exact same age to every body in a given system. The black hole is orbited by nearly 30 stars, and the whole thing is displayed to be as old as probably the "youngest" of them.
raptor_x_x, the great lakes are above sea level. SE uses a sphere around the planet for water so there is no way to fill them without raising the water everywhere.
Intel Core i7-5820K 4.2GHz 6-Core Processor G.Skill Ripjaws V Series 32GB (4 x 8GB) DDR4-2400 Memory EVGA GTX 980 Ti SC 6GB
ENG
New site
Russian Federation 
Canada 
United States 
Guatemala 
United Kingdom 
Germany 
Pirate 
Poland 
