sNeaksieGarrett on 11/1/2010 at 04:51
I realize this is a long shot, but I'm looking to TTLG for answers.:p
So, I've got this fucking problem on Diablo 1 on my machine. If I play it on my desktop computer, the colors get all funky. I DID try searching for help elsewhere, but no suggestions worked. Except for one: if you alt tab and go back, it apparently fixes it for a time. HOWEVER, that was before I upgraded my graphics card and machine. I've now got an ATI RAdeon HD 4650, and it stays permanently rainbowish. :(
So, any ideas? Anyone even know what I'm talking about?
Oh, and on another note: this game is fucking difficult. :wot: (compared to Diablo 2, which is what I first played in the series.)
june gloom on 11/1/2010 at 04:52
are you sure you didn't just get a leaked version of diablo 3
sNeaksieGarrett on 11/1/2010 at 04:54
Yes.
No, I'm not on crack. I'm not the only person that's seen this before... it's a problem with newer machines
EvaUnit02 on 11/1/2010 at 04:58
Newer gen video cards have a problem with 8-bit colours, Starcraft and Thief 2 have similar issues. Look for some sort of mod which forces the game to be displayed in 32-bit colours.
june gloom on 11/1/2010 at 05:11
i should have added the AHAWHAW at the end of my post to signify that i was in fact joking
gunsmoke on 11/1/2010 at 05:29
Quote Posted by dethtoll
are you sure you didn't just get a leaked version of diablo 3
LOL. That was fucking clever. :thumb:
sNeaksieGarrett on 12/1/2010 at 01:22
Thanks for the suggestion, but that'd take forever to find. In any case, I have a solution! I did some more research. Hopefully this will help others.
DISCLAIMER: You do this at your own risk, so don't blame me if it doesn't work, or screws up the computer.
I found this executable called (
http://www.beyondlogic.org/consulting/processutil/processutil.htm) Process.exe which allows you to kill a program from command line. Well, you put this into a batch file, and kill explorer.exe for diablo 1 to work properly. I know, it's a pretty crazy fix, but it works for me. I was looking up diablo and found a (
http://www.facepunch.com/showthread.php?t=874586) facepunch thread where someone suggested that it was explorer.exe in windows xp that was causing the problem (something to do with how windows looks?) and a solution. Solution was to create a batch file that kills explorer (temporarily) while playing diablo. Doing so fixes the color problems!
Oh, the reason I'm using process.exe instead of windows'
tskill command (win xp home) or taskkill (win xp pro) is because A. I use win xp home, and B. tskill doesn't work right.
Code:
ECHO OFF
process -k explorer.exe
"C:\Games\Diablo\diablo.exe"
pause
START C:\Windows\explorer.exe
Copy and paste the above into a notepad file and save it as diablo.bat (Save as type should be set to All Files) Then, whenever you want to play diablo, just use this file. You will need to press spacebar on the little window after quitting diablo. Make sure you put the correct paths for diablo.exe and explorer.exe (Note: I tried doing it without the PAUSE command and explorer was restarted right as diablo was starting, and therefore the fix does not work.)
doctorfrog on 15/1/2010 at 08:08
Try lowering your color depth to 256 colors. Try running the game in a VM.
e: whups nvm, seems you have your own fix. carry on.
catbarf on 15/1/2010 at 11:28
Forcing it to run in 256-bit color mode (using the compatibility option in the exe) would probably solve that problem without needing to kill explorer.exe.
sNeaksieGarrett on 15/1/2010 at 17:30
Nope, believe me I tried that. Doesn't work.
Tried different compat. modes, tried 256 colors, tried 640x480 resolution... any and none of those fixed the problem. Which is why I had to use the explorer trick.
Doctorfrog, my computer can't run on 256 colors from the Display panel. Modern graphics cards don't even give you the option. I've tried to use a VM before, and those just aren't meant for anything other than basic tasks it seems.
