← Back to AI Insights
Gemini Executive Synthesis

Eglantine emulator's stability and compatibility with AMD RX 5700 (RDNA 1) GPUs when running Mario Kart World.

Technical Positioning
Achieving stable and functional game emulation across diverse hardware configurations and emulator build versions.
SaaS Insight & Market Implications
This issue highlights critical stability and compatibility challenges within the Eglantine emulator, specifically its failure to run 'Mario Kart World' on AMD RX 5700 (RDNA 1) GPUs. The problem manifests as consistent crashes during the race introduction or even at the initial loading screen, varying by build version. The fact that the original 'Eden NX2 emulator' does not exhibit this issue points to regressions or specific architectural incompatibilities introduced in Eglantine. The pain point is the fragmented and unreliable user experience across different hardware and software iterations. Market implications include the significant engineering effort required to ensure broad hardware compatibility and maintain stability in experimental software, underscoring the difficulty of delivering a consistent, functional product in a rapidly evolving technical landscape.
Proprietary Technical Taxonomy
Mario Kart World crashes race intro AMD RX 5700 (RDNA 1) Builds 94 and 96 EGLANTINE Eden emulator Eden NX2 emulator

Raw Developer Origin & Technical Request

Source Icon GitHub Issue Nov 1, 2026
Repo: Djihads80/Eglantine
Mario Kart World crashes during race intro on AMD RX 5700 (RDNA 1)

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Affected Build(s)

Builds 94 and 96

### Description of Issue

Mario Kart World crashes during race intro on AMD RX 5700 (RDNA 1) – Builds 94 and 96

### Description

I am experiencing consistent crashes when trying to play **Mario Kart World** using EGLANTINE, which is based on the Eden emulator.

The game behaves differently depending on the build version, but I have not been able to get past the race introduction and actually start a race.

Interestingly, I do not experience this issue when using other emulator builds, including the original Eden NX2 emulator.

### Issue on Build 94

The game launches successfully and I can get into the game.

However, when starting a race, the emulator consistently crashes during the race introduction.

More specifically:

1. The game loads successfully.
2. I can start a race.
3. The race introduction begins, showing the track/map.
4. The camera flies across the map to showcase the track.
5. Normally, this is where the player can press the A button to skip the introduction.
6. At this point, the emulator crashes consistently.

Even if I do not press anything and let the entire track preview play until the end, the emulator still crashes.

As a result, I cannot get into an actual race.

### Issue on Build 96

Build 96 behaves differently.

When launching Mario Kart World, the game gets stuck/crashes at the initial loading screen.

I cannot get past t...

Developer Debate & Comments

