FPLoader.exe not opening Future Pinball

[Kratos Spartan]

Hello everyone! so, i have new hardware and with that a new installation of W10 to the latest update. I already had my Future Pinball working like a charm in my previous build, but upgrade was required. I already installed every VC reddist, Directx, Net Framework, Java, Nvidia driver, latest BAM version and tried setting compatibilty mode from Windows XP up to 8 and run SFC /scannow to fix Windows damaged system files but there's no way. FPloader.exe refuses to open Future Pinball. Now FP open on its own .exe but my tables are not working because they have BAM scripts. FPloader.exe actually does open FP for a second where the splash image of FP appears but then nothing. I don't know what to do, i read a lot of stuff and nothing worked, even plugged some speakers because apparently for someone that worked. Any help would be much appreciated guys, or if there's a way to remove BAM scripts from the tables so i can play although is not the same experience. I leave now everything that the BAM_Crash.log says

------------------- BAM crash-report -------------
BAM path: D:\HyperSpin_1.5.1\Emulators\Future Pinball\BAM
XML:
table:
1: TAG: FILE=dllmain.cpp, LINE=4149, FUNC=DllMain
2: TAG: FILE=dllmain.cpp, LINE=4149, FUNC=DllMain
SBC: -1
NFC: 0
Loaded modules:
Future Pinball.exe, 1.9.2008.1225 : 00400000 - 01F3F000
ntdll.dll, 6.2.19041.2075 : 776D0000 - 77874000
KERNEL32.DLL, 6.2.19041.1889 : 756A0000 - 75790000
KERNELBASE.dll, 6.2.19041.2075 : 761B0000 - 763CC000
apphelp.dll, 6.2.19041.2075 : 6FC00000 - 6FCA0000
AcGenral.DLL, 6.2.19041.2075 : 70BA0000 - 70DF2000
msvcrt.dll, 7.0.19041.546 : 775E0000 - 7769F000
sechost.dll, 6.2.19041.1865 : 77060000 - 770D6000
RPCRT4.dll, 6.2.19041.1806 : 76F90000 - 7704E000
SHLWAPI.dll, 6.2.19041.2075 : 77260000 - 772A5000
USER32.dll, 6.2.19041.2075 : 76DF0000 - 76F8D000
win32u.dll, 6.2.19041.2075 : 76610000 - 76628000
GDI32.dll, 6.2.19041.2075 : 775B0000 - 775D4000
gdi32full.dll, 6.2.19041.2075 : 76BA0000 - 76C84000
msvcp_win.dll, 6.2.19041.789 : 772B0000 - 7732B000
ucrtbase.dll, 6.2.19041.789 : 75580000 - 756A0000
ole32.dll, 6.2.19041.1202 : 759C0000 - 75AA3000
combase.dll, 6.2.19041.1949 : 77330000 - 775B0000
OLEAUT32.dll, 6.2.19041.985 : 771C0000 - 77256000
SHELL32.dll, 6.2.19041.2075 : 75B60000 - 76115000
ADVAPI32.dll, 6.2.19041.1682 : 76590000 - 7660B000
UxTheme.dll, 6.2.19041.2075 : 70730000 - 707A4000
WINMM.dll, 6.2.19041.546 : 6FE20000 - 6FE48000
samcli.dll, 6.2.19041.1466 : 70B80000 - 70B95000
MSACM32.dll, 6.2.19041.1 : 70B60000 - 70B79000
VERSION.dll, 6.2.19041.546 : 75460000 - 75468000
USERENV.dll, 6.2.19041.572 : 70A30000 - 70A55000
dwmapi.dll, 6.2.19041.746 : 6BD00000 - 6BD26000
urlmon.dll, 11.0.19041.2075 : 70E30000 - 70FD8000
WINSPOOL.DRV, 6.2.19041.2075 : 6FF20000 - 6FF93000
MPR.dll, 6.2.19041.1806 : 70B40000 - 70B59000
SspiCli.dll, 6.2.19041.1586 : 74B10000 - 74B31000
winmmbase.dll, 6.2.19041.1 : 70B20000 - 70B3D000
iertutil.dll, 11.0.19041.2075 : 710D0000 - 712FD000
shcore.dll, 6.2.19041.1645 : 76630000 - 766B7000
srvcli.dll, 6.2.19041.1645 : 70E10000 - 70E2D000
netutils.dll, 6.2.19041.1466 : 70E00000 - 70E0B000
IMM32.DLL, 6.2.19041.546 : 76CB0000 - 76CD5000
symsrv.dll, 5.1.2600.5512 : 10000000 - 10033000
COMDLG32.dll, 6.2.19041.1806 : 76D40000 - 76DEF000
COMCTL32.dll, 6.10.19041.1110 : 707B0000 - 709C0000
DINPUT8.dll, 6.2.19041.1 : 70AE0000 - 70B17000
GLU32.dll, 6.2.19041.2075 : 70AA0000 - 70ADF000
OPENGL32.dll, 6.2.19041.2075 : 69820000 - 69924000
Newton.dll, : 04180000 - 041F1000
fmod.dll, 3.7.4.0 : 04200000 - 04296000
libcurl.dll, 7.13.1.0 : 042A0000 - 0433D000
DevIL.dll, 0.1.6.5 : 04340000 - 044B3000
ILU.dll, 0.1.6.5 : 02210000 - 02223000
ILUT.dll, 0.1.6.5 : 02230000 - 0223D000
WSOCK32.dll, 6.2.19041.1 : 70A90000 - 70A98000
WININET.dll, 11.0.19041.2075 : 71300000 - 71757000
WS2_32.dll, 6.2.19041.546 : 763D0000 - 76433000
BAM.dll, 1.5.349.0 : 69010000 - 69693000
PSAPI.DLL, 6.2.19041.546 : 76750000 - 76756000
SETUPAPI.dll, 6.2.19041.1741 : 76760000 - 76B99000
cfgmgr32.dll, 6.2.19041.1620 : 76540000 - 7657B000
bcrypt.dll, 6.2.19041.1023 : 76C90000 - 76CA9000
HID.DLL, 6.2.19041.546 : 6FE80000 - 6FE8A000
renderingengine.dll, : 68AE0000 - 69008000
--------------------------------------------------
Error code C0000096: (unknown)

