game-compatibility
game-compatibility copied to clipboard
xenia-project
4D5307E6 - Halo 3
Tested on https://github.com/xenia-project/xenia/commit/068b2056ca02a707b164693fefc9e0dd9637e6f2
Log:
https://gist.github.com/thesymbol/aa2e7305fde89c4a57be
Issues:
- Nothing happens black screen.
Screenshots:
Halo 3 depends on unimplemented IO Completion Ports. See MSDN.
Kernel methods would be NtCreateIoCompletion/NtRemoveIoCompletion
Someone with nVidia should check this now. With git 16c9718 I am hearing sound for about 10-15 sec. and then it crash. Unfortunately, I have AMD HD7870. Maybe with nVidia someone could see intro.
Also checked with 980. Black screen with main menu audio. Can hear main menu reacting to dpad movement but cannot see results.
After running the game in menu for a few minutes (crashes shortly after):
w> 0000000C libav: Too small input buffer
w> 0000000C libav: is not implemented. Update your Libav version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented.
w> 0000000C libav: If you want to help, upload a sample of this file to ftp://upload.libav.org/incoming/ and contact the libav-devel mailing list.
!> 0000000C libav: Could not collect frame!
A> 0000000C libav failed to decode a frame!
A> 0000000C Processing context 85 (offset 30612, buffer 0, ptr 07304000)
!> 0000000C libav: Could not collect frame!
A> 0000000C libav failed to decode a frame!
I get a black screen with sound with little issue then i pulled out my controller and click some buttons and heard clicks and got into what i assume is the game then then some sounds would repeat over and over and after letting it set there my windows froze with the audio still playing i was forced to restart.
Intel HD reporting in. No crash for me, but black screen and just audio as well.
i7 6700, MSI GTX 1070 running latest drivers as of 30/04/2018, black screen with audio on latest version of Xenia.
Interfacing with the game works sounds and responds, lack of graphical display.
Tested on (https://github.com/xenia-project/xenia/commit/b623c33e0038414824ccf7bd4828a3aeadcd1627)
Issues:
(Black screen during startup intro videos and during main menu, audio is correct however. Wait until you think you should be at the main menu and press "A" twice I think it was, and a new solo campaign will start. Audio is sped up and garbled, out of sync with video which is not hard because the video is slow, and badly corrupt. When you are supposed to have control of master chief, the video from the cutscene had froze, but audio continued. You are asked to look up and then eventually look down, after doing this the game hangs with no further progression.)
Log:
Screenshot(s):
Labels:
(audio-slow gpu-corrupt-drawing gpu-missing-drawing gpu-slow) I gave my best educated guess for the labels.
tested on windows 10 april2018update, intel i5-7600k, 16gb ram, PowerColor PCS+ AMD Radeon R9-290, 3840x2160@60hz monitor
Was able to get into custom games from the menu, menu function seems to work fine just not visible. Once in custom game, shaders and textures do not all load properly, it appears audio is out of sync. Performance is around 0-1fps while playing in custom game but still game play nonetheless.
Game play video - https://youtu.be/vokAxZQOrdc
Campaign now works and fps is much more playable. Fps spikes happen a lot though, audio is sped up during cut scenes, graphics still missing textures and shaders. Video: https://youtu.be/qAdMc3kx9is may 30th release
https://youtu.be/wpm_nWcQWuc Another video showcasing Campaign working, graphic device lost seems to happen commonly around enemy encounters
For me, Halo 3 has now entered regression, crashing when attempting to load into any campaign level. Levels load fine with previous builds of Xenia. Anyone else having same issue? xenia-project/xenia@43b987d
@timernight just about EVERYONE using a Nvidia GPU is having this issue, nobody knows why as it happens at random intervals i got all the way to the part where Chief's vitals spike then got xenia to crash like everyone else later i tried to do this again but got the infamous graphics device lost error way before that.
@aharkboy1006 I was having random crashes like you mention with previous builds with Xenia. With the latest build of Xenia, 43b987da, it consistently crashes at the start the level. Have you tested the latest build or is it just something going on with my computer?
@PyramidH spam the a button the menu still works You could like READ THE COMMENTS AND FIGURE THAT OUT YOURSELF IN 20 SECONDS
Ingame campaign, some major fps drops and freezes, playable framerate most of the time
It loads the game, audio works, the buttons response quickly, except the display which is corrupt most of the time. I'm using the build 1.0.1537-master-pweayvfm from AppVeyor. PC specs:
- Intel Core i5 4460 3,20 Ghz
- 8 GB RAM DDR3 1600 Mhz
- NVIDIA GT 610 2 GB VRAM
- Windows 10 1809 October Update 2018
I know that this graphics card doesn't satisfy the requirements, but the game has never crashed, so I think it could be fixed with some kind of patch.
The intro works well.
Once it loads the menu, the drawing corruptions start appearing. (This time it showed the difficulty menu, which is rare because most of the time is just a noisy pattern as shown in the background).
Then, the campaign is being loaded but the screen still corrupted all the time. In the right section of the window, you can see a dark part where the Halo ring is moving, but the rest of the window just got stuck there and gets brighter until the mission starts.
The cinematic works and I can skip it. I can interact with the game but nothing is being shown on the display except for the load screen. Then, it loads the next mission and it keeps doing the same thing as above.
Here's the log file: xenia.zip
Is the same happening on the d3d12 branch because I am not getting these issues
It seems like no matter what version of Xenia I use, I still only get a black screen with audio and launching campaign is met with rainbows. Seems to only do this with Halo 3. Reach (somewhat) works.
I'm Running an Nvidia GTX 1050ti, Intel i5 7th gen, 8 Gb of ram. I see no reason why it shouldn't be running. Maybe I'm just stupid? What am I missing?
The game seems to be working at a decent rate with Xenia D3D12, But has the black screen with audio with the Vulkan version of Xenia. I said decent because there are some noticeable loading times/freezing between each menu and graphical issues. The Graphical issues that its having are some shading and probably choppy models and geometry (unless the game is already like that). So what I am saying in a nutshell, is that Halo 3 is working at a very decent rate with a good frame rate of around 50 FPS.
PC Specs: CPU: Intel Core i7-8700K CPU @ 3.7GHz RAM: Corsair Vengeance RGB 32gb 3200mhz ddr4 GPU: NVIDIA GeForce GTX 1080 OS: Windows 10 version 1803
The game seems to be working at a decent rate with Xenia D3D12, But has the black screen with audio with the Vulkan version of Xenia. I said decent because there are some noticeable loading times/freezing between each menu and graphical issues. The Graphical issues that its having are some shading and probably choppy models and geometry (unless the game is already like that). So what I am saying in a nutshell, is that Halo 3 is working at a very decent rate with a good frame rate of around 50 FPS.
PC Specs: CPU: Intel Core i7-8700K CPU @ 3.7GHz RAM: Corsair Vengeance RGB 32gb 3200mhz ddr4 GPU: NVIDIA GeForce GTX 1080 OS: Windows 10 version 1803
the game can not go higher then 30 its capped
okay so I've been using the D3D12 Version of xenia and I've been testing Halo 3 just to see how far I can get. I've played up to The Storm. I've experienced a few crashes. Had 2 on Arrival, 2 on Crows Nest, and one on Tsavo Highway. It's really only thanks to rally points that I could get this far. I Should also mention that I got a crash on the cutscene between Tsavo Highway and The Storm. Sadly the Storm is where my journey came to an end. Seems Like every time I get to the scarab battle, my game crashes. It's always at the exact point that the scarab gets loaded in on the checkpoint. I might try looking at the ground to see if it can make it through that way. That's how I got through some other trouble areas.
Update: So other problems I've noticed is that I cannot see the muzzle flash, projectile, and trajectory of the projectiles. the game at random points has a frame spike. And only experienced one crash (i played for a short while for testing). I've probably missed other bugs in the game (excluding this post and the previous one) so I will list them as I continue.