Forums » Bugs
Artifacts - roids in jump-screen?
Hey
I'm getting asteroids showing in the between-sectors piccy (while loading the next sector.) It seems to happen when I'm playing the game in a window, and change focus or even desktop (Linux2.6.1/KDE3.1.5) - worst case the backdrop image for the next sector will be eigther black (not bad) or seriously messed up (bad!)
I have a snapshot of the roids if you want it...
/G
I'm getting asteroids showing in the between-sectors piccy (while loading the next sector.) It seems to happen when I'm playing the game in a window, and change focus or even desktop (Linux2.6.1/KDE3.1.5) - worst case the backdrop image for the next sector will be eigther black (not bad) or seriously messed up (bad!)
I have a snapshot of the roids if you want it...
/G
that happens occasionally to me when I bump buttons that bring up a screen, such as Players In-system, or press the ESC key while entering warp, during warp, or exiting warp.
They dissappear after the warp returns to my HUD.
They dissappear after the warp returns to my HUD.
yeah, this is pretty old. I'm not sure it's a bug, just a design flaw.
yeah this happens to me when i press "u" or ESC
It's not a flaw or anything like that. It's a feature(hehe)...when you press "u" twice(once to enable it and the other to hide the stupid window) it shows how loading is going. Before we didn't have a loading bar so pressing "u" twice was kind of a way to tell how far the sector was loaded. I still do it sometimes as I like to see what's going on.
[Edited.. oops, re-read original post]
There's two separate issues here. First, yeah, various actions can cause the scene to render as it's being downloaded, such as pressing U.
In Linux, random shapes sometimes get clipped out of the background image, or the background image just doesn't render properly. It seems to be a bug in the Linux nvidia drivers with render-to-texture. It doesn't do it on the other platforms. It may not allow rendering to a GLX context that's not visible, even if we're rendering to an off-screen buffer instead of the screen.
Aside from that, there are sometimes problems with the Z-buffer not being cleared, or something, so shapes get cut out.
There's two separate issues here. First, yeah, various actions can cause the scene to render as it's being downloaded, such as pressing U.
In Linux, random shapes sometimes get clipped out of the background image, or the background image just doesn't render properly. It seems to be a bug in the Linux nvidia drivers with render-to-texture. It doesn't do it on the other platforms. It may not allow rendering to a GLX context that's not visible, even if we're rendering to an off-screen buffer instead of the screen.
Aside from that, there are sometimes problems with the Z-buffer not being cleared, or something, so shapes get cut out.
Good thing I dont own an nV-card then .. Well, I do but I dont .. erhm... Oki, I use Matrox!
To confirm what a1 said, on my Mac/nvidea, the loading appears for me but in it's complete form (no clippings or cut-outs)