View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001064 | FSSCP | multiplayer | public | 2006-09-23 13:09 | 2006-11-01 04:20 |
| Reporter | martellato | Assigned To | taylor | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Platform | PC | OS | Windows XP Professional | OS Version | SP2 |
| Product Version | 3.6.9 | ||||
| Summary | 0001064: -gamename parameter doesn't work | ||||
| Description | When running with -standalone -gamename mygame, the standalone UI still initiallizes the game name to "Standalone Server". | ||||
| Steps To Reproduce | Using 3.6.9 RC7 with no mods, run fs2_open_3_6_9.exe -standalone -gamename mygame | ||||
| Additional Information | * System: Windows XP SP2 Graphics: nVidia GeForce FX 5200 | ||||
| Tags | No tags attached. | ||||
|
|
I don't think that it ever did this, did it? From the code it doesn't look like it was ever supposed to do this. |
|
|
Perhaps you're right. Today was the first time I took a look at the fs2_open source, so I wasn't able to figure it out just yet. I guess I was led to this impression from whoever added this to the Wiki: http://www.hard-light.net/wiki/index.php/Command-Line_Reference#-gamename By the way, would you be able to shed any light on the multiplayer command-line args that are listed without descriptions here? http://www.hard-light.net/wiki/index.php/Command-Line_Reference#Multiplayer Thanks man. |
|
|
-gamename (plus all of the other multi cmdline options) is something from retail, so we don't really mess with it to avoid any compatibility issues. None of othe options are specific to the standalone server, some don't even apply to it at all. Some have to be used in combination with others (which might be the case here with -gamename not doing anything) -password, -allowabove, -allowbelow, -closed and -restricted apply to both standalone and normal modes. They do the same thing as the options that you set when you manually create a game/host in multiplayer. The primary use for these, is when used with the -startgame option which jumps directly to a multiplayer game automatically using the last used multi pilot (ie, it basically skips the pilot select and mainhall screens). -gamename goes with these parameters, as you would typically use -startgame plus any of the other options to setup your multi mission. Like -port, -connect defines the connection parameters to use. This will be the port number (with -port) and the address to connect with (for -connect). -connect would mainly be for direct IP games rather than FS2NetD stuff. I don't think that -oldfire and -clientdamage actually do anything. I beleive that they were debugging items used by Volition for network testing, but all of the code to actually make use of either option is commented out. -timeout sets the timeout for client connects, to determine when to drop them due to inactivity. It is specified in seconds, the default value being 30. All timeouts are logged to multi.log, so you would always know if that was your problem with clients who keep getting dropped unexpectedly. |
|
|
This is really helpful - I'll add this stuff to the Wiki. Thanks!!! |
|
|
Hi Taylor, I was just adding some info about these command args to the Wiki, and came up with a few possible issues. None of these are very critical, if indeed they are bugs. I'm writing this rather late at night, so if it doesn't make sense, kindly ask me to rephrase with my head on straight. Here's what I found… -startgame When I have this on, I still have to select the pilot, but afterwards it jumps me straight to a game created with whatever parameters I’ve specified. -closed I was expecting that the "Close" button in-game would be highlighted when I started up with the following options, but it wasn't: -startgame -closed -connect -connect doesn’t seem to work as expected. If I run the game (gamma build) with parameters: -connect 123.123.123.123 –port 7809 Then my software firewall will tell me that FreeeSpace is trying to connect to 89.136.12.174:7808. 89.136.12.174 is the only ip listed in my data\Tcp.cfg file The same thing happens when I simply call -connect -port Definitely modifies the default port as a host for either standalone or in-game hosting. However, I couldn't get this to change the port when used in conjunction with -connect -timeout Calling -timeout 3 –connect did not seem to shorten the timeout period to connect to a tcp/ip host Calling -timeout 3 did not seem to shorten the timeout period to connect to FS2NetD either (I tried this once with –connect, and once with PXO pre-checked in-game) |
|
|
Regarding the last bugnote I added... I had meant to mention that all of my tests regarding the various multi arguments in that bugnote were done with the gamma build. |
|
|
This is getting a bit off-topic. You can start a thread in the HLP forums if you want to continue the cmdline option discussion (that would probably be more helpful for everyone else anyway). I will correct one thing though, I messed up on my description of -connect. It doesn't get used with -port, the port is specified as part of -connect. So you would have -connect 123.123.123.123:7809 to set your target IP and port number. If -connect doesn't work in general then open a new bug on that and I'll take a look. Closered, Not-A-Bug. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2006-09-23 13:09 | martellato | New Issue | |
| 2006-09-23 13:40 | taylor | Note Added: 0006687 | |
| 2006-09-24 04:29 | martellato | Note Added: 0006693 | |
| 2006-09-24 07:48 | taylor | Note Added: 0006695 | |
| 2006-09-24 11:51 | martellato | Note Added: 0006698 | |
| 2006-09-25 05:37 | martellato | Note Added: 0006719 | |
| 2006-09-25 05:48 | martellato | Note Added: 0006720 | |
| 2006-10-01 20:12 | taylor | Status | assigned => closed |
| 2006-10-01 20:12 | taylor | Note Added: 0006770 | |
| 2006-11-01 04:20 | taylor | Resolution | open => no change required |
