Main > Driving & Racing Cabinets

Ridge Racer 2 and Rave Racer link play working in MAME WIP test build.

<< < (16/17) > >>

holmes:
Really thank you for the tip to make FFB working! I can confirm it works!
To help others, I will try to clarify the procedure:
In Mame, once the game is launched, use Tab to:
      -  go the machine configuration and choose Twin
       - go to the Service menu through the DIP switch menu and activate Wheel Steering Force (or something similar). You can also choose configure several things such as the color of the car.
You need of course to have FFB plugin properly configured for Mame. You also need to activate outputs for windows in mame.ini. At least this is what I have on my PCs.
Good luck!

frankrizzo2:
Thanks for the solution! I'll give it a shot next time I turn the machine on.

John Bennett:
Hi folks, sorry, not looked in here for ages - thanks for the nice comments.


--- Quote from: Super-Becker on May 09, 2024, 11:24:25 pm ---I'm having a lot of fun. Thank you very much John Bennett! Is there any update to link Ace Driver?

--- End quote ---

Sorry, no. I've been distracted having too much fun making my own arcade PCB using the Raspberry Pi Pico chip (RP2040/2350), so I've not tinkered with this in ages.

I kinda reached a wall with ace driver and other non-working stuff where I'd ran out of things to poke and prod.
I guess, for a test I need to see what happens if you put two PCBs into one instance of MAME so there's perfect sync , to see if it's just super fussy about timings. Just takes a lot of code hackery to do that.


Kaneda06:
Hello guy


I have 2 pc for play network (with model 2.3 , teknoparot etc )

Pc1 192.168.1.2
Pc2 192.168.1.3

If i good understand

I go to mame.ini and modify

For pc 1 :


# CORE COMM OPTIONS
comm_localhost            192.168.1.2
comm_localport            15111
comm_remotehost           PC2
comm_remoteport           15112
comm_framesync            0

And for pc 2 :



PC#2 Right side, Car 2, hostname: PC2 mame.ini settings:

# CORE COMM OPTIONS
comm_localhost            192.168.1.3
comm_localport            15112
comm_remotehost           PC1
comm_remoteport           15111
comm_framesync            0


It's correct ?


I need to start by Mame or by batch files ?


linkup1_to_2.bat for pc1
linkup2_to_1.batfor pc2
?


Big thanks


SailorSat:

--- Quote from: John Bennett on September 06, 2024, 03:50:07 pm ---Sorry, no. I've been distracted having too much fun making my own arcade PCB using the Raspberry Pi Pico chip (RP2040/2350), so I've not tinkered with this in ages.

I kinda reached a wall with ace driver and other non-working stuff where I'd ran out of things to poke and prod.
I guess, for a test I need to see what happens if you put two PCBs into one instance of MAME so there's perfect sync , to see if it's just super fussy about timings. Just takes a lot of code hackery to do that.

--- End quote ---

As far as I can tell, I know which wall you are talking about.

Got to a point where most games (mostly those "mode 9" ones) reliably send data out, and show a "link 1" in service mode when "single".
Once linked up, they show "link error", but at least suzuka8h works fine in 2 player mode.

one thing I did different - I do not automatically forward frames (yet), my tx logic is entirely based on the vblank signal.
judging from the memory contents, games place multiple frames in tx memory (spaced by exactly 0x0100), but never advance the tx offset or change the registers in a meaningful way.

So far:
- finallap is sending frames, but fails to read them (link "NG FE01")
- suzuka8h kinda works in 2 player

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version