svenks

"Is that a refuelling probe on the nose of your Concorde?""No, it's carrot that Tom put there!:+ BRGDSSven Sorensen, EKCH

Hi NormanI haven't forgotten this issue, I've just not taken the time to report here. But I have been flying the Concorde quite a bit, in preparation for the RTW event. And I have some further info: I can get it to miss the ALT CAP any time, if I mess with VERT SPD setting close to the ALT CAP altitude. For instance, descending with AP IAS HOLD can bring on a hefty descent rate. As you approach your selected altitude, you might want to slow your descent. So you engage VERT SPD (and A/T at IAS HOLD), which initially has the same descent rate as before. Using the Datum Change you raise the nose, but if you are fairly close to the selected altitude, the 'pitch selector' (for lack of a better word) will simply continue upwards, and you will end up climbing. ALT CAP never occurs and thus ALT hold will not be engaged.BRGDSSven Sorensen, EKCH

Considering my ILS approach difficulties yesterday, that might have been better....At least I'm sure I would have been able to see the smoke from far away!BRGDSSven Sorensen, EKCH

Hi ManfredYes, the P-38 is an all-time winner. It may not be the fastest hen in the coop, but it is solid, forgiven - and good-looking :)Only thing missing is ILS capabilities, but i'm assume there is an add-on for that.BRGDSSven Sorensen, EKCH

BrgdsSven Sorensen, EKCH

Hi all,As you may have seen, over the last couple of days people have begun to report various problems with Bushnet/multiplayer in general. The biggest issue is the inability to join a session. Yesterday evening Gazer75, arrvoo, DarkCharisma, sfoofficer, Jozef and myself joined forces to see if we could identify and hopefully solve the problem. We do have some clues, but unfortunatly, the problem is still there...First, this is not a Bushnet problem. We also had problems on Gazers MP server. Second, it seems to have something to do with peoples setup at home: Router, Firewalls etc (however, there was 1 thing speaking against this! See later).Examples of what happens is: When arrvoo is connected, DarkC and myself can't join. When I'm connected, arrvoo can't join but DarkC can - but only if sfoofficer hasn't joined before him. And sfoofficer had no problem joining when either arvoo or myself had joined first. Gazer had no problems whatsoever, he could join regardless of who and where. There were other variations, but these are the basicsNow, I think that everyone was tinkering with their firewalls, and I believe we all ended up with port forwarding enabled for at least the default port - but we still had the problem.The really strange thing happened when Gazer did something to his MP server: We were all able to join! Alas, not for long: DarkC was kicked off after a couple of minutes. Then we tried the same on Bushnet - and were all able to join! Then the same thing happened: DC got kicked, then I tried to disconnect and rejoin and couldn't! Back to Gazer's MP, but by now we were back to square 1.In conclusion: I still think it has to do with the individual router/firewall settings, however the fact that we were all able to connect at 2 instances points to a router/ISP problem instead.As this is close to being a showstopper for me, I will continue to look into this, and I hope we can set up another session like yesterdays - there are still things that can be tried!And if anyone has any ideas as what to do - let's hear them!Sorry for the length of the post (and for my indiscretion, Gazer!)BRGDSSven Sorensen, EKCH

Menu: Setting, Sound Input/Outpout Setting, Voice Send MethodThen you just need to assign a key - I use F12.BRGDSSven Sorensen, EKCH

Klas could you try to joins MP now?if you have teamspeak, join us at Sven Sorensen, EKCH

Hey KlasYou still there ?Sven Sorensen, EKCH

No, it's more of a backup for now.You got kicked, because you need to enable Push to Talk, otherwise all our conversations gets screwed upBrgdsSven Sorensen, EKCH

Jozef, when you join teamspeak, you got use the Push to Talk option. Otherwise it all goes wrong.BRGDSSven Sorensen, EKCH

arrvoo, Gazer75 suggests that we both try to connect to his multiplayer, Then we can see if there is a problem... :)Sven Sorensen, EKCH

arrvoo, I'm definately not sure this has anything to do with you or your setup.In fact, I can see that other people has connected after you, so this might be a wild goose chase.But it is worth a try to see if there is any difference when you disconnect - but wait until your flight is over! BRGDSSven Sorensen, EKCH

