Installer Steam
log på
|
sprog
简体中文 (forenklet kinesisk)
繁體中文 (traditionelt kinesisk)
日本語 (japansk)
한국어 (koreansk)
ไทย (thai)
Български (bulgarsk)
Čeština (tjekkisk)
Deutsch (tysk)
English (engelsk)
Español – España (spansk – Spanien)
Español – Latinoamérica (spansk – Latinamerika)
Ελληνικά (græsk)
Français (fransk)
Italiano (italiensk)
Bahasa indonesia (indonesisk)
Magyar (ungarsk)
Nederlands (hollandsk)
Norsk
Polski (polsk)
Português (portugisisk – Portugal)
Português – Brasil (portugisisk – Brasilien)
Română (rumænsk)
Русский (russisk)
Suomi (finsk)
Svenska (svensk)
Türkçe (tyrkisk)
Tiếng Việt (Vietnamesisk)
Українська (ukrainsk)
Rapporter et oversættelsesproblem
In the game installation path, go into the BH2Game folder, inside this folder you can find DDrawCompat.ini You can try to play around with some values there, I would suggest changing RenderColorDepth from 16 to 32 (RenderColorDepth = 32). If this do no work try removing the ddraw.dll from the BH2Game folder. You can also try update your graphics card drivers.
Thanks, but none of these suggestions worked to remove the black boxes. The boxes are only around the rocks, trees & men. They are not around vehicles or helicopters.
AMD Radeon RX 6600 with the newest drivers.
Any other suggestions ?
Windows 10 x64 Home
16 GB RAM
Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz, 3501 Mhz, 4 Core(s), 4 Logical Processor(s)
Desktop PC
Everything up to date.
It must be an AMD problem. Updating my drivers seems to be the culprit as far as I can tell. BH 2000 runs flawlessly though.
I've owned the original boxed versions of 2000 & 2002 since they were released. I've installed them again and used dgVoodoo to make them run. The problem is still present with 2002 but not 2000.
Definitely an AMD driver problem.
I'm going to keep searching for a wrapper to try to fix this if at all possible.
Btw, for the menu we use dgVoodoo, and for the game we use DDrawCompat, this is the way we found to make it work with all games. Maybe you can try dgVoodoo working with the game program or maybe you can try another wrapper as you said. Let me know if you managed to make it work.
After clicking "Play", the opening "gameplay" screen seems to freeze and does not respond, the only way out is to log out of the system or reboot.
Also graphics from AMD, RX 6700 XT, latest drivers 24.1.1
It works for myself flawlessly after exhausting every other option.
1. Download dgVoodoo v2.54 (the ONLY version I found to work correctly with this game).
2. Copy the file dgVooDooCpl.exe into your game directory. (where the game exe. is)
3. Copy the files from dgVoodoo from the inside of the MS folder into the same game directory. (D3D8.dll, D3Dlmm.dll and DDraw.dll). Overwrite OLD files when prompted.
4. IMPORTANT STEP : Also copy & Paste the same 3 MS files (D3D8.dll, D3Dlmm.dll and DDraw.dll) into the game subfolder "BH2Game" again overwriting the old files within that folder when prompted (should only be the "DDraw.dll" which overwrites.
5. Open the dgVooDooCpl.exe you placed in your game folder and click the ".\" to the right of "config folder\running instance" to add the game to the address.
6. Within dgVoodoo, click the DirectX tab and set the following :
Resolution: 1920×1080 (or your monitor’s resolution)
dgVoodoo Watermark: Uncheck
Optional:
VRAM: 1024 MB (lower it depending on your graphics card memory)
Filtering: Force point sampled (this will allow you to have pixelated texture bringing the original graphics for nostalgia)
Bilinear blit stretch: Checked (fixed some 3D glitches)
Antialiasing (MSAA): 2x (Remove jagging edges on 3D objects)
This worked perfectly for me. If it doesn't work for you I'm sorry. The only step I did not use was Filtering for nostalgia.
This also worked for Beach Head Desert War by using the same steps.
Here is the actual link to the solution if I'm allowed to put it here :
https://gamingph.com/2022/07/how-to-play-the-beach-head-2002-in-modern-pc-windows-10-or-11/#:~:text=Once%20you%20have%20a%20license,G%3A%2FOldGames%2FBH2002).
This is amazing G66, we are going to evaluate this solution and maybe delivery by default on the next builds.
Thank you for sharing this solution.