kraibse • Nov 1, 2026
Attach the log file so I can check out that issue. We'll be getting some updates for the experimental AMD build today.
CloudP4bbs • Nov 1, 2026
Same GPU here, RX 5700 (RDNA 1) on Windows 11 / MSVC 19.44, build-96 lineage (base `feff94e` + local fixes) — and the race intro does **not** crash, so it is probably not the RDNA 1 driver by itself. The crash I had on every boot of a race was a division by zero in the emulator, not the driver: `Vulkan::Image::InitSparseLayers` divided by `imageGranularity.width/height`, and this driver answers `VkPhysicalDeviceProperties.limits.imageGranularity = {0, 0, 0}`. That is a hard `0xC0000094` at `InitSparseLayers+0x296`, usually 55 s to 4 min into the session and most reliably when a course starts loading (that is when the sparse image set is created). It is reported with the address and the patch in . With the guard applied (`tile_width = granularity.width ? granularity.width : block_width`, same for height/block_height), on this exact GPU: ``` menu 60 FPS / 16.68 ms race (Whistlestop) 51 FPS / 17.32 ms course-select globe 60 FPS, terrain missing (tesse...
kraibse • Nov 1, 2026
The division by zero errors are fixed on the [Experimental AMD builds](https://github.com/Djihads80/Eglantine/releases/tag/build-99) that will soon be merged to mainline.
CloudP4bbs • Nov 1, 2026
This may be your crash, and there is a PR for it: ****. If your log ends right after a sparse image is created and the Windows event log shows `0xc0000094` (integer divide by zero) with a fault offset in `Vulkan::Image::InitSparseLayers`, it is the zero `imageGranularity` case I described above — not the RDNA 1 driver. The PR falls back to the format block size instead of dividing by zero. If instead you get `0xc0000005`, then it is a different path and the log of that run would settle it.

Adjacent Repository Pain Points

Other highly discussed features and pain points extracted from Djihads80/Eglantine.

Extracted Positioning
Eglantine emulator's development platform choice (GitHub) and legal vulnerability to DMCA claims.
Maintaining legal defensibility and operational continuity for an experimental emulator project against corporate legal action.
Top Replies
PastaLaPate • Nov 1, 2026
already synced on https://git.panintegr.al/Backup/Eglantine
bachimusprime • Nov 1, 2026
No, I'm saying that the main development itself shouldn't be on GitHub lmao
AverageDood • Nov 1, 2026
If the repo is synced as a mirror, then development can continue on the mirror without problems at any time. Besides, Yuzu got DMCA'd because they blatantly admited to piracy by pushin TotK commits...
Extracted Positioning
Eglantine emulator's texture cache management and VRAM utilization
Achieving stable and accurate emulation, particularly regarding graphics rendering and memory management, on specific GPU architectures.
Top Replies
NicoRipenn • Nov 1, 2026
Found the exact trigger, and a correction to the description. **Trigger:** it closes when I skip the pre-race intro sequence (the cutscene shown before the race) and the game tries to go to the ne...
NicoRipenn • Nov 1, 2026
One more setting I forgot to mention: I changed the System setting for the emulated memory size from the default (4 GB) to 8 GB (the log shows `Core.memory_layout_mode: Memory_8Gb` for the run tha...
CloudP4bbs • Nov 1, 2026
Two of the three symptoms here I have reproduced on an 8 GB AMD card (RX 5700, RDNA 1, Windows 11, Vulkan), and there are patches open for both. Details so you can match them against your runs. **1...
Top Replies
Takoroka • Oct 31, 2026
Take your game off of accurate mode, it's a side effect of using that
AverageDood • Oct 31, 2026
Yep, that did it. Now there's like some kind of white tint over the gameplay (not during the cutsecenes and dialogues tho), but idk if I should report that as a bug or if is an expected side effect...
asomidaksd • Oct 31, 2026
Similar setup to yours, 6900xt + ryzen 9800x3d Image shows the worst case scenario, basically if runs flawless if I look back right on spawn first time you get to play, but the other way looks like...
Top Replies
Bonepunk • Oct 31, 2026
I have the same problem except that in-game the problems from the preview are also present, but only on my Xbox elite controller (wired and Bluetooth), the problem is not there with my PS5 controller.
MIAMIcooler • Oct 31, 2026
> in-game the problems from the preview are also present Just found that out too
AlistairAA • Oct 31, 2026
yeap the new version has messed up the controller support somehow, same with xbox controller, go use an older version
Top Replies
DavidinCT • Oct 31, 2026
Same issue in Windows....
Haxorzz • Oct 31, 2026
that loading/sticker texture seems to be used in place of normally animated textures (I've seen it in ad billboards like choco mountain) On the latest build small "foldiage" including stuff like sc...
purpasmart96 • Nov 1, 2026
Not sure If I should make a seperate issue but for me, but the tree's/vegetation geometry flickers like crazy. OS: Linux GPU: AMD 9070XT

Frequently Asked Questions

Market intelligence mapped to Eglantine emulator's stability and compatibility with AMD RX 5700 (RDNA 1) GPUs when running Mario Kart World..

What is the technical positioning of Eglantine emulator's stability and compatibility with AMD RX 5700 (RDNA 1) GPUs when running Mario Kart World.?
Based on our AI analysis of the original developer request, its primary technical positioning is: Achieving stable and functional game emulation across diverse hardware configurations and emulator build versions.
Are engineers actively discussing Eglantine emulator's stability and compatibility with AMD RX 5700 (RDNA 1) GPUs when running Mario Kart World.?
Yes, we have tracked 8 direct responses and active debates regarding this specific topic originating from GitHub Issue.
Which technical concepts are associated with Eglantine emulator's stability and compatibility with AMD RX 5700 (RDNA 1) GPUs when running Mario Kart World.?
Our proprietary extraction maps Eglantine emulator's stability and compatibility with AMD RX 5700 (RDNA 1) GPUs when running Mario Kart World. to adjacent architectural concepts including Mario Kart World, crashes, race intro, AMD RX 5700 (RDNA 1).

Engagement Signals

8
Replies
open
Issue Status

Cross-Market Term Frequency

Counts stored text matches for foundational terms like crashes and Mario Kart World in analysed public discussions. These counts do not measure adoption.

Stored text matches, not adoption or market-share measurements.

  • crashes: 10 records
  • Mario Kart World: 2 records
  • loading screen: 2 records
  • race intro: 1 records
  • AMD RX 5700 (RDNA 1): 1 records
  • Builds 94 and 96: 1 records
  • EGLANTINE: 1 records
  • Eden emulator: 1 records
  • Eden NX2 emulator: 1 records
  • game launches: 1 records