hi arrvoostand by 5Sven Sorensen, EKCH

Hmm, it seems like my theory about one having a less-than-ok setup might be correct. see this (from fshost):QTEWhat is the error "Unable to connect to all players"?This error is displayed by FS2004 when trying to connect to a session. Usually it happens when someone else that's already in the session is using a router and hasn't forwarded the correct ports. When your FS2004 tries to join, it gets a list of all the players currently in the session and tries to connect to them. But when it tries to connect to the player with the bad router, it isn't able to communicate with it, so FS2004 aborts the connection (note that FS2002 would happily connect anyway and just not show that player, but FS2004 now uses newer DirectX functions that return an error in this case, so FS2004 actually isn't able to connect this way anymore). Unfortunately there's not an easy way of figuring out which player is causing the problem, but if you ask everyone if they're using a router, and one of them says they are, and doesn't know about port forwarding, it's a good chance it's him UNQTESven Sorensen, EKCH

Hi JozefTrue, and I think we both have connected first. I think the problem occurs once they guy with the bad setup connects - then everybody else might have problems.I also use a router with a firewall. But that is a 'Stateful Packet Inspection' firewall, which means (among other things), that it know that I started the connection, hence it allows other ports to be open to the same connection (simplified, I know).BRGDSSven Sorensen, EKCH

arrvoo, the only reason I'm adressing this to you, is that you are the only one I haven't flown with. Also, When I first logged on, only you and Jeroen were there (with Jeroen logged on first), so it might be one of you inadvertenly causing the problem.Anyway I found some more info. If the following applies to you, you need do something to your router.QTEWhat is the error "Unable to connect to all players"?This error is displayed by FS2004 when trying to connect to a session. Usually it happens when someone else that's already in the session is using a router and hasn't forwarded the correct ports. When your FS2004 tries to join, it gets a list of all the players currently in the session and tries to connect to them. But when it tries to connect to the player with the bad router, it isn't able to communicate with it, so FS2004 aborts the connection (note that FS2002 would happily connect anyway and just not show that player, but FS2004 now uses newer DirectX functions that return an error in this case, so FS2004 actually isn't able to connect this way anymore). Unfortunately there's not an easy way of figuring out which player is causing the problem, but if you ask everyone if they're using a router, and one of them says they are, and doesn't know about port forwarding, it's a good chance it's him :-)UNQTEBRGDSSven Sorensen, EKCH

This is really annoying!!Sven Sorensen, EKCH

Yes I tried that - it hung up my PC, something that *VERY* seldom happens.Sven Sorensen, EKCH

Klas I see you on and off.Jozef, you seem to have no problems?Sven Sorensen, EKCH

well, you were there for a minute!Sven Sorensen, EKCH

arrvoo, I'm looking into the Bushnet connect problem. Only you and Jeroen are on at the moment. Any chance of getting you to disconnect, and report here when done?Otherwise, what time is your ETA - then we can try it when the Baton is free (whoever is carrying it)Any chance of you getting on teamspeak?BRGDSSven Sorensen, EKCH

OK, time is 1900 UTC, and I can't get on! Only Jeroen and arrvoo is on.If my theory holds, it's either arrvoo or Jeroen keeping me out. Now, I've flown with Jeroen both connecting before and after him, so maybe I should se what happen if I could get arrvoo to disconnect.Unfortunately, neither of them is on teamspeak...Have any of you been able to connect?BRGDSSven Sorensen, EKCH

Hmm, I get a nasty suspicion:What if it is particular user's setting causing this? Like, when I try to connect, FSHOST must notify all clients of this. If one guy's firewall setting (or other settings) prevents this, I can't join as long as he is active - and neither can anyone else!!!Guess we need to troubleshoot this. I'll connct around 1900z tonight, and see what I can see. Then we can discuss this on Teamspeak or the forum.BrgdsSven Sorensen, EKCH

Hi ManolitoGuess the thing with EGLL is that we have flight plans for that route. Also, we know we can make on a full fuel load :)Mano, a thing about your posts: When you grab the Baton, please reply to the first post in the thread, not the last. Then, when you free it, reply to your own 'grab' post. This makes it much easier to see where the baton are by just looking at the headers.Thanks, and see you in the race!Sven Sorensen, EKCH