[BlackDove]

That's because it doesn't work, and you should never try it, because you lag the game for everyone else, and everyone else can see your name ingame.

They usually use the "f" word in conjunction with your name when they see you trying to join a running game too.

[Cobra]

this is why FS2NetD's servers need a major upgrade... inquisitor even told me that...

[Inquisitor]

This has nothing to do with the hardware needing upgraded

Sounds like WM might have busted something

[Taristin]

's why I only use 20040103 for multi.

[BlackDove]

Originally posted by Cobra
this is why FS2NetD's servers need a major upgrade... inquisitor even told me that...

The only thing that needs an upgrade are morons that are trying to join my game while it's doing anything but "forming".

[WMCoolmon]

They shouldn't be able to. The change to allow/disallow ingame joining is a simple change of which packet the server sends to the client.

Here's the line that I changed, looks ok to me:

Code: [Select]

// check to make sure we are otherwise in a state to accept
if((Netgame.game_state != NETGAME_STATE_FORMING && !Cmdline_ingamejoin)
|| (Netgame.game_state != NETGAME_STATE_IN_MISSION || Netgame.game_state != NETGAME_STATE_FORMING)){
return JOIN_DENY_JR_STATE;
}

Maybe the build you're using isn't new enough and doesn't have the ingame join flag? (If it has the flag, it's disabled by default; otherwise, it's enabled)

[Taristin]

They seem to be joining as an observer.

[Kie99]

Let me clarify.

We tried turning ingame joining on (as a last resort) for a few minutes after trying IP Games which failed to work.

We didn't try joining as observers.

[tom]

"You cannot join because the game is not in an appropriate state"

Regarding the OEB this message appears when trying to join a game which is not in "forming" state. In that case the game host uses the OEB and it doesn't matter which build the client uses.
Thus it is no OEB bug, but a regular mechanism.

Joining in "forming" state works without any problems, because there are no code changes in months.
Just to clarify it, "forming" is the only valid joining state for OEB hosts.

Don't know if this helps anyway...

[WMCoolmon]

Originally posted by tom
"You cannot join because the game is not in an appropriate state"

Regarding the OEB this message appears when trying to join a game which is not in "forming" state. In that case the game host uses the OEB and it doesn't matter which build the client uses.
Thus it is no OEB bug, but a regular mechanism.

Joining in "forming" state works without any problems, because there are no code changes in months.
Just to clarify it, "forming" is the only valid joining state for OEB hosts.

Don't know if this helps anyway...

The decision as to whether or not a game is in the appropriate states to join rests solely in the server, AFAIK. "Forming" should be the only valid state, the ingame code simply doesn't work right for the most part. When Kazan and I were fooling around with it, people would generally get sync errors (IIRC) randomly.

[Kie99]

It works in retail and Tom's Old Build.

[Cobra]

...how the hell can normal retail work for FS2NetD? I thought the OEB and SCP could use it.

[WMCoolmon]

IP games.

[Cobra]

bah. (as usual )

*tries to sound intelligent and fails*

[karajorma]

Originally posted by kietotheworld
It works in retail and Tom's Old Build.

Although we did have a problem getting my computer to see your game for some reason didn't we.

On top of that there was another bug where I'd join the game but remain in the lobby while Kie could see my pilot on his list.

No idea what was causing that one.

We'll try OEB as a FS2NetD game later.