Make sure that your bugs are not on the following list of known issues. 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 system folder of SpaceEngine's directory). Only the log file will help me to understand your problem and find a solution.
Known Issues
Green items have been fixed for the next release
- Star catalog have 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. This is not a bug. - Ships do not render in the interstellar space - Ships do not render in systems belonging to a star cluster and displayed as "Interstellar" - Few issues with asynchronous loading (stars don't always generate properly, especially when flying to new galaxies) - Holes in some giant stars when camera is directly above a very tall spot [example] - Impossible to find very dim objects (like stellar remnants) in the map mode - Star browser does not detect stars belonging to the central galaxy star cluster and some globular cluster stars - Star browser is not effective at detecting halo stars - In the Map mode, Star browser performing search around camera position, not around the map center - Star browser sometimes shows incorrect star multiplicity data - Flashing landscape LOD on a planet when Wiki for it is displayed - Unfinished text editor for descriptions - When transition from lens flare to star flare begins, the star point turns black and shines through flares/objects when using star style "points". Examples: [1][2] - Unable to select something with cursor for several seconds after repeated clicks sometimes - Star clusters not displayed in Wiki - 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 - Digital value/edit field in planet editor may completely disappear sometimes - Music player doesn't work - Deep space objects (e.g. stars, galaxies) will shine through planets when HDR for DSO is off, but HDR is on and Bloom is on [example] - Comet nucleus star-sprite will shine through planets [example] - Aurora radius limited to planet radius (not a bug, just catalog parameter limitation) - Some neutron stars can have very low temperatures [example] - Flickering flare color in close binary systems [example] - Bugs with some catalog planets with textures from files when using the Editor [example] - Dwarf planets not only generated in asteroid belts - Sunspot distribution is not always realistic - Auto-exposure does not react when a sun is blocked while diffraction spikes are set to normal or super - Planet rings have an unrealistic color palette - "Eclipse bug" on distant planets (weird dark shimmering on outer planet caused by inner planet crossing the sun or two suns eclipsing) - Rounding errors (e.g. 30° in catalog rounds to 29°59'59.99" displayed on HUD) - Shimmering bloom splotch when very close to the surface of a gas giant [example] - Setting StarProcBifurcation to false in the universe config disables generation of all multi-star systems, including procedural - Planets with life are not generated in single-star systems - Cloud cyclones have cut edges sometimes - Galaxy/nebula sprites will rotate when seen from certain angles. This is not a bug. - Level horizon command (End key) doesn't work properly on oblate objects - FOV ignored when choosing default camera position in game mode - Problems when releasing Left+Right click - Solitary brown dwarfs are not generated - The primary planet of a barycenter displays one too many satellites in the Wiki - Wiki displayed luminosity of the Sun as 0.9 - Some bugs with exported surface maps - Auroras and rings can be rendered in front of ships/moons sometimes - Comet tails can be rendered in front of ships/planets - Lens flares are distorted by gravitational lensing (black holes) - Lines or junctures are visible on planetary surface - Problems with shaders loading (disappearing of water, eclipse shadows, etc) - Weird behaviour of Shift-G with star clusters - Switching to fullscreen doesn't work sometimes - Procedural landscape uses only snow detail textures - VSync mode is always Auto (2)
Edited by HarbingerDawn - Monday, 30.09.2013, 22:45
Intended feature. When looking at a sun/planet in real life, the light would cause the camera to lower the exposure so the planet/star doesn't look washed out, thus as a consequence making stars too dim to see. It's similar to walking inside a building after being outside on a sunny day. Notice how dim everything looks for a couple minutes?
Also why the Moon Landing photos have no stars in the background.
You can also test looking up at the night sky, and hold a flash light and let the light hit your eyes. Not many stars can be seen.
Quote (smjjames) Also, there were a few times while I was hunting around for the challenge that SE froze up and became unresponsive and the only way I could shut it down was to end proccess, could I have messed something up? I didn't seem to have that problem with the challenge galaxy though.
Did you use Star browser before? I fixed the cause of great slow-down then using SB in the dense parts of the galaxy (ie star clusters).
Yeah, that was while I had been using the star browser in that challenge galaxy. However, the galaxy in this case was a large elliptical (100kp I think) and I was still pretty much on the outskirts. I was using a search of 100 parsecs and in the later stages of my search, the SB varied between 300-500 or something like that.
Although for the two cases where the system unexpecedly dissapeared, I did use the star browser before the first one but not the second.
Since this isn't an 'asking for help' post, I guess I could post this crash report here.
While going around open clusters pretty close to the core of this galaxy (between 5k and 2800 parsecs), I had noticed that sometimes while in clusters, I would get a massive FPS drop from my normal FPS of around 30-40 (sometimes 20s) to averaging 1-3 FPS. It seemed sort of random, almost every other cluster or two. I didn't check the distance of every cluster from the core, so I don't know if that is a factor.
When I had gone to what might have been the closest (2,800 parsec from core), I was having the heavy lagspike as usual and was trying to ride it out as it just sort of spontaneously goes away, so I was looking around trying to find a good triple star system when SE crashed from the lag.
However, when I started SE back up, the FPS was fine.
Oh yeah, I'm seeing the object not found in the journey log from some systems I visited. So, there's something going on with clusters. There's also something interesting, the journey log coordinate boxes (that you select) for the selected star system with planets that dissapeared and the system above it both say that they are triple systems, yet the infobox says a different star luminosity and they're binary.
One thing I'm noticing is that while systems outside star clusters are fine, stars inside clusters are screwed up (at least most of the ones I visit anyway).
I did some testing by clearing out the cache to see what would happen, the star I have in the example changed, then I went to a distant cluster, restarted and the star system had changed again. I went to that particular star (now a white giant), restarted and it didn't change. Then I went some way distance away (was double checking on stars outside clusters) and somehow it seems to have locked into that and didn't change even though I restarted. The other triple system in the log in the screenshot also seems to have settled as a single A2 V star.
Since it's already messed up for me, could someone check that star coordinate and see what is there, for SCIENCE!
To summarize, there is something screwy going on with star clusters, and I have the loader mode on interleaved.
Edit: Just adding an observation note that Globular clusters are unaffected.
When I had gone to what might have been the closest (2,800 parsec from core), I was having the heavy lagspike as usual and was trying to ride it out as it just sort of spontaneously goes away, so I was looking around trying to find a good triple star system when SE crashed from the lag. However, when I started SE back up, the FPS was fine.
Again, did you use the Star browser before? Low FPS probably caused by 20 planetary systems, rendered at once.
Quote (smjjames)
I did some testing by clearing out the cache to see what would happen, the star I have in the example changed, then I went to a distant cluster, restarted and the star system had changed again
This is a seed changing bug. First time you visit that star, it being generated with wrong seed in some reason. When you restart SE, the seed for that star becomes right.
Quote (smjjames) When I had gone to what might have been the closest (2,800 parsec from core), I was having the heavy lagspike as usual and was trying to ride it out as it just sort of spontaneously goes away, so I was looking around trying to find a good triple star system when SE crashed from the lag. However, when I started SE back up, the FPS was fine.
Again, did you use the Star browser before? Low FPS probably caused by 20 planetary systems, rendered at once.
Nope, hadn't even used the star browser in that galaxy. I did suspect it was caused by loading stars in dense clusters since it went away after a while, however, I was also getting those memory errors in the log, which is mainly why I decided to post it before I discovered this other problem.
Quote (SpaceEngineer)
Quote (smjjames) I did some testing by clearing out the cache to see what would happen, the star I have in the example changed, then I went to a distant cluster, restarted and the star system had changed again
This is a seed changing bug. First time you visit that star, it being generated with wrong seed in some reason. When you restart SE, the seed for that star becomes right.
Strange, It changed multiple times for two stars before it settled (and one of them I didn't actually visit again) and it seems to only affect stars in clusters (haven't looked into globular clusters). I actually had the same problem in a different galaxy, so it's not just one galaxy.
I hope that gets fixed because it's annoying when trying to find a system that I like only to have it dissapear if I crash or close the program or simply come back to find it not there.
That transparent rimmed crater that I posted earlier was strange as well and could have been related to the seed changing bug. If I run into that again (assuming it doesn't vanish due to seed changing bug), I'll definetly post it.
Restarting usually clears it for me, sometimes changing the angle might work
As for what causes it, I don't know the specifics of it and all I really know is that it's a graphical glitch with the skybox that has been around for a long time. Also, you could have posted this in the troubleshooting thread rather than make a new one.
Hmuda, seams in the skybox on bright parts of the galaxy is a long-known issue, and there's no way to fix it at present. If it bothers you then you can toggle skyboxes on and off in the graphics menu (via the sidebar buttons or Ctrl-F4).
Also you should have posted this in the bug reports thread.
Quote (smjjames)
changing the angle might work
Changing the camera angle will have no effect as the skybox is only regenerated after moving a large distance.
Quote (smjjames)
you could have posted this in the troubleshooting thread
Bug reports, not troubleshooting.
All forum users, please read this! My SE mods and addons Phenom II X6 1090T 3.2 GHz, 16 GB DDR3 RAM, GTX 970 3584 MB VRAM
I've run into two graphics errors in the same system which seem to be different types, the other planets in the system are unaffected. I didn't see any errors in the SE log, but I've included it to provide graphics related information.
The first one resembles the shimmering that happens with an eclipse, but I checked and it's not an eclipse. and if you turn the atmosphere off, the effect goes away. Although if you turn the atmosphere off and pan the camera around slightly while looking at the same spot, you can see little flashes of light. Also turned comet tails off and both glitches still persist.
This one I don't think I've seen before and unlike the previous, it shows up with atmosphere off. This is the second planet of the binary pair at the location.
It's a globular cluster btw, so I know it didn't dissapear on me.
Place "atmospheric shimmer bug" { Body "RSC 0-7-1860209-74-2573-0-0-158 3" Parent "RSC 0-7-1860209-74-2573-0-0-158 3-3.1" Pos (7.205026805756111e-010, -3.95583722842454e-010, -6.513736170452381e-011) Rot (0.550584847566603, -0.08955572355498177, 0.729026306196614, -0.3966821685958737) Date "2013.06.05 19:11:17.83" Vel 8.5010679e-011 Mode 1 }
I have a problem with galaxies. Some galaxies (both catalog and procedural) render, but a huge number of both types do not. it is impossible to select them with the mouse or see them. The search function will lead you to where they are supposed to be, but there is nothing there- not even stars.
The galaxies shown are Andromeda and the Milky Way.
The clouds on this world are out of the atmosphere.
Yes, I notice that clouds are sometimes too high on 0.97.
Wow, I was playing with Star Wars ships and I saw this in the sky :
Then I noticed the screenshot havn't worked, so I can only describe what I saw : a white streal in the sky. It seemed to be big.
Other bug I saw, I was going to Jupiter with the Discovery One ship, then one side of Jupiter was suddenly covered by the texture of the keyboard of the computer of the ship.
When I saw this, I checked several oceanias, including one that just happened to be slightly bigger in diameter (was much more massive though), and this 3D water problem seems to be only happening with this particular planet.
As you approach, it looks opaque as it should, but around 65k km out, it starts transitioning to transparent and somewhere between 50k and 45k out, it starts transitioning to the near surface opaquity. It's like the transition isn't overlapping correctly with this one
Edit: Spotted another one that is somewhat larger and has the same problem. Anybody remember whether this bug happened in 0.96? I don't remember if it did or not.
Place "3D water problem" { Body "RS 0-6-117028-1097-896-7-739585-4 A4" Parent "RS 0-6-117028-1097-896-7-739585-4 A4-A4.1" Pos (3.43086601825842e-010, 1.489883642348013e-009, -1.465604871622381e-009) Rot (-0.2340996600167925, 0.7003610192927421, 0.596238453743853, 0.3149468179112039) Date "2013.06.06 22:21:06.63" Vel 3.2407764e-011 Mode 1 }
ENG
New site
United States 
Sweden 
Russian Federation 
Hungary 
France 
