there is certainly a sync that must be done during the exchange of the first network frame to align the master and slave at the timings (vsync based that should perhaps pause, slow down or speed up the client ??) , but I have no idea how it should happen and then we cheat a bit by synchronizing on the first frame received. So we're not in normal operation at all (otherwise everything would work, )

Wow, quelle bidouille! (in french) oups, what a hack, lolCan't be working since master and slave have a unique id and have different bytes set. In addition, the savestate is not implemented for the net version (no net memory save / restore). But I agree, it had to be trying

Model-1 and Model-2 both have a code block that checks for 120 VINTs, then counts the nodes (sending 'K' 'a' 'z' 0 <id> <total nodes>) and afterwards does some kind of network sync (150 VINTs on Model-1) before going "ingame".

Super, a network pro goes into the dance very interesting document!I recognize some elements, there is a lot of similarity (ioreg, commram, operation flow)I do not know if you have already watched the operation on model3, but you risk to navigate in known world

I haven't peeked too far into model-3 yet.Currently in the process of documenting the Model-2 firmware (actually there are two).

Once I got that I might try the Model-3 Firmware, although I have next to no expertise on mc68k assembly

As for Satelite/Relay Nodes:For Model-1 there can be any number of relay/satelite nodes, they don't get a Node ID and don't count up the node count either.For Model-2 this feature seems to be missing - Sega Rally "Live Cam"-nodes get an active node id and the total node count goes up.

Spindizzi,I could log the traffic in Nik's supermodel network version if that would help?I already had a small look at the network traffic. Assuming his code is not inserting other data into the stream I figured out a little of the protocol0xFF is used to mark the end of data packets. Probably the first byte is used to identify the packet type. I see one of the bytes that is used to mark the node ID.

I think we are no need to worry about data packet protocol. model3 just sends a big packet containing slots inside and sets the data received in right place. slot = 1 block of datas for 1 machine. Address and size of packets/slots are predetermined for each games in the start of commram [8 to 0xf]The log could be useful to verify what is transfered and may be where is it placed in commram but it would be a giant amount a datas. Not sure it could really help, but I would like to study thatis Nik's version working with all games or only daytona2/daytona2pe?

I haven't done much testing with itBut it works with scud (but the car's orientation is broken). Like in multiplayer cars face backwards and inverted. Probably some endian swappage or somethingI haven't tested daytona yet but I think it works with thatHarley will work with it, but it hangs on the player selection screen. It doesn't get any further.