BAM BAM Update v317

ravarcade

Pinball Wizard
Look at this table.
Keys H, J, K, L can will change TimeScale to 0.05, 0.1, 0.5, 1.0.
This tool should be used for testing, not for production.
I has impact on all FP time realated things.
It will change camera movement, timers, etc and may create a lot gliches.
 

Attachments

  • spotlight-test-oct.fpt
    224.5 KB · Views: 26

TerryRed

Pinball Hall of Famer
@ravarcade

I released my updated Star Wars DSA UPro - PinEvent today.



With 1.5-317:

Some people seem to have a problem with the table. It completely loads for them at the point where BAM starts the table with the yellow text showing everything it's doing. When it gets to "Done", then the table crashes back to desktop. I've had them disable the shadowmaps code, but that doesnt help.

Most people have no problems.... but these guys have very good PCs and cabinets and have no problems with any previous PinEvent tables, or pup-packs or other FP tables.

Any idea what it could be or what else they could try doing?


I've had no problems on any of my PCs or even my 12 year old laptop.
 
Last edited:

TerryRed

Pinball Hall of Famer
@TerryRed I will check this next weekend.
In mean time, please look at this: https://pinballnirvana.com/forums/i...arcades-instructions.19650/page-2#post-123912
Maybe it is again something related to AntiVirus?

It's been a very small number of people with the problem out of the 100's who have tried playing it. With recent Win 10 updates to security, etc there are always issues with people not having proper gpu drivers, etc as Win 10 tends to replace them with their own crappy versions.
 

shiva

Pinball Wizard
Staff member
Site Supporters
Same problem. I fixed mine by turning images off at the editor, in other words... maybe the white texture error has crept back in, or are people using such huge image files they are overloading the amount of graphics memory a person has? I've notice my laptop with dedicated graphics (1 gig) crashes quite a bit especially if the images are huge. I've had to export a lot of large pf images, and downsize them so my computer doesn't crash.
 

TerryRed

Pinball Hall of Famer
I test all my updates on my 12 year old laptop with 4 GB ram and a 1GB ATI Radeon to be sure it will work for desktop users.

It work fine on that for me as well.

These guys having problems have good modern PCs, and had no problems with and other tables.
 

TerryRed

Pinball Hall of Famer
@ravarcade

Here's is the BAM crash log from someone who has the problem. Again... it's a small number of people having the issue. Not sure it's helpful... but here it is:

Code:
------------------- BAM crash-report -------------
  BAM path: C:\Games\Future Pinball\BAM
       XML: C:\Games\Future Pinball\BAM\default.zip
     table: C:\Games\Future Pinball\Tables\Star Wars DSA (ULTIMATE Pro 1.06) - ESB 1.1 - PinEvent 1.0.fpt
         1: TAG: FILE=dllmain.cpp, LINE=1420, FUNC=Routed_SizeofResource
         2: TAG: FILE=dllmain.cpp, LINE=726, FUNC=Routed_SwapBuffers
       SBC: -1
       NFC: 0
