I am at loss how to deal with the FMV clips in fullscreen.
The introduction videos when starting up works somewhat, there is some quality loss in both sound and video and
they are always set to 640x480 with black side bars, no matter what. No big problem, absolutely fine.

I can't manage to do anything really with the GOG Graphic Mode Setup launcher, only make it worse actually.

However, the glide.ini in the exterior DOSBox folder, can at least change the resolution in menu
and in game (I guess), provided you get as far...

The real problem occurs when starting a new game or starting Laura's house.
Those launched videos show just blackness and giving off stuttering noises.
Forcing me to ctrl+alt+delete and simply close the application, because the desktop is then inheriting that
resolution, making it impossible to even watch the clip in window mode..

Why are the introduction videos the only ones working somewhat? o.O
Because they seem to be of the very same type as the other video clips.

Don't change glide.ini; delete or rename Glide2x.dll in Tomb Raider's DOSBOX folder, then install nGlide and use that to set the resolution and so forth. Videos are still interlaced but will play correctly.

Had this same issue

This fixed it:

Ok, so I had it fixed before, but after trying to add the PS1 music files, I somehow broke everything and had to delete and reinstall.

So, now when I try to do this fix I get an error message that says SDL.dll is missing from my computer and it recommends reinstalltion of the program. I know if I reinstall the only thing that'l change will be that Glide2x.dll will be re-added and the game will work as such but the FMVs still won't appear aside from the opening one.

So does anyone know if there is another fix for this or at least something I can change on top of this to fix whatever is causing this new error?

Btw, the issue is not that SDL.dll is missing, it is very clearly in the Tomb Raider 1 folder. Plus this is following a fresh reinstall so everything should be there, since I have changed nothing save for pasting my old saves and renaming the Glide2x.dll file.

you don't say if this is happening on windows 7/8 or earlier, x86 or x64 version &c.
were it eg the Win7 x64 case, the dll could be moved or copied to SysWoW64 folder

other than that, why not try an installer for TR1 I made and published (Tomb Raider 1 Advanced Installer) here: http://www.tombraiderhub.com/
to see if it makes the trick.

Thanks for the response, I'm running Windows 8, x64. I'll try the installer and get back to you if it works for me. I really don't know what the issue could be, it was running just fine before, FMVs and everything.

Alright, here's what I did. First I ran the custom installation. I installed joyToKey (I am interested in getting controller support) as well as nGlide. Then I ran the patch. After doing this, my GOG version of Tomb Raider ran no problem, except that the FMVs still didn't show up (the only one I actually tested was the one that plays when you go to Lara's House since that's easy to test). So, I opened nGlide and changed the screen resolution to 1920 x 1080 and the aspect ratio to 4 : 3. This didn't change anything.

Then I tried running the 'play tomb raider 1.exe' file in the custom installation folder. Norton originally flagged that file as a virus (as well as the UB exe) and quarantined it so I had to restore it. I'm trusting that it isn't actually a virus :0 That does a bunch of stuff and then eventually opens up Tomb Raider in a very tiny window. I pressed escape once (which skips the opening bits) and that put the game in fullscreen. Then I went to Lara's Home again. Once the FMV started, the game went back into a tiny window again. Pressing escape skipped the movie but I could see that it worked and I was also put back in fullscreen mode. Now when I go to run it a second time, everything starts in fullscreen as it should and the FMV to Lara's house doesn't put the game back in a window. So that works perfectly. I copied my saves over to that folder and they loaded up just fine.

But when I tried to load the GOG Tomb Raider from the shortcut on the desktop it still didn't play the FMVs. So I tried deleting the custom installation, and rerunning the patch, since I'm unsure of how the patch works and whether it just looks for an installation of Tomb Raider to patch and patches it and maybe just patched this custom installation and not my GOG files. Still didn't work. I restored the glide2x.dll file in the dosbox folder and ran the patch again. This time it seemed to do a bit more. Still having issues with the FMV though.

At this point the GOG version will run, when it starts the opening bits I can see the little dosbox toolbar at the top with the drop down menus, File, Edit, etc. I press escape and it glitches out a bit but the toolbar disappears. When I go to run the part FMV at Lara's home, the screen goes black and a black mouse cursor appears on the screen, but no FMV. When I press escape here, it glitches out again and sometimes I can catch a glimpse of the FMV but never more than a glimpse.

So I redid the custom installer and fixed the nGlide settings once more.

So at this point I'm a bit confused. It seems with this custom installer, I can run the exe and everything works just fine. I'm just confused as to what it's running exactly since the GOG version still seems broken. I mean I guess it must be running the GOG files since the installer and the README specifically states that I need Tomb Raider installed for it to work. I assume it doesn't include a full version of Tomb Raider? It wasn't able to find my save files until I moved them to the same folder as the exe as well which seems odd.

But whatever, it works so I'm happy. Thanks for the help, friend :)

Also the splash screen for 3dfx is different for the custom install then it is on the GOG version if that is significant at all. The GOG splash is the same one it was before.

And sorry for this long post, I like to be thorough I guess.


TL;DR: The custom installer works but the running the GOG shortcut for the desktop still has issues. Running the exe from the custom install folder works just fine.

but I like long posts ;) it's proof someone read mine :p which I am never so sure of
as long as they're meaningful as yours I like them much better than the shorter counterpart: u suck or this **** won't work period (without the smallest hint as to what software/hardware combos &c. are involved..)

1st of all no panic: no viruses are sneaking in, I know what Norton & al. do, I also wrote about it when this surfaced at tombraiderforums.com (sticky thread about my installer) well I assure you there's no danger there, I use it myself, plus those exe's are but good old .bat files I script then convert (via bat2exe utility) to .exe so they can't be edited just like that by anyone and there's all there's to it

now, the installer never minds about gog/steam stuff, tbh it's gog who plainly has been using the cdrom image I made before, so let gog happen to be broken
my thing pays no heed as it only relies on the installed image I put in there--now the image as I said is the same, but all the install process of going about it is different of course and I can only discuss of my scripting, including dosbox little tricks and stuff

that cdrom image btw not only is a complete and self-contained one, but as of v. 1.6+ it has all the playstation audio tracks too that pc was missing
as for the fmv patch you find in my zip, it naturally only patches those exe's of mine in \tombraider and does nothing to the gog/magog/steam/whatever setups

to fmv's.. a tricky spot anyway
consider that when gameplay kicks in, going fullscreen is handled by the glide/3dfx wrapper, but before that: namely the fmv stage, then it's dosbox itself that rules, and their (fmvs') settings are read grom the .conf (for configuration) files
mine are in \tombraider where else?, gog's I dunno :p but they must be somewhere
if you edit them w/notepad, find the fullscreen= and fullresolution= parameters and you're free to customize them until the cows come home
fullscreen I'd set =true
fullresolution would probably be fine =original, but here's where you can adjust ad libitum :)
hth