Editing Xbox 360 emulators

Jump to navigation Jump to search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 84: Line 84:
 
:Xenia is the leading [[High/Low_level_emulation|hybrid approach]] Xbox 360 emulator that's made it the furthest. While it isn't nearly as compatible as RPCS3 is for [[PlayStation_3_emulators|PlayStation 3]], impressive performance outshines RPCS3 due to RPCS3's [[PlayStation_3_emulators#Emulation_issues|extremely challenging SPU emulation]] resulting reasonably higher CPU demands. Another reason for performance difference is Xenia utilizes [[High/Low_level_emulation|very high-level emulation (HLE) approach for the CPU, while relying heavily on Low-Level Emulation (LLE) for the GPU]]<ref>[https://discord.com/channels/308194948048486401/308194948048486401/1192362532212576348 Rick's xenia discord message about LLE and HLE]</ref><ref>[https://discord.com/channels/308194948048486401/701111856600711208/1090315143226863616 chrispy's comments about xenia's approach]</ref>. Due to these approaches and other reasons/optimizations (see [[Emulation accuracy]] page): it's making Xenia more reliant on GPU performance instead of CPU (especially compared to RPCS3). But keep in mind that, it's still depends heavily on CPU single thread performance due to graphics API-related calls and focusing solely '''average''' CPU utilization percentage numbers may give you false impression[https://discord.com/channels/308194948048486401/308194948048486401/1199060658059235479]. So in summary: just like most other software emulators, CPU's with better [https://www.cpubenchmark.net/singleThread.html single threaded performance] will give you better framerates than before (considering you're not hitting GPU bottleneck)[https://discord.com/channels/308194948048486401/308194948048486401/518932236746096640]. Xenia supports various [[#Enhancements|enhancements]] and some of the [[#Hardware_features_and_peripherals|hardware features]]. For emulation on Linux: see [[Xenia#Linux_and_SteamOS.2FSteam_Deck|this page]]. For checking if your games work and any fixes, tweaks, or settings, see compatibility list. For people who follow the dev progress, Android builds in CI don't mean there is anything you can even install or "make work" on your device. It's just fragments of Xenia that are compiled into binaries, and those aren't even the most complex parts of the emu. More information on [https://discord.gg/Q9mxZf9 Xenia Discord] in the #dev-android channel under the 'Development' category.
 
:Xenia is the leading [[High/Low_level_emulation|hybrid approach]] Xbox 360 emulator that's made it the furthest. While it isn't nearly as compatible as RPCS3 is for [[PlayStation_3_emulators|PlayStation 3]], impressive performance outshines RPCS3 due to RPCS3's [[PlayStation_3_emulators#Emulation_issues|extremely challenging SPU emulation]] resulting reasonably higher CPU demands. Another reason for performance difference is Xenia utilizes [[High/Low_level_emulation|very high-level emulation (HLE) approach for the CPU, while relying heavily on Low-Level Emulation (LLE) for the GPU]]<ref>[https://discord.com/channels/308194948048486401/308194948048486401/1192362532212576348 Rick's xenia discord message about LLE and HLE]</ref><ref>[https://discord.com/channels/308194948048486401/701111856600711208/1090315143226863616 chrispy's comments about xenia's approach]</ref>. Due to these approaches and other reasons/optimizations (see [[Emulation accuracy]] page): it's making Xenia more reliant on GPU performance instead of CPU (especially compared to RPCS3). But keep in mind that, it's still depends heavily on CPU single thread performance due to graphics API-related calls and focusing solely '''average''' CPU utilization percentage numbers may give you false impression[https://discord.com/channels/308194948048486401/308194948048486401/1199060658059235479]. So in summary: just like most other software emulators, CPU's with better [https://www.cpubenchmark.net/singleThread.html single threaded performance] will give you better framerates than before (considering you're not hitting GPU bottleneck)[https://discord.com/channels/308194948048486401/308194948048486401/518932236746096640]. Xenia supports various [[#Enhancements|enhancements]] and some of the [[#Hardware_features_and_peripherals|hardware features]]. For emulation on Linux: see [[Xenia#Linux_and_SteamOS.2FSteam_Deck|this page]]. For checking if your games work and any fixes, tweaks, or settings, see compatibility list. For people who follow the dev progress, Android builds in CI don't mean there is anything you can even install or "make work" on your device. It's just fragments of Xenia that are compiled into binaries, and those aren't even the most complex parts of the emu. More information on [https://discord.gg/Q9mxZf9 Xenia Discord] in the #dev-android channel under the 'Development' category.
 
::'''canary''' builds compared to the master builds offer improved performance (thanks to [https://web.archive.org/web/20220815204859/https://github.com/chrisps chrisps]/chrispy, disjtqz, Gliniak, AdrianCassar and [https://github.com/xenia-canary/xenia-canary/graphs/contributors other contributors]), it has experimental changes that may or may not work, but it also has more functions/tends to work better. Also some of the [[#Hardware_features_and_peripherals|hardware features]] and [[#Enhancements|enhancements]] are currently only available in this fork and its branches mentioned below. Use [https://github.com/xenia-canary/game-patches this repository] for game-patches which some of them may fix graphical or performance issues.
 
::'''canary''' builds compared to the master builds offer improved performance (thanks to [https://web.archive.org/web/20220815204859/https://github.com/chrisps chrisps]/chrispy, disjtqz, Gliniak, AdrianCassar and [https://github.com/xenia-canary/xenia-canary/graphs/contributors other contributors]), it has experimental changes that may or may not work, but it also has more functions/tends to work better. Also some of the [[#Hardware_features_and_peripherals|hardware features]] and [[#Enhancements|enhancements]] are currently only available in this fork and its branches mentioned below. Use [https://github.com/xenia-canary/game-patches this repository] for game-patches which some of them may fix graphical or performance issues.
::'''canary-netplay'''; this branch is used for online play, see [[Xbox_Live#Xbox_360|Xbox Live]] page Xbox 360 section. Also supports some of the [[#Hardware_features_and_peripherals|system link]] titles.
+
::'''canary-netplay'''; see [[Xbox_Live#Xbox_360|Xbox Live]] page (Xbox 360 section).
 
::'''canary-nukernel''' branch emulates: The [[#Emulation_issues|six individual hardware threads on the original Xbox 360 CPU]], certain kernel timing quirks (clock interrupt update every 1millisecond, "background scheduling"), the kernel's thread scheduler, deferred procedure calls, asynchronous procedure calls (done more accurately than on normal canary, plus kernel ones are supported), much more accurate and portable emulation of synchronization primitives, supports guest objects without creating host objects for them. So certain games that do not work on normal canary can be played on this branch, because the features/quirks they expect are implemented here, but nukernel branch mostly focuses on reimplementing parts of the threading subsystem of the kernel, not io or memory, which are also messed up. Developer of this branch said that: "It really felt like starting from scratch on the kernel side, because for a long time nothing booted on it".[https://discord.com/channels/308194948048486401/701111856600711208/1200116567489384548]
 
::'''canary-nukernel''' branch emulates: The [[#Emulation_issues|six individual hardware threads on the original Xbox 360 CPU]], certain kernel timing quirks (clock interrupt update every 1millisecond, "background scheduling"), the kernel's thread scheduler, deferred procedure calls, asynchronous procedure calls (done more accurately than on normal canary, plus kernel ones are supported), much more accurate and portable emulation of synchronization primitives, supports guest objects without creating host objects for them. So certain games that do not work on normal canary can be played on this branch, because the features/quirks they expect are implemented here, but nukernel branch mostly focuses on reimplementing parts of the threading subsystem of the kernel, not io or memory, which are also messed up. Developer of this branch said that: "It really felt like starting from scratch on the kernel side, because for a long time nothing booted on it".[https://discord.com/channels/308194948048486401/701111856600711208/1200116567489384548]
  

Please note that all contributions to Emulation General Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Emulation General Wiki:Copyrights for details). Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)