Unnamed SF Rush the Rock to Mame Racer Conversion

[nipsmg]

Unnamed SF Rush the Rock to Mame Racer Conversion

I recently picked up a Rush the Rock for $400 in "working" condition.  The NT-2701 is faded and needs a recap, and has no anode cup?!, and the active steering didnt work.  I replaced a bad belt and got it working, but with the monitor the way it is it's underwhelming -- but I love the Force Feedback. 

I found L2Happ, a Logitech to Happ active steering conversion board, and started looking at the FFB Plugin lately and seeing all the racers in MAME, Model2, and Teknoparrot and was sold on converting it.

Here's the cabinet after I cleaned up the plastics:



The following is a list of my everything (that I know of so far) that I need to do to get this up and running:

• Install and Test the Gonbes GBS-8200
• Throw crappy TV in cabinet to test GBS-8200
• Test new monitor / GBS-8200 with Rush the Rock boards
• Order 27" gaming monitor
• Install new gaming monitor
• Identify CPU / GFX card to purchase
• Build Racing PC
• Purchase and install additional buttons on cabinet and on steering wheel
• Buy Logitech Driving Force wheels and pedals
• Buy LED control interface
• Order L2Happ boards for print
• Order L2Happ Components
• Purchase 24v Power Supplies
• Build and test L2Happ board
• purchase and install audio amps
• Wire up existing controls
• Wire up LEDs
• Install PC in cabinet
• Initial Test

I've already purchased the Gonbes GBS-8200 CGA/EGA/YUV to VGA adapter to wire up the existing SF Rush board to the new monitor.


I've also purchased a Dell U3014T 30" lcd monitor to replace the existing 27" NT-2701 Medium Res monitor:

---

PC Specs

PSU: Corsair 650W Semi-Modular PSU
CPU: AMD Ryzen 5 3600
Motherboard: ASRock B450M Pro4
GPU: HP NVIDIA GeForce GTX 1060 3GB
RAM:  Corsair Vengeance LPX 16GB (2x8GB) DDR4 DRAM 3000MHz C15 Desktop Memory Kit

OS: Windows 10 PRO v1803

Windows 10 updates disabled using gpedit.msc per instructions here: https://www.windowscentral.com/how-stop-updates-installing-automatically-windows-10

-----
Also, there is tons of scattered information for setting up games but nothing concrete.  I plan on adding a DETAILED setup log and build log -- I'll probably make a separate thread either in Driving/Racing or the Software forum for setting up LaunchBox/BigBox with all of the different emulators, ffb plugins, etc.

I'll probably work on this more in the fall, but will make incremental progress and post updates here.. 
Stay Tuned.

\[/list][/list]

[nipsmg]

Setback #1:  The measurement I got online for the interior dimensions of the cabinet was off by 1.5 inches. (I think they measured from the outside of the wood).  So the monitor I bought won't fit, nor will the other one I was planning on swapping out of my PGA cabinet if this is too tight.

[jennifer]

That seems like a curious project, quite ambitious to say the least...I happen to be building a modernized version of the Red Baron sit down, and can't help noticing that seat looks like a VR global, Blazing Angels, but in green...Jennifer don't say that to be stupid, Just may help you cross platform some of those parts before you start gutting that thing...😘

[nipsmg]

I found a 27" Acer low latency IPS Gaming Monitor that'll fit in the space.  But I'm losing a full 2" of vertical picture which SUCKS, but I don't have a lot of options.  The interior dimensions on this cabinet are TIGHT, they barely fit that monitor.  The "bezel" is just a piece of cardboard, not enough room to fit a bezel surround in there.

[nipsmg]

Threw a crappy TV I have in the cabinet that I float around to watch sports outside and stuff.  Wired up GBS-8200 and after some calibration the picture is excellent.  I'm impressed with the signal quality for such a cheap board.  No artifacts, no noise.





The monitor I ordered should be in Wednesday.  Will be testing that monitor then permanently mounting in the cabinet and putting the case back together --

Next steps after that:  get L2Happ boards created, test that, and identify what computer hardware to buy for the PC.

[nipsmg]

Screen mounted and bezel created.



Needs some brightness adjustments (too bright) but all in all looks pretty good.

[nipsmg]

Bought a Ryzen 5 3600, MB, Cooler, and GTX 1060.  Need RAM, asked for it for Father’s Day. Already have PSU.

