Jump to content

[New VP10 Alert] Special Force (Bally Midway 1986) VPW


Recommended Posts

Special Force (Bally Midway 1986) VPW


“Aaaahhraaaaa!!”

 

This was a real team effort that spanned over a year. Special Force is an underappreciated, grubby, rowdy, 80’s war movie pin. Kinda feels like you got dropped into a bad version of Rambo (but in a good way!) We hope you enjoy.

 

VPW Platoon

Apophis - Blender work, table work, scripting, physics tuning

Flux - Blender work, toolkit scripting and fixes

Cyberpez - Blender work and support

Sixtoe - Table building and VR work

ArmyAviation - Playfield photos, plastics scans, expert testing (owns the real table)

EBisLit - Inital playfield stitch

TastyWasps - VR room integrations, backglass and desktop digits

Benji - Blender and refraction probe help

HauntFreaks - Backglass resources

Bord - Modeling help

Mlager8 - Support

VPW Testers - PinStratsDan, Studlygoorite, DGrimmReaper, DarthVito, BountyBob, somatik, Colvert

 

Special thanks to:

Siggi - Playfield redraw

3rdAxis - The jungle VR room

Toxie - Fixed some VPinMame issues for this game

Destruk & TAB - For their VP9 table that was used as a reference

Niwak and the VPX team for everything they do


 

Link to comment
Share on other sites

  • Content Provider
14 minutes ago, JCalhoun said:

It's the only table that occasionally crashes on me.

Mostly plays fine — and then maybe once every other day, crash.

I'm on VPX 10.8 RC.

 

Wish I knew where to find a crash log.

Crash logs get dropped in the same folder as the table file, AFAIK

Link to comment
Share on other sites

Hey guys, table looks amazing. But I have a problem. How do you change the volume on the table. Usually with Bally tables you open the coin door (end) and use 9 and 8 keys to adjust volume. Doesn't work on this table for some reason. Am I doing something wrong?

Link to comment
Share on other sites

18 hours ago, Wylte said:

Crash logs get dropped in the same folder as the table file, AFAIK

Thank you. The text file is almost worthless, no backtrace:

 

Crash report VPX - v10.8.0 Beta (Rev. 1807 (39824d6), windows DirectX 64bits)
============
Process: VPinballX64.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0033:000000014018F270
Attempt to write to 0x54975C52
Thread ID: 0x181C [6172]

Call stack
==========
000000004018F270  (0x00000000 0x00000000 0x00000000 0x54975c20)

Environment
===========
Date/time: 22/2/2024, 18:10:02:486
Number of CPUs: 12
Processor type: 8664
System: Windows 10 (10.0 19045)

Memory status
=============
Total Reserved: 705548K (689M) bytes
Total Commited: 963108K (940M) bytes
Total Free: 2525584K (2466M) bytes
Largest Free: 2055892K (2007M) bytes

Registers
=========
RAX=00000000 RBX=00000000 RCX=00263000 RDX=00000000
RSI=00000000 RDI=54975C20 RBP=00000000 RSP=0014E5A0 RIP=4018F270
FLG=00010206 CS=0033 DS=002B SS=002B ES=002B FS=0053 GS=002B


Failed to save minidump.

 

I'd attach the crash dump but it is too big for VPU to allow. I have no idea how to parse those - maybe a Google search will help me.

Link to comment
Share on other sites

  • 4 weeks later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
  • Create New...