VOGONS


Black water? in tr1

Topic actions

Reply 20 of 27, by Glidos

User metadata
Rank l33t
Rank
l33t

The glimpse of the desktop is because it closes one window and creates another. I'd be interesting to know if playing in a window stops it happening because that would show that it wasn't a VESA mode change dodging around Glidos.

Reply 21 of 27, by Kaminari

User metadata
Rank Oldbie
Rank
Oldbie
Glidos wrote:

The glimpse of the desktop is because it closes one window and creates another.

Good call, Paul. I tried the window mode + VESASupport and this is exactly what happens.

Now, since my card has native support for VESA mode -- and the 'desktop glimpse' issue doesn't happen with native VESA -- I personally don't need VESASupport. Of course, the res switch is a bit annoying, but in that case it is to be expected and is not that bothering.

Reply 22 of 27, by Glidos

User metadata
Rank l33t
Rank
l33t

I think most cards are ok with VESA these days. There was just a period where both ATI and nVidia took turns to mess it up in their drivers, and then VESASupport was quite important.

Reply 23 of 27, by Gambit37

User metadata
Rank Oldbie
Rank
Oldbie

I've tried lots of different settings for this, and the olnly soutlion to avoid all the res switching that I've found is to play in a window. Bum

Incidentally, if I switch VESA support to No in the INI file, I get nothing but a black screen. Is that expected?

Reply 24 of 27, by Glidos

User metadata
Rank l33t
Rank
l33t

Not really expected with modern nVidia or ATI drivers. I put VESA support in because for a while, after XP came out, a lot of graphics drivers had trouble with VESA, but I thought most worked these days.

Reply 25 of 27, by Gambit37

User metadata
Rank Oldbie
Rank
Oldbie

I just tried VesSupport:No again, and it worked this time -- both fullscreen and in a window. The only difference over 'Yes' is that I now the see the blue Eidos Interactive text on a white background before the game starts, which I don't recall seeing before.

When I tested it last night and got the black screen (ie, crash), my machine had been on for hours and I had very fragmented memory -- Photoshop and other apps were also open. I guess it might be something to do with that?

Reply 26 of 27, by Gambit37

User metadata
Rank Oldbie
Rank
Oldbie

I just discovered that it's nothing to do with memory thrashing or anything else I might have mentioned, it appears I was the victim of the 'bad startup' bug that I've always suffered from. Maybe 1 out of every 10-15 starts of TR from Glidos never completes -- the DOS window just sits there doing nothing after the usual startup message. I have to manually close the TOMB.EXE from the taskbar and try again.

I wonder if the black screen is something to do with that? I don't know what the bug is -- I've had it ever since I started using Glidos. At first, I thought it was something to do with my Tomb Raider CD having a scratch on it, but now I use a mounted BIN image, and it still does it.

Reply 27 of 27, by Glidos

User metadata
Rank l33t
Rank
l33t
Gambit37 wrote:

I just tried VesSupport:No again, and it worked this time -- both fullscreen and in a window. The only difference over 'Yes' is that I now the see the blue Eidos Interactive text on a white background before the game starts, which I don't recall seeing before.

You should see another difference, in that even when you select windowed, you get the FMVs full screen.