I thought it was best to create a topic for all the games I test with lxdream instead of one for each single game.

The first game is "Giana's Return", which is a freeware homebrew game, see http://www.gianas-return.de. After the Sega logo, there is only the message "Press Y for 60 Hz" displayed, after pressing Y, the screen is just dark.

I genrally have quite huge sound issues with lxdream, I mostly hear mush.

If tried out the game "Rush Rush Rally Racing Deluxe". It's a commercial independent game. It's region free and published on a CD, not GD-ROM.

The game stops after the Sega logo with the error message:

"Received bad packet: 01 00 01 00 A0 68 0C 0C 01 60 00 01"

I've tried the US-version of Grandia II.

The cinematic intro runs at normal speed (>95%) most of the time, sometimes goes down shortly to 70%.
The in-game graphics are almost flawless concerning the 3D. There is some occsional texture flickering, and some minor problems with lighting (shadows).

The game's speed is between 50 and 60 % percent most of the time, most can break down to 20%-40% when the camera moves or a larger part of the environment is shown.

There is problem with the display of two-dimentional things like menus, HUDs or text: Everything that's somehow shaded is too dark on the upper half, and too transparent.

Another game with the same problem as Giana's Return:
M.A. Software's " Abusimbel Profanation Deluxe", which can be downloaded from theire website:
http://www.masoftware.es/

I have tried out Gunlord, a new independent game by NG:Dev. Team. So far, it worked welll and surprisingly fast.

I have tried to apply the patch file, but I did not manage it. Either I'm too stupid or too ignorant.
I copied the lines of code manually into the program files and compiled again. Now the game also start on my computer. There are still some issues with them I have to regard, but both games to not disappear into Nirvana after the "Press Y for 60 Hz mode" message.

Thanks a lot for your help.

Assuming you are in lxdream directory, this should work : patch -p1 < path/to/name.patch

Cool that it works for you too We'll have to see with Nathan if this is the correct fix (entirely possible that I overlooked something). If it's correct then there's more to do. It only covers vram32 DMA accesses ; vram64 accesses would need to be updated too (and it looks more complicated).