Future Pinball crashing after ~4 minutes with AMD 6600

[MrDionysus]

Hi all, I'm using an AMD 6600 as my GPU, and it runs VPX and Pinball FX tables just fine. When I try to run any Future Pinball tables, however, they crash after roughly 4 minutes. The only exception to this crashing is the free table that comes with Baller Installer (I forget its name, it's the retro arcade one). All the tables are made by TerryRed and are recent. I've updated FP with Pinup Popper Baller Installer's auto-update. 

 

Troubleshooting:

• Followed initial instructions at https://www.nailbuster.com/wikipinup/doku.php?id=emulator_future_pinball
• Followed TerryRed's recommendations at https://www.vpforums.org/index.php?showtopic=51972. I've tried Win8 compatibility mode, my board doesn't have Nahimic, I've tried with/without admin mode
• Problem is identical whether FP is launched directly from BAM\FPLoader.exe or from Pinup Popper Frontend
• Crash occurs whether actively playing or just loading the table and letting it sit
• Problem has persisted through entire reinstall of Pinup Popper Baller Installer, as well as an entire OS reinstall.
• If I swap in my RTX 4070 I have zero problems and can launch any FP table for presumably any amount of time (I let it run for 30 minutes with no problem)

 

Windows Event Viewer throws the following error, identical to this thread from February (https://community.amd.com/t5/general-discussions/game-crashing-to-a-atioglxx-dll-error-in-future-pinball/m-p/704362), with the only solution being to swap to an nvidia card.

-----

Faulting application name: Future Pinball.exe, version: 1.9.2008.1225, time stamp: 0x4d1d68d3

Faulting module name: atioglxx.dll, version: 32.0.12033.1030, time stamp: 0x6746e91c

Exception code: 0xc0000409

Fault offset: 0x00e7b903

Faulting process id: 0x0x44C8

Faulting application start time: 0x0x1DB59665E25423E

Faulting application path: C:\vPinball\FuturePinball\Future Pinball.exe

Faulting module path: C:\Windows\System32\DriverStore\FileRepository\u0410212.inf_amd64_daae2c8b5eb35aaa\B409877\atioglxx.dll

Report Id: c52aed00-394f-4243-96a9-1d27cc0a69cd

Faulting package full name:

Faulting package-relative application ID:

 

Any guidance other than "buy a new GPU" is appreciated, although I'm probably going to get an ARC B580 if I can't find a solution to this. I'd absolutely love to play some of TerryRed's amazing tables now, though!  Is anyone else using an AMD card, particularly a 6600, for FP?

 

Thanks for all assistance!

[MrDionysus]

@TerryRed I got notified of your Reddit response right after I submitted this, I'll follow the guidance you put there tomorrow and see if I can get any FP tables working.  Sorry for any drama caused, I personally really appreciate your work, which is why I'm trying to get FP and your tables working on my system! 

[MrDionysus]

Is it possible to run Future Pinball without OpenGL, like force it to use DirectX?  With the consistent Event Manager error for "atioglxx.dll" combined with the fact that FP runs perfectly fine when I swap in my nvidia 4070 I'm assuming that the problem is due to AMD's OpenGL driver.

[TerryRed]

10 minutes ago, MrDionysus said:

@TerryRed I got notified of your Reddit response right after I submitted this, I'll follow the guidance you put there tomorrow and see if I can get any FP tables working.  Sorry for any drama caused, I personally really appreciate your work, which is why I'm trying to get FP and your tables working on my system! 

 

No drama from you at all... please don't apologize. I just addressed the other crabby boomers on there

 

4 minutes ago, MrDionysus said:

Is it possible to run Future Pinball without OpenGL, like force it to use DirectX?  With the consistent Event Manager error for "atioglxx.dll" combined with the fact that FP runs perfectly fine when I swap in my nvidia 4070 I'm assuming that the problem is due to AMD's OpenGL driver.

 

FP uses OpenGL only. (same with the GL version of VP 10.8)

 

The problem may come from AMD's driver.... its certainly a common thing with not just FP but many PC games, sadly.

 

Wish I had more to offer for AMD related issues.

[eustonr]

I have the same issue, but sadly swapping in an NVidia card isnt an option, as I run my cabinet with a NUC - a GMKtec M7 to be precise with a 6850H graphics chip. It works great with Arcooda, VP, and the like - but FP will crash after about 5 minutes, even sitting idle. It doesnt do it for every table, but it does for quite a number. I've re-installed everything multiple times, Win 10, Win 11, old or updated drivers - its the same. Very frustrating.

Seems like a memory leak to me.

 

I'm using the Future Pinball and BAM Essentials - All in One package, latest version. One interesting thing - it DOESNT crash if I run it without the backglass. so it seems specific to a cabinet setup.

ANY suggestions welcome.

[TerryRed]

31 minutes ago, eustonr said:

I have the same issue, but sadly swapping in an NVidia card isnt an option, as I run my cabinet with a NUC - a GMKtec M7 to be precise with a 6850H graphics chip. It works great with Arcooda, VP, and the like - but FP will crash after about 5 minutes, even sitting idle. It doesnt do it for every table, but it does for quite a number. I've re-installed everything multiple times, Win 10, Win 11, old or updated drivers - its the same. Very frustrating.

Seems like a memory leak to me.

 

I'm using the Future Pinball and BAM Essentials - All in One package, latest version. One interesting thing - it DOESNT crash if I run it without the backglass. so it seems specific to a cabinet setup.

ANY suggestions welcome.

 

 

This is a common issue with AMD specific chips / drivers (only when the FP backbox is enabled). It doesn't occur with nvidia GPUs and we don't know a solution.

 

If you are running PinEvent FP tables, you can use the pup features which requires you to disable the FP Backbox anyway. For other DMD based tables, you can use DMDext to display the DMD and a front-end to display something for the backbox.

 

 

[eustonr]

Thanks Terry - This is has been driving me mad.

 

I've not used PinEvent before, but I've found your guide, so I'll give that a go.   

[GeorgeH]

I read nearly all FP postings and have found that some guys have pretty good success using the AMD Ryzen CPU but AMD GPUs usually perform poorly with FP. 

[eustonr]

Hi Terry,

 

I got the PinEvent stuff working ok - took me all day, but I got there in the end - thank you. I grabbed your Sonic table, and it works great.:)

 

