chaos

Admin
  • Content Count

    1,776
  • Joined

  • Last visited

  • Days Won

    23

chaos last won the day on October 15

chaos had the most liked content!

Community Reputation

169 Excellent

2 Followers

About chaos

  • Rank
    Spambot Exterminator
  • Birthday 10/15/1981

Previous Fields

  • Preferred System
    SNES
  • Favorite Way To Score
    I Don't

Profile Information

  • Gender
    Male
  • Location
    New Jersey

Contact Methods

  • Website URL
    http://
  • Discord
    chaos

Recent Profile Visitors

21,480 profile views
  1. I'd also like to note that you should NOT have Hamachi running when you try connecting (if you have Hamachi installed). This will cause problems. Also, there may be some situations where canyouseeme.org cannot connect, but you will still be able to host a game. So don't use it as an end-all be-all, still attempt to host a game with someone and have them try to connect. If there are any issues, I am happy to try and help troubleshoot your setup. If you don't feel comfortable messing around with settings, we can try doing a Teamviewer remote desktop setup, where I can connect and try some things out. This tends to go quicker, too (Teamviewer is free software, you don't need to register) Link to Teamviewer - TeamViewer 14
  2. With the upcoming season of Classic, I would like everyone to use Direct Connect for netplay. As of this date (10/14/2019), relay server is not working. This is actually very simple to set up. Just requires a few minutes of work, and more time to find the instructions for your router/modem. Check out this video from therexershow - RetroArch - How to Set up Port Forwarding Introduction When playing a game against someone via netplay (P2P - Peer to Peer), one player acts as the host (or server), and the other acts as the client. The host creates the game, and the client connects to the host. In order for a connection to be made, the host needs to allow some kind of access to the client. This is where something called a "Network Port" is used. By opening a specific port, the host allows the client a direct connection to their computer. Now, it is important to note that the port is ONLY OPEN when it needs to be, and is opened and closed by the emulator. For instance, Player 1 hosts a game. They turn on netplay hosting. They start the ROM. At this point, the emulator opens a specific port (designated by the emulator). The client then connects via the network port, and has a direct connection with the host. The game begins, and everyone has fun. This situation sounds very simple, and it is. Where it gets complicated, is when there are multiple devices that the communication has to pass through, like a modem, router, switch, etc. Then, on top of that, everything has its own firewall, limiting unwanted and wanted connections from the internet. This is where port forwarding and uPnP come in to help streamline the communication. Just for clarity, all the stuff on the host's side of things affects if the communication can be established. The emulator on the host's side just puts up a message, saying "Hey, anyone want to play", where the client's side says "I want to play with you, specifically". Since the host does not know the specific client who is connecting to them, it's security features (router, Windows firewall, etc) will prevent the connection. Therefore, the security stuff on the host's side is the one that has to provide the exception to allow the connection (i.e. port forwarding or uPnP). So, if you plan on hosting netplay games, you need to set this up. IP Address - The network address assigned to your network card in your computer. Note, you will have 2 separate IP address for WiFi and Ethernet, because they are 2 separate "cards". When you are connected to a router, your router will assign a "local" IP address to your computer and other devices. These usually start with 192.168.x.x, or 10.10.x.x. Your ISP (Internet Service Provider) assigns your router an IP address, which is used by the internet. If you type in "What's my IP" in google, it will show you your router's IP address. Those people who don't have a router, and just have their computer connected directly to their modem, don't have a local IP address. The IP address assigned by their ISP is given to the computer. Note, your "modem" might actually be a modem/router combo (check and see if it has an antenna and multiple ethernet ports on the back of it), and in that case, works like a router (see above paragraph). uPnP (Universal Plug-n-Play) - A feature in some routers that allows a workaround to port forwarding. It kind of lets the program choose a port, and configures port forwarding on the fly. Many new routers (2010+ I'd say) have this feature, and it is most likely disabled by default. This is the easiest solution. DHCP Reservation - Reserves the local IP address for your computer on your router. This keeps the IP address of your computer from changing, and is important to set, because we use a local IP address when setting up Port Forwarding. Port Forwarding - This is an exception to the security features of your router. We allow a local IP address (your computer in this case, set with DHCP Reservation, so it never changes), the ability to open and close a port through the router firewall. This allows the client's communication to pass through, and directs it (or forwards it) to the correct local IP address. To do either uPnP or Port Forwarding, it will be very helpful to download your router's instruction manual. Most manuals will have sections instructing how to log in to your router, set up uPnP, DHCP Reservation (might also be called IP reservation), and Port Forwarding. If not, you should be able to find instructions pretty easily on the internet via search engine. uPnP Setup uPnP or NAT Traversal, is the easiest way to set up direct connect. But, you need a router that supports uPnP. The easiest way to check is to do a google search of your router model with uPnP. If you can find your router instruction manual, this would be perfect. Step 1: Log in to router - Look up instructions online how to login to your router. Go to a web browser, and type in your router's gateway IP address (usually 192.168.0.1, or 192.168.1.0, it will say it in the instructions). You will be asked for a user name and password, enter those (again refer to instructions, they should be a default, something like "admin" and "password"). Note, the only computer who can login to your router, are those that are connected to it (outside people cannot login to the router). Step 2: Turn on uPnP - Refer to the instructions on how to turn on uPnP. If there are any other uPnP settings, just ignore them. The default values will work fine. Step 3: Turn on NAT Traversal in RetroArch - This setting should be turned on by default if you have downloaded the package from nhl94online.com as of 10/14/2019. - To check if its turned on (or if you need to turn it on): Open RetroArch Go to Settings-User Interface. Turn "Show Advanced Settings" to ON. Go to Settings-Network. Turn "Netplay NAT Traversal" to ON. Go back to Settings-User Interface. Turn "Show Advanced Settings" to OFF. Close RetroArch (to save the configuration if needed). Restart and play! - Note: This only needs to be done once. Once it is turned on, the setting does not have to be touched again. If you have Port Forwarding set up, it will use Port Forwarding before it tries uPnP. - Note: You may see a "Port Mapping Failed" error when hosting a game when this setting is ON. You can ignore this. Port Forwarding Setup Part 1 - DHCP Reservation Step 1: Find your computer's current IP address - This may or may not be needed, depending on your router. But it's quick and easy to do. - For Windows PC: Hit the Windows key and R key at the same time to bring up a "Run" window. At the prompt, type "cmd" (no quotes). A command prompt window will open up. Type "ipconfig" (no quotes) at the command prompt. You should see a window similar to this: Write down the "IPv4 Address" of your Ethernet Adapter (might also say "Local Area Connection"). In the above screenshot, this is 192.168.1.184. - For Mac: Go to the Apple logo on the top menubar, then choose "System Preferences". A new window will open up, and inside that window click on "Network". In the Network window, select Ethernet from the left side. Your Mac's IP address will be displayed on the right side as "IP Address". Step 2: Log in to your router - Look up instructions online how to login to your router. Go to a web browser, and type in your router's gateway IP address (usually 192.168.0.1, or 192.168.1.0, it will say it in the instructions). You will be asked for a user name and password, enter those (again refer to instructions, they should be a default, something like "admin" and "password"). Note, the only computer who can login to your router, are those that are connected to it (outside people cannot login to the router). Step 3: Find the DHCP Reservation page and set it up - Look up this information on the internet, or in your router's instruction manual. This is usually located in the "LAN" section of your router's home screen. I attached a screenshot of an example. - When we open up the LAN section, we see the following page. You'll see a section referred to as "Reserved IP Table", usually called something similar to DHCP Reservation. You will see some entries already here in the screenshot, but most likely on your router, it will be blank. Click the Add button. (Also, note at the top of this screen, this router supports uPnP). - On the Add screen, it asks us to enter the IP address, MAC address (physical address of network card), and a Device Name. If you need to get the MAC address, we can go to "Attached Devices" (black arrow) and get the MAC address of the network card by looking for the IP Address on the list. On many routers, there may be a drop-down where you can select from connected devices. In this case, you can just choose your computer from the list, comparing IP address of the list to the one you wrote down in Step 1. Once done hit Apply. If you go back to the LAN page, you should now see your entry in the Reserved area. - Now, you have reserved your IP Address for your computer. This insures that whenever your computer is restarted, or whenever your router decides to change up the IP Addresses, the one set for your computer will not change. Now we can move on to Port Forwarding. Part 2 - Port Forwarding Step 1: Log in to your router - If you closed out your router screen from the previous part, log back in. Step 2: Find the Port Forwarding page and set it up - Look for your router's instructions on port forwarding. If you can't find them, it's no big deal. The page is usually located in the Advanced section or Firewall/Security section of a router. In this example, the following screen will show: - For Service Name, enter RetroArch (this doesn't matter, its just to identify it for you). - For Protocol, choose TCP. This could either be TCP or TCP/UDP. But you should not set it to UDP only. This may also be called "Service Type". - For External Starting Port, put "55435". This is the port that is used for RetroArch netplay. - For External Ending Port, I also put "55435". (This is used if you were to open a range of ports, but since we are only using 1 port, we put the same number in both spots). - You'll also notice the "Use the same port range for Internal port". If your router doesn't have this, but has Internal Starting and Ending Ports, set them both to 55435. - Rule of thumb, anywhere it says "Port", set to 55435. - For Internal IP address, you would enter the IP address of your computer. This is the address we set to reserve in Part 1: DHCP Reservation - After I'm done, I click Apply. - Note: This is a typical Port Forwarding page, but not all will look like this. There may be less things to enter, or more. Point being, any port should be set to 55435, service to TCP or TCP/UDP, and Internal IP address set to your computer's IP address. If there is an entry for External IP address, this should be set to all 0s. Testing NOTE: Windows Firewall needs to either be disabled, or allow RetroArch to pass through. When you host for the first time, a Windows Firewall message should pop up, asking if the program should be allowed to pass through. I usually check both boxes for Private and Public networks, then hit the OK button. If you hit Cancel on this message, please look up online how to allow a program to pass through the Firewall. If you set up with uPnP, the easiest way to test is hosting a game and having someone connect to you. There is no easier way to test this setup. If you set up Port Forwarding with DHCP Reservation, you should be able to test your setup. This can be done without another person. We can use a website like canyouseeme.org to test if RetroArch can open the port successfully. There are a few steps in testing this: Open RetroArch, and Start Netplay host (under Main Menu-Netplay). You can also load the ROM first, and hit the "n" key to toggle netplay host. Open a ROM. When the ROM opens, you should see a message similar to "Waiting for client..." Go to https://www.canyouseeme.org/. Enter 55435 as the port and hit the "Check Port" button. If successful, you should see a message similar to below: If you see a message that says it is blocking the port, or a timeout, double check your computer's IP address hasn't changed, and that the port forward IP address is the same as your computers. NOTE: The IP address you see on canyouseeme.org is your router's IP address from your ISP, so don't get those confused. If you have any questions, please feel free to DM me in Discord (chaos).
  3. @clockwise @angryjay93 I'm asking on the RA discord about this problem. I'll get back to you guys.
  4. Can you save state during netplay on this one? That's a limiting factor for leagues.
  5. chaos

    SNES 2vs2 ROM

    Please leave them headered. They need a header if you want to play them on real hardware with a flash cart or repro (SNES Everdrive, SD2SNES, etc). I dont think Snes9x cares either way, header or no.
  6. chaos

    SNES 2vs2 ROM

    Yes, header and checksum. The newer versions of Snes9x require it to be correct I believe. The old nhl94 rom that was on the site didnt work with new versions of snes9x either.
  7. Congrats bud. I bought a Framemeister years ago when I added an NESRGB board to my NES. RGB made it look like a whole new console. I then bought all the cables for the rest of my systems. Modded my SNES Jr. (only the old SNES outputs RGB without a mod), and was living the life. Then, early last year, I was able to pick up a 20" PVM free from work (looks just like yours). It was in MN, so I packed the living hell out of it and shipped it to myself back in NJ. It's so much more enjoyable to play on there than on the Plasma with my Framemeister. Now, the Framemeister just sits there. It's a sad story for the little guy. Then, a month or so ago, I picked up a 14" PVM for free (well it was broken). Fixed it up and we used it at the tourney. Worked at a museum in Phili last week, they has 2 PVMs and a BVM laying around. I'm not sure if I can take them though. These things went for big money back in the day. Now people just rip you off on eBay selling these. I think PVMs were $2-5k new (depending on size), BVMs (Broadcast Video Monitor) were in the 10k range. The reason they are so much better than a traditional CRT, is the line count and the quality of the tube. A line count on a reg. CRT maybe below 300 lines. On a PVM they are 600-800 lines (depending on the model). And the tubes are made to last a long time. Even playing on a $20 CRT, composite video looks much better than on an LCD.
  8. You can get a lot of interference calls with manual GC, using the goalie as a third defensemen near the crease. I don't think best-of-5 would be good. At this point both guys had already played a ton of games, it would be mentally draining. Keep it at a good length with best of 3, so if momentum screws you in one game at least you have another to bounce back.
  9. chaos

    SNES 2vs2 ROM

    Hahahaha. Those who downloaded the previous one, use this new one I just updated (7/6/19 - ends in fix2). I fixed the checksum (previous worked for me, rexershow said it didn't work for him). This should work for everyone.
  10. Should be fixed
  11. chaos

    SNES 2vs2 ROM

    This version of the ROM should work in RetroArch (along with ZSNES). EDIT: Download this new one, I fixed the checksum. NHL94-2on2-xstioph-fix2.smc
  12. Yeah, this is covered in another thread - The host is the only one who needs to have set up port forwarding. Anyone can connect to the host.
  13. Doesn't support Windows 7 as a host. Worth trying, but there are many guys on here that play online with older laptops. All Parsec is basically doing is giving the person who connects to you a "Twitch" video stream and using their inputs as player 2. So the person connecting is actually not running the emulator, just streaming the video and sending inputs.
  14. Full Rosters, Includes Tex Add G/Drop F, Ray Ray trade, Luc-Courtnall trade No Lines, no graphics done yet. ETB3_PreseasonV1.bin
  15. Calgary Flames C - Cam Neely LW - Wayne Gretzky RW - Stephane Richer LD - Ulf Samuelsson RD - Scott Stevens XA - Craig Janney First Forward Sub - Craig Janney First Defense Sub - Vachslav Fetisov Goalie - Grant Fuhr