Main > Driving & Racing Cabinets
Ridge Racer 2 and Rave Racer link play working in MAME WIP test build.
flybynight:
Replace PC1 and PC2 with the hostname of your two pc's. Confirm you can ping them from each other.
Temporarily turn off windows firewall on both.
Super-Becker:
--- Quote from: flybynight on December 24, 2022, 09:11:57 am ---Replace PC1 and PC2 with the hostname of your two pc's. Confirm you can ping them from each other.
Temporarily turn off windows firewall on both.
--- End quote ---
When doing the ping test the results were:
PC1
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
PC2
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
I don't know what happened to PC1. I can even only link SF Rush, which is through a bridge connection. Model 2, Supermodel and Teknoparrot are not working in link. A few days ago I've been messing with the properties of "IP Protocol Version 4 (TCP/IPv4)" on PC1. I believe I have changed something and have not come back. But I don't know what it is anymore. Is there a way to reset?
*Edit: Actually what I messed up was in "Realtek Gaming 2.5GbE Family Controller Properties" in the "Advanced" tab. I'm trying to fix this. I am ashamed that I know so little about these things, talking to people who understand so much about the subject. I am very grateful to everyone.
John Bennett:
--- Quote from: flybynight on December 22, 2022, 06:24:41 am ---That was a great read! Seems like the guy made up that story of moving into a house and "finding" the PCB's but anyway great news the roms were saved.
Did you see in the new November MAME and soon to be released in December's MAME, MAME developer "Windyfairy" has added in some new graphics fixes to Ridge Racer (accurate shadows) plus added network card emulation to the Konami hornet and viper systems. Another MAME developer Ville had previously worked on this and said the network emulation was holding back a bunch of the Konami 3D Racers so fingers crossed for more working driving games soon.
@John Bennett perhaps yourself and Windyfairy could collaborate on your excellent work?
--- End quote ---
Happy new year!
Yeah, that was all made up about finding a Fullscale in the house, same bloke. So bloody annoying, the whole thing, but at least we saved the main parts.
If you look down on in that arcadeblogger page, there's a link to a video of an MX-5 dash on the floor - that's me. My current plans are:
Build up a PCB (parts arrive this week) so I can drive an MX-5 dash from a PC (without piles of wires and stripboard). Fullscale used a 'V138' PCB to drive the room lights and the dashboard. I cloned that for documentation purposes, then made my own version that talks to a PC and uses a dsPIC to control everything.
This'll draw a line under the fullscale emulation.
Tidy up the driver, and pull any recent updates (like the shadows you mention).
Put the code out there in the state it's in now.
Keep tinkering when I can.
I'm not really interested in putting the code into MAME myself, but it'll be there for people to pick apart. Code reviews are bad enough in a job, I'm not enduring them for a hobby :D (plus that code is hack-central, it'll have people twitching, but I wanted it playable).
SailorSat:
--- Quote from: John Bennett on December 08, 2021, 06:52:11 am ---mms (in the test mode) and that gave me the basic gist of what's going on.
Incase I needed more, I bought a Final Lap dual boardset I could wire-up.
But I haven't needed to yet...- I tend to find just using the MAME debugger and a text window (turn on 'verbose' in the mame cfg and you can see some of my debugs) and I can get a good enough idea of what's going on. It's about stepping through the game code and commenting it, in order to work out what it's expecting from the chip, in terms of where data should be. I effectively need to see what the comms IC has to do in order to keep the game code happy.
I'm starting to think the 'loop' is purely a software thing. One board sends to the next, then the game code has to take the data and put it back into the comms IC buffer to send to the third board. I'd previously assumed this was automated. So might have made a little progress - I think there's something fundamental like this which is stopping 3/4 of the games from working.
--- End quote ---
well, that is what I did when I reverse engineered the model-1 comm board.
sorry for being late to the party ;)
did you ever upload your code somewhere? would love to take a peek :)
John Bennett:
--- Quote from: SailorSat on January 12, 2023, 06:06:01 pm ---
well, that is what I did when I reverse engineered the model-1 comm board.
sorry for being late to the party ;)
did you ever upload your code somewhere? would love to take a peek :)
--- End quote ---
No, I hadn't - you might know how it is, you want to get something into a decent state before sharing it. But I PROMISE, I'll upload it in the next 2 weeks. I think I have to realise I'll never get the time to work out why I can't get 3 games working, or any System 2 games.
I'll never get it MAME-worthy, but I'd also like to take out some of the shameful hackiness and make it at-least understandable for anyone wanting to try and help evolve it.
Did you implement the synchronisation for the Model 1 games? I think that's possibly where what I've done falls apart (not all games tolerate missing packets).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version