teropa

Pete, I read the documentation of the Maddog again, and it seems that the multicrew synch in FSX is supplied by Simconnect exclusively; FSUIPC is not used there for synchronization at all. Do you have any estimate if the position data grabbing and forwarding with FS9+FSUIPC (where FSUIPC takes it from FS9 innards) would be any different from FSX+Simconnect? Basically, if the FSX+Simconnect combination could theoretically be possibly a tad faster than FS9+FSUIPC, assuming that Simconnect gets the position data somehow more directly from FSX, than FSUIPC from FS9. Is this speculation entirely without base, what do you think? Btw, when it comes to smooth operation over the internet, it's not surprising at all. It's just a matter of latency between the computers. If we are talking 5-10ms latencies, you will get absolutely stutterfree synch in all first person shooter games through the network. I would expect an airline flight simulation be completely smooth, unless there are some really rapid changes in attitude, altitude etc. like in fighter flying. rgds, Tero

Pete, I may have posted vaguely, so I'll correct one misunderstanding. We are using FS9 at the moment (both of us), but the MD SW itself is also FSX compatible (there's an own version of it for FSX). What I am after is that if there is something one can do to make the situation better (let's say for FS9 situation, where both are flying on FS9). Interestingly, the MD developers say that in multicrew ops, it is possible for one pilot to use FSX and the other to use FS9. But I really don't want to get into that to keep things as simple as possible (unless... there is something to gain from flying different FS versions). If FSX would bring benefits in this regard (both flying MD on FSX), then we'd be more than happy to switch to it. But from your post I got the impression that actually FS9 could be better synch-wise? I read this one thread here in your forum about the importance of perhaps having the exact same FPS for both sides to minimize any stutters due to the fact that the other pilot is getting a more fluid experience than the other and thus causing the position, altitude, attitude etc. getting more "updates" than the other side, thus causing stutters in the process. Is there any validity in this for this kind of multicrew operation, with regard to stutter-free experience? At the moment we have the same FS version, all the same sceneries, same settings in MD, very similar settings in FS9, and we start out with the same situations and time, and try to have it all in perfect synch. But still there are these intermittent moments in flight when the going gets really rough on the PNF side, and it affects the whole multicrew experience greatly. regards, Tero

Hi, I am flying the Leonardo Maddog 2008 with its multicrew mode, ie. sharing a cockpit with someone. We are doing this in FS9 but it's possible also in FSX, as the SW is available for both. My question is: Are there any differences in the FSUIPC's position/attitude synchronization with regard to accuracy/update interval between different FSUIPC versions? The multicrew flying is great, but the client of the connection (PNF) always sees rather jerky movements, and this is caused by the position/attitude synchronization between the two planes. And the FSUIPC is doing the synchronization between the two pilots, according to the developer. It is obvious that no SW can keep synch in real-time between two different computers through the internet (even with pings as low as 5-8ms between the computers), so there alwas has to be some amount of unsynch between the computers. However, we have noticed that the amount of jerkyness and unsynch in the pos/att varies throughout the flight. At one point the ride could be very smooth in the PNF side ie. client (PF side is always smooth as it's the host). But at times the PNF side experiences heavy jerkyness and twitches without any apparent reason. And then it's suddenly better again. The traffic between the computers is ensured fully open, by making proper port forwards everywhere, disabling firewalls, and testing that it all works. So connectivity is not an issue. So, if anyone (besides Pete of course) has any suggestion for FSUIPC version or some settings that I could change to increase the synch interval or do something else to alleviate this problem that surfaces on each flight, I'd appreciate the info greatly. It's not a show stopper but the overall experience suffers somewhat from this phenomenon. I would also be willing to test out some unofficial FSUIPC modules from Pete, if something could be done inside the DLL to increase the synchronization (decrease the interval between the synchs or something else), smoothing etc. etc., if that should be possible. Thank you for reading. rgds, Tero

Pete, Changing the PollInterval to a lower value (in my case 30) worked!! Perfect. There was no such entry in the ini by default, so I guess the default value is somewhere hard coded ? Or should there have been the "PollInterval=55" there anyway ? Anyhow.. thanks for the help, all systems are go once again! regards Tero

Well Pete, It's a problem that might be related to FSUIPC, so I guess it is related to you. "Hi, Recently I've discovered a problem that I didn't have before. I have programmed four buttons in my CH yoke to send keypresses in FS through FSUIPC: a/t disconnect, a/p disconnect (PIC767), RW push to talk key (scroll lock) and a "throttle cut" parameter to enable reverser functionality in PIC767. The problem. The keypresses experience a serious LAG for some reason. Many times when I press the buttons, nothing happens. Sometimes after a delay, and very rarely immediately as it's supposed to work. This is so weird because I never had this problem before. Some people over at PIC forum have complained about the same thing, and no one knows what to do ? It's seriously annoying when the button -> keypress thing "misses" all the time, especially when using the PTT to talk on RW and when disconnecting the automatics on approach in PIC. Also, I run FS in windowed mode, since I have 3 monitors (and have PIC's different panels undocked in them), that I need to access with the mouse. (could this have effect?) Any help much appreciated!" Tero

Hi, Please check this thread I posted at Avsim about the problem. http://forums.avsim.com/dcboard.php?az=6524&page= Thanks for the help! regards Tero