Loaded modules:
Future Pinball.exe, 1.9.2013.25 : 00400000 - 02169000
ntdll.dll, 6.2.17134.1425 : 77B70000 - 77D00000
KERNEL32.DLL, 6.2.17134.1425 : 773B0000 - 77490000
KERNELBASE.dll, 6.2.17134.1792 : 75B80000 - 75D63000
USER32.dll, 6.2.17134.1667 : 74AF0000 - 74C7D000
win32u.dll, 6.2.17134.1 : 75D70000 - 75D87000
GDI32.dll, 6.2.17134.285 : 74EE0000 - 74F02000
COMCTL32.dll, 6.10.17134.1792 : 72B20000 - 72D24000
gdi32full.dll, 6.2.17134.1792 : 74F10000 - 75076000
msvcrt.dll, 7.0.17134.1 : 77150000 - 7720F000
msvcp_win.dll, 6.2.17134.619 : 75840000 - 758BD000
fmod.dll, 3.7.4.0 : 10000000 - 10096000
combase.dll, 6.2.17134.1792 : 74C80000 - 74EDC000
ucrtbase.dll, 6.2.17134.677 : 749D0000 - 74AED000
ADVAPI32.dll, 6.2.17134.471 : 75B00000 - 75B78000
RPCRT4.dll, 6.2.17134.1726 : 745F0000 - 746B0000
sechost.dll, 6.2.17134.1610 : 75A00000 - 75A43000
COMDLG32.dll, 6.2.17134.1 : 77210000 - 772E6000
SspiCli.dll, 6.2.17134.376 : 74430000 - 74450000
shcore.dll, 6.2.17134.1610 : 75930000 - 759B8000
CRYPTBASE.dll, 6.2.17134.1 : 74420000 - 7442A000
ole32.dll, 6.2.17134.1726 : 746C0000 - 747BC000
bcryptPrimitives.dll, 6.2.17134.1488 : 77300000 - 77357000
SHLWAPI.dll, 6.2.17134.1 : 77360000 - 773A5000
SHELL32.dll, 6.2.17134.1726 : 75DF0000 - 77140000
cfgmgr32.dll, 6.2.17134.1 : 759C0000 - 759F9000
windows.storage.dll, 6.2.17134.1726 : 750D0000 - 7568F000
MSACM32.dll, 6.2.17134.1 : 6DA00000 - 6DA19000
WINMM.dll, 6.2.17134.1 : 72930000 - 72954000
kernel.appcore.dll, 6.2.17134.112 : 747C0000 - 747CF000
WSOCK32.dll, 6.2.17134.1 : 6EC60000 - 6EC68000
profapi.dll, 6.2.17134.1 : 74860000 - 74878000
WS2_32.dll, 6.2.17134.1098 : 758C0000 - 75927000
powrprof.dll, 6.2.17134.1 : 75080000 - 750C5000
FLTLIB.DLL, 6.2.17134.1 : 75690000 - 75698000
winmmbase.dll, 6.2.17134.1 : 722C0000 - 722E3000
OLEAUT32.dll, 6.2.17134.1610 : 757A0000 - 75836000
DINPUT8.dll, 6.2.17134.254 : 70320000 - 70359000
GLU32.dll, 6.2.17134.1 : 680F0000 - 6812F000
Newton.dll,  : 02890000 - 02901000
libcurl.dll, 7.13.1.0 : 02910000 - 029AD000
DevIL.dll, 0.1.6.5 : 029B0000 - 02B23000
ILUT.dll, 0.1.6.5 : 00030000 - 0003D000
ILU.dll, 0.1.6.5 : 001E0000 - 001F3000
OPENGL32.dll,  : 02B30000 - 02E1B000
imagehlp.dll, 6.2.17134.1 : 77490000 - 774A9000
WININET.dll, 11.0.17134.1726 : 67260000 - 676B4000
IMM32.DLL, 6.2.17134.1 : 74450000 - 74476000
BAM.dll, 1.5.317.0 : 66BE0000 - 67258000
PSAPI.DLL, 6.2.17134.1 : 746B0000 - 746B6000
SETUPAPI.dll, 6.2.17134.1 : 774B0000 - 778DB000
VERSION.dll, 6.2.17134.1 : 72960000 - 72968000
HID.DLL, 6.2.17134.1 : 71120000 - 7112A000
renderingengine.dll,  : 667C0000 - 66BD4000
--------------------------------------------------
Error code 000006BA: (unknown)

   Address: 75C949C2 -> KERNELBASE.dll:001149C2
     Flags: 00000001

  Fault Occured At $ADDRESS:75C949C2 ->KERNELBASE.dll:001149C2
         with BA 06 00 00 01 00 00 00 00 00 00 00 00 00 00 00 BA 06 00 00

   Address: 7462EA8E -> RPCRT4.dll:0003EA8E
***  0 called from $ADDRESS:7462EA8E
         with BA 06 00 00 61 64 02 05 2C 20 4A 62 00 00 00 00 D4 E0 19 00

   Address: 745F6391 -> RPCRT4.dll:00006391
***  1 called from $ADDRESS:745F6391
         with 18 18 3F 62 30 03 40 62 54 E0 19 00

   Address: 745F51D4 -> RPCRT4.dll:000051D4
***  2 called from $ADDRESS:745F51D4
         with 18 18 3F 62 30 03 40 62 68 FE BD 37 E8 E0 19 00 0C 04 00 00

   Address: 62419DDC -> UNKNOWN:62419DDC
***  3 called from $ADDRESS:62419DDC
         with E8 E0 19 00 0C 04 00 00 A8 AB 17 15 D4 E0 19 00 E4 E0 19 00

   Address: 6244453B -> UNKNOWN:6244453B
