jaltuve

Ok, this is interesting.. I will take a look. But, let me see if I understood you correctly. Can I run an instance of wideclient on a machine that is running FS2004 already just by using a different Class name? Oh that I know ;) thats the way I use it for my current setup. But remember that what I'm trying to do here is a bit more complicated. I'm trying to make a SECOND computer running FS2004 send commands over another computer running FS2004 too. SO, WHat I basically want is that a user running FS2004 on computer #2 can press the letter H and on the computer #1 that is also running FS2004 you can see the effect of H being pressed remotely. Now, if H is assigned for PPT I can have a remote user activate PPT and have BOTH pilots share a single SB3 connection when using FSNet for cockpit sharing.

Thanks for the prompt response! Pete, An unrelated question to the problem.. but I don't want to open a new thread ;) I use a software called FSNet to share the cockpit with friends over the internet. My friends DO have FSUIPC and WideFS. I was wondering if it would be possible to have MULTIPLE WideFS Servers send keystrokes to a single Wideclient using the SendKey facility of WideFS even when there is no session established between the WideClient and WideFS machine. In the wideclient everything works PERFECTLY fine *IF* the WideFS computer doing the keysend is the one in the wideclient.ini ServerName= parameter. My impression, was that WideFS would do a SendKey to ANY wideclient machine, but I guess this is a security concern so thats why the feature is not there... Do you know what my options are to have a FS2004 machine send (over the network) a command to a wideclient machine when there is no session established between them? I just want my friends to be able to PPT the squawkbox running on the Wideclient machine so we BOTH can talk to ATC while in VATSIM. Sorry If All this is confusing... but i'm pretty sure you know exactly what I'm talking about :)

More on this subject: ServerIPAddr is either deprecated and not stated in the manual -OR- simply a bug if I use ServerName everything works perfectly fine. TIP: you CAN use an IP Address in ServerName instead of a server name

Fixed my problem Pete. But the manual is incorrect. ProtocolPreferred does NOT automatically sets the client for Wideclient when not specificed. At least not for UDP. I fixed the problem by modifying the wideclient.ini file adding protocol=UDP (even though protocolpreferred=udp is set on wideserver.ini)

Hi! I've been using WideFS for a long time, I'm very familiar with it, with FSUIPC configuration in general and yes, I do read the manuals :) I never had any problems of any kind connecting Wideclient with WideFS until today, I saw there was a new version of WideFS and decided to upgrade. (I had the version released in december and upgraded with the one released June 27) The only thing i did was: Replace WideServer.dll in my modules folder in fs9 in the server machine, and replace wideclient.exe in the client machine. Now, it does not work. If I check the log there is a message (in the client) that says: Trying to locate server: Protocol not yet decided I never had this message in the previous version of WideFS, why I'm getting this now? I tried adding the ProtocolPreferred in the Server ini file to see if this was the problem and nothing... I don't get it, i've spent more than two hours fixing this problem... WHY a simple upgrade is causing a problem??