Skip to content
Search PyroSoft

Bourbon 26 development journal · Part 2 of 10

When the menus work but the game world is black

Following the real game executable and isolating the graphics route.

By Mike Rodriguez2 min readDevelopment work: Aug 17, 2026Updated New

A game can show you a perfectly readable menu and still have a broken 3D world. That makes compatibility work a little deceptive, because getting a window on screen can look like we're almost finished. The August 17 Bourbon update has a couple of good examples of what had to happen next.

Palworld moved to the dedicated Twelve Year route, using CrossOver-source Wine with official D3DMetal, and launched its actual Shipping executable. The release record includes character creation and the opening beach cinematic. MECCHA CHAMELEON reached a correct main menu through the same general route. Those are different test milestones, so I'm keeping them separate rather than calling both games fully tested.

There were smaller fixes with very visible effects. LEGO Batman 3 received a windowed 1280 by 720 configuration after Retina backing pixels caused the picture to overflow. Legends of IdleOn needed its own Wine 11.10 setup and launch option. Keeping Wine versions side by side meant fixing that title didn't move the runtime underneath everything else.

Smart Play's profiles also became harder to accidentally undo. Verified choices kept control of their known-bad routes, and preparation happened in the bottle that would actually launch the game. That is useful when an old configuration or remote recipe would otherwise put a broken setting right back.

This update also reduced setup dependencies and improved signing, settings and accessibility presentation. But the part I want people to understand is the troubleshooting approach: find which executable is really running, identify the rendering path it needs, and keep that choice scoped to the game. We can explain a specific improvement without turning it into a claim that every Unreal game now behaves the same way.

Bourbon 26 development journal

View the journal

Live10 entries so farUpdated New (10 entries updated in the last 14 days)

  1. Part 1Bourbon 26: choosing the right way to playDevelopment work: Jul 31, 2026Updated , new
  2. Part 2When the menus work but the game world is blackDevelopment work: Aug 17, 2026Updated , new
  3. Part 3Making setup and repair less disruptiveDevelopment work: Aug 30 – Sep 6, 2026Updated , new
  4. Part 4Smart Play starts figuring out unfamiliar gamesDevelopment work: Sep 29 – 30, 2026Updated , new
  5. Part 5Activation, installers and knowing which program we launchedDevelopment work: Oct 2 – 8, 2026Updated , new
  6. Part 6Giving SteamOS its own place in BourbonDevelopment work: Oct 9 – 12, 2026Updated , new
  7. Part 7Keeping older tools and newer Steam clients in their own lanesDevelopment work: Oct 13 – 16, 2026Updated , new
  8. Part 8Native Steam integration and a library you can use from the couchDevelopment work: Oct 17 – 18, 2026Updated , new
  9. Part 9The audit that put saves and reset safety firstDevelopment work: Oct 19, 2026Updated , new
  10. Part 10Moving Bourbon safely, then making the verification fasterDevelopment work: Oct 19 – 20, 2026New

Arrow keys move through the results, Enter opens one, Command or Control with Enter opens it in a new tab. Tab and Shift+Tab change which kind of results are shown.