***  4 called from $ADDRESS:6244453B
         with 78 E1 19 00 74 E1 19 00 70 E1 19 00 00 00 00 00 40 E1 19 00

   Address: 62419793 -> UNKNOWN:62419793
***  5 called from $ADDRESS:62419793
         with B0 B4 CF 37 A4 8A 55 62 78 E1 19 00 74 E1 19 00 70 E1 19 00

   Address: 6256030F -> UNKNOWN:6256030F
***  6 called from $ADDRESS:6256030F
         with D0 E1 19 00 40 9F 51 3A FF FF FF FF 00 00 00 00 E0 5E C8 37

   Address: 6256499D -> UNKNOWN:6256499D
***  7 called from $ADDRESS:6256499D
         with 78 9F 51 3A A8 BD B4 37 A8 BD B4 37 C8 BD B4 37 00 00 00 00

   Address: 62560450 -> UNKNOWN:62560450
***  8 called from $ADDRESS:62560450
         with 20 9F 51 3A 90 E2 19 00 A8 BD B4 37 00 00 00 00 A8 BD B4 37

   Address: 62563F4B -> UNKNOWN:62563F4B
***  9 called from $ADDRESS:62563F4B
         with 00 00 00 00 60 80 58 62 00 00 00 00 A8 BD B4 37

   Address: 6256489D -> UNKNOWN:6256489D
*** 10 called from $ADDRESS:6256489D
         with 38 76 0B 15 A8 CF 1D 02 00 00 00 00 94 80 58 62 00 00 00 00

   Address: 625647C8 -> UNKNOWN:625647C8
*** 11 called from $ADDRESS:625647C8
         with 94 80 58 62 E0 75 0B 15 10 C5 55 62 58 E4 19 00 A8 CF 1D 02

   Address: 6255D00C -> UNKNOWN:6255D00C
*** 12 called from $ADDRESS:6255D00C
         with A8 9F 51 3A 72 2E 97 1F 10 C5 55 62 F2 A8 D6 01 20 76 0B 15

   Address: 6255C587 -> UNKNOWN:6255C587
*** 13 called from $ADDRESS:6255C587
         with E0 75 0B 15 DC E3 19 00 58 E4 19 00 38 E4 19 00 DC 15 31 70

   Address: 703165C4 -> UNKNOWN:703165C4
*** 14 called from $ADDRESS:703165C4
 

StevOz

Administrator
Staff member
Site Supporters
Works for me on my 6 year old PC, core i3 dual core 2/4 threads @ 3.4 Ghz and a nvidia GTX 660...only do desktop here..All updated to the latest Windows 10 build with BAM/FP running with full Admin privileges.
 
Last edited:

TerryRed

Pinball Hall of Famer
Well, 2 of the guys seem to have it working now.

It seemed to require doing a fresh install of BAM completely. Maybe there's some problem with older BAM\CFG files or other BAM cfg files causing a problem with newer tables that use newer features like Custom Models,etc.
 

ravarcade

Pinball Wizard
@TerryRed Thanks for that debug log.
I'm 99.9% sure, that it was old renderingengine.dll in user BAM dir. So, they updated BAM.dll but not renderingengine.dll.

Here is why:
I compared with my own crash log. For renderingengine.dll i don't have version number in log, but there is size of used memory.
From log you provide:
Code:
renderingengine.dll,  : 667C0000 - 66BD4000
Math in hex: 66BD4000 - 667C0000 = 00414000 <- this is file size

From my own crash log:
renderingengine.dll, : 7A6D0000 - 7ABF8000 : size = 00678000
That must be 2 different files.

(btw. to calc in hex you can use windows calculator. Just select "programer" mode and you can select "hex")
 

outhere

Pinball Nudger
That would explain why I'm not having the problem
When I download the bam update I copy everything over except for the default.cfg
Thank you for your hard (Fun) work --> ravarcade
 

TerryRed

Pinball Hall of Famer
@ravarcade

Thanks rav. It's hard to help people out when they come up with a problem and it's only a small portion of people having the issue. Thank you for including crash logs (and understanding what they mean) :)

Star Wars DSA ESB - PinEvent has proven to be very popular, and since it's also the first released table to start using Custom Models and spotlight flashers. I'm glad to see that the vast majority have had no problems.

