5 replies to this topic

[TerryRed]

File Name: Robocop (Ultimate Edition) (p2.7) (DOFLinx)

File Submitter: TerryRed

File Submitted: 28 Oct 2016

File Category: Future Pinball

Author(s): SLAMT1LT<br />Rom<br />TerryRed
Manufacturer: Original
Year: 2016
Permission to MOD?: Yes, without approval

 A video demonstration of this table running on a cabinet using DOFLinx can be seen at:
 

 
DOFLinx - "A powerful utility for cabinet owners to make the most of force feedback and lighting." - by DDH69
 
This Future Pinball table has DOFLinx commands added to it. This will enable support for pinball cabinet force feedback devices such as solenoids (flippers,bumpers,slingshots,drop targets,etc), RGB lighting and flashers, beacon, strobes, blower fan, shaker, FIRE and other buttons lights, and more! This will work with Led-Wiz, Sainsmart USB, PACLED64, and KL25Z.
 
Requirements / Installation: Regardless of using this table with force feedback (Pinball Cabinet) or without (Desktop), you MUST install the current DOFLinx.vbs script into your ‘Future Pinball\Scripts’ folder. Running the table without DOFLinx.vbs will cause an error. (FF_INIT)
 
Copy the *.fpt and .xml files to your Future "Pinball\Tables" folder
 
DOFLinx.vbs is included with the DOFLinx install package. This file is not included with this table to avoid version mismatches.
 
DOFLinx install package download:
 
The current download of DOFLinx can be found through this post at vpforums:
 
http://www.vpforums....showtopic=35852
 
It is recommended to use this table with BAM (Better Arcade Mode), in order to get the most accurate version of physics intended for this table. Copy the *.fpt and *.xml within this archive to your "Future Pinball\Tables" directory.
 
 
Cabinet Use:
For cabinet users running DOFLinx: This table will function with the in-game sounds for mechanical devices such as flippers, slingshots, bumpers, etc muted.  Instead, you will only hear your cabinet's feedback devices for those actions. The rest of the game's sounds will play normally as intended by the table author.
 
Desktop Use:
For desktop users: This table will still function normally without the need for DOFLinx to be running or installed (read "Requirements / Installation"). It will play perfectly with the original in-game mechanical sounds playing through your PC's speakers. Note: Any DMDs or HudOverlays intended for desktop use were moved out of view so that they will not appear on the playfield (this was intended for DOFLinx cabinet use) .
 
Night Mode:
For cabinet users who want to play at night with their cabinet noise makers turned off, this table can be toggled between Cabinet Use (noisy), and Desktop Use (Night Mode). Please consult the DOFLinx guide (included with the DOFLinx install package) for more information on how to use Night Mode.
 
Please read Requirements / Installation to setup DOFLinx.
 
I hope you enjoy the DOFLinx RoboCop (Ultimate), cabinet feedback and lighting experience!
 
SLAMT1LT gave permission to mod and host this table. - TerryRed
 
For SLAMT1LT's newest versions of his tables (without DOFLinx support), goto his website:
 
http://speak1970.wix...pinballemporium

Click here to download this file

[senseless]

Thanks TerryRed! Love the table but with DOFLinx enabled it is great!

[xantari]

Great! Thanks for your work on this this!


Sent from my iPhone using Tapatalk

[Vizzini]

Thanks. Looks good! 

 

I had to increase FP_LINK_WAIT_TIME=. I'm using a Samsung 850 EVO. Odd that I seem to be having much slower load times than you guys. 

[TerryRed]

Thanks. Looks good! 

 

I had to increase FP_LINK_WAIT_TIME=. I'm using a Samsung 850 EVO. Odd that I seem to be having much slower load times than you guys. 

 

If you have Future Pinball's settings for "Texture Filtering" set to Trilinear, then change that to Bilinear. Trilinear seems to slowdown the loading of tables for some reason, and there is no real graphics benefit from using it.

 

That being said, how fast your CPU (processor) is will probably determine the load speed as well.

 

Changing the FP_LINK_WAIT_TIME=    to 45 or 55 might not be a bad idea for some people.

[Vizzini]

Thanks. I'm on bilinear. i5-6400. Should be plenty fast. It is no problem though. I can wait a few more seconds!