It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
GOG usually does a good job in making it's games playable on a modern computer,but sad to say that I have had problems with both Tomb Raider 1...the game menu spins out of control and if you press a key dosbox crashes....and the cut scenes do not work in Tomb Raider 2.
Come one GOG, you can do better then this. Hopefully you will fix these bugs.
And yes,I did email GOG support about both these problems.
Regarding spinning menu in tr1 - try unplugging gamepad, if you have any. It happend to me and that was the solution. Hopefully this will also fix the crashes in menu. If you want to play the game with gamepad (using xpadder or similar software) connect it after the game is launched - it does not make your menu spin (at least for me).
avatar
dudalb: GOG usually does a good job in making it's games playable on a modern computer,but sad to say that I have had problems with both Tomb Raider 1...the game menu spins out of control and if you press a key dosbox crashes....and the cut scenes do not work in Tomb Raider 2.
Come one GOG, you can do better then this. Hopefully you will fix these bugs.
And yes,I did email GOG support about both these problems.
You can also resolve the spinning issue by editing the dosboxTR.cfg file and changing joysticktype from auto to none.

As stoyan said, there are a number of programs you could use to map a gamepad to keyboard controls if you wish to use a gamepad to play. Personally, I've always played TR with the keyboard, so disabling joystick support is not a big deal for me.
avatar
cynicalmatt: You can also resolve the spinning issue by editing the dosboxTR.cfg file and changing joysticktype from auto to none.
Wasn't the initial purpose of GOG to not having to jump through all kinds of hoops to get old games to work properly?
avatar
cynicalmatt: You can also resolve the spinning issue by editing the dosboxTR.cfg file and changing joysticktype from auto to none.
avatar
Elbart: Wasn't the initial purpose of GOG to not having to jump through all kinds of hoops to get old games to work properly?
People really need to remember that not all games will work on all systems (given how many different kinds of software/hardware configurations there are), so tweaking may be required for your setup. And changing one line of text is not a lot of hoops, imo.
avatar
cynicalmatt: As stoyan said, there are a number of programs you could use to map a gamepad to keyboard controls if you wish to use a gamepad to play. Personally, I've always played TR with the keyboard, so disabling joystick support is not a big deal for me.
yes, another software to do it is joytokey. Though I think xpadder is the best option here, but also more expensive. Btw, back then i played TR on keyboard and yesterday I tried it with gamepad - but it doesn't work well for me.
Yep.
After Interstate 76 and Moto series, I have taken a 'wait and see' approach to gog.
Way too many game breaking issues have surfaced with new releases.
:(
avatar
Dave3d: Yep.
After Interstate 76 and Moto series, I have taken a 'wait and see' approach to gog.
Way too many game breaking issues have surfaced with new releases.
:(
That's a reasonable approach. TET has mentioned that they test games on 30+ computers of various combinations before release, however.
avatar
cynicalmatt: You can also resolve the spinning issue by editing the dosboxTR.cfg file and changing joysticktype from auto to none.
avatar
Elbart: Wasn't the initial purpose of GOG to not having to jump through all kinds of hoops to get old games to work properly?
Editing one line in a .cfg file is "jumping through hoops"?

Like pretty much any PC game ever, not all releases will work flawlessly with every one of the almost innumerable PC configurations out there. When I bought Dark Forces way back in 1995, the game simply refused to run on my PC, despite the fact that I more than met the requirements. It just simply would not run until I spent HOURS tweaking every possible variable. That's a game I paid $50 for.

Paying $10 for three games, one of which requires one simple modification, doesn't quite seem like "jumping through hoops." As a veteran PC gamer, I understand that sometimes you have to tweak settings because PCs are not like consoles. Things don't always just work. In the vast majority of cases, they will, but it's like those weird side effects that come with certain medications. Less than 1% of the users will experience it, but because SOMEONE did, they have to mention that eating grapefruit while taking cholesterol medicine can kill you (and yes, that is an actual example).
avatar
dudalb: GOG usually does a good job in making it's games playable on a modern computer,but sad to say that I have had problems with both Tomb Raider 1...the game menu spins out of control and if you press a key dosbox crashes....and the cut scenes do not work in Tomb Raider 2.
Come one GOG, you can do better then this. Hopefully you will fix these bugs.
And yes,I did email GOG support about both these problems.
GOG still does a good job and they get better at it with every release, but every release also brings up new issues. As for the first, that one can be corrected by unplugging gamecontrollers or editing the Dosbox.conf as said. As for the second, non playing videos is in most cases a problem with videocodecs, either the codecs are not present or you may have conflicting codecs.
despite what the fanboys are saying here GOG, i just paid 10 dollars for these games and this broken buggy crap is unacceptable. so i would appreciate if you would FIX IT.
I did find a fix which works, but it requires jumping through quite a few hoops.
I put up a thread describing it in this forum.
And it did NOT involve installing or conflicting codecs.
I am a big customer of GOG, but they blew it with this release, since the issue with music and cut scenes for TR 2 and 3 is a well known one, has been around since Windows XP came out, and a solution was developed long ago. THere is no real excuse for the professional programmers at GOG to have missed this. An explanation,maybe,but no excuse,and it needs to be fixed. I don't consider the fix I found to be a real solution snce it requires quite a few hoops to jump through (including burning 2 cds).
i'm hoping that by the time i'm done with tomb raider one gog will have fixed it, but if not i'll definitely try your fix dudalb.