Per Ole, You [u]are[/u] missing a step (not following my guide step-by-step) or it would be working! :) It's that simple really. [i]As my guide states, you're probably in a "double-NAT" situation (where your cable/dsl modem is also setup to be a "router" at the moment) so as I've stated in my guide you'll have to verify if that in fact is happening. If that is the case, then you'll need to do what I instructed the other's who were in the same boat to do (ie. forward the port
the_Monk
[quote] OK, I'm totally confused. I have a linksys WRT54GS. I've been tinkering with this thing for an hour, and did my best to follow Monk's guide. Under the Applications and Gaming Tag there are a number of boxes. Under application, I wrote sins. Start I put 6000, end I put 6003. Someone else who has the same router told me these settings worked for him. Protocol I put both. There's an IP address already filled in 192.168.1. with a blank space after the last dot...I left that totally empty
Tough_Nutz and hunter281 Follow the steps in my guide "Networking and SINS" (linked in my stickied thread, in the OP under the GREEN writing). Since SINS is P2P my guide isn't only useful for those wishing to "host" but with the current netcode (we don't have 1.1 yet) it most definately helps connection issues with all clients. In my lab-testing I have concluded that if everyone (host and clients) has their network configured according to my guide (most clients don't
Usually when a PC spontaneously reboots it's a powersupply, heat issue or flaky hardware. Sounds to me like as a game goes on (and more and more stress is put on your hardware) something isn't getting the power it wants and voila reboot! Or something (ie. Video Card) is overheating and viola reboot. Could also by flaky hardware (ie. RAM) that isn't used most of the time, but in a longer game.... Some things to check out.
Could be your ISP is doing P2P-traffic filtering/shaping? Although, asking them if they're doing it may or may not yield an answer. I'm sure as you've stated you did everything in my guide that you have in fact disabled any hardware firewall on your router (SPI) while gaming in SINS?
[quote]I have a router that doesn't seem to have NAT controls (NETGEAR WGT642 v3). Is there any way to be able to host through this router? I've already tried forwarding the required ports, but it still doesn't work.[/quote] @ JephirDromulus You need to follow the steps in my guide "Networking and SINS" (linked-to under the GREEN writing in my OP). Everything in my guide is in there for a reason. Go through it step by step. If you've forwarded the ports to the c
The "migrating thing" doesn't work for many people (even some that have their networks properly configured). However if you're looking for info on configuring your network correctly..... Please check my stickied post in the "Technical" forum and look for the link to the "Networking and SINS" guide (not the other one). thanks, the Monk
A "mini-dump" (ie. illegal operation) can happen for any number of reasons, bad latency, bad hardware/software, drivers, etc. Instead of posting YET ANOTHER thread on this topic. You could SEARCH?? MP-related mini-dumps: https://forums.sinsofasolarempire.com/307544 MOD/Hardware/Driver etc. related mini-dumps: check the forums for the various threads. Search before posting people. Some of us who are on here (in a volunteer ca
Read the "stickies" always helps!!! :p Download my guide "Networking and SINS" linked-to from the bottom of the "Technical FAQ". If you can't actually do what I tell you do in that guide (ie. you're not allowed to forward port 6112 to only your PC from the router) then you're out of luck untill patch 1.1. the Monk
*sigh* why I bother replying to the same bloody posts time and again I'll never know.... :( [b]Tumbler,[/b] to quote myself from another thread... "People have no problems with having to teach themselves how to use facebook, torrent anything and everything, rip&burn movies, texting while driving/in-school etc. Some of which require more steps to learn (and for which I myself would need a tutorial..hehe) than forwarding a couple of ports. I have no sympathy if those
@ Per Ole As Hollow Man already pointed out, you should be using the guide "Networking and SINS" [u]not[/u] "Networking for the Gamer" (Networking for the gamer was written with any/all client-server games in mind, SINS is P2P). That's why I wrote a special SINS-only guide. :) Per, look for the link under the GREEN writing at the top of this page! :D That's the guide you'll want to use. thanks, the Monk
SINS is P2P That means that the entire game simulation is run on each client (all players). There will be no "dedicated server" for sins, as the only added role for a the "host" is that he/she SYNC's all of the players together. This is also why the slowest cpu/connection in the mix causes slowdown for everyone. the Monk
@ Sparksalot I "feel" your frustration even from just reading your post. :) So here's my suggestion. Please download, read/follow the steps in my guide "Networking and SINS" ([u]not[/u] Networking for the Gamer...that one is generic) linked-to from the Technical FAQ or my sticky near the top of the technical forum. My guess (from the info in your posts) is that your cable/dsl modem is also functioning as a router so you're in a double-NAT scenario. Check my g
You're welcome. I'm glad I could help! :D the Monk
Please download, read and follow the steps in my guide: http://kiclan.com/monk/networking_and_sins_by_the_monk.pdf Follow the steps (don't skip pages/steps) and you'll be fine. :) If you do have problems implementing the steps I'll get you onto my TS Server to talk you through the steps. the Monk PS. You know, all of this is covered in the "stickies" at the top of the forum you posted under...... :NOTSURE:
@ Earthpigg Not to take this thread too far "off-topic" but..... Think of the massive number unit/econ etc. updates that would need to flow to/from each client to the host and back if SINS had been made client-server. Now try to imagine how much network bandwidth that would consume for only [b]one[/b] 10-player game. As far as your "car analogy"...hehe Let me add this.... Try driving a car without first knowing which is the gas or brake pedal, how fast
Yes I have been a victim of "impersonation" several times now on ICO (by "Minidump" and several others). The unfortunate part is that the "impersonators" know what I do/have done for this community and are deliberately trying to sabatoge the work/time I've invested. These individuals spam the chat with demoralizing comments about people's intelligence (using my name) when hosting/network-related questions pop up and are in general highly offensive to [u]anyone[/u] watching the lobby
1. As has been stated several times :) patch 1.1 will give us "optional" (hopefully it stays optional) tunneling netcode which should eliminate the need to forward ports on routers etc. 2. One cannot compare client-server games to peer-to-peer games. There are many inherent differences in the network transport model alone (SINS doesn't have a "server" per say, [u]all[/u] players run the etire game sim on their own machines, the "host" just sync's all of the clients together) wh
@ Megavolt It has been stated several times on these forums now, that patch 1.1 will give us "optional" tunneling netcode for SINS. I guess 10-page guides aren't the only thing you don't like to read? ;p *tongue in cheek* the Monk
[quote]Monk, I've read your networking HW guides, etc. definitely good stuff. I have no clue what could be causing the minidumps on our end and they have exclusively occurred in multi. Obviously it's driving us nuts. So you have tested multi on all of those platforms? It seems that the likelihood of a dump increases for us as we play for in excess of an hour or so and there are more variables to track in-game is about the only correlation I have found. Annatar, thanks for the link I'll go hit th
Since you already feel that my advice to the community should be disregarded... [b]Quote from sc456a:[/b] [quote]I would advise anyone not to follow Monk's guide. It actually advises you to open ports, then disable your firewall. Sheer madness. Why anyone would recommend turning off your firewall and state that "all" consumer level firewalls are "marketing crap" is beyond me. Advising anyone to use Windows Firewall is also a sin of the gravest nature to anyone in the industry. Furth
[b] Sorry for the double-post, the forum dumped on me when I wanted to add something[/b] [quote]I would advise anyone not to follow Monk's guide. It actually advises you to open ports, then disable your firewall. Sheer madness. Why anyone would recommend turning off your firewall and state that "all" consumer level firewalls are "marketing crap" is beyond me. Advising anyone to use Windows Firewall is also a sin of the gravest nature to anyone in the industry. Further, UPnP has not
[quote]I would advise anyone not to follow Monk's guide. It actually advises you to open ports, then disable your firewall. Sheer madness. Why anyone would recommend turning off your firewall and state that "all" consumer level firewalls are "marketing crap" is beyond me. Advising anyone to use Windows Firewall is also a sin of the gravest nature to anyone in the industry. Further, UPnP has nothing to do with Sins and in no way affects it, therefore disabling it will serve no purpose. Wow - I ca
Sounds like a network latency issue to me. Have you tried a pingtest to your local ISP's gateway? On the "laggy days" try the following From the command-prompt: ping -t xxx.xxx.xxx.xxx > pingtest.txt Let that run for a few minutes, then Ctrl-C (break the run) and find the pingtest.txt. If there are many ping values that are above 20-30ms I'd suggest sending a copy of the pingte
Well, since you're posting your hardware configs I guess it's open season! ;p In my "lab" here are the various configs of several machines I've tested SINS on (since those "mini-dump" threads started rearing their heads) in order to try to replicate some of the issues the community has been reporting... [b]Monk-tested configs:[/b] Two of the following: Intel 805D (OC'd to 3.32GHz) 2GB 667MHz RAM nVidia 8800 GTS 320MB (no OC) Win XP Pro x64