PinballFX 2 and Hyperspin Question

[BlueGoblin]

I'm trying to get PinballFX 2 to work in my Hyperspin 1.3 arcade machine.

 

All of the media - videos, themes, wheels, database, etc are already in the correct folders but

I do not understand how to get the game working. I'm stuck configing properly in HyperLaunch.

 

Help-

[BlueGoblin]

I have these files but not sure where to place them.

See attached image.

[alcoatjez]

I'm using RocketLauncher myself, but I think you have to put them in the Modules\Pinball FX2 folder.

[BlueGoblin]

im using Hyperlaunch - i guess that is an older version of RocketLauncher?

[gigapig]

I have these files but not sure where to place them.

See attached image.

 

Those files should already be in :\RocketLauncher\Modules\Pinball FX2, the reason they are not already there is a big problem and that it's probably very outdated. 

 

The method of launching the tables has changed in the new module and no longer uses the grid method. How you would use the old grid method with the increasing number of tables, I don't know.

 

Any idea what version that is? 

 

The module you are using was not made for HyperLaunch unless someone made it for you.

[alcoatjez]

Yes, it is. The HyperLaunch guys moved to a new site, but the old HyperLauch is still supported here.

 

Did you already try putting it in the Modules\Pinball FX2 folder?

[BlueGoblin]

i am using Hyperspin 1.3 and RocketLauncher.0.1.1

[32assassin]

I have these files but not sure where to place them.

See attached image.

 

 

it looks like you have the module that uses the grid method. 

 

right click on the PinballFx2.ahk   and Open with Notepad,  to see what version of the module you have.

the latest version is MVersion = 2.1.2  (this module uses the command line loading)

 

the older versions use the grid loading.

 

you can still use your current module if 

 

- set PInball FX2 as a virtual emulator, in your Global emulators tab

 

-update your  Pinball Fx2.ini  file

when a table comes out its assigned to a grid number

the first able is  in grid is set to

X=1

Y=1

 

you will need to update all the numbers for the tables in your grid.

the titles found in the INI file must match the tittles in the XML,  if you are using the most current official XML.  You will find that many tittles don't match your current INI file.

this is because many of the names changed when the command line format was released.

 

 

I recommend you update yoru Module.  You can probably drag and drop the current module into your outdated folder and use the command line loading (MUCH FASTER LOAD TIMES)

with Hyperlaunch_3 or an outdated version of RL.  provided you have the latest version of FX2

[BlueGoblin]

Pinball Fx2 ahk is 2.1.0

 

im in the Global tab but cant find where to click on the virtual emulator

[32assassin]

I don't know what version started supporting the Command line loading;  you need to go to the RL forums and ask what type of module you have

 

grid loading  or command line loading

 

the set up is completely different.

 

Givent that your module is not that old,  I would suggest you use GigaPigs  youtube tutorial.  Witch uses the command line  set up.

 

 

 

 

instead of adding a path to your PinballFX2 or Steam  exe ,   you should see a virtual emulator option.  (Again this is IF!!!  you have a module that only supports the grid loading method)

 

 

 

 

 

if you have a command line loading module

you would

-add a path to your exe

- make sure the  PXP extension is added

- add rom path to your data_steam  folder found inside your Pinball FX folder  (Grid loading does not use rom paths)

[BlueGoblin]

im getting an error message that says -   No exe path defined

 

 

and I am also getting this message.

 

 

 

 

 

[gigapig]

I did a Teamviewer session earlier and found the Database did not match the ini file where the grid coordinates are. Also EpicGod was trying to set up as if using the command line method which RocketLauncher would not support, by adding the pxp extension and path to those files.

 

But the main problem is the Autohotkey dll error which we all know know means something is out of date. I'm not sure if it's the module that's wrong or some other ahk file. Does anyone know what might be wrong or does someone have old files to try.

 

The best thing to do if someone must have this working is to update and use the simpler command line method.

[Jpacheco]

Have the same problem