Crack No Cd Star Wars Episode 1 Racer Windows

Yes, now I remember: I grabbed the crack because the original installer can't run on 64 bit architecture. But thank to your links, I downloaded the patched installer and reinstalle dthe game from scratch from the CD, so that now I can enjoy the game with its movies (see picture). But surprises aren't finished: despite the fact that the 'Clean ZBUFFER @1.0 fix' flag fixed the texture problems in the first race, today I won the race (usually I am a very bad pilot!) and I passed to the second race, to discover with my disappointment that the bug replicates in there (curiously, with textures in red rather than in white.) and the game freezes. Definitely there's still work to do.

Star Wars Episode 1: Racer. More Star Wars Episode 1: Racer Fixes. Star Wars Episode 1: Racer SPA Star Wars Episode 1: Racer FRA/US.

Hey, I also tried out the game after finding out about DXWnd and I got the game working with it in Fullscreen (1920x1080 with Widescreen executable editing) with the settings as screen shows in the attachment. At first I also ran into the same error as posted by gho, but with the patched executable - which was on the ftp from LucasArts - I was able to fix it. Windowed mode only crashed for me, that is why I tried Fullscreen.

I am getting some graphical glitches though on some maps (objects from far away are visible, as seen in the 2nd attachment), which - depending on the race - can get very annoying. I am using Windows 8 Pro 64-Bit and an NVidia graphic card. Very interesting stuff. Yesterday evening I was busy, so I just had a quick glance to this new ideas, but the 'language barrier' didn't make it easy to make my opinion on this.

One problem is the russian forums, that translated with google translator seemed to tell that not everyone was happy with the patch (actually, I couldn't understand if anyone was happy at all), maybe (but I have to read it again) it works with the reactos ddraw libraries, that I tried but with no success. Second language problem is the source code all in assembly. Most of it is pretty straight forward, it is a ddraw proxy that intercepts only a few specific operations (DirectDrawCreate, CreateSurface) with a test condition where the new surface has ZBUFFER requested capability. The problem is that is was not so easy to understand what the proxy is doing in such a case. Maybe the quickest way would be to find a contact with this guy and simply ask, then replicate the trick in C language within DxWnd.

The patch includes two game executables (plain and no-CD cracked) but I think this is only because of the PDRAW.DLL library rename, but this is not at all necessary with dxWnd. So, in conclusion, there's some investigation to carry on.

BTW, may I ask if the patch worked for you? Here it didn't work, but I fear it is because of the 64bit architecture. It doesn't matter. Since he left his assembly source code, I assume he won't mind if we get inspired. The logic seems pretty simple: the hooker intercepts every CreateSurface() method in order to find out which is the currently used ZBUFFER surface (I take there can't be more than one active at a time) and grab its characteristics (through a GetSurfaceDesc() method). Shabloni kassovih chekov word. Then, for this surface triggers a cleanup action on the Unlock() termination that is simply this sequence: Unlock() Lock() - again, probably to be sure to get the surface memory pointer memset(0xFFFFFFFF) to all surface size Unlock() An interesting thing is that the size is calculated as w*h/2, that is good for 16bit ZBuffers only, so maybe the lack of support for nVidia cards may lay in this detail.