D
Deleted User
Crowd Member
jcsix and I were screwing around today with this, and it seems to work. There are quite a few kinks to work out, so let's get to playing some No Mercy and get this figured out.
First off, you will need this. This is the AQZ Netplay Input Plugin, and it's your new best friend for Project 64. It's easy enough to get set up, the instructions are fairly strait forward. One thing to keep in mind is the dll. file goes in your 1.6 plugins folder.
<div class='spoiler_toggle'>Quote from original site</div><div class="spoiler" style="display:none;">
Instructions:
1) Unzip the dll into the Plugin folder.
2) Open Project64 and select AQZ NetPlay as the input plugin.
3) Go to Options, Configure Controller Plugin. Then, select and configure an input plugin to use. (The netplay plugin relies on another input plugin to do the actual work of reading input from the keyboard/controller.) Make sure one and only one controller is plugged in for each player that will be playing locally (at the same computer). To be a spectator, unplug all controllers.
4) Select a game to play. Send the save file for that game to each player you plan to play with. The save file is located in the "Save" folder by default. If each player does not have the exact same save file, the emulators will probably desync. (If I could, I would have the netplay plugin automatically distribute the save file to everyone else, but it is impossible for an input plugin to know where the save files are located.)
5) Open the game. The netplay plugin window will appear. One person will host the server and everyone else will connect to the host.
The host needs to type the "/server port" command in the box at the bottom and hit enter, where "port" is the port number the server will listen on for connections. The port can be any number between 1 and 65535. A message from a firewall may appear. Be sure to click Allow. Also, if the host is behind an NAT (home router), the port will needed to be forwarded.
Everyone else needs to use the command "/connect host port" to connect to the host, where "host" is the IP address of the host and "port" is the port that the host chose to host the server.
(Note: If anyone is using WiFi (excluding spectators), the game may be laggy unless they have a strong signal with low interference. You're better off using an ethernet cable.)
6) Use the "/name name" command to change your name. The name you choose will be remembered next time you play.
7) Use the "/start" command to start the game.
8) Use the "/lag lag" command to change the lag of the game, where "lag" is the number of frames of delay between when you press a button and when that information reaches the game. Choose the lowest number possible. If you set the lag too low, the game will run slow, especially if there is a lot of latency on the connection between the players. If you set the lag too high, the game will be difficult to play.
Golf Mode:
To turn golf mode on and off, use the "/golf" command. Every player must turn golf mode on for golf mode to work.
What golf mode does is allow certain games to be played with absolutely no lag no matter how much latency there is on the connection. It will only work with games where only one player plays at a time. The reason it is called golf mode is because I designed it specifically for Mario Golf.
To use golf mode, wait until it is your turn to play. Before you play, press the L button. What this will do is set your own lag to 0, but set everyone else's lag to what your lag was previously set to. Now you are free to do your turn without any lag. When it is someone else's turn, they will simply to the same thing. I chose the L button because it is unnecessary in Mario Golf and uncommon in other games. I could always change this or make it more flexible if people find use for golf mode in other games.
Notes:
From my experience lag is fairly low and often not very noticeable. It is much better than my experience with Kaillera. Of course, the huge advantage of the netplay plugin has over Kaillera is that it works with Project64 1.7, the best N64 emulator in my opinion. You can use the netplay plugin with other N64 emulators, too. However, in my experience, most of them, including Project64 1.6, will desync while playing a game. I have never had a desync occur while using Project64 1.7 though.
I recommend going to Options, Settings, and unchecking "Pause emulation when windows is not active?" That way you can adjust the lag easily while the game is running. Otherwise, every time you click the window that lets you adjust the lag setting, the game will pause.
Let me know if you encounter any bugs.
Enjoy Project64 1.7 with netplay support!
</div>
So basically, one person acts as a server, and the other people playing connect to him (up to 4 players). jcsix and I were booted off a few times due to my crappy wi-fi, but later on we'll try with a solid connection.
This seems to work with both vanilla No Mercy and WM2000 with very little lag. However, we had to reset our emu to their default No Mercy settings to get consistency.
Now here's the exciting part, textures and cheats WORK. However, we've noticed a lag, so we still need to play with it and see what can be done, as this is one of the coolest things we've needed for No Mercy for quite some time.
If anyone ever cares to setup a game or anything, this is the thread to make your intentions heard and we can connect and get some gameplay going.
We may need to start scheduling a tournament.
First off, you will need this. This is the AQZ Netplay Input Plugin, and it's your new best friend for Project 64. It's easy enough to get set up, the instructions are fairly strait forward. One thing to keep in mind is the dll. file goes in your 1.6 plugins folder.
<div class='spoiler_toggle'>Quote from original site</div><div class="spoiler" style="display:none;">
Instructions:
1) Unzip the dll into the Plugin folder.
2) Open Project64 and select AQZ NetPlay as the input plugin.
3) Go to Options, Configure Controller Plugin. Then, select and configure an input plugin to use. (The netplay plugin relies on another input plugin to do the actual work of reading input from the keyboard/controller.) Make sure one and only one controller is plugged in for each player that will be playing locally (at the same computer). To be a spectator, unplug all controllers.
4) Select a game to play. Send the save file for that game to each player you plan to play with. The save file is located in the "Save" folder by default. If each player does not have the exact same save file, the emulators will probably desync. (If I could, I would have the netplay plugin automatically distribute the save file to everyone else, but it is impossible for an input plugin to know where the save files are located.)
5) Open the game. The netplay plugin window will appear. One person will host the server and everyone else will connect to the host.
The host needs to type the "/server port" command in the box at the bottom and hit enter, where "port" is the port number the server will listen on for connections. The port can be any number between 1 and 65535. A message from a firewall may appear. Be sure to click Allow. Also, if the host is behind an NAT (home router), the port will needed to be forwarded.
Everyone else needs to use the command "/connect host port" to connect to the host, where "host" is the IP address of the host and "port" is the port that the host chose to host the server.
(Note: If anyone is using WiFi (excluding spectators), the game may be laggy unless they have a strong signal with low interference. You're better off using an ethernet cable.)
6) Use the "/name name" command to change your name. The name you choose will be remembered next time you play.
7) Use the "/start" command to start the game.
8) Use the "/lag lag" command to change the lag of the game, where "lag" is the number of frames of delay between when you press a button and when that information reaches the game. Choose the lowest number possible. If you set the lag too low, the game will run slow, especially if there is a lot of latency on the connection between the players. If you set the lag too high, the game will be difficult to play.
Golf Mode:
To turn golf mode on and off, use the "/golf" command. Every player must turn golf mode on for golf mode to work.
What golf mode does is allow certain games to be played with absolutely no lag no matter how much latency there is on the connection. It will only work with games where only one player plays at a time. The reason it is called golf mode is because I designed it specifically for Mario Golf.
To use golf mode, wait until it is your turn to play. Before you play, press the L button. What this will do is set your own lag to 0, but set everyone else's lag to what your lag was previously set to. Now you are free to do your turn without any lag. When it is someone else's turn, they will simply to the same thing. I chose the L button because it is unnecessary in Mario Golf and uncommon in other games. I could always change this or make it more flexible if people find use for golf mode in other games.
Notes:
From my experience lag is fairly low and often not very noticeable. It is much better than my experience with Kaillera. Of course, the huge advantage of the netplay plugin has over Kaillera is that it works with Project64 1.7, the best N64 emulator in my opinion. You can use the netplay plugin with other N64 emulators, too. However, in my experience, most of them, including Project64 1.6, will desync while playing a game. I have never had a desync occur while using Project64 1.7 though.
I recommend going to Options, Settings, and unchecking "Pause emulation when windows is not active?" That way you can adjust the lag easily while the game is running. Otherwise, every time you click the window that lets you adjust the lag setting, the game will pause.
Let me know if you encounter any bugs.
Enjoy Project64 1.7 with netplay support!
</div>
So basically, one person acts as a server, and the other people playing connect to him (up to 4 players). jcsix and I were booted off a few times due to my crappy wi-fi, but later on we'll try with a solid connection.
This seems to work with both vanilla No Mercy and WM2000 with very little lag. However, we had to reset our emu to their default No Mercy settings to get consistency.
Now here's the exciting part, textures and cheats WORK. However, we've noticed a lag, so we still need to play with it and see what can be done, as this is one of the coolest things we've needed for No Mercy for quite some time.
If anyone ever cares to setup a game or anything, this is the thread to make your intentions heard and we can connect and get some gameplay going.
We may need to start scheduling a tournament.
This rules!