If/when that happens will start configuring (and documenting configuration of) the software.  Haven’t got the L2 Happ on order yet.. still waiting for the board design from my father. Moving forward pretty quickly.

[nipsmg]

Pc completed.. 1st post updated with pc specs. Wrote up detailed configuration for first game:  SF Rush the Rock (of course).

Trying to figure out the best way to post them..  blog/wiki/etc.  will post tomorrow and will make
Detailed setup instructions for each game and the frontend as I configure it.

[nipsmg]

Will write up OS config as well.

[bobbyb13]

This is awesome.
I may have just scored a second one of these cabinets but it is so thrashed that I may save the good components for my first one and follow your lead.

Thanks for posting this build!

[nipsmg]

***Reserved for OS Setup***

[nipsmg]

Configuration Log for Setting Up First Game w/ FFB - SF Rush the Rock



Overview
The first game I wanted to install and get working was SF Rush the Rock (and the whole SF RUSH series), as once the machine is up and running I want to be sure I can play the original game FIRST before I add anything else to the cabinet.  This is going to requre:

   - The rom
   - The chd
   - The FFB Plugin
   - Mame.

Step 1: Download FFB Plugin


   In this tutorial I'm using v 2.1.7 from the following Url https://github.com/Boomslangnz/FFBArcadePlugin/releases
   
Step 2: Download MAME
Using version 220 form here: https://www.mamedev.org/oldrel.html

Step 3: Download MAME64Arcade
Downloaded MAME v.220 with nonag  and all mess systems removed from here: https://forums.launchbox-app.com/files/file/2383-mame-0220-nonag/

Step 4: Extract MAME
Launch MAME220b_64bit.exe and extract to c:\emulators\mame

Step 5: Extract mame64arcade.zip to c:\emulators\mame

Step 6: Procure roms for SF RUSH games
I raided my MAME cab and copied over the following files from my MAME NON-MERGED set to c:\emulators\mame\roms

Sfrushrk\sfrushrk.chd
Sfrush\sfrush.chd
Sf2049\sf2049.chd
Sf2049\sf2049se.chd
Sf2049\sf2049te.chd
Sf2049.zip
Sf2049se.zip
Sf2049te.zip
Sfrush.zip
Sfrusha.zip
Sfruskrk.zip
Sfrushrkw.zip
Sfrushrkwo.zip


Step 7: Test that game launches.
Once copied over, I tried launching the game using mame64arcade from the command line to be sure it launches:





Step 8: Install FFB Arcade Plugin 2.1
   - Unzip the zip file
   - Find folder for MAME 64-bit outputs
   - Copy all files into c:\emulators\mame
   - Open FFBPluginReadme.txt and read instructions
   - Create MAME.ini by typing MAME64 -cc
   - Add the foillowing:

Code: [Select]

# OSD OUTPUT OPTIONS
#
output                    windows
Step 9 - Download the visual runtime pack as instructed in the readme and install:
      ○ https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/
      ○ Unzip
      ○ Run InstallAll.bat
      ○ Wait until complete.
Step 10- Launch and Configure FFBPluginGui.exe




   1. Click "Force Feedback Setup"
   2. From the dropdown, select the wheel


   3. Click SF Rush the Rock:




I'm going to leave as-is for now to test.

   4. Click Go back to previous menu

   5. Click Force feedback test

Test out effects.




Step 11: Relanch mame and configure controls

   1. Re-launch mamearcade64 sfrushrk

   2. Attempt to configure controls -- it looks like the pedals are backwards (always at max).

   3. Reverse the pedals… 
      a. Analog Controls setting in mame menu lets you change the settings to match properly.




Step 12: Fix the deadzone
There is a SIGNIFICANT deadzone in the game -- After some research I found you can set this in Mame UI.

   1. Download mameUi220: https://www.emutopia.com/index.php/item/2100-mameui64-0-220

   2. Find the game, right-click, properties, click "Controllers"


   3. Change Joystick Deadzone to 0.00
   4. Click apply
   5. Close mame ui
   6. Launch from command line again.
 
The game now plays successfully and has good controls.  Something about the force feedback feels… off.. From the original.  I'll have to see why that is.


Step 13: Configure SFRUSH / SF2049
Follow the same configuration steps above for SFRUSh and SF2049 as they are identical

