View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002731 | FSSCP | Platform-Engine interaction | public | 2012-11-18 16:48 | 2012-11-19 17:17 |
| Reporter | FUBAR-BDHR | Assigned To | Valathil | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| OS | Windows | OS Version | XP and 7 | ||
| Product Version | 3.6.15 | ||||
| Summary | 0002731: PXO disabled in one game disabled in all | ||||
| Description | Basically if you disable PXO for testing on one game (say TBP) and you want to run another game (say a FS2 standalone server) PXO is also disabled there as well. This is due to the flag being stored in the registry and read by all games. This becomes more of an issue because running a standalone with the flag disabled acts like it successfully connects to PXO so you don't know it's not connected unless you check FS2netD. Toss in remote desktop for launching standalones at a remote location and the only way to change it is to actually edit the registry. | ||||
| Steps To Reproduce | Launch a game (FS2 for instance) in normal mode, select multiplayer. Make sure pxo is enabled and a username/password is entered. Go to the lobby to make sure it's working. Exit the game. Repeat for another game (TBP for instance). Before exiting this game disable the PXO flag. Now run the first game again as a standalone. Note that it appears to load and validate the missions. Check FS2netD and note the server is not listed. Shutdown the standalone and run normal. Check the multi setting and you will see the PXO flag is off. Turn it back on, exit, and run as standalone. Server will come up just as before but should now show up on FS2netD. | ||||
| Additional Information | Username (and I believe password) already have the ability to be overrode for a standalone in multi.cfg. Adding that ability for the PXO flag there as well would be a good workaround. | ||||
| Tags | No tags attached. | ||||
|
|
multi_options.patch (522 bytes)
Index: code/network/multi_options.cpp
===================================================================
--- code/network/multi_options.cpp (revision 9354)
+++ code/network/multi_options.cpp (working copy)
@@ -179,6 +179,10 @@
if ( SETTING("+lan_update") ) {
Multi_options_g.std_datarate = OBJ_UPDATE_LAN;
} else
+ // use pxo flag
+ if ( SETTING("+use_pxo") ) {
+ Om_tracker_flag = true;
+ } else
// standalone pxo login user
if ( SETTING("+pxo_login") ) {
NEXT_TOKEN();
|
|
|
I attached a patch that should fix the issue please test. |
|
|
I'll give it a shot when FS2netD is back up. |
|
|
Fix commited to Trunk @ 9360 |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2012-11-18 16:48 | FUBAR-BDHR | New Issue | |
| 2012-11-18 17:22 | Valathil | File Added: multi_options.patch | |
| 2012-11-18 17:24 | Valathil | Note Added: 0014049 | |
| 2012-11-18 17:25 | Valathil | Assigned To | => Valathil |
| 2012-11-18 17:25 | Valathil | Status | new => code review |
| 2012-11-18 17:39 | FUBAR-BDHR | Note Added: 0014051 | |
| 2012-11-19 17:17 | Valathil | Note Added: 0014082 | |
| 2012-11-19 17:17 | Valathil | Status | code review => resolved |
| 2012-11-19 17:17 | Valathil | Resolution | open => fixed |
