game-compatibility
game-compatibility copied to clipboard
xenia-project
544307D5 - Ninja Gaiden II
https://github.com/xenia-project/xenia/commit/b5469b57bacdba11d13c9052fda9e2128abef5ba Loads, plays some sounds for a moment and crashes.
Tested on (https://github.com/xenia-project/xenia/commit/2314f25fb7252bb9054fd7c863e1a57bee90282d)
Issues:
Black screen on 3D part (there intro video on game engine)
Log:
Screenshot(s):
Labels:
gpu-missing-drawing kernel-save-file-errors state-menus
It kicks out for me when the old man talks in the intro... Surprisingly the Vulkan Build makes it the farthest.
As someone with programming experience, what can I do to help with this issue? I've been looking for an open-source to contribute to and this is the only one that interest me. Plus, I've always wanted to play this game again, but I sold my 360 years ago, and Team Ninja, unfortunately, does not seem interested in remaking this game for PC or making another Ninja Gaiden.
Tested on https://github.com/xenia-project/xenia/commit/c51cba080b4ecbbc2b4c55e1338a630b363b1843
No change since Dec 4 comment. Menus run fine, but anything 3D renders as black. Xenia freezes during first cutscene.
Brought it up in the debugger... THis is the first exception...
case 0x0007003D: {
// XMPCaptureOutput - not sure how this works :/
XELOGD("XMPCaptureOutput(...)");
assert_always("XMP output not unimplemented");
return X_STATUS_UNSUCCESSFUL;
}
then this assert gets triggered multiple times... assert_true(!fetch_instr.attributes.stride || vertex_binding.stride_words == fetch_instr.attributes.stride); the stride_words is like 11 when stride 12
Then when it finally crashes this is the exception... Unhandled exception at 0x00007FFAB706CCB7 (ntdll.dll) in xenia.exe: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFFF.
static int do_signal(_Cnd_t cond, int all) { // release threads if (all) { cond->_get_cv()->notify_all(); } else { cond->_get_cv()->notify_one(); }
return _Thrd_success;
}
I am out of my depth with this 3D stuff...
assert_true(!fetch_instr.attributes.stride ||
vertex_binding.stride_words == fetch_instr.attributes.stride);
So what information can I gather. I am programmer and past QA engineer.
This is the main reason I keep downloading builds... Does it work? Nope.
So I am choosing Start Path of the Accolate
and it stops at a text screen that needs an A button... and even then the rendering is squirly...
then I think it is playing a video I don't see (I don't care) and some sounds.
and then eventually crash...
Like I think the engineers did some magic with the 360 to get their performance and unless they help with the emulator it will never be ported.
Hi guys, i am from Brazil. I come here to encourage developers to emulate this game. Ninja Gaiden is the most famous ninja in the world and, in this series, this version is considered by all to be the best! When she went to Playstation they removed many aspects including blood, skills and other factors that everyone loved. Please guys! We need to keep the Ninja legend alive! This can only be preserved if we have it on the PC since the consoles over time get lost or spoiled ... That's what we do folks! We collect games, we collect our various lives as heroes! They are our adventures! That's what we do! You will make it! Just don't give up! I'm sure they will find a way if they keep trying and thinking about other possibilities! Hugs! Stay in Peace!
The game gets in game as of xenia-project/xenia@9a74df49 from January 4 2021, but only parts of the UI draw. Everything else isn't rendered. If you can defeat the enemies without the visuals, it seems to trigger the next cutscene where the game hangs.
Strangely, that that older xenia build (0807076e6) finally runs this game with proper 3d image and gameplay, but models are missing, but newer xenia build (a577a4ae8) have same issues like 2 years ago - only ui with artifacts.
Xenia 0807076e6 (15feb):
Xenia a577a4ae8 (18feb):
The worst thing is that unfortunately so far they haven't been fixed and this game is just incredible! It's sad that I couldn't be playing it, I really wanted to! Just a miracle for me to be able to play before I die.
@NeTw0rK21 I can't see any master commits on February 15th or 18th, those are probably pull request builds for branches based on some older version of Xenia. We shouldn't be showing them publicly in the history of course, but we haven't found a way yet to do so without disabling building itself for pull request checking.
all of the UI ive seen is perfectly fine, the hit counter also works. all the game needs now is for the 3D(?) image sorry idk the term but all it needs now is the actual gameplay
it was even in 60fps lol im gonna pop off whenever this is playable
Is there a specific module that you would recommend as a starting point?
On Mon, May 17, 2021, 3:36 AM sukarettov @.***> wrote:
[image: image] https://user-images.githubusercontent.com/84314158/118459002-49eeca80-b6c9-11eb-93ff-1bbee6988c7b.png [image: image] https://user-images.githubusercontent.com/84314158/118459020-4f4c1500-b6c9-11eb-93d8-730de0b8b9c7.png all of the UI ive seen is perfectly fine, the hit counter also works. all the game needs now is for the 3D" image dsorry idk the term but all it needs now is the actual gameplay
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/xenia-project/game-compatibility/issues/296#issuecomment-842135323, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEXRPVLGB6UOSLR7UFTYHDDTODISJANCNFSM4BWH5Y6Q .
Is there a specific module that you would recommend as a starting point? … On Mon, May 17, 2021, 3:36 AM sukarettov @.***> wrote: [image: image] https://user-images.githubusercontent.com/84314158/118459002-49eeca80-b6c9-11eb-93ff-1bbee6988c7b.png [image: image] https://user-images.githubusercontent.com/84314158/118459020-4f4c1500-b6c9-11eb-93d8-730de0b8b9c7.png all of the UI ive seen is perfectly fine, the hit counter also works. all the game needs now is for the 3D" image dsorry idk the term but all it needs now is the actual gameplay — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#296 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEXRPVLGB6UOSLR7UFTYHDDTODISJANCNFSM4BWH5Y6Q .
what do you mean by module?
for model fix without downgrading to a previous canary build, go to d3d12_clear_memory_page_state in the config file and set this setting from false to true.
Tested on https://github.com/xenia-project/xenia/commit/7977d7ab9
Started a new game and defeated a few enemies. Saves work. :warning:Minor graphical issues with corrupted textures. :warning:Major wonkiness going on with missing character models. Use latest Canary to mitigate.
More Screenshots
state-gameplay | vsync-off-speedup | requires_protect_zero_false | gpu-drawing-corrupt
Tested on master@c4eae232f (Apr 2 2022) build from a blank save. While the DX12 renderer works fine, on Vulkan (or at least Vulkan combined with Win 7) the opening video is a black screen and the emulator stops dead afterwards. Leaving Xenia open for 1.5 hours showed no progress or sound. Given that the CPU was pegged at 100% all this time I'm sure some of this is down to a CPU bottleneck, but that can't fully explain this (I hope).
PC Specs: Windows 7 SP1 Professional Intel Core i3-6100 AMD Radeon Pro WX3100 8GB DDR3 Xenia Log Ninja Gaiden 2.zip
Hello, I just got to play Ninja Gaiden 2 again. My playthrough has been really good so far. Minor bugs here and there but I'm really happy that the game runs well. But I've encountered an Issue that I'm not able to find any reference to at all.
I've reached Chapter 5 by now and while the opening cutscene plays the game/emulator freezes and closes. I've looked at the logs folder but cannot really work something out of it but maybe you can.
I think this is the point inside the logs where the emulator starts to crash.
Log (click to expand)
i> F8000004 XE_SWAP
G> F8000004 Loaded tiled 1280x720x1 2D k_8_8_8_8 texture with 1 unpacked mip level, base at 0x1F045000 (pitch 1280, size 0x00398000), mips at 0x00000000 (size 0x00000000)
A> F80000E0 XmaContext: kicking context 2 (buffer 0 362374/524288 bits)
A> F800000C Processing context 2 (offset 362374, buffer 0, ptr 0x21ef8d000)
A> F80000E4 XmaContext: kicking context 3 (buffer 0 357786/524288 bits)
A> F800000C Processing context 3 (offset 357786, buffer 0, ptr 0x21ef6a000)
A> F80000E4 XmaContext: disabling context 2
A> F80000E0 XmaContext: disabling context 3
A> F80000E0 XmaContext: kicking context 2 (buffer 0 367118/524288 bits)
A> F800000C Processing context 2 (offset 367118, buffer 0, ptr 0x21ef8d000)
A> F80000E4 XmaContext: kicking context 3 (buffer 0 362355/524288 bits)
A> F800000C Processing context 3 (offset 362355, buffer 0, ptr 0x21ef6a000)
A> F80000E0 XmaContext: disabling context 2
A> F80000E4 XmaContext: disabling context 3
A> F80000E4 XmaContext: kicking context 1 (buffer 0 103712/524288 bits)
A> F800000C Processing context 1 (offset 103712, buffer 0, ptr 0x21efc0000)
A> F80000E4 XmaContext: kicking context 3 (buffer 0 366682/524288 bits)
A> F80000E0 XmaContext: kicking context 2 (buffer 0 371671/524288 bits)
A> F800000C Processing context 2 (offset 371671, buffer 0, ptr 0x21ef8d000)
A> F800000C Processing context 3 (offset 366682, buffer 0, ptr 0x21ef6a000)
A> F80000E0 XmaContext: disabling context 1
A> F80000E4 XmaContext: disabling context 2
A> F80000E0 XmaContext: disabling context 3
A> F80000E0 XmaContext: kicking context 2 (buffer 0 373968/524288 bits)
A> F800000C Processing context 2 (offset 373968, buffer 0, ptr 0x21ef8d000)
A> F80000E4 XmaContext: kicking context 3 (buffer 0 368878/524288 bits)
A> F800000C Processing context 3 (offset 368878, buffer 0, ptr 0x21ef6a000)
A> F80000E0 XmaContext: disabling context 2
A> F80000E4 XmaContext: disabling context 3
A> F80000E0 XmaContext: kicking context 2 (buffer 0 376270/524288 bits)
A> F80000E4 XmaContext: kicking context 3 (buffer 0 371172/524288 bits)
A> F800000C Processing context 2 (offset 376270, buffer 0, ptr 0x21ef8d000)
A> F800000C Processing context 3 (offset 371172, buffer 0, ptr 0x21ef6a000)
A> F80000E0 XmaContext: disabling context 2
A> F80000E4 XmaContext: disabling context 3
A> F80000E4 XmaContext: kicking context 3 (buffer 0 375602/524288 bits)
A> F80000E0 XmaContext: kicking context 2 (buffer 0 380859/524288 bits)
A> F800000C Processing context 2 (offset 380859, buffer 0, ptr 0x21ef8d000)
A> F80000E4 XmaContext: disabling context 3
A> F80000E4 XmaContext: kicking context 3 (buffer 0 375602/524288 bits)
A> F800000C Processing context 3 (offset 375602, buffer 0, ptr 0x21ef6a000)
A> F80000E0 XmaContext: disabling context 2
A> F80000E4 XmaContext: kicking context 1 (buffer 0 104672/524288 bits)
A> F80000E4 XmaContext: disabling context 3
A> F800000C Processing context 1 (offset 104672, buffer 0, ptr 0x21efc0000)
A> F80000E4 XmaContext: disabling context 1
A> F80000E0 XmaContext: kicking context 2 (buffer 0 385424/524288 bits)
A> F80000E4 XmaContext: kicking context 3 (buffer 0 380208/524288 bits)
A> F800000C Processing context 2 (offset 385424, buffer 0, ptr 0x21ef8d000)
A> F800000C Processing context 3 (offset 380208, buffer 0, ptr 0x21ef6a000)
A> F80000E0 XmaContext: disabling context 2
A> F80000E4 XmaContext: disabling context 3
A> F80000E0 XmaContext: kicking context 2 (buffer 0 388043/524288 bits)
A> F80000E4 XmaContext: kicking context 3 (buffer 0 382568/524288 bits)
A> F800000C Processing context 2 (offset 388043, buffer 0, ptr 0x21ef8d000)
A> F800000C Processing context 3 (offset 382568, buffer 0, ptr 0x21ef6a000)
A> F80000E0 XmaContext: disabling context 2
A> F80000E4 XmaContext: disabling context 3
A> F80000E4 XmaContext: kicking context 3 (buffer 0 387334/524288 bits)
A> F800000C Processing context 3 (offset 387334, buffer 0, ptr 0x21ef6a000)
A> F80000E0 XmaContext: kicking context 2 (buffer 0 392460/524288 bits)
A> F800000C Processing context 2 (offset 392460, buffer 0, ptr 0x21ef8d000)
A> F80000E0 XmaContext: disabling context 2
A> F80000E4 XmaContext: disabling context 3
A> F80000E0 XmaContext: kicking context 2 (buffer 0 396945/524288 bits)
A> F80000E4 XmaContext: kicking context 1 (buffer 0 105824/524288 bits)
A> F800000C Processing context 1 (offset 105824, buffer 0, ptr 0x21efc0000)
A> F80000E0 XmaContext: kicking context 3 (buffer 0 391678/524288 bits)
A> F800000C Processing context 2 (offset 396945, buffer 0, ptr 0x21ef8d000)
A> F800000C Processing context 3 (offset 391678, buffer 0, ptr 0x21ef6a000)
A> F80000E4 XmaContext: disabling context 1
A> F80000E0 XmaContext: disabling context 2
A> F80000E4 XmaContext: disabling context 3
A> F80000E0 XmaContext: kicking context 2 (buffer 0 401057/524288 bits)
A> F80000E4 XmaContext: kicking context 3 (buffer 0 395450/524288 bits)
A> F800000C Processing context 2 (offset 401057, buffer 0, ptr 0x21ef8d000)
A> F800000C Processing context 3 (offset 395450, buffer 0, ptr 0x21ef6a000)
If you need further insight of the log just let me know.
I'm currently using:
Xenia-canary (canary_experimental@32a7b38f) Windows 11 Home AMD Ryzen 7 3700X NVIDIA RTX 2070 SUPER 32GB DDR4 @3200MHz
Should be the frame at where the game freezes and closes:
I've also added the CH10 patch in hope that it's a similar issue but that didn't help either. If you got any idea on how to fix the issue I'd greatly appreciate it.
Hello, I just got to play Ninja Gaiden 2 again. My playthrough has been really good so far. Minor bugs here and there but I'm really happy that the game runs well. But I've encountered an Issue that I'm not able to find any reference to at all.
I've reached Chapter 5 by now and while the opening cutscene plays the game/emulator freezes and closes. I've looked at the logs folder but cannot really work something out of it but maybe you can.
I think this is the point inside the logs where the emulator starts to crash.
Log (click to expand) If you need further insight of the log just let me know.
I'm currently using:
Xenia-canary (canary_experimental@32a7b38f) Windows 11 Home AMD Ryzen 7 3700X NVIDIA RTX 2070 SUPER 32GB DDR4 @3200MHz
Should be the frame at where the game freezes and closes:
I've also added the CH10 patch in hope that it's a similar issue but that didn't help either. If you got any idea on how to fix the issue I'd greatly appreciate it.
This must be a regression with the speedup update because this game was perviously playable start to finish with no issues (apart with the freezing that the patch resolved). Using an older version of Xenia before that speedup should resolve this. In my experience the game runs full speed before this if you have a strong enough computer.
Hello, I just got to play Ninja Gaiden 2 again. My playthrough has been really good so far. Minor bugs here and there but I'm really happy that the game runs well. But I've encountered an Issue that I'm not able to find any reference to at all. I've reached Chapter 5 by now and while the opening cutscene plays the game/emulator freezes and closes. I've looked at the logs folder but cannot really work something out of it but maybe you can. I think this is the point inside the logs where the emulator starts to crash. Log (click to expand) If you need further insight of the log just let me know. I'm currently using: Xenia-canary (canary_experimental@32a7b38f) Windows 11 Home AMD Ryzen 7 3700X NVIDIA RTX 2070 SUPER 32GB DDR4 @3200MHz Should be the frame at where the game freezes and closes:
This must be a regression with the speedup update because this game was perviously playable start to finish with no issues (apart with the freezing that the patch resolved). Using an older version of Xenia before that speedup should resolve this. In my experience the game runs full speed before this if you have a strong enough computer.
Thank you, with the older emulator the game works again. Appreciate it!
Thank you, with the older emulator the game works again. Appreciate it!
How did you transfer your save? Game crashes when I try to load saves from the Canary version.
Thank you, with the older emulator the game works again. Appreciate it!
How did you transfer your save? Game crashes when I try to load saves from the Canary version.
Are you using save states? You shouldn't be because I would imagen that doesn't work.
If you use the saves created Content folder, I'd just copy over the folder ID that corresponds to the game and that works. I'm able to move my save back and forth from a Xenia build from August 2021 to work around crashes.
May i ask , why my contribution was deleted? it took a lot of time to wrote that guide. i made a full guide on how to emulate this game back in april, i addressed every issue i knew about and wrote a workaround for that. i know for a fact that some , if not every single issue that was present then, is still present. may i ask , why that was deleted AND could you restore it for a few days, so i can at least copy my text and share it elsewhere?
May i ask , why my contribution was deleted? it took a lot of time to wrote that guide. i made a full guide on how to emulate this game back in april, i addressed every issue i knew about and wrote a workaround for that. i know for a fact that some , if not every single issue that was present then, is still present. may i ask , why that was deleted AND could you restore it for a few days, so i can at least copy my text and share it elsewhere?
@Finnsen1 It was full of typos and other errors, and had the resolution patch embedded in the message instead of a link to it so users could potentially use an outdated version. The main reason it was deleted is because it contained links to piracy, so I can't provide a copy of your guide here.
If you want to continue this discussion you can add me on Discord: Margen67#9510
I'm also on the Xenia Discord server: https://discord.gg/Q9mxZf9
This is a longstanding audio issue, but I don't see it reported anywhere.
Ninja Gaiden II has an audio bug where randomly all sound will completely stop working & an emulator restart is required to get audio to return.
It's impossible to force it to trigger, and happens sometimes very quickly (As soon as you get to the main menu) other times, it doesn't trigger for over an hour.
I've tried to consistently replicate by starting up the game and leaving it idle, and letting the title screen loop, and sometimes it will happen right as the game starts, other times I've seen it take over 20 mins, both times doing the exact same thing (Booting the game, pressing no buttons)
This happens in all versions of Canary. I have no tested the non-canary builds, but the game is unplayable in those.
Hello, I just got to play Ninja Gaiden 2 again. My playthrough has been really good so far. Minor bugs here and there but I'm really happy that the game runs well. But I've encountered an Issue that I'm not able to find any reference to at all. I've reached Chapter 5 by now and while the opening cutscene plays the game/emulator freezes and closes. I've looked at the logs folder but cannot really work something out of it but maybe you can. I think this is the point inside the logs where the emulator starts to crash. Log (click to expand) If you need further insight of the log just let me know. I'm currently using: Xenia-canary (canary_experimental@32a7b38f) Windows 11 Home AMD Ryzen 7 3700X NVIDIA RTX 2070 SUPER 32GB DDR4 @3200MHz Should be the frame at where the game freezes and closes:
This must be a regression with the speedup update because this game was perviously playable start to finish with no issues (apart with the freezing that the patch resolved). Using an older version of Xenia before that speedup should resolve this. In my experience the game runs full speed before this if you have a strong enough computer.
Thank you, with the older emulator the game works again. Appreciate it!
Which older build made the game work for you? Also, where did you find the Ch 10 patch?
Hello, I just got to play Ninja Gaiden 2 again. My playthrough has been really good so far. Minor bugs here and there but I'm really happy that the game runs well. But I've encountered an Issue that I'm not able to find any reference to at all. I've reached Chapter 5 by now and while the opening cutscene plays the game/emulator freezes and closes. I've looked at the logs folder but cannot really work something out of it but maybe you can. I think this is the point inside the logs where the emulator starts to crash. Log (click to expand) If you need further insight of the log just let me know. I'm currently using: Xenia-canary (canary_experimental@32a7b38f) Windows 11 Home AMD Ryzen 7 3700X NVIDIA RTX 2070 SUPER 32GB DDR4 @3200MHz Should be the frame at where the game freezes and closes:
This must be a regression with the speedup update because this game was perviously playable start to finish with no issues (apart with the freezing that the patch resolved). Using an older version of Xenia before that speedup should resolve this. In my experience the game runs full speed before this if you have a strong enough computer.
Thank you, with the older emulator the game works again. Appreciate it!
Which older build made the game work for you? Also, where did you find the Ch 10 patch?
August 31st 2021 (9c74b4cab) build wont freeze at Chapter 5, it might be worth just playing the whole game with the build unless you're not getting fullspeed. The patch was removed by a mod, it used to he posted above.
The user you quoted misspoke, it's Chapter 12 actually that needs the patch.
Keep in mind there is currently no fix to the audio randomly turning off in the game.
I've reposted the patch below: [[patch]] name = "Skip Chapter 12 crash" desc = "None" author = "Gliniak" is_enabled = flase
[[patch.be32]]
address = 0x82834C78
value = 0x3BC00000
Tested the game today and it's all garbled polygons. Was there a regression?
@Tasosgemah
Make sure you set the following parameter in your config toml from false to true in the latest canary build. It took me an ordinate amount of time to find this..
d3d12_clear_memory_page_state = true