Address: 10003A42 -> symsrv.dll:00003A42
Flags: 00000000

Fault Occured At $ADDRESS:10003A42 ->symsrv.dll:00003A42
with B3 33 01 10 48 0E CA 03 48 0E CA 03 00 00 00 00 2B 00 00 00

Address: 1000DCBA -> symsrv.dll:0000DCBA
*** 0 called from $ADDRESS:1000DCBA
with 00 00 00 00 B3 33 01 10 B3 33 01 10 48 0E CA 03 00 00 00 00

Address: 10013434 -> symsrv.dll:00013434
*** 1 called from $ADDRESS:10013434
with 48 0E CA 03 10 FA 6B 75

Address: 756BFA29 -> KERNEL32.DLL:0001FA29
*** 2 called from $ADDRESS:756BFA29
with 48 0E CA 03 66 70 EB 06 00 00 00 00 00 00 00 00 48 0E CA 03

Address: 77737C3E -> ntdll.dll:00067C3E
*** 3 called from $ADDRESS:77737C3E
with FF FF FF FF EE 8D 75 77

Address: 77737C0E -> ntdll.dll:00067C0E
*** 4 called from $ADDRESS:77737C0E
with

Address: 00000000 -> UNKNOWN:00000000
*** 5 called from $ADDRESS:00000000

 

[TerryRed]

When you updated BAM, did you use the installer or the zip file? Many people who use the installer don't install BAM to the correct location, which is why I recommend using the zip file to update instead.

Be sure the new BAM update is not installed to a different location than where you actually had FP installed before.

 

[GeorgeH]

Do you have W10 set to use the English language? I have read that some folks have trouble when it is not set to English.

 

[AnonTet]

You mentioned everything but the most likely cause of problems in windows: the antivirus, especially Microsoft Defender. If you happen to use this one, either use another AV, disable it before play FP, or make an exception to the whole FP folder.

 

[Kratos Spartan]

When you updated BAM, did you use the installer or the zip file? Many people who use the installer don't install BAM to the correct location, which is why I recommend using the zip file to update instead.

Be sure the new BAM update is not installed to a different location than where you actually had FP installed before.

I used the zip and then i tried a new fresh install with the 2 in 1 installer and nothing.

 

[Kratos Spartan]

You mentioned everything but the most likely cause of problems in windows: the antivirus, especially Microsoft Defender. If you happen to use this one, either use another AV, disable it before play FP, or make an exception to the whole FP folder.

yeah i forgot to mention that, i excluded the exes and the folder in my antivirus and i disabled Defender.

 

[AnonTet]

in the zip files, go to Properties, General tab and in the lower right corner of the window syou have Unblock. Click it, hit Apply, OK.

Try unzip it like that

 

[Kratos Spartan]

Do you have W10 set to use the English language? I have read that some folks have trouble when it is not set to English.

Just tried that, nothing.

 

[AnonTet]

did you try running it with administrator privledges

 

[Kratos Spartan]

did you try running it with administrator privledges

in the zip files, go to Properties, General tab and in the lower right corner of the window syou have Unblock. Click it, hit Apply, OK.

Try unzip it like that

Did both things and nothing. There's no way, it's not opening and the crash log is the same.

 

[AnonTet]

Can you try to install it in the default folder c:\games\Future Pinball (if my memory serves me well)

 

[Kratos Spartan]

Can you try to install it in the default folder c:\games\Future Pinball (if my memory serves me well)

Just tried that and nope..... i

 

