JulianDr14/jadyx v0.3.11.0

Jadyx 0.3.11.0 Beta

on GitHub

Game compatibility

See game compatibility for console test results, community reports and known limitations.

New: amiibo

Games can now detect and read amiibo. The controller already asked for engine:virtual_amiibo, but only the virtual gamepad was registered, so HasNfc stayed false and no game could see a tag. The engine is now registered, and the files are managed from the Jadyx Portal and chosen from the in-game menu. Jadyx ships no amiibo files or keys: use your own.

How to use them

1. Start the portal: Settings → File manager → Jadyx Portal → Start portal. Open the address it shows on a PC or phone on the same network and enter the connection code.
2. Open the Amiibo tab, go to Add, choose your .bin files and press Upload.
3. In the game, go to the place where it asks for an amiibo.
4. Hold View + Menu, open Amiibo and choose one. The menu closes and the game reads it.
5. To take it away, open the same row and choose Remove.

Details

• Files: a .bin of 532, 540 or 572 bytes, encrypted or decrypted. Anything else is refused at upload, so it can't reach a game as a damaged tag. Files upload one by one with their own result, so one bad file doesn't stop the rest.
• Key (optional): with a valid 160-byte key_retail.bin, uploaded under Key, games can save data on an amiibo, and that data is kept in its file. Without it, amiibo are read-only. The key stays on the console and can't be read back through the portal.
• Replacing and deleting: a taken name needs an explicit replace, because replacing erases what games saved in the file. Deleting takes two presses.
• List: search that ignores case and accents, A-Z or Z-A order, and a count.
• In-game row: it says when the game isn't looking for an amiibo. The choice is applied after the guest resumes, so the kernel event isn't signalled with the guest paused.
• File names: amiibo paths now open as UTF-8.

Performance

• CPU write queue is off by default. A queued write left its page tracked until the GPU thread drained, so every later store to that page took the slow path. On the console it took one game from about 59 to about 27 FPS. It is now CPU write queue in Settings → Graphics and in each game's Graphics options, for a game that does better with it. cpu_write_defer in boot.cfg still wins over both.
• New per-game setting: Exact GPU reads, off by default. The wait that stopped core 0 for the GPU's whole queue on each rewritten page now only runs when this is on. In one game on the console, turning the wait off took blocking flushes from 150-190/s to under 2/s and the average from 50.1 to 52.2 FPS, with about 8% more draws. See the known issue below. exact_gpu_reads=0|1 in boot.cfg overrides it.

Jadyx Portal

• New layout. The header now picks one view: Games (library and import screens), Amiibo, or System (keys, firmware and logs). Amiibo has its own My amiibo, Add and Key panes, and opens on Add while the list is empty.
• Save loaded into the wrong folder, fixed. A save unpacked from a portal download and zipped again with its <id>-save folder imported "successfully" one level too deep, so the game started from the beginning. The same happened with a save inside a renamed folder. Title id folders may now carry a suffix, such as <id>-save or Windows' (1).
• Saves are found at any depth. The archive folder that shares the most files with the current save is where the new one starts, whatever it is called. If nothing matches and everything sits in one unexplained folder, the import is refused and the current save is left untouched, with a message that names the folder. Another game's id is still refused as a wrong game.

Diagnostics and tools

• Hunt captures sum the frame chain over the CPU profile window, and hunt-report.py opens with a verdict on why the GPU sits idle. The verdict is correlation over the window, not proof.
• The sampling profiler names the guest block behind JIT samples, gives thunk samples to the calling block, and keeps the bytes of the hottest blocks.
• jit_thunks=0 in boot.cfg puts the page table lookup in each block instead of calling a shared thunk, to compare both. Thunks stay the default, because inline code fills the caches much sooner.
• cpu_write_test in boot.cfg compares the current queue, the queue with touching writes merged, and no queue, and logs what each phase costs.
• The renderer test suite runs its scenes with exact GPU reads, the log fetch tool reads the newest registered package, and there is a no-LTO build folder for fast iteration.

Known issues

• Exact GPU reads off by default. With the setting off, a game that reads a preflushable range right after a fence can see the old contents. If a game fails or behaves oddly, turn it on for that game. It can lower the FPS.
• Black objects or screen while shaders build. With New shaders set to Skip or Balanced, a draw whose pipeline is still building is skipped. When later passes depend on it, whole objects or the screen can go black for a moment. Wait avoids this at the cost of more stutter.
• Cold pipeline stutter. Compiling a pipeline can still stutter the first time a new area or effect is seen.
• Pop-in in some engines. In games built on one family of engines, objects and parts of the scenery pop in and out as the camera moves.
• Memory limit. Some games reach the 5 GB (5120 MiB) that Dev Mode gives an app in Game mode. Permafrost keeps more of them running, but heavy games can still stutter while it swaps.
• Frame generation artifacts. Fast-moving edges and some HUD elements can show ghosting with frame generation on.
• Network label. The Ethernet/Wi-Fi label in Device Portal can be wrong on Xbox Series. This is a platform limitation.

Full changelog: v0.3.10.3...v0.3.11.0

Install

You need an Xbox Series X|S in Dev Mode. No keys, firmware or games are included: use your own dumps.

1. Download Jadyx_0.3.11.0_x64.appx and Microsoft.VCLibs.x64.14.00.appx from the assets below. Since Jadyx 0.3.9.0, you no longer need to upload a separate .cer file.
2. On a PC on the same network, open Device Portal at https://<xbox-ip>:11443 (Dev Home shows the address) and accept the browser's certificate warning.
3. Choose Add, pick the Jadyx appx, add the VCLibs appx as a dependency if a compatible version is not already installed, and install.
4. In Dev Home, select Jadyx → View details and set App type to Game. In App mode it runs out of memory.
5. Start Jadyx and send your keys, firmware and games from a PC or phone with the Jadyx Portal: Settings → File manager → Jadyx Portal → Start portal, open the address it shows in a browser on the same network and enter the connection code.
6. Other ways: import keys and firmware from a folder or ZIP on a USB drive in Settings → File manager, and add games from an external folder or USB drive, or copy them to the app's LocalState\games folder with the Device Portal file explorer.

A newer version installs over the previous one and keeps your games, saves and settings. Do not uninstall to update: uninstalling deletes them.

Reporting bugs

Open an issue at https://github.com/JulianDr14/jadyx/issues/new/choose with the Bug Report form. A good report has:

• The Jadyx version (0.3.11.0) and whether it is a Series X or S, in Game mode.
• What you did, what you expected and what happened instead, with the steps to make it happen again.
• The logs from the app's LocalState\jadyx\log folder (Device Portal → File explorer): jadyx_log.txt, jadyx_diag.txt and, for graphics problems, jadyx_graphics_bugs.log. Grab them right after the problem, before launching another game.

Search the existing issues first. Reports about pirated keys, firmware or games are closed. If the bug also happens in the desktop builds of Eden, report it to Eden instead.

Questions, install help and compatibility reports: join the Discord.