search

ptitSeb / box86-compatibility-list

Box86 Compatibility List (Games and Software)
MIT License
61 stars 2 forks source link

Halo: Combat Evolved #69

Open Hacker1245 opened 3 years ago

Hacker1245 commented 3 years ago

Description

Menu text is glitched, game and sound seem to work fine. Multiplayer is untested. Needed to use a patched nocd exe.

Tested on

RPi 4 with Twister OS

Status

Previous behavior: None reported

Current behavior: Menu text is glitched, game works fine overall.

Screenshots

image

OpenGL

Mesa 20.2 - no overrides

Additional Information

Link to the patched exe - http://www.gameburnworld.com/dl/dl.php?file=HaloCombatEvolvedv1.01NoCDPublicServerPatchFixedexeEng.rar

olivergrosche commented 3 years ago

hi there, i got the demo version of halo running on a rp400 ingame with around 5 fps. the full version states an error "Cannot allocate required memory Some other application has loaded".

Hacker1245 commented 3 years ago

@olivergrosche I had no such error, grabbed the iso from here: https://archive.org/details/HaloCEPC

olivergrosche commented 3 years ago

thanks, can you tell me how you installed it?

Hacker1245 commented 3 years ago

just mounted the iso, ran the installer and swapped the exe (patched exe is linked)

marcospampi commented 2 years ago

actually, there's no reason to use an unofficial nocd, use the Custom Edition one and update to 1.10. It should fix a great deal of issues.

vrdaveb commented 8 months ago

Regardless of whether you use Halo 1.0 or Halo 1.10, it performs a memory mapping check at start that fails on some 64-bit memory managers. 1.0 shows a message about the system having 0MB of system memory (and 0MB of graphics memory), which you can dismiss, but then it crashes with a mapper error. 1.10 just says "Cannot allocate required memory" as described above. This does not happen on a real x86-64 linux system (Steam Deck), even with the same versions of Halo and Wine/Proton.

ptitSeb commented 8 months ago

Halo: The Mastechief Edition do works fine on my side (without EAC), but the system requirement are higer than the orginal version.

Regardless of whether you use Halo 1.0 or Halo 1.10, it performs a memory mapping check at start that fails on some 64-bit memory managers. 1.0 shows a message about the system having 0MB of system memory (and 0MB of graphics memory), which you can dismiss, but then it crashes with a mapper error. 1.10 just says "Cannot allocate required memory" as described above. This does not happen on a real x86-64 linux system (Steam Deck), even with the same versions of Halo and Wine/Proton.

That might be a regression, I'm pretty I've seen a version running of it.