game-compatibility
game-compatibility copied to clipboard
xenia-project
584108A9 - Bean (GoldenEye 007 XBLA)
@kabomber I got a little bit farther into the game when I plugged in my controller instead of using Bluetooth, but get stuck at the Dam opening music.
@kabomber I got a little bit farther into the game when I plugged in my controller instead of using Bluetooth, but get stuck at the Dam opening music.
Yes i am at the same situation and i dont know what to do to get past this any ideas?
Tried on two different machines, but get stuck at the same spot. Tried redownloading both the game and Xenia just in case, but same issue.
Tried on two different machines, but get stuck at the same spot. Tried redownloading both the game and Xenia just in case, but same issue.
ive been looking online and someone on reddit has same issue but no word of it being fixed
https://www.reddit.com/r/Roms/comments/lbpl0y/goldeneye_007_project_bean_xb360/
Tried on two different machines, but get stuck at the same spot. Tried redownloading both the game and Xenia just in case, but same issue.
ive left a comment on here about it not working so hopefully someone will have answers
https://www.youtube.com/watch?v=aIwWLCcY1bw&feature=share
After some tinkering I tried to launch the game, but I also run into the black screen issue - I can make it through the menus but once I load the first level I get a black screen and the music. Ryzen 7 3700X / Radeon RX 5700 / 16GB RAM
About the same here :
_1rst launch : Xenia create the save, then crash (see log) 2nd launch : Xenia run the game, black screen but I hear the sound/music, and I can even hear that I can naviguate trough menus ! Xenia doesn't crash (I end it manually) (see log)
Other Xbox360 marketplace game = works
Tryed with gpu_allow_invalid_fetch_constants either false or true = same
AMD R9 270 on Win7
xenia_1rst_startup.log xenia2ndstartup.log
I'm running the game on a i7 7700K with a RTX 2060 and the game crashes every single time I complete a mission.
UPDATE: Be aware of your antivirus. Put Xenia as an exception to allow the emulator to make changes or else it will crash because your antivirus (in my case AVG) will denie access to making changes.
I'm running the game on a i7 7700K with a RTX 2060 and the game crashes every single time I complete a mission.
Please consider attaching your "xenia.log" files. Coders arent's magicians.
EDIT : Seems I have report of the same problem with Nvidia users aswell, so it's definitly not AMD only
Im running AMD Ryzen 5 3600 16gb ram ATI Radeon RX 5500 XT Seagate ST6000NE000-2KR101 (SATA 5TB
From: Benoit Adam [email protected] Sent: 04 February 2021 02:06 To: xenia-project/game-compatibility [email protected] Cc: GitHubDan01 [email protected]; Comment [email protected] Subject: Re: [xenia-project/game-compatibility] 584108A9 - Bean (Goldeneye 007 XBLA) (#1704)
I'm running the game on a i7 7700K with a RTX 2060 and the game crashes every single time I complete a mission.
Attach your "xenia.log" files. Coders arent's magicians.
— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/xenia-project/game-compatibility/issues/1704#issuecomment-772969284, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH3RZ3QOUASSFNPL5V5ZFTTS5H6LTANCNFSM4XBDPPTA.
Maybe it's from that, but with latest nvidia drivers (461.40) i have too many issues on Xenia (crashs/bugs and a unwanted reboot), then rollback to 457.51. Now all works and i don't have any strange crashs/issues. I have a 2070 RTX card.
where can i get the 457.51. xenia build?
From: backgamon [email protected] Sent: 04 February 2021 18:18 To: xenia-project/game-compatibility [email protected] Cc: GitHubDan01 [email protected]; Comment [email protected] Subject: Re: [xenia-project/game-compatibility] 584108A9 - Bean (GoldenEye 007 XBLA) (#1704)
Maybe it's from that, but with latest nvidia drivers (461.40) i have too many issues on Xenia (crashs/bugs and a unwanted reboot), then rollback to 457.51. Now all works and i don't have any strange crashs/issues. I have a 2070 RTX card.
— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/xenia-project/game-compatibility/issues/1704#issuecomment-773508924, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH3RZ3RGZKWEVENUXF72EJDS5LQGNANCNFSM4XBDPPTA.
where can i get the 457.51. xenia build?
he talk about nvidia driver version, not xenia.
ok but nvidia drivers 2070 RTX card?
i thought rtx wasnt nvidia
From: Benoit Adam [email protected] Sent: 04 February 2021 20:15 To: xenia-project/game-compatibility [email protected] Cc: GitHubDan01 [email protected]; Comment [email protected] Subject: Re: [xenia-project/game-compatibility] 584108A9 - Bean (GoldenEye 007 XBLA) (#1704)
where can i get the 457.51. xenia build?
he talk about nvidia driver version, not xenia.
— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/xenia-project/game-compatibility/issues/1704#issuecomment-773576999, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH3RZ3S77QIMRUDBTQRPIWTS5L57HANCNFSM4XBDPPTA.
Worked flawlessly from start to finish on my end.
R5 3600, GTX 1060 on driver version 460.79
And yes @GitHubDan01 RTX is NVidia's 2000 and 3000 series.
Runs without issue, played right through to the end.
AMD Ryzen 3700X and Nvidia RTX 2070 Super on driver version 461.09.
Also crashing with 6800XT as soon as the dam opening starts. Both with ROV off and on.
Once or twice it didn't crash, the screen just went black and the music played. Unable to recreate this though.
Note that the released build came pre-modified by the leaker so it's possible any issues could be down to those changes, only two are mentioned in the nfo:
Removed crashing leaderboard from menu & watch Replaced 16:10 aspect ratio with 21:9
Other changes are also apparent though (XBL option removed from MP menu, and 9+ different nops/branches to .reloc section), who knows how many more things were patched.
Had a look at undoing some of them, managed to revert all the ones I could find by searching for nops & .reloc branches, but could always be other kind of code/data patches that I missed.
Seems like a good place to post how to revert these, hopefully the info might come in useful for someone. Don't know the effect of all of these but I'm 100% sure the addresses here were changed, hopefully the replacements bring it closer to how it was originally.
E: we now have the original XEX for this "August 2007" (actually November 2007) release! I posted more details in a post below. The patches here aren't really needed any more, but in case anyone was wondering my replacements were correct for 7 out of the 9 patches (with one of the incorrect ones I was already uncertain about) :)
Revert 21:9 to 16:10 (strings inside files\loc\english\options\default.str were also patched)
82003D40: 40 15 55 55 -> 3F CC CC CD
Destructable-prop related?:
8209F5F0: 49 04 10 80 -> 3D 60 82 00
Something related to gun shots:
820A3E50: 49 03 C6 10 -> 48 00 00 20
Prop related? uncertain (replacement may be incorrect):
820B40E0: 3D 00 82 F2 49 02 C6 6C -> D0 2B 01 F0 4E 80 00 20
Restore leaderboards on watch/pause menu:
820C4914: 49 01 B8 EC -> 7F 8B E2 14
Allow leaderboard watch menu option to be selected:
820C742C: 49 01 91 34 -> 91 49 F9 BC
820C7450: 49 01 90 80 -> 91 49 F9 BC
Menu/signin related:
820F774C: 48 FE 8E E4 -> 3B DE 00 01
Restore leaderboards on main menu:
820F7D00: 48 FE 89 B0 -> 3B 5A 00 01
Restore XBL option inside multiplayer menu, at 0x820FFC00 change
60 00 00 00 60 00 00 00 60 00 00 00 60 00 00 00 60 00 00 00
to
48 03 6E D9 7F E4 FB 78 38 A0 00 01 38 C0 00 00 4B FF 59 49
Note that the released build came pre-modified by the leaker so it's possible any issues could be down to those changes, only two are mentioned in the nfo:
Removed crashing leaderboard from menu & watch Replaced 16:10 aspect ratio with 21:9
Other changes are also apparent though (XBL option removed from MP menu, and 9+ different nops/branches to .reloc section), who knows how many more things were patched.
Had a look at undoing some of them, managed to revert all the ones I could find by searching for nops & .reloc branches, but could always be other kind of code/data patches that I missed.
Seems like a good place to post how to revert these, hopefully the info might come in useful for someone. Don't know the effect of all of these but I'm 100% sure the offsets here were changed, hopefully the replacements bring it closer to how it was originally.
Revert 21:9 to 16:10 (strings inside files\loc\english\options\default.str were also patched)
82003D40: 40 15 55 55 -> 3F CC CC CDDestructable-prop related?:
8209F5F0: 49 04 10 80 -> 3D 60 82 00Something related to gun shots:
820A3E50: 49 03 C6 10 -> 48 00 00 20Prop related? uncertain (replacement may be incorrect):
820B40E0: 3D 00 82 F2 49 02 C6 6C -> D0 2B 01 F0 4E 80 00 20Restore leaderboards on watch/pause menu:
820C4914: 49 01 B8 EC -> 7F 8B E2 14Allow leaderboard watch menu option to be selected:
820C742C: 49 01 91 34 -> 91 49 F9 BC820C7450: 49 01 90 80 -> 91 49 F9 BCMenu/signin related:
820F774C: 48 FE 8E E4 -> 3B DE 00 01Restore leaderboards on main menu:
820F7D00: 48 FE 89 B0 -> 3B 5A 00 01Restore XBL option inside multiplayer menu, at 0x820FFC00 change
60 00 00 00 60 00 00 00 60 00 00 00 60 00 00 00 60 00 00 00to48 03 6E D9 7F E4 FB 78 38 A0 00 01 38 C0 00 00 4B FF 59 49
What files do we need to edit, and I assume it's just a standard hex editor that's required?
What files do we need to edit, and I assume it's just a standard hex editor that's required?
Just the default.xex really, decrypt/decompress it using xextool -eu -cu default.xex then with a hex editor search for eg 40 15 55 55 and replace with 3F CC CC CD, same for the other patches.
Xenia should load the modded XEX fine, but for running on an actual 360 you might need to resign it with xextool -md default.xex first.
(if you're running it via the 700MB 30BA9271... file you'll need to extract that with Velocity first)
What files do we need to edit, and I assume it's just a standard hex editor that's required?
Just the default.xex really, decrypt/decompress it using
xextool -eu -cu default.xexthen with a hex editor search for eg40 15 55 55and replace with3F CC CC CD, same for the other patches.Xenia should load the modded XEX fine, but for running on an actual 360 you might need to resign it with
xextool -md default.xexfirst.(if you're running it via the 700MB
30BA9271...file you'll need to extract that with Velocity first)
Hmm... I've extracted default.xex using XEXTOOL with the syntax you provided, but when I open default.xex it in a hex editor, I don't have the offsets that you've listed. My offsets start at 00000000 and go up to 00F22FF0. Not sure what I'm missing here.
@hardeejr: The addresses @emoose is refering to are in-memory patches. You can get the file offsets by subtracting 81FF 62C0 from those given values (for example the first offset is at 00006D40). Also FYI when replying to the comment literally before yours, the quote comment context is not needed!
@hardeejr: as @Stealthii said the addresses in my post are for the in-memory XEX, for modifying the XEX itself you can just search for the bytes I'd given (should only be a single match for each one), or adjust the address as @Stealthii suggested.
E: actually it seems subtracting from the memory addr might not give the proper file offset for every address I posted, as different XEX blocks can have different amounts of 'compressed' zeroes inside (even when XEX has been set to uncompressed...)
I've added a new feature to my xex1tool app that can convert between addresses for you, it should give accurate results for uncompressed XEX2 files, haven't tried it with any others yet though: https://github.com/emoose/idaxex/releases
xex1tool is a command-line app, just run it using cmd like xex1tool.exe -a 0x82003D40 uncompressed.xex and it'll print the file offset in the command-prompt.
crash on open: i5-6500 CPU with GTX 1060 6GB
logs attached.
notice a few:
w> 00002FB8 Too few processor cores - scheduling will be wonky
not sure if that is the root cause
before the CRASH DUMP notice this:
w> F8000008 Too few processor cores - scheduling will be wonky
!> F8000028 ==== CRASH DUMP ====
!> F8000028 Thread ID (Host: 0x00002D68 / Guest: 0x00000006)
!> F8000028 Thread Handle: 0xF8000028
!> F8000028 PC: 0x82370E68
!> F8000028 Registers:
my CPU has 4 and the warning comes if smaller then 6 (logical_processor_count) https://github.com/xenia-project/xenia/blob/ff5c5f01e0e31abee675be7e48c11c20642a40fb/src/xenia/kernel/xthread.cc#L771
Hi, Getting a black screen and then the windows closes and no alert or notification. I am running it on a PC with an AMD Ryzen 5 2600 3.4 GHz and an NVIDIA GeForce GT 610. Attached are the logs I dont see anything in the log that is giving me any clue as to why its not working as I was able to get it running on a PC with less processing power and no GPU UPDATE - I tried running it with ROV off also and same result, I can attach a copy of that log if needed. Thanks xenia.log
I tried it on two pc's. On the weaker PC (i5 4570 + Radeon RX580) the game runs fine. On the more capable PC (Ryzen 7 3800x + RX Verga64) it only runs the intro and menu. When starting the mission, the screen stays black, but i can hear the music of the first level. After i close xenia, and restart the game, it doesn't run at all, just a white screen. i have to deleted shaders. Seems like the shaders are not compiled correctly? Is it a problem of the two different GPU's or CPU's?
I tried it on two pc's. On the weaker PC (i5 4570 + Radeon RX580) the game runs fine. On the more capable PC (Ryzen 7 3800x + RX Verga64) it only runs the intro and menu. When starting the mission, the screen stays black, but i can hear the music of the first level. After i close xenia, and restart the game, it doesn't run at all, just a white screen. i have to deleted shaders. Seems like the shaders are not compiled correctly? Is it a problem of the two different GPU's or CPU's?
did you get on your i5 also in log: w> F8000008 Too few processor cores - scheduling will be wonky ??
AMD 5700 XT users, I've had success with rolling back to the AMD 5/26/2020 20.4.2 driver and the 5/18/2020 build of Xenia. (also delete old xenia config from your documents folder)
