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

×
I have a 1.73ghz dual core with 2gigs of ram, windows sp3, intel 945 video card.
I tried (in vain) to fix my own issue with parts of the menu being hidden while playing the original Redneck Rampage, by changing the resolution with the original setup and with the graphic mode setup, and it was fruitless, it was negative fruit. Because now whenever I kill someone, or get hit by the car (intentionally), it lags and I get graphical errors (not an error message, just large portions of the screen turning one color). After changing my settings back, I'm still suffering the same issues.
How can I get it back to a playable state?
This question / problem has been solved by Fallomimage
avatar
Weclock: I have a 1.73ghz dual core with 2gigs of ram, windows sp3, intel 945 video card.
I tried (in vain) to fix my own issue with parts of the menu being hidden while playing the original Redneck Rampage, by changing the resolution with the original setup and with the graphic mode setup, and it was fruitless, it was negative fruit. Because now whenever I kill someone, or get hit by the car (intentionally), it lags and I get graphical errors (not an error message, just large portions of the screen turning one color). After changing my settings back, I'm still suffering the same issues.
How can I get it back to a playable state?

I have the same issues with the same specs. Changing the graphics mode to OpenGL and 640x480 helped a lot.
I appear to have the same issues with Suckin' Grits route 66.
Attachments:
dfdfd.jpg (97 Kb)
avatar
Fallom: I have the same issues with the same specs. Changing the graphics mode to OpenGL and 640x480 helped a lot.

that did it!
I have a terrible framerate, no matter what options I tried - I tried to change the graphics mode, the resolution in both the game's exe and the setup.exe, the compatibility mode to other versions of Windows (I use XP), and so on... but nothing worked, I get a pretty bad framerate :( Also, because of the framerate, the audio isn't quite right either, and I need to press the buttons more times in some cases in the menu. Anyone can help?
Pentium IV 2.5 GHz
768 MB RAM
nVidia GeForce 7300 GT 256 MB
Windows XP Professional
I am not alone. I have a Wibrain B1h (1.2 ghz processor) w/ 1 gb ram. I tired EVERYTHING. GOG should post updated system reqs if they are going to use DOSbox! I am going to try it later on my quad core desktop later and if it doesnt run on there I want my money back! I have done some research on the web and see that there are some other things people have tried other than dosbox that has worked. BuildXP or something. I thought that GOG would have tested this stuff and done this kind of work for me! It runs, don't get me wrong, but the framerate is totally unplayable. I already owned 2 of the 3 games in the package!
I'm having similar problems with unplayable frame rate. No matter what option I select, this computer (1.7 GHz Intel w/ 1 GB RAM) can't run it fast enough.
Any ideas? BuildXP experiences?
avatar
tsel: I'm having similar problems with unplayable frame rate. No matter what option I select, this computer (1.7 GHz Intel w/ 1 GB RAM) can't run it fast enough.

Same here. Game is unplayable :(
(Sempron 2500+, 1GB RAM)
I hope, that admins also read the so-called SOLVED posts, for these problems are just NOT solved.
I've tried to play this game on my Dell inspiron 1525, and the best performance I got was from "overlay" mode in the graphics setup.
Still, when the screen got a bit more crowded, or I just picked up things, the framerate dropped, and this caused some sound breaking too.
VERY annoying indeed.
I've tried all other settings, direct3d doesn't help, and the game doesn't even start in Opengl mode (note: I have the latest directx installed.)!!!
Why is that?
Post edited March 01, 2009 by rob.liefeld
My frame rate in Bioshock on 1440x900 everything on high dx9 is better than 640x480 in Redneck Rampage. I was very dissapointed i have double system requirements and this is unplayable!
same here only reason i even gave this company a shot was this game i already owned it but wanted to play it on my laptop(vista 4 gigs of ram)and nada what gives
I'm having the same problems here. my computer is an old junk heap (1.8Ghz, 1.75Gb Ram) and I was looking forward to playing this. Unfortunately it lags like hell. Any help would be greatly appreciated!
Intel Core duo, 3GB ram laptop, Vista Home, Rides Again works as it did 12 years ago on my pentium II, meaning very well and smooth. Original redneck does not work on my Vista though. The only option was to manually work in DosBox with the following commands

core=dynamic
cycles=auto
cycleup=500
cycledown=20

This is for frame rate
Then use the dosbox to get into the game folder, run setup, choose a resolution no more than 800x600, choose the sound and play with the interrupt if it doesn't work with the default, then save and exit. Type nolfb in the dosbox and press enter, then type rampage and it should work fine. The only problem is that the game will apear in a window and not full screen.
avatar
vercingetorix52: Intel Core duo, 3GB ram laptop, Vista Home, Rides Again works as it did 12 years ago on my pentium II, meaning very well and smooth. Original redneck does not work on my Vista though. The only option was to manually work in DosBox with the following commands

core=dynamic
cycles=auto
cycleup=500
cycledown=20

This is for frame rate
Then use the dosbox to get into the game folder, run setup, choose a resolution no more than 800x600, choose the sound and play with the interrupt if it doesn't work with the default, then save and exit. Type nolfb in the dosbox and press enter, then type rampage and it should work fine. The only problem is that the game will apear in a window and not full screen.
NOLFB is no necessary with DOSBox.

Instead open dosbox.conf and change machine=svga_s3 to machine=vesa_nolfb
Post edited October 05, 2010 by DosFreak
Also, as well as changing the machine setting to vesa_nolfb, you might like to set your memory to 32mb instead of the default 16mb. To do so, change memsize=16 to memsize=32. Works a charm for me.