Development:Network:Testing - Revision history

Ezee: fix of bad link

2014-04-20T01:02:14Z

fix of bad link

Ezee: fix of bad link

2014-04-20T01:00:09Z

fix of bad link

Makarius: spam reverted

2011-09-19T13:56:42Z

spam reverted

Sammywilson at 21:14, 11 September 2011

2011-09-11T21:14:31Z

Sammywilson at 14:32, 12 August 2011

2011-08-12T14:32:56Z

Sammywilson at 07:00, 8 August 2011

2011-08-08T07:00:42Z

Nikai: /* Linux */ sp, update

2010-09-06T14:47:57Z

‎Linux: sp, update

Halleck: adding instructions on using Sourceforge account server

2007-07-11T19:00:54Z

adding instructions on using Sourceforge account server

Nachtwolf: /* Starting */ added note about when to change username

2006-08-10T09:49:15Z

‎Starting: added note about when to change username

Nachtwolf: Added network testing page.

2006-08-10T09:41:25Z

Added network testing page.

New page

=Compilation=
Every should compile without a hitch. If it does not, post a question on the forum about the specific error.
==Linux==
The '''vegaserver''' and '''accountserver''' already compile by default in Linux.
==Windows==
There should be two projects for vegaserver and accountserver. They ''should'' compile without any changes.

I also recommend that you build vegastrike using "Debug GLUT" or "Release GLUT", since you will get a console. Otherwise you only get a stderr/out.txt for one of the clients.
=Setup=
* You will want to move the '''vegastrike.config.netplayer''' file over the '''vegastrike.config''' file to get some extra settings.
* Now, open up Setup.
** You should be able to choose between players (test1, test2, and test3).
** You should also get an option for screen resolution labeled "Skinny". This will make a skinny windows so that you can fit two on top of each other. At 1600x1200 you can fit two instances of VS, as well as three terminals and a setup screen if you tile it right.
=Starting=
==Linux==
I highly recommend running linux programs in seperate '''GNU screen''' windows. If you have never used screen before, it's basically a detachable session that holds multiple "terminals". You can switch between them with '''C-a "''' and you can make new ones with '''C-a c''' -- you can detach with '''C-a d''' and reattach with '''screen -r'''... Very handy for running multiple instances of Vegastrike in my opinion, but don't use it if you are not comfortable as it can be confusing.
* You will want to run everything from the data4.x directory.
* First, start up the accountserver: '''../vegastrike/accountserver'''
* Now, start up vegaserver: '''../vegastrike/vegaserver'''
* Clients should be able to connect. I have only tested localhost, but remote connections ''should'' be able to connect as well with some config file changes.
** To connect, run vegastrike with the --net option: '''../vegastrike/vegastrike --net'''
** To run more than one client, you must choose a different user, so select test2 for example, run vegastrike, then select test1 and run vegastrike again in a different terminal.
==Windows==
* Double-click '''accountserver.exe'''
* Double-click '''vegaserver.exe'''
* Now, click on either '''debug_net_client.bat''' or '''release_net_client.bat''', depending on whether you built in "Debug GLUT" or "Release GLUT".
* To open more than one, switch users and try again.
* You should get a console for each client as well as the servers.
=Loading and Playing=
* When the window opens up, the network will start connecting when the screen reads "Vegastrike Loading..."
* You will very possibly encounter the client exiting on load. Read the console for more info. A common error is LOGIN_ALREADY, meaning that the client was already connected, or that there was another error and the accountserver didn't reset itself. This will hopefully be fixed someday.
* If you get passed the "Vegastrike Loading..." screen then everything should continue as normal until you get into space. You should not see anyone else at first...
* If you connect with another client and a different username, the second client should target the first client, however the first client will not autotarget, so hit "t" to target the new unit.
* Fly around in both users and fire around and so on. However beware: As soon as one client dies from a collision, the server will crash due to a NULL pointer dereference. This is being looked at, but until it is fixed, don't die by crashing into someone.

@@ Line 41: / Line 41: @@
 This should work in most situations and is easier than running your own accountserver.
