Donkey Kong Bananza on PC: Eglantine setup and the recorded blue-screen workaround
ItsOOGWAY · PC guides & recorded tests
Donkey Kong Bananza on PC: Eglantine setup and the recorded blue-screen workaround
Play Donkey Kong Bananza on PC with Eglantine: the Windows setup, recorded settings and the blue/purple screen fix, followed by working gameplay.
The key checkpoint: Use the demonstrated game and graphics baseline, then distinguish the recorded blue-screen workaround from a universal fix.
Before you start
- Follow this video’s recorded build and prepared input requirements.
- Keep a baseline before changing advanced settings.
- Test a playable scene after the setup and recovery steps.
With Eglantine closed, open %APPDATA%\eden and edit nx2_switches.txt. Preserve existing entries and add EDEN_NX2_TENSOR=1 on its own line. Save with a single .txt extension, then fully restart Eglantine. The recorded baseline also uses Vulkan, Accurate CPU accuracy and Accurate GPU mode. These settings worked together in build 204; the recording does not isolate the effect of each change.
Resources from this video
Links, downloads & documentation
Every original URL from the video description is collected here, including recorded releases, setup discussions and related videos. Use the version-specific notes when following a recorded build.
Watch the complete video
Open this video on YouTube ↗. Screenshots below link to their exact recorded moments.
Walkthrough 01
Donkey Kong Bananza on PC
Donkey Kong Bananza is running on my PC. I'll take you from the Windows download to this working scene, including the blue screen I hit and the settings and text file change that got me past it. Open the Eglantine project linked in the resources section and go to Releases.
Walkthrough 02
Download the Windows build
The recorded build is number two zero four. In the Windows section, choose the standard Windows sixty four bit M S V C ZIP shown here. Download it, then extract the whole archive into its own folder. Keep the executable and its supporting files together. Use your own prepared Donkey Kong Bananza files.
Walkthrough 03
Open your prepared game
My game folder has base, with exefs and romfs inside it. Open Eglantine, choose File, then Load File. Browse into base, open exefs, select main, and click Open. This recording starts with prepared game files and an existing emulator profile. First run requirements are linked in the resources section. The game can reach its menus and still show this flat blue or purple scene when the opening starts.
Walkthrough 04
Recognise the blue screen
That is the problem I ran into. Close the game and return to Eglantine. I'll show the combination of changes from the successful run, starting with the configuration pages. Go to Emulation, then Configure.
Walkthrough 05
System settings
Under System, set Memory Layout to eight gigabytes. In this test, CPU clocks are Normal and GPU clocks are Boost. Keep the speed limit at one hundred percent so the game runs at its intended speed. Open CPU and set Accuracy to Accurate.
Walkthrough 06
CPU and Vulkan
Then open Graphics, choose Vulkan, and select the graphics card you want to use. My test uses an RTX 4070 SUPER. Start with the one times resolution shown here, so you can check the result before raising image quality. In Graphics, open Advanced and change GPU Mode from Fast to Accurate.
Walkthrough 07
Accurate GPU mode
Leave the other rows aligned with this screen. For this recorded fix, Accurate is the setting to match before trying the game again. Go to Extras.
Walkthrough 08
Extras and save settings
Enable asynchronous presentation and asynchronous shader compilation, as shown. Click OK to save the configuration, then close Eglantine completely. We also need to save one line in its user folder before restarting. Open File Explorer and enter percent app data percent, backslash eden, in the address bar.
Walkthrough 09
Open the user folder
The exact path is on screen and in the description. In this folder, look for nx two underscore switches dot t x t. Open it in Notepad. If it is missing, create a text file with that exact name. Add the line shown on screen.
Walkthrough 10
Save the tensor setting
Copy it from the description to keep every character correct. Keep any other settings already in the file. Save your changes, then check the filename shown here. It should end with dot t x t only once. Now reopen Eglantine and load the same main file again through File, then Load File.
Walkthrough 11
Restart and load again
The restart matters because the application reads this file when it starts. Give the game time to launch. I'll shorten the loading section here and return to the original speed when the scene begins. Here is the result after those changes.
Walkthrough 12
Verify the picture
The opening scene now has its scenery and characters, and we can move into the mining tunnel. Check this same point on your PC before changing more settings. Reaching a title screen alone doesn't confirm that the three dimensional scene is rendering. Once you're in control, test movement, the camera, jumping and punching.
Walkthrough 13
Check controls and gameplay
The game is building shaders as new effects appear in this recording, so keep the settings you just tested as your starting point. That's the setup I used: the recorded Windows build, your prepared main file, the configuration changes, and the saved tensor setting followed by a restart.
Walkthrough 14
Recap and community
If you're testing Eglantine or need help comparing a result, join my Discord from the description. Share your build, graphics card and the screen you're stuck on, so we can help with the right step.
If your result differs
| Situation | Next useful check |
|---|---|
| A blue-screen-like game image appears | Compare the specific Eglantine graphics steps in the guide; a game-rendering problem is different from a Windows system crash. |
| Game selection fails | Check the prepared game and expected executable path before changing graphics. |
| The workaround does not reproduce | Record the build, scene, driver and changed settings; newer versions may differ. |
Comments
Post a Comment