I'm doing an update for Halloween Upro PinEvent that will also use spotlight flashers and custom models...and its looking pretty cool!
 

Gramps

Pinball Nudger
Well, 2 of the guys seem to have it working now.

It seemed to require doing a fresh install of BAM completely. Maybe there's some problem with older BAM\CFG files or other BAM cfg files causing a problem with newer tables that use newer features like Custom Models,etc.
If I do a fresh install of BAM, do I use the cfg file that comes with BAM, or the cfg file you provide in your guide, Terry? And by "fresh" install, are you talking about just deleting all the files in my current BAM folder and downloading the BAM zip files and not the all in one installer?
 

TerryRed

Pinball Hall of Famer
The easiest solution.... backup your entire BAM folder, just in case.

Then you can remove the BAM folder completely....then try installing just the newest BAM from the latest zip file.

Then try running SW DSA ESB PE and see if that works.

If that works then you can try copying my default.cfg and see if that works.

If SW still doesnt work try another clean install with the installer first.... if having problems still...try updating on top of that from the zip.

Try whatever combination you need until it works. You can always copy over your backed up BAM\CFG files afterward if needed.
 

ravarcade

Pinball Wizard
The easiest solution.... backup your entire BAM folder, just in case.

Then you can remove the BAM folder completely....then try installing just the newest BAM from the latest zip file.
Easy way to do backup is just rename BAM dir. Just change BAM into BAM-OLD.
You will be able to do full new BAM install and you still can run FPLoader.exe from BAM-OLD. So, you can compare what is working and what is not.
 

DuMichAuch72

Pinball Nudger
Easy way to do backup is just rename BAM dir. Just change BAM into BAM-OLD.
You will be able to do full new BAM install and you still can run FPLoader.exe from BAM-OLD. So, you can compare what is working and what is not.
That's why I am using different BAM folders for a long time to keep my working BAM clean, and separate beta versions etc.
 

Gramps

Pinball Nudger
Easy way to do backup is just rename BAM dir. Just change BAM into BAM-OLD.
You will be able to do full new BAM install and you still can run FPLoader.exe from BAM-OLD. So, you can compare what is working and what is not.

I'm running everything on a 2 screen desktop system Win 10.
I don't know if this has anything to do with BAM or not but, the SW pin hangs up on me at "Loading Models" 3 of the PuP Pack Screens are running while it's trying to do that and remaining running after I shut down the program. I can't delete the PuP Pack folder until I reboot my machine because Windows tells me it can't delete because

I get a Microsoft Visual C++ runtime Library - "Runtime Error - Program: J\Games\Future Pinball\Future Pinball.exe. - The application have requested the Runtime to terminate it in an unusual way" Reinstalling and/or updating Microsoft Visual C++ doesn't solve the problem.

I'm to try reinstalling BAM as you all suggested, but I've done it several times. Been driving TerryRed crazy I'm sure. Thank goodness for backups because I've blown up the entire Visual Pinball system several times trying to get this one table to work. One would think that I'd be happy that I have 300 + pins and pup packs working just fine and just leave it alone. I even bought a program that checks for and installs updates. That blew up everything and I still don't have bluetooth working. But the table is so cool and I can see this as the future, I want to be part of it !

Off to trying yours and TerryRed's BAM reinstall suggestions just in case I missed something. Thank you all.
 

TerryRed

Pinball Hall of Famer
You should be testing this table without any pup features enabled first until you can get the table running normally first.

Trying to also get a pup-pack running on a table you can't even get to start will just add way more confusion.
 

Gramps

Pinball Nudger
I have tried running it without the pup pack in the PuPVideos folder if that's what you mean. Doing that gets it past "Searching for Models" to "Found:DarthVadar" then hangs up and shuts down after a few seconds. I do NOT get that Microsoft C++ error though. I also run non PinEvent table and it works fine. All the other PinEvent tables also run fine with PuPPack.
 

TerryRed

Pinball Hall of Famer
No... DO NOT remove the pup-pack with pup options enabled, that is asking for problems.

You disable the PinEvent pup options "for that table only" in the table script in the "PinEvent Custom Settings For this table only" section near the top.

Follow the instructions it says there.

If you ever get the table running normally...then you can disable the custom settings again to use the global PinEvent settings in PinEvent_Settings.vbs
 
General chit-chat
Help Users
  • No one is chatting at the moment.
    @ Todd: Hey hey hey!
    Top