[AnonTet]

You did get the future pinball 2-in-1 from www.ravarcade.pl right?

v353?

 

[Kratos Spartan]

You did get the future pinball 2-in-1 from www.ravarcade.pl right?

v353?

yeah dude, i tried that and older versions, zip and installer. i install it on C drive and to another drive. i don't know what else to try.

 

[AnonTet]

I know this questions are a pain but I deal with troubleshooting (not this type :D ) everyday and sometimes its really the littlest things we overlook.

Can you disable UAC (that priveledge elevation prevention thing from windows)?

Also, if you call future Pinball.exe (forget fploader) does it open?

Are you calling FPloader from Hyperspin?

Since it is new hardware, go to nvidia settings and make sure the preferred GPU is nvidia and not the iGPU.

And i'm officially out of ideas :D

 

[Kratos Spartan]

I know this questions are a pain but I deal with troubleshooting (not this type :D ) everyday and sometimes its really the littlest things we overlook.

Can you disable UAC (that priveledge elevation prevention thing from windows)?

Also, if you call future Pinball.exe (forget fploader) does it open?

Are you calling FPloader from Hyperspin?

Since it is new hardware, go to nvidia settings and make sure the preferred GPU is nvidia and not the iGPU.

And i'm officially out of ideas :D

Yeah i had already disabled UAC, Future Pinball.exe does open but of course the tables i have uses BAM scripts so i can't play them. I've been trying to fix this outside Hyperspin but i have everything set to launch from the front end, that how i played in my previous build. And as i haven't installed the AMD graphic, i have a Ryzen 7 5700g, there's no option in the Nvidia settings windows to select between Intagrated or the Nvidia card. Well i can just wait for someone to fix this, or Microsoft with a new update that doesn't fu..ed everything up or a new Nvidia driver update. Or use a virtual machine with W7 but that's not the point here because i want to use it through Hyperspin. Thanks anyway dude.

 

[AnonTet]

you don't need the drivers for the integrated GPU to be active. It just has to be enabled in UEFI (usually is by default) for windows to know it exists.

Go to device manager and make sure it is not in there if it is, disable it (or go to the UEFI and disable it there.

Since windows 10 ( i dont remember Win7 anymore :D) the only time I got problems was with W11 until the fisrt major update. After that it has been a breeze (for my surprise). I'm on W11 fully updated on latest nvidia drivers.

I find your problem REALLY weird.

 

[Isaac Sauvage]

You mentioned everything but the most likely cause of problems in windows: the antivirus, especially Microsoft Defender. If you happen to use this one, either use another AV, disable it before play FP, or make an exception to the whole FP folder.

Just for the record, as a W10 + Defender user, I've never had Defender interfere with FPLoader. Are some people having that problem? (because it doesn't seem common)

In terms of a silly little thing one might try-- has FPLoader itself changed over time? Because all versions of BAM are archived at Rafal's place IIRC, and I'm curious if launching a slightly-different one might work.

Btw, some more suggestions here, from Terry, George and others:
https://www.vpforums.org/index.php?showtopic=48232

 

[Kratos Spartan]

you don't need the drivers for the integrated GPU to be active. It just has to be enabled in UEFI (usually is by default) for windows to know it exists.

Go to device manager and make sure it is not in there if it is, disable it (or go to the UEFI and disable it there.

Since windows 10 ( i dont remember Win7 anymore :D) the only time I got problems was with W11 until the fisrt major update. After that it has been a breeze (for my surprise). I'm on W11 fully updated on latest nvidia drivers.

I find your problem REALLY weird.

I don't think it'll do any difference cause is not Future Pinball the problem, is the FPloader that for some reason can't reach Future Pinball exe or does it for a second and crashes. I know is weird and i'm pulling my hair out with this because any other emulator i have runs without any problem.

 

[GeorgeH]

Just for the record, as a W10 + Defender user, I've never had Defender interfere with FPLoader. Are some people having that problem? (because it doesn't seem common)

In terms of a silly little thing one might try-- has FPLoader itself changed over time? Because all versions of BAM are archived at Rafal's place IIRC, and I'm curious if launching a slightly-different one might work.

Btw, some more suggestions here, from Terry, George and others:
https://www.vpforums.org/index.php?showtopic=48232

When execute or eval commands are used in the script, Defender will scan them. All resources go to the scan so it causes ball stuttering. There is no problem if the commands are not used.

Rav hasn't changed FPLoader in years.

You can try setting FPLoader to Windows 8 compatibility mode but Rav fixed the bug that causes the crashing problem. It might be worth trying it anyway.

 

[padps]

Hi all.
Was there a solution on this issue? I'm having exactly the same problem, and followed all steps...

Thanks

 

[AnonTet]

I think after some point it's just best to rename the FP folder to FP_old or something and install from TerryRed's AIO pack.

If it still crashes, then you you'll probably have some hardware problem.