Additional Info: Deadzone Setting in .Ini
The deadzone setting from MAMEUI created an sfrushrk.ini file in the /mame/ini folder.
The setting that we care about from there is joystick_deadzone:


Globally Setting MAME Deadzone to 0

This can be set globally by launching mame64 without a rom name
Click "Confgure Options" -> "Advanced options".  Scroll down to the bottom and set joystick deadzone to 0.
Make sure to click "Save Configuration"

[nipsmg]

*** Reserved for Mario Kart GP DX Arcade Setup ****

Installation Steps

   1.  Go to https://teknoparrot.com/ and download the latest version.
In this case, I'm using 1.0.0.140
   2. Extract into your Emulators folder
   (in this case, c:\dropbox\emulators\TeknoParrot_1.0.0.1403
   
   3. Locate Mario Kart GP DX v 1.10 online somewhere and extract it into a folder of your choosing
   (in this case, c:\dropbox\games\Mario Kart GP DX 1.10
   
   4. Launch techno parrot.  You'll probably get a message saying you need to do first time setup.
   5. Technoparrot might dump a bunch of windows on you saying there are updates for specific components. 
      a. If there is an update for Technoparrot UI, update that first as it will require a reboot
      b. Update each component until there are no more updates.
   6. Technoparrot will ask if you want to set up a game.  Click yes.
   
   
   
   7. Click Mario Kart: Arcade GP DX, then click "Add Game" on the right.
   
   
   8. Click Game Settings on the main screen with Mario Kart: Arcade GP DX selected on the left.
   9. Click the line under Game Executable and select the exe file for the game (in my case: "C:\Dropbox\Games\Mario Kart GP DX 1.10\MK_AGP3_FINAL.exe").
   
   
   10. Uncheck "General - Windowed" and click Save Settings
   11. Click "Controller Setup"

   12. Click the line next to each setting and set the controls using your steering wheel and the required buttons.
   
   
   13. Click "Save settings"
   14. Click "Launch Game"
   A message appears stating Mario Kart GPDX needs to be run as admin to work properly..
   
   
   15. Click "no" and close technopoarrot
   16. Navigate to the Teknoparrot folder (in my case C:\Dropbox\Emulators\TeknoParrot_1.0.0.140)
   17. Right lickc teknoparrotUI.exe and click Properties
   18. On the Compatibility tab check Run this program as an Adminsitrator
   19. Click Apply, then OK.
   20. Re-launch technoparrot.
   21. Click Launch game
   Got an error:
   
   
   22. This game requires both the DX runtimes and the DX SDK.  Install the following:
   Runtimes:
   https://www.microsoft.com/en-us/download/details.aspx?id=8109
   
   SDK:
   https://www.microsoft.com/en-us/download/details.aspx?id=6812
   
   (Ignore the error at the end of this installation)
   
   23. Launch technoparrot and try relaunching the game again.
   
   
   Hanging…..
   
   
   Nope, just takes a long time..
   Launched just fine.
   

   
   24. Gas and brake are reversed.  Hit ESC to quit the game, go back into game settings, and reverse the gas and brake pedals.


Installing the Translation Patch
   1. Download the translation patch from https://github.com/Harmmmm/MKDX-English-Mod
   2. Extract the zip to somewhere
   3. Run MKDX Patcher
   
   4. Click "Select MKDX to Patch" and select the MKDX Exectuable (in my case, it's in "C:\Dropbox\Games\Mario Kart GP DX 1.10\MK_AGP3_FINAL.exe")
   The patcher willl run and say "Done! " when complete.
   
   5. Close the patcher and relaunch the game.?,lp


English!!!




Configuring the FFB Plugin

   1. Copy the files from the Maro Kart GP DX v110 folder in the FFB Plugin dir
   
   
   
   2. Paste the files into the root of the Mario Kart GP DX Arcade folder (in my case, C:\Dropbox\Games\Mario Kart GP DX 1.10)
   3. Launch the FFBPluginGUI.exe
   4. Click the Force Feedback Setup button.

   
   When I first started this my DeviceGUID dropdown was blank.  To fix:
      a. To fix a missing DeviceGUID
         i. Close FFBPluginGUI.exe
         ii. Navigate to your MAME folder and open the FFBPlugin.ini file from the SFRush setup
         iii. Copy the DeviceGUID value
         iv. Close the FFBPlugin.ini file
         v. Navigate to your Mario Kart GP DX v110 folder.
         vi. Open the FFBPlugin.ini file
         vii. Paste in the DeviceGuid value
         viii. Save the ini file.
         ix. Launch the FFBPluginGUi.exe file again
         x. Ensure it's workign by going into the Test section and testing it.
   
   Setting Up Banapassport (to allow saving games).
   1. Go to www.teknoparrot.com and log in
      a. If you don’t' have an account, sign up then sign in.
   2. Go to https://www.teknoparrot.com/mkdx
   3. Copy the number shown on this page
   
   
   4. Open teknoparrot and click on Game Settings for Mario Kart GP DX
   5. Paste your profile identifier number into the Network - Player ID setting
   
   6. Ensure the Network - Gateway setting is correct for your local network
   7. Save settings
   8. Launch the game.
   9. When you start a game, on the "Scan banapassport" screen, choose yes.
   
   10. Press the F2 Key on the keyboard to insert the banapassport.. Now your progress will be saved

       
       
       

   
   
   

[nipsmg]

Chase HQ 2 Setup Log

   1. Find and download the Chase HQ 2 files.
   2. Unzip files to the target game folder ( in my case, c:\dropbox\games\Chase H.Q. 2 (2007)
   3. Launch Technoparrot
   4. Click the "hamburger" menu at the top left and click "Add game
   
   
   4. Select Chase HQ 2 and click Add Game
   
   

   5. Select the game executable  (note: In my case, the copy I got had already been modded to be run directly, so I had a game.exe and a gameorig.exe.  I ended up having to use gameorig.exe)
   
   
   
   6. If  you had a pre-modified version you might have gotten the following message:
   
   
   If so, just delete the files listed.
   
   7. Configure the controls.  You will need the start key, so I'd suggest mapping it to something on the wheel.
   (NOTE: the gas/brake weren't actually reversed in Mario Kart.  To map properly here, click "Gas", hold down the gas, then click "Brake" and release.  Click "Brake" again then click something else like shift-low and release.  Then set all the other settings and click "Save settings".  That way it's measuring the positive depression as the axis you're using.
   

   
   8. To enable english, open chq2.ini in the game install directory and set DEST_COUNTRY to 3.
   
   
   
   9. Configure FFB by copying the files for Chase HQ 2 from the FFB plugin folder for Chase HQ2 and pasting them in the Chase HQ2 install folder.
   
   
   
   
   10. In Game Options in Teknoparrot, uncheck Game - Windowed
   11. Run the game from TeknoParrot.

[javeryh]

This is a wealth of information.  Great post(s).   

[nipsmg]

Crusin USA / World Setup

These were some of my favorite racing games growing up.  Psyched to add these.

   1. Copy the roms from your mame collection.  These are the files I added from the non-merged set:.



   2. Launch CrusinUSA in MAME
   3. Hit Tab - > Go to Analog Settings, invert the 2 pedals
   
   4. Set input settings for this game.  You will need to map:
      a. Radio
      b. View 1
      c. View 2
      d. View 3
      e. Wheel
      f. Pedal 1
      g. Pedal 2
      h. 1st gear
      i. 2nd gear
      j. 3rd gear
      k. 4th gear
      l. Start
      m. Enter/Test (mapped to F2 by default)
      n. If you want to be able to control the service menu from the wheel you also need:
         i. Volume Up
         ii. Volume Down
   5. Calibrate Controls -- "Enter" is your "enter/test" button for confirming calibration.
   6. Play.


Force Feedback
If you're following along, Force feedback should be working as it was set up for MAME already for SF Rush / Rush the rock.   This can be confirmed through the service menu in the utilities / steering test…  it does move the wheel left/right, but I hate the feeling in-game.. It feels nothing like how it did in the arcade.. I am going to need to make adjustments.

As I find good adjustments for games I'll add them in this thread somewhere.


Crusin World
Steps are identical to Crusin USA

[nipsmg]

Setting up Initial D Stage Zero Arcade

Setting up the game...
   1. Download the game from the internets…. Somewhere…
   2. Once downloaded, extract the SDDF_1.31.00 folder to somewhere on disk (in my case, c:\dropbox\games\Initial D Zero Arcade\SDDF_1.31.00\
   3. Unzip the minime server zip to somewhere on disk (in myt case, c:\dropbox\games\Initial D Zero Arcade\minime  -- this is no longer necessary with teknoparrot.
   4. Open up PowerShell.  If you don't have it ,install it somehow.
   5. Launch powershell AS ADMINISTRATOR
   6. Execute the following: Set-ExecutionPolicy Bypass -Scope Process
      a. Hit Y + enter at the prompt.
      b. Excute the following command:
         i. Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))
      c. This will install chocolatey on your machine.
      d. Close your powershell window.
      
   7. Download and install NodeJS server from https://nodejs.org/en/download/ (in this case, I'm installing node-v12.13.0-x64.msi).  You should be safe with a  version 12 LTS version of NodeJS server.
      a. Note, when installing, if prompted with a checkbox, check the box that will download all necessary tools to build required binaries.  If you do, you will see a command window popup like the one below.
               
      
      Follow Prompts.
      
      The first message might be an error but since you isntalled chololatey, it will continue ..
      
      Installation will begin of all of the needed tools, etc.
      
               
      
      
      NOTE: This might take some time ( 10 mins ish).
      Note: one package required a reboot --- so I rebooted and re-ran the installer.. It didn't say anything os I did a repair to be sure.
      
      
   8. Open the MIniMe folder (inside your teknoparrot\segatools\minime folder ) and run start.bat as administrator.
   
    
   Hit any key and the builds will start.
   If you get a windows popup stating that nodejs wants access to the internet, allow it.
   
   If all is will, you should see that the server has started, as you'll see some lines with app: switchboard and app:checkdb at the beginning, and a  Startup OK message.
   
   
   
   9. Click Ctrl-C to kill the server and exit.
   
   
   10. Launch TeknoParrot UI,. Add new game, Initial D Stage Zero Arcade.
   11. Click Game settings
   12. Set the following:
      a. For Game Executable, choose the  InitialD0_DX11_NU.exe  file under under games main folder\app\package folder ("C:\Dropbox\Games\Initial D Stage Zero Arcade\SDDF_1.31.00\app\package\InitialD0_DX11_Nu.exe")
      b. For network adapter, enter your local IP address (in my case 192.168.2.164)
      c. Check all other boxes (other than enable xinput)
   

   
   
   Click Save Settings.
   
   13. Go into Controller Setup
      a. Map all controls except gear 1-6.  We'll be using Gear Up / Gear Down in this game so there's no need for the shifter controls.
   
   14. Click Save Settings.
   
   15. Launch the game.. (Hopefully this works??)
Note: the black screen may end up there for a while..
The game may not launch the first time.  Try re-running it.

You should get a "Initial D Initializing) window.




The game should be playable.






Install the Fullscreen Patch

To make the game fullescreen, you need to patch the exe.
   1. Download HxD from https://mh-nexus.de/en/hxd
   2. Unzip and run the installer.
   3. When done, launch HxD
   4. Open the Initial D Zero executable
   5. Click Search -> Go To or press CTRL+G
   6. In the Offset box type 35E205 and click OK
   7. Set the 01 value to 03
       


   8. Click Search -> Go To  or press CTRL+G again
   9. Type A3A05F into the Offset box and click OK.
   10. Change C8 00 to 00 10
   
   
   
   11. Save changes and exit.


IMPORTANT NOTE-- the 00 10 at A3A05F ended up with significant slowdown in game and a lack of playabilty.  To fix, change the 00 10 to 00 80.

Force Feedback Plugin
   1. Navigate to the location where you unzipped the FFB Plugin
   2. Copy all files in the InitialD Zero folder and paste them in the app/package folder under the main Initial D Game folder. 
   3. Launch the FFBPluginGui.exe , click Force Feedback Setup and select the wheel.
   4. Close the plugin and launch the game.

[nipsmg]

Improved footprint and layout from the original design.  I believe I should have pictures of populated boards by tonight!!

[nipsmg]

Just needs heat sinks installed.  All populated and soldered.

[Justin-Credible]

Awesome! I'm looking forward to hearing how they work out. I'm definitely interested in one for my setup!

[nipsmg]

Boards in hand. Just threw on heat sinks. I really hope to test this weekend.

[nipsmg]

So I went to go look at wiring it up.. and realized it’d be easier to use existing wiring. I’ve got a bunch of wiring harnesses from my Tekken 3/SmashTV that will work for most connections and I bought a JAMMA breakout board to wire up everything else to the JAMMA harness.

I spent a good 3 hours looking at the wiring diagram for the cabinet to map what is going to where.  I also realized I’m gonna need a new 24V power supply for the motor, so I ordered that.  i
It’s in Tuesday, and I hope to be able to test out steering, the shifter, pedals, audio (via the 2 audio amps I bought) and FFB on Tue evening after work.  Stay tuned.

[nipsmg]

I just finished testing the L2Happ board:

It works!! Kinda. -- When running the force feedback tests the wheel moves but not the way I would expect.  I didn't hook up the steering pot yet, and I think some of these (Spring, etc) need the pot hooked up so the software knows where the wheel is.  I'm going to be working on that over the next few days.  But it works.   Getting there...

[nipsmg]

Got the steering pot hooked up.  Now all of the effects in FFBPluginGui work properly.

[nipsmg]

Still working some of the kinks out of the system, and waiting for my jamma breakout to start wiring up the buttons.  But I did get a chance to secure everything down to a board and route some wires cleanly.  This is going to make it much easier to work on without everything sliding all over the table.  I have another 24v power supply coming in sat, that goes just to the right of the other one for the audio amps..  beyond that, I'm waiting for some couplers, and I really just need to get things wired up.

[nipsmg]

 -- deleted --  --- Reserved for the next tutorial update maybe.

[nipsmg]

So, I completed wiring up all the controls last night.



I got in a jamma breakout board and mapped wires to the reverse button, abort button, and view buttons.  Got in my 2nd 24v power supply as well.  Yesterday I brought the whole board outside on my patio and wired the JAMMA breakout to  an old Ipac4. 

I bring it into the garage where the cabinet is, bring out the pc, and connect all the wires to the wiring harnesses and the jamma breakout to the jamma connector..  I boot the PC, plug in the Logitech board's USB, and hear the USB "ding" sound.. so far so good.

I open up logitech profiler and it can't detect the controller.

I open device manager: "Windows stopped this device" "Cannot read device descriptor."  ....    I go to look at the board, and there is liquid pooled up on the top of the primary IC on the circuit board.  Turns out, because it was like 97% humidity yesterday, either while working on it or while carrying it into the garage, I dripped sweat onto the main IC. --- I unplugged everything, let it all dry out, cleaned it all up with rubbing alcohol, let it all dry, and turned on the PC again this morning.  I connected the USB to the computer and ...... nothing.  No ding, no sound, nothing detected, nothing.  I think I fried the Logitech board that I ripped out of the wheel.

So now.... I have to find ANOTHER donor wheel.   

[bobbyb13]

Of course this continues to be awesome.

Bummer about that wheel board- sorry to hear.

I really need to do this to one of my 2049s.

[nipsmg]

So, I haven't really posted in a while because I've been very busy and troubleshooting some issues.

I built some L2Happ boards for force feebdack based on an old design on the gamoover.net forums...

They worked for a while (with some weird issues where "left" pulls were stronger/worked better than "right" pulls), and then broke down.

 

Eventually the first transistor overloads and gets so hot it burns off the annodized black covering on the heatsink, and "left" pulls stop working entirely for the FFB.

--- so after a bunch of sunk costs trying to go the "cheaper" way (which ended up being more expensive), I literally JUST ordered a PWM2Happ from Aganyte in the gamoover.net forums.  This is a custom board with an arduino that runs one of two FFB solutions on it that emulates a wheel and all of the inputs and the FFB in one board. 

Expensive at $130 ish (110 euro shipped to the US), but compeltely worth it to me... considering after sourcing and killing multiple donor logitech wheels, and dealing with the issues that come from having to marry joystick + keyboard support because the buttons go through an IPAC and not the wheel, etc..

So this is going to be on hold a bit, besides maybe setting up a bunch of games until I get the FFB board back in, then I'll have to re-do all the wiring.. (yay).

-----

this project is by no means dead.

[bobbyb13]

Well, I certainly appreciate your efforts anyway.

Hard to stay tough while engineering on the fly but you already know it isn't for the cowardly.

Really stoked for you getting this working the way you want it to!

[nipsmg]

I've been doing some work on a theme for BigBox.  I don't need all kinds of crazy info, just a way to select the games and see the video previews.

I really liked the round logos people were doing for TeknoParrot, and came across a picture of the dash of a 2011 mini -- and figured it'd be a perfect fit for those icons.  Some photoshop and tweaking later and i have a functional theme.

Would love feedback:

[nipsmg]

I noticed after I uploaded the video that I missed a cutout for the windshield above the tachometer in the middle of the top of the steering wheel..

That's been fixed already.



**EDIT** -- I updated the video in the previous post with corrections.. Here's how it looked before:

[nipsmg]

Also,

    I took my last working L2HAPP board and was very careful to dial down the power on the board so that it woudl not move AT ALL when power was applied, then set the output at something that felt good for FFB but wasn't super strong.
   
    So far, so good..  it's been holding up and not frying.  I think the probelm was not knowing where to set the power output and it was dumping too much through.   I've specifically adjusted FFB for each game now and it all feels great.

[bobbyb13]

I was so busy thinking how cool the mini dashboard looked I never noticed the cutout until you mentioned it.

This whole thing continues to be outstanding.

[Justin-Credible]

The theme looks awesome! Will you be making it available for others to use? I'd love to run it on my setup.

[nipsmg]

Yes, I definitely will. 

Still in progress at the moment but I will share it with whoever wants it once it's a little more complete.  I was going to keep it from having a platform view, but now I'm thinking I'm going to separate arcade games, PC Arcade-Style, and PC Sim-Style games.

I made a change to the way the control works, I wanted to use the pedal to select (Needs Joy2Key)..  couldn't find a good animation of a pedal being pressed. I tired using perspective tools in Photoshop but it just mashed it up..  Come to find out Photoshop has some 3D tools that are pretty useful.  I cut the pedal out into a new layer, created a 3d extrusion, rotated the whole pedal layer in 3d space to where it would be if pressed down, rasterized the layer, then added shadows and it looks pretty good for an icon animation..



Short video of the animated icon in action: 

[bobbyb13]

...and the project continues to be beyond awesome.

Game selection animations look excellent.

[nipsmg]

So I haven't made any progress with the frontend at all due to work obligations, but I did finally receive my PWM2Happ board from Aganyte from the gamoover forums.

I had been running into issues with the Logitech interface namely:

• Support for only 2 pedals (cabinet has 3)
• Buttons are not each wired discretely, use a matrix and diodes, making it difficult to wire up buttons to interface
• Combination of Keyboard interface and Joystick causing control issues with some PC driving games

I bought the PWM2Happ board for a few reasons:

• Improvement on L2Happ design
• Pairs with inexpensive Arduino Mega 2650
• Arduino + njz3 code allows for 3 pedals, 16 buttons, and even a 12 number keypad

The wiring diagram for this setup is here:



The guys over at gamoover have been really helpful, even with the language barrier (it's a French forum).  Google translate has been helping out a bunch.

I've got the mega flashed and can confirm that a button wired to the board fires and operates as a joystick button. 





I'll be (hopefully) wiring up the rest of the interface within the next week.  I can't really test out the PWM2HAPP driver board until I get a heatsink in, which should be early next week.

[kingofpoon]

hello i am a new member i found this site because what you created here is exactly what i want to do it looks like you have worked out a few kinks and id like to talk a little about whats needed to make this work without having to hit all the dead ends you ultimately had to go through specifically starting with l2happ/pwm boards to use the fbb from the original cab i have a working san fran rush (original not rush the rock) but due to limited space i can only afford to have one machine and this would allow me to enjoy the games i grew up on and at the same time allow the kids to play there favorite (mario kart) i cant pm as i am a new member but hopefully you can message me or send me on the right path to get started i have read through this post quite a few times now but this is more of a work log then a tutorial any help is greatly appreciated and you have done some amazing work here

[nipsmg]

Soooooo.. I'm back.  I got a new PWM2Happ board and attempted to get the force feedback to work trying multiple things for a month with a language barrier, then winter came and it's too damn cold to work in the garage so this went by the wayside.

Then i picked it up in the spring and tried everything to no avail.  After talking with Aganyte over at gamoover.net, he was gracious  enough to send me the newer, updated board for a free exchange.  I got the new board, put it in, and BOOM -- Working FFB again!! (Whoot!!)



video:


I Just really started dialing it in and trying it with a few games and have gotten Outrun 2 SP DX and Sonic All Stars racing to work properly.  I'll be starting on a complete soup-to-nuts write-up on setting up the hardware for a PWM2HAPP build (in english) as the main forum is in French.  That should be coming sometime in the next week, then back to finishing up my BigBox theme and more configuration details. 

Stay Tuned...