Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: BlackDove on September 15, 2004, 07:04:45 am
-
This is for multiplayer..
Like in FS1, are you people able to code in the "join while in flight" game mode? That owned in FS1, and they never managed to implement that into FS2 for some reason.
Joining a game that's in briefing or while it's in game.... that'd own.
Don't know if it has been asked before, but some input would be great.
-
I seem to remember this being discussed before. I can't remember where the discussion went though.
-
Well... actually someone alredy took that part of code |V| done and enabled it which causes about this...
1. If the person click to join as observer he'll get to screen like right before start mission and will be able to type message to ppl in game, but wont be able to see anything from inside or see messages from in game pilots.
2. If the person clicks normal join the funny part starts... The poor vicim will completly crash imediatly, if he's lucky he'll get just few error messages if he isn't lucky his PC will completly crush and burn (restart). For ppl in game real fun starts as well... splat of that guy causes typical huge lag spike which can be ok on good hosts, otherwise will lead to chain-reaction of other clients splatting (possibly crushing and burning) which can even cause hosts PC to crash and burn (restart).
...something tells me that |V| knew why it was disabled. :D
Anyway please could you turn that off again by default? If you want to fix that code please could you put it on custom flag for good hosts only? There is nothing worse than if you can host 2 clients max and right before end of mission someone joins and causes all clients alredy in game to lag-out splat...
P.S. Only way how to defend yourself from in-game joining right now is to host with password, even if the person knows pass it won't let him in.
-
Anyone who runs a passworded game on FS2NetD needs to be whacked by the almighty trout.
-
There are hosts who have to choose between password game and no game at all... What would you pick? Belive me it's not fun if you can't finish a single missiong in 3 hours because someone joining always crush your game... just my 2 cents.
But that might likely change with new Tom's build i hope... but what do i know i can't host at all...
-
Boo :wtf:
-
i might add if u join ingame and still in while host jumps
u get kicked+autoban and then u get whined or flamed cuz of it
like u woulda done it deliberately....
-
Originally posted by Lightspeed
Anyone who runs a passworded game on FS2NetD needs to be whacked by the almighty trout.
*preps the trout*
someone.. like cetanu has been running nothing but passworded games
-
...so is it possible to somehow code what I've asked in my first post?
-
Originally posted by karajorma
I seem to remember this being discussed before. I can't remember where the discussion went though.
If it has been discussed before, there is a reason why it wasn't implemented. I guess there was something that is (extremely) difficult to code.
-
i might add again as i did mention this in the other topic about ingame join.
if that ingame join will be installed as workin,ingame boot would be nice also.
<< not got smaked with nice soft trout for while..
usually BD and company smaks with everything else thats damn hard :P
-
We all want to fix ingame-join; we just have to figure out how to do it. It was disabled in FS2, and what's there is a half-implemented version. We just need to figure out which half we need to fix. ;)
-
Source code for FS1 hasn't been released, huh? :wtf:
-
fs2 source = fs1 source + changes
they didn't make a nice comment "//this right here is why ingame join doesn't work"
-
To be honest, i don't see why |V| has not released the FS1 code. Maybe just maybe they'll give it to us if one of the SCP guys explains to them politely the current issue and what code we need to fix it.
Unless there is some huge reason why they CAN'T release it that I'm not aware of...
-
they _HAVE_ released the fs1 code, the fs2 code _IS_ the fs1 code
-
...
Oh...
-
Originally posted by Kazan
fs2 source = fs1 source + changes
they didn't make a nice comment "//this right here is why ingame join doesn't work"
-
Got also a good idea...what about fixing all the bugs the build has instead of putting in new stuff?
-
Originally posted by gevatter Lars
Got also a good idea...what about fixing all the bugs the build has instead of putting in new stuff?
You have no idea what you're talking about.
The exact reason all the current builds crash like madness is since none of the new features were properly implemented and integrated into the main CVS build.
Ever tried or used 3.6 for an extended time - it is the most stabile build sine 3.5.5 and the most stabile since HTL was implemented.
What we need is the new features to be properly integrated, so coders can go bugsquashing wiht real fine stuff under their fingers instead munching over the same stuff once more.
I know there may be some bugs still left in 3.6, but to tell the truth there is one thing that CAN make them go away - use Mantis (some coder pls. correct me I guess it is outdated) and report what's wrong with it.
If FS_SCP is unstable use an actual release build, not a CVS or a feature test build (of which Bob built a thousand ones since he made a dozen new features :D ) - so I suggest use 3.6.
-
Originally posted by Kazan
*preps the trout*
someone.. like cetanu has been running nothing but passworded games
looks like I have to argue all the time why I am forced to use passworded games...
- I can safely host 1 client, 2 in some missions, 3 experimental - the chance to crash my computer is very high if I break this rule
- 2-5 squad mates are usually around - I can't even host for all of them
- the password is known by most former PXO players - even more people that I can't host for
so tell me:
why should I drop the password?
to allow even more players enter my game so we can say "hi & bye" and if they don't leave themselves I have to kick them out?
what's that good for?
a hint if you want more FFA games: host yourself if your computer and internet connection allow it! mine don't
thanks a lot and keep your trout
-
recommendations: don't take flippiant tones with Bastard Operators from Hell
-
should I feel threatend now? or are we still dealing jokes since someone started it with a trout? did you read my reasons for passworded games or just the last line which was a reply?
anyway, the more I think about it, the less I really care - the general hostility against former PXO players in this forum makes me sick and tired. don't expect another reaction, because I simply stop posting here
-
im just giving you a hard time, chill
-
Cetanu, you've really got to back off. There isn't any hostility to PXO players (well, no more than to anyone asking for features) but a number of you are asking for more from the SCP team in a shorter time expectation than they can fulfill. You're expecting a level of support above and beyond what you can expect from a professional software company. The SCP neither can nor wants to be that. The current multi system is, like all of FSO, still in development. It's open source. You've got to allow for the bugs while the coders are tracking them down, if only to isolate reproducability. I agree that passworded games are all well and good, but if you've got new community members (yes, they do exist) who want to play, then if all that is up is a passworded game then they're going to get annoyed. There simply isn't the level of traffic as there was on PXO. I don't know how many times I've told you to stop being so aggressive in complaints or requests, and to allow the coders some time to deal with things. You're as (if not more) hostile to them than they are to you, unless your sarcasm is getting lost. Use smilies, and don't rub old wounds in public.
EDIT: Looks like the forum is hungry tonight. It ate this post at least twice before I got it up :rolleyes:
-
I think Cetanu is being the level-headed one in this confrontation. Kazan, your attitude is disgraceful, and not at all the public image we're trying to convey. We're trying to accommodate people, not alienate them.
Multi is just as high a priority for us as anything else; it just depends on what the coders have time to work on. We said we'd try to make a SCP Lite build for you, and now thanks to Tom you're able to run the original codebase on FS2NetD. (We're still working on an official full-featured SCP Lite build with all the latest code in it.) We said we'd fix in-game join, and we will. It may not happen as quickly as you'd like, but it's happening.
-
Done.