Hi, I have just bought a new desktop computer. I have a 1080p monitor, which is probably why it sometimes runs a little slow, but anyway the stars aren't rendering correctly; I have set the magnitude to default but not very many stars load, and the stars don't get fainter as the distance increases, they just pop in and out of view.

Here is my SE log: se.log

Looks like SE is having a lot of trouble with your graphics card.  It's a quite old AMD card so perhaps it might explain it.

Okay, so SE was working just fine these last few days with the minor error of black screen, fixed by turning off comet tails. Now, the planets seem to be translucent and have no textures -- they're just white. Also, Nebulae seem to be invisible, some star clusters at the center of some galaxies aren't rendering, and some galaxies like the LMC and Black Eye Galaxy are invisible. I'm not sure it's my graphics card because of the fact that SE was working fine just a few days ago with all the proper textures and such. Any solutions?

Any solution

My guess is that my video card is not strong enough but is it enough to prevent the software to start

Atmospheric Extinction does not work fro Spacecrafts:

► Show Spoiler

I was trying to recreate the famous Rogue 1 Death Star rise scene

► Show Spoiler

// Depth buffer options
DepthBuffer
{
    DepthBufferMode         1        // Z-buffer mode (0 - standard, 1 - reversed, 2 - log in vertex shader, 3 - log in pixel shader) (remove cache to apply changes)
    ShipDrawMode            4         // use 1 for DepthBufferMode = 0, and 2...4 otherwise
    ClipHeight              0.001    // collision detection height in kilometers
    ClipZNear               0.005    // near plane clip distance (ignored in reversed and logarithmic z-buffer mode)
}

// Depth buffer options
DepthBuffer
{
    DepthBufferMode         1        // Z-buffer mode (0 - standard, 1 - reversed, 2 - log in vertex shader, 3 - log in pixel shader) (remove cache to apply changes)
    ShipDrawMode            1         // use 1 for DepthBufferMode = 0, and 2...4 otherwise
    ClipHeight              0.001    // collision detection height in kilometers
    ClipZNear               0.005    // near plane clip distance (ignored in reversed and logarithmic z-buffer mode)
}

Is this a known issue that can be reproduced or something that only I'm encountering? If I were to suspect something I would think that it is some kind of graphics memory glitch as it gets worse over time and eventually causes a crash

mine does nothing when pressing record.