game-compatibility
game-compatibility copied to clipboard
xenia-project
4E4D084F - Armored Core V
Tested on https://github.com/benvanik/xenia/commit/b5469b57bacdba11d13c9052fda9e2128abef5ba
Hangs at intro...
Log
Screenshots:
LABELS:
state-intro
Tested on benvanik/xenia@52c75c8 i7, 16GB RAM, 8GB NVIDIA GPU(Vulkan support)
Issues:
Game now crashes when pressing start after the "intro"
Log:
Screenshot(s):
Labels:
(recommended labels)
state-crash
Xenia crashes after the game issues a Visual Studio exception to set a thread name. Possibly can't read the string or something?
chances are you can ignore anything that shows in visual studio. Try running the exe outside of VS and see if it makes a difference
Update:
Results are the same.
!> 00000028 ResolvePath(system:) failed - no root found !> 00000028 MmAllocatePhysicalMemoryEx: bad protection bits
GPU:
!> 00000028 GPU: Read from unknown register (044B) writes to unk. register
- 0081
- 0082
- 0E00
- 0E40
- 1E4E
Unimplemented:
- XamPartyGetUserList
- XamPartySendGameInvites
- XamPartySetCustomData
- XamPartyGetBandwidth
- XamShowPartyUI
- XamShowCommunitySessionsUI
Undefined:
!> 00000028 XMsgStartIORequest: app 00000000 undefined
Tested:
On (https://github.com/benvanik/xenia/commit/eecc9d0aea1a0c841d9ddfa0d182c22a10ea4f86)
Log:
Labels:
- state-intro
- regression
- kernel-unimplemented-features
Tested on https://github.com/xenia-project/xenia/commit/af61a9764778096928245a1e3dde4b6e6b169160
Completed first mission. Xenia guest crashes after that. 50-60FPS with vsync off and shaders cached.
:warning:Textures do not render on AC units unless you set d3d12_readback_resolve=true. This will severely impact performance though.
More Screenshots
state-gameplay | gpu-readback
I have some findings about this game. My config is the same as the one generated by Xenia on startup, with three lines changed: kernel_display_gamma_type = 1 log_level = 3 protect_zero = false (Required for the guest to not crash after completing or exiting any mission, a similar issue happens on the PS3 version using RPCS3, the game seems to have some weird memory handling)
Moving onto actual in-game issues, they are the following:
- Random host crashes/CTDs that leave behind a crashdump. These happen randomly inside missions, big or small, and it seems to be associated with how fast the player plays the missions. Playing some missions slow fixes the issue, but to play the entire game slowly is not an optimal fix. Reliability history shows this.
- Player-controlled units like ACs lack all colors while inside any missions (inside menus like Workshop it shows completely fine), and render black (part previews in the Shop also render black), no matter what colors you chose in the Paint category in the Workshop. Fixed by setting "d3d12_readback_resolve" to "true" at the cost of a massive performance impact.
Above is inside the Workshop.
Below is in the AC Testing Ground.
Unrelated to Armored Core V, but these issues happen on Armored Core - Verdict Day as well, as they're the same engine!
Here is the log for Armored Core V. xenia.log Here is the crashdump for Xenia (host crash). Crashdump Here is the crashdump analysis using WinDbg. crashdump_analysis.txt
Edit: Goes without saying that I should have specified what that 'protect_zero' change was for. It's to fix a crash that happens after exiting or completing any mission. The guest crashes if the value isn't set to false. Here is the link to the log of the occurence. armoredcorev-crashaftermission.log
Could likely do with some new labels. gpu-readback state-gameplay (almost playable if the mission crash and random CTDs are fixed)
A little bit of testing later...
A contributor in the Discord server gave me a build that still used libav (before ffmpeg) after another contributor found out that the random host crashes was related to audio problems in the latest builds. Using the libav build, and the mission that I could always recreate the host crash bug on, I was able to complete it successfully.
This is right before the end cutscene of the mission.
Below is an image of subquest progress, I had done quite a few things in the mission to try and force a host crash to happen (playing faster than usual, etc.) but it just didn't crash anymore on libav.
Still, the same typical guest crash after completing or exiting a mission will happen if protect_zero isn't set to false
Other than that, something about ffmpeg likely broke the game.
Edit: New labels, likely? regression gpu-readback state-gameplay
So I believe the game is running smooth now with the libav build and protect_zero = false settings. But I have encountered a new issue. When I get through tutorial mission and have to input TEAM NAME prompt, I can't enter any characters. I'm am using a Xbox 360 controller with Xinput settings. This is strange because I could input PILOT NAME fine previously with the keyboard even though the Xbox controller as primary input. I'm open to suggestions. Meanwhile, I'll try some workarounds.
So I believe the game is running smooth now with the libav build and protect_zero = false settings. But I have encountered a new issue. When I get through tutorial mission and have to input TEAM NAME prompt, I can't enter any characters. I'm am using a Xbox 360 controller with Xinput settings. This is strange because I could input PILOT NAME fine previously with the keyboard even though the Xbox controller as primary input. I'm open to suggestions. Meanwhile, I'll try some workarounds.
Use cheat engine speedhacks to slow down the game when you enter the team name entry
Game is playable at 60fps if protect_zero=false. I had to limit the game to 5fps in rivatuner so I could input the team name without the text box immediately disappearing. AC textures are still pich black if readback_resolve=false but game runs under 30fps with it enabled. Still experiencing ffmpeg related crashes: xenia.log
Hello everyone i tried the Xenia Master download and the setting changes everyone suggested and nothing new but some crashes here and there.Although i tried Xenia Canary with protect_zero=false, readback_resolve=false and d3d12_readback_resolve=true and the game works perfectly with high fps and no texture or sound issues so i thought finally it works but when i try to play the story mission 00 after some time playing(different every time) it crashes and shows this:
I searched online to no avail and the problem persists after many retries of the mission it has a 100% crash rate.All other missions work normally without issues so something in that mission i imagine causes the error?Also i use the latest canary build .
When I get through tutorial mission and have to input TEAM NAME prompt, I can't enter any characters. Decreasing CPU speed do not help.
Hey despot I had exactly the same issue I solved it by reseting all the changes on the config that previous users suggested and kept only protect_zero=false and then after finishing the name entry putting the config changes back also the FPS problem that exists I have solved by changing to Xenia canary the December 5th version and now the game runs perfectly and hasn't crashed once !!
Alas, it doesn't help. Lowering the FPS doesn't help either. have yoy tried it on xenia canary ?Perhaps that will help and running the game stock without the config tweaked
@Petrouvis can you give me the link to the version of xenia canary you're using? i tried downloading this version as you said ur using december 5th version. but i am still having crash issue like you were. maybe i downloaded wrong version
@Petrouvis can you give me the link to the version of xenia canary you're using? i tried downloading this version as you said ur using december 5th version. but i am still having crash issue like you were. maybe i downloaded wrong version
Of course its version 43d7fc515 of December 11th i said the wrong date my mistake here is the link https://github.com/xenia-canary/xenia-canary/releases/tag/43d7fc5 and if this doesnt work i spoke yesterday on the discord the team has about the crashing issue and i think they fixed it with today's release so try that too!
Hello everyone i tried the Xenia Master download and the setting changes everyone suggested and nothing new but some crashes here and there.Although i tried Xenia Canary with protect_zero=false, readback_resolve=false and d3d12_readback_resolve=true and the game works perfectly with high fps and no texture or sound issues so i thought finally it works but when i try to play the story mission 00 after some time playing(different every time) it crashes and shows this:
Same crash in Mission 00. Happens reliably at some point in the mission, but not consistently. I've made it to the tunnels once, but usually it happens before the first big helicopter. This is using Xenia_Canary from yesterday.
Hello everyone i tried the Xenia Master download and the setting changes everyone suggested and nothing new but some crashes here and there.Although i tried Xenia Canary with protect_zero=false, readback_resolve=false and d3d12_readback_resolve=true and the game works perfectly with high fps and no texture or sound issues so i thought finally it works but when i try to play the story mission 00 after some time playing(different every time) it crashes and shows this:
Same crash in Mission 00. Happens reliably at some point in the mission, but not consistently. I've made it to the tunnels once, but usually it happens before the first big helicopter. This is using Xenia_Canary from yesterday.
It also happened to me around the point of the helicopter but I tried a different version from December 11th like I am saying at a comment above and somehow it fixed it , perhaps I got lucky.
Hello everyone i tried the Xenia Master download and the setting changes everyone suggested and nothing new but some crashes here and there.Although i tried Xenia Canary with protect_zero=false, readback_resolve=false and d3d12_readback_resolve=true and the game works perfectly with high fps and no texture or sound issues so i thought finally it works but when i try to play the story mission 00 after some time playing(different every time) it crashes and shows this:
Same crash in Mission 00. Happens reliably at some point in the mission, but not consistently. I've made it to the tunnels once, but usually it happens before the first big helicopter. This is using Xenia_Canary from yesterday.
It also happened to me around the point of the helicopter but I tried a different version from December 11th like I am saying at a comment above and somehow it fixed it , perhaps I got lucky.
I'm happy to report i got through story mission 00 without crashes on first try. I was using a xenia-canary build from the xenia discord:
https://discord.com/channels/308194948048486401/701111856600711208/1053217251840503848
here is the file, if you don't use discord xenia_canary.zip
my config changes: max_queued_frames = 5 d3d12_readback_resolve = true protect_zero = false
For story mission 01, i tried it with "d3d12_readback_resolve = false". Also worked without crash on first try. Still black ACs though
edit: third and fourth story missions also worked without crashes also "vsync = false " massively boosts the framerate. it feels like 140 FPS
I've been able to get through most story missions with few issues using the changes listed here and a little brute force, however I'm now getting hard walled by Story Mission 06, and Order mission 63 was giving me problems for a while. I am currently using the Jan 9 2023 build of Canary, though i did have to use an old master build with config edits listed in this thread to get through the Team Name prompt at the beginning of the game.
my config changes: kernel_display_gamma_type = 1 max_queued_frames = 5 protect_zero = false vsync = false
I've been able to get through most story missions with few issues using the changes listed here and a little brute force, however I'm now getting hard walled by Story Mission 06, and Order mission 63 was giving me problems for a while. I am currently using the Jan 9 2023 build of Canary, though i did have to use an old master build with config edits listed in this thread to get through the Team Name prompt at the beginning of the game.
my config changes: kernel_display_gamma_type = 1 max_queued_frames = 5 protect_zero = false vsync = false
using the build i mentioned in my earlier post, i had no problems going through story mission 06 and all missions leading up to it. No crashes, on first try
Oddly enough, even though i'm using "d3d12_readback_resolve = false" which makes your AC and all enemy ACs black, in story mission 05 the corporation-mech at the end with the giant energy weapon is fully textured
edit: i've beaten all the story missions now. last few missions again with "d3d12_readback_resolve = true". not because of crashes (there were none 👍) but to see the AC textures again. Was able to start up VD on same build and transpher save-data without problems.
I've been able to get through most story missions with few issues using the changes listed here and a little brute force, however I'm now getting hard walled by Story Mission 06, and Order mission 63 was giving me problems for a while. I am currently using the Jan 9 2023 build of Canary, though i did have to use an old master build with config edits listed in this thread to get through the Team Name prompt at the beginning of the game. my config changes: kernel_display_gamma_type = 1 max_queued_frames = 5 protect_zero = false vsync = false
using the build i mentioned in my earlier post, i had no problems going through story mission 06 and all missions leading up to it. No crashes, on first try
Oddly enough, even though i'm using "d3d12_readback_resolve = false" which makes your AC and all enemy ACs black, in story mission 05 the corporation-mech at the end with the giant energy weapon is fully textured
I completely missed the link, whoops I did have a minor hiccup in story mission 07 where the game froze a few times in the span of maybe 2 minutes but that aside, i was able to finish up story missions 06-09 with no issues using the build you mentioned.
I've been able to get through most story missions with few issues using the changes listed here and a little brute force, however I'm now getting hard walled by Story Mission 06, and Order mission 63 was giving me problems for a while. I am currently using the Jan 9 2023 build of Canary, though i did have to use an old master build with config edits listed in this thread to get through the Team Name prompt at the beginning of the game. my config changes: kernel_display_gamma_type = 1 max_queued_frames = 5 protect_zero = false vsync = false
using the build i mentioned in my earlier post, i had no problems going through story mission 06 and all missions leading up to it. No crashes, on first try
Oddly enough, even though i'm using "d3d12_readback_resolve = false" which makes your AC and all enemy ACs black, in story mission 05 the corporation-mech at the end with the giant energy weapon is fully textured
That is because Chief (the enemy in the pictures) has a few different forms throughout the campaign's story mode. Two of which are considered enemies instead of customized ACs (you fight his AC form at one point, and that one is completely black) due to the way they use their Overed Weapons (the giant cannon you see in the images) in a way that violates game rules (they fire faster than you can with the same build, have infinite time to use them whereas you have a time limit.
And since, in those cases, he's not a player-customization, his textures work fine.