Excellent suggestion about dmdext too - I'm using VLC to display a video of the backglass in a loop, and dmdext to display the DMD over the correct space. Sized correctly its completely seemless, so I'm very happy.

 

However I had some trouble getting DMDext to work. It worked in DESKTOP mode, exactly as per your instruction video. However in CABINET mode, it didnt  work. Thats with the same Sonic table.

DMDext does not recieve anything when in cabinet mode using your batch files. (BAM settings - Cabinet - Reset and Install). Took me a while to work out the reason - its "Arcade mode". Switch that off, and the DMD starts to work. You might want to add that to your guide. I think its a bug because if you switch the overlay on in cabinet mode, the DMD shown on the Sonic table playfield does not work if Arcade mode is on.

 

Thank you good sir - now I just need to fix the older tables. Do you have any suggestions on what to do for EM scoring? Is there a way to get B2SServer talking to future pinball tables (I was thinking I could use directb2s files from a matching VP table)? Or is there a way to get the FP's overlay to show on the backglass?

 

Thanks.

[TerryRed]

34 minutes ago, eustonr said:

Hi Terry,

 

I got the PinEvent stuff working ok - took me all day, but I got there in the end - thank you. I grabbed your Sonic table, and it works great.:)

 

Excellent suggestion about dmdext too - I'm using VLC to display a video of the backglass in a loop, and dmdext to display the DMD over the correct space. Sized correctly its completely seemless, so I'm very happy.

 

However I had some trouble getting DMDext to work. It worked in DESKTOP mode, exactly as per your instruction video. However in CABINET mode, it didnt  work. Thats with the same Sonic table.

DMDext does not recieve anything when in cabinet mode using your batch files. (BAM settings - Cabinet - Reset and Install). Took me a while to work out the reason - its "Arcade mode". Switch that off, and the DMD starts to work. You might want to add that to your guide. I think its a bug because if you switch the overlay on in cabinet mode, the DMD shown on the Sonic table playfield does not work if Arcade mode is on.

 

Thank you good sir - now I just need to fix the older tables. Do you have any suggestions on what to do for EM scoring? Is there a way to get B2SServer talking to future pinball tables (I was thinking I could use directb2s files from a matching VP table)? Or is there a way to get the FP's overlay to show on the backglass?

 

Thanks.

 

No bug. Arcade mode and the FP Backbox settings must both be enabled or disabled together. Having only one enabled will cause issues like you describe.

 

The "BAM Settings" bat files are meant to only change BAM settings. They don't change your FP settings which is separate. If you are changing from desktop to cabinet... you not only need to run the "BAM Settings" bat (for setting BAM settings correctly for the mode you are using), but you also need to to run the correct "Start FP" bat file to start FP in the mode / setup that matches what you are running. Doing this would have disabled Arcade mode along with the FP Backbox correctly in FP settings.

 

The Overlays are intended for desktop mode only. They won't look correct in cabinet mode. You don't want them displayed if using cabinet mode.

 

All this was covered in my Guides.

 

EM scoring is baked into the FP Backbox. No other app can display them (b2s is only for VPX because it has no second screen support). Since your issue is because of AMD drivers, there is nothing that can be done on the FP end to get around it that we know of.

 

You need to decide what you are using and stick to it. Cabinet or desktop mode. You can't keep going back and forth without needing to reset your BAM and FP settings each time to run correctly in that mode.

 

 

 

 

Edited February 16, 2025 by TerryRed