|
|
Are you using an existing multi pilot or did you create a new one? What filters did you set? |
|
|
|
fresh install so, new pilot, and I just tried again with a new pilot (though the pilot shouldn't matter for the -standalone problem). No filters either, I just left it as default, Open. |
|
|
|
I don't know if it matters, but I am on a router, though sitting in the DMZ. |
|
|
|
You don't have PXO selected on the multi options screen in-game by any chance do you? Try again with PXO not selected and see if the problem persists. This only happened once for me and then worked fine afterwards. It was something that was passed to cfile that was causing the problem. I'll try and figure out where the problem is located and get it fixed. |
|
|
|
nope, PXO's not selected. /Multidata is. As is TCP (not IPX). Any other settings of interest? Also, I'd been running eMule when trying before. When I kill eMule, instead of crashing to the desktop, the game locks up and I can't alt-tab away or ctrl-alt-delete to task manager, and ACPI power-button shutdown doesn't work (or doesn't succeed... it closed all the processes and sat at a black screen when I let it go for a while). Have to do a hard reset in that case (though if I run it in a window I can get to task manager and kill it). |
|
|
|
With PXO selected I get servers and can connect... First time I got a warning that my pilot had been used with PXO (though he'd never been used)... trying again from scratch. I don't think I got the same message, though this time I was more concerned with getting back into the server I was on before. |
|
|
|
After turning on PXO and having network options work, I am able to go back and forth without issue. However, the game may incorrectly decide that a pilot has been flown on PXO when he's only been flown on FSNetd if he's flown while PXO is turned on. However, I get no server list unless PXO is turned on.
edited on: 09-26-04 14:52 |
|
|
|
This should be fixed now. I'm going to go through my unstable tree just to make sure I'm not missing anything but if this isn't 100% solved in the next build for you dostatochno then please reopen this bug. |
|