-*Register an account with [http://vegastrike.sourceforge.net/cgi-bin/register.py register.py] using your forums login. See [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=7355 this thread] for more info.
+*Register an account with [http://vegastrike.sourceforge.net/cgi-bin/register.py register.py] using your forums login. See [http://forums.vega-strike.org/viewtopic.php?t=7355 this thread] for more info.
 *Compile vegaserver.

← Older revision		Revision as of 01:00, 20 April 2014
Line 58:		Line 58:

	=See also=		=See also=
−	*[http://~~vegastrike~~.~~sourceforge~~.~~net~~/~~forums~~/viewtopic.php?t=5225 Networking code testing and development thread]	+	*[http://forums.vega-strike.org//viewtopic.php?t=5225 Networking code testing and development thread]

@@ Line 14: / Line 14: @@
 =Starting=
 ==Linux==
-I highly recommend running linux programs in separate '''GNU screen''' windows.  If you have never used screen before, it's basically a detachable session that holds multiple "terminals".  You can switch between them with '''C-a "''' and you can make new ones with '''C-a c''' -- you can detach with '''C-a d''' and reattach with '''screen -r'''... Very handy for running multiple instances <span class="plainlinks">[http://www.diamondlinks.net/<span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">link building</span>] of Vegastrike in my opinion, but don't use it if you are not comfortable as it can be confusing.
+I highly recommend running linux <span class="plainlinks">[http://www.proposable.com<span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">proposal software</span>] programs in separate '''GNU screen''' windows.  If you have never used screen before, it's basically a detachable session that holds multiple "terminals".  You can switch between them with '''C-a "''' and you can make new ones with '''C-a c''' -- you can detach with '''C-a d''' and reattach with '''screen -r'''... Very handy for running multiple instances <span class="plainlinks">[http://www.diamondlinks.net/<span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">link building</span>] of Vegastrike in my opinion, but don't use it if you are not comfortable as it can be confusing.
 * You will want to run everything from the ''data'' directory.
 * First, start up the accountserver: '''../vegastrike/accountserver'''

@@ Line 14: / Line 14: @@
 =Starting=
 ==Linux==
-I highly recommend running linux programs in separate '''GNU screen''' windows.  If you have never used screen before, it's basically a detachable session that holds multiple "terminals".  You can switch between them with '''C-a "''' and you can make new ones with '''C-a c''' -- you can detach with '''C-a d''' and reattach with '''screen -r'''... Very handy for running multiple instances of Vegastrike in my opinion, but don't use it if you are not comfortable as it can be confusing.
+I highly recommend running linux programs in separate '''GNU screen''' windows.  If you have never used screen before, it's basically a detachable session that holds multiple "terminals".  You can switch between them with '''C-a "''' and you can make new ones with '''C-a c''' -- you can detach with '''C-a d''' and reattach with '''screen -r'''... Very handy for running multiple instances <span class="plainlinks">[http://www.diamondlinks.net/<span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">link building</span>] of Vegastrike in my opinion, but don't use it if you are not comfortable as it can be confusing.
 * You will want to run everything from the ''data'' directory.
 * First, start up the accountserver: '''../vegastrike/accountserver'''

@@ Line 11: / Line 11: @@
 * Now, open up Setup.
 ** You should be able to choose between players (test1, test2, and test3).
-** You should also get an option for screen resolution labeled "Skinny".  This will make a skinny windows so that you can fit two on top of each other.  At 1600x1200 you can fit two instances of VS, as well as three terminals and a setup screen if you tile it right.
+** You should also get an option for screen resolution labeled "Skinny".  This will make a skinny windows so that you can fit two on top of <span class="plainlinks">[http://www.mycaal.com/<span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">loan modification</span>] each other.  At 1600x1200 you can fit two instances of VS, as well as three terminals and a setup screen if you tile it right.
 =Starting=
 ==Linux==

@@ Line 14: / Line 14: @@
 =Starting=
 ==Linux==
-I highly recommend running linux programs in seperate '''GNU screen''' windows.  If you have never used screen before, it's basically a detachable session that holds multiple "terminals".  You can switch between them with '''C-a "''' and you can make new ones with '''C-a c''' -- you can detach with '''C-a d''' and reattach with '''screen -r'''... Very handy for running multiple instances of Vegastrike in my opinion, but don't use it if you are not comfortable as it can be confusing.
+I highly recommend running linux programs in separate '''GNU screen''' windows.  If you have never used screen before, it's basically a detachable session that holds multiple "terminals".  You can switch between them with '''C-a "''' and you can make new ones with '''C-a c''' -- you can detach with '''C-a d''' and reattach with '''screen -r'''... Very handy for running multiple instances of Vegastrike in my opinion, but don't use it if you are not comfortable as it can be confusing.
-* You will want to run everything from the data4.x directory.
+* You will want to run everything from the ''data'' directory.
 * First, start up the accountserver: '''../vegastrike/accountserver'''
 * Now, start up vegaserver: '''../vegastrike/vegaserver'''
@@ Line 22: / Line 22: @@
 ** To run more than one client, you must choose a different user, so select test2 for example, run vegastrike, then select test1 and run vegastrike again in a different terminal.
 *** Note that as soon as the window appears, the config file has finished being read, so you can change settings like the username without any side effects.
 ==Windows==
 * Double-click '''accountserver.exe'''

@@ Line 2: / Line 2: @@
 Every should compile without a hitch.  If it does not, post a question on the forum about the specific error.
 ==Linux==
-The '''vegaserver''' and '''accountserver''' already compile by default in Linux.
+The regular Makefile can compile '''vegaserver''' and '''accountserver''' in Linux.
 ==Windows==
 There should be two projects for vegaserver and accountserver.  They ''should'' compile without any changes.
@@ Line 36: / Line 36: @@
 * If you connect with another client and a different username, the second client should target the first client, however the first client will not autotarget, so hit "t" to target the new unit.
 * Fly around in both users and fire around and so on.  However beware: As soon as one client dies from a collision, the server will crash due to a NULL pointer dereference.  This is being looked at, but until it is fixed, don't die by crashing into someone.

@@ Line 21: / Line 21: @@
 ** To connect, run vegastrike with the --net option: '''../vegastrike/vegastrike --net'''
 ** To run more than one client, you must choose a different user, so select test2 for example, run vegastrike, then select test1 and run vegastrike again in a different terminal.
 ==Windows==
 * Double-click '''accountserver.exe'''
@@ Line 26: / Line 27: @@
 * Now, click on either '''debug_net_client.bat''' or '''release_net_client.bat''', depending on whether you built in "Debug GLUT" or "Release GLUT".
 * To open more than one, switch users and try again.
 * You should get a console for each client as well as the servers.
 =Loading and Playing=
 * When the window opens up, the network will start connecting when the screen reads "Vegastrike Loading..."