camaflight

No, I can't see the three mode states as Joy#xx button #8xx, xx and xx". And Pete, please, I allways try for myself, I'm sitting here (alone :o ) and try for myself over and over again, then I saw this post and by jumping into it I hoped I could gather some more info. And thanks, so I did. I will look into the Lua plug-in and Paul's way as the mode states are not visible. I'll never looked into this Lua thing and I don't really know it's capacity, but I will look..and learn... Regards, Carl

Hello Pete, does that mean it should be possible to make the mode selector visible in FSUIPC 3.998q's Buttons & Switches assignments tab? Or maybe I misunderstand what this is..... Regards, Carl

Paul, thanks again. I'll make a forum search although I think I've seen that post allready. I'm afraid that was FSX - FSUIPCX related. I do a search though. I will also take the time to study your solution - sooner or later I have to take the step towards your level ;) Regards, Carl

Hi Paul, thank you so much for responding to my question here. Realizing that I will need some time getting the grasp of your coding I don't want to postpone thanking you until I'll be that far. There are obviously some differences between FSX with FSUIPC 4.xxx and FS9 with FSUIPC 3.xxx. As an example I can't see the mode selector visible in FSUIPC's Buttons & Switches assignments tab from the latest version of FSUIPC. However, as mentioned I will need some time understanding your way of doing it. As you know; the Saitek yoke has a button-wheel allowing you to switch between 3 available modes which again makes it possible to asssign every other buttons for three different purposes depending on the mode in use. This is possible when using the Saitek assignment programming tool. However, I would much more take the FSUIPC fully in use leaving both the Saitek and the FS way "in rest". I'm not quite sure if my additional information here makes any difference regarding your answer. If so I would very much appreciate you giving a signal about that as I'm pretty much a novice when it comes to handle such problems as you are capable of. Best regards, Carl

Hello and Happy New Year, I'm running FS 2004 and wonder if it's possible making different assignments for the same button by changing mode. I also have the Saitek Yoke and throttle quadrants. Regards, Carl

Yes, absolutly all your suggestions have been tried out. Sorry I haven't been quite clear about that I have carried out tests in between. :wink: I will follow your newest suggestions as well. Before that it would be really interesting to know if there actually is some unsolved or perhaps poorly developed network linkage between Vista Home Premium and XP Pro. Another option for me is to upgrade to Windows 7 as I receive my W7 shortly. Then I could consider upgrading my old computer with W7 as well (just have to run a feasible test first). Regards, Carl

No. Ok I looked it up; it was "ProtocolPreferred=" not "PreferredProtocol=". It didn't help I'm afraid. Everything you have suggested I have tried. Unfortunately I have so far no success with my network setup in order to take use of WideFS. Regards, Carl

But, I have done so ! - at both ends - as regards speed/duplex settings; set to 100 Mbps full duplex instead. Please confer: No, of course I haven't been messing with it. The reason I didask was that you told me to try changing the "PreferredProtocol=" from TCP to UDP and I didn,t find that line PreferredProtocol=" in the server ini. So I just wanted check if there was anything wrong with the server ini I have. That's all. Regards, Carl

I'm not finnished with the UDP test yet. So many new variables pop up so I have to slow down a little and take fewer things at a time: Not really, the Wide Client log told 357 sec. I never looked at the log regarding this before, just clocked it myself figuring out it was something between 31/2 to 5 minutes. I think we should consider that as the same. Yes it was ! ---------------------------------------------- Furthermore - from the server log this was the result: Throughput maximum achieved: 2 frames/sec, 172 bytes/sec Throughput average achieved for complete session: 0 frames/sec, 7 bytes/sec Average receive rate from "KONTORET": 0 frames/sec, 8 bytes/sec Last time I had 34 frames Max (FS limited to 31), 7 frames min, 11 frames average. I discovered a new thing: WideClient isn't totally frozen after all. It will be impossible to shut down and it will be impossible to move the WideClient window around at the desktop or restore it when minimized. I discovered this by turning FS off, and then looking at the logs showed that this was registrated as much as it was registrated when I started FS again and once more shut it down. What was impossible though was starting an application - it stated "not connected to FS". The only way to get an application connected for a few minutes again is to reboot the client machine. So, some questions if I may; For the network adapter there is an option to set the Speed & Duplex to even 1.000mbps full duplex on both ends. Would that make any difference you think? When looking in the WideFS technical manual there is a section where some users have made adjustments to exactly the advanced network adapter settings. As I have dual network adapters build into the motherboard this section could absolutly be relevant to me. However, as stated before; this is stuff I don't understand too much from. The properties as regards the advanced settings for the one adapter I have in use are with options respectivly as follows: (present settings in bold) Energy Star -------------------------- Disabled / Enabled Flow Control--------------------------Tx & Rx Enabled / Disabled Interrupt Moderation--------------Disabled / Enabled IPv4 Checksum Offload----------- Disabled / Rx Enabled / Tx & Rx Enabled / Tx Enabled Jumbo Packet-------------------------1514 Bytes / 4088 Bytes / 9014 Bytes Large Send Offload (IPv4)---------Disabled / Enabled Log Status Maessages--------------All Maessages / Errors / None / Status Messages / Warnings Max IRQ per sec----------------------1000......5000........30000 Network Address--------------------Value / Not Present Priority & VLAN----------------------Priority & VLAN Disabled / Priority & VLAN Enabled / Priority Enabled / VLAN Enabled Receive Buffers----------------------256........512 Speed & Duplex----------------------10 Mbps Full Duplex / 10 Mbps Half Duplex / 100 Mbps Full Duplex / 100 Mbps Half Duplex / 1000 Mbps Full Duplex / Auto-Negotiation TCP Checksum Offload (IPv4)---Disabled / Rx Enabled / Tx & Rx Enabled / Tx Enabled Transmit Buffers--------------------256........512 UDP Checksum Offload (IPv4)---Disabled / Rx Enabled / Tx & Rx Enabled / Tx Enabled Wake From Shutdown--------------Off / On Wake-Up Capabilities--------------Link Change / Magic packet / Magic Packet & Pattern Match / None / Pattern Match Do you have any idea what should be done here if anything ? Regards, Carl Oh, I forgot something; Here is a copy of the server ini: [Config] Port=8002 AdvertiseService=1 AutoRestart=0 AutoUpdateTime=13 MaximumBlock=4096 NoStoppedRestarts=Yes Port2=9002 RestartTime=10 SendTimeout=15 TCPcoalesce=No ; ----------------------------------------------- [user] Log=Errors+ ; =============================================== [ClientNames] 1=xxxxxx Is this basically OK. I will test the UDP the next thing. Carl

Hi Pete, seems an effect of putting my question in a new topic bridged the original topic about this issue over here. To add some new info here. I just started WideClient without any client applications - just WideClient connected to FS. After 31/2 to 5 minutes WideClient got frozen. This doesen't indicate anything wrong with what you tell; it just tells that there is no que created because of any client application alone. I try to be a little restrictive with bringing into the discussion things I pick up on the net. Being no capasity on computers I may mix in stuff that's completely way off. Nevertheless, reading through the server log from the the last try running only WideClient I found this: " 2046327 Error 10054: client socket disconnected at Client: removing (skt=10228) TCP" Then searching for error 10054 I found inter alia these links: - http://go.microsoft.com/fwlink?ProdN...4&LinkId=20476 - http://support.microsoft.com/?kbid=919710 - http://support.microsoft.com/?kbid=942861 I have done that and no memory leak is indicated. In fact memory usage is quite low. Okidoki, checking now. Haven't tried that. I'm not experienced with this but I will read, learn and do now. Wow, that gave me an instant feeling of proudness being at the same level as you. Very short moment I'm afraid.......... Regards, Carl

Hi Dave, thanks for responding. I'm not sure were to find the WideFS related info on that site though. Another thing, that I'm frankly not quite sure about, is that Vista Ultimate is probably a total different OS than Vista Home Premium when it comes to networking against a XP machine. But I'm emphasising that this is only an impression I got reading through a huge number of related ( and quasi related) topics on the net. Hope you can give me a lead where to search on the given link. Kind regards, Carl

Hi all, I'm still having problems running applications on the WdeClient macine (the applications loose contact with FS after 31/2 to 5 minutes). I have also great difficulties in finding out if my two OS's really are capabel of running with the WideFS. Hence I wonder: Could those of you who reads this topic please tell if you have managed or not to run WideFS with the same configuration as I do: WideFS-server machine: Vista Home premium 64 Bit WideClient machine: XP Pro 32 Bit I just need to know if you succeeded or not, but of course if you have the time then just briefly tell what you did to achieve this and/or if there were any particular problems that occured during the set up process. Thanks in advance Kind regards, Carl

Ok, I will work on this. I think I also will try my old router as a second router to use between the two machines "only". I had already set upper limit for FPS i FS to 31. You're really a stayer Pete still keeping up with my issue, you know I'm grateful ! Regards, Carl

Hello again, well now things begin to happen. I have reset the network settings back to square one and started all over again and done so several times without any success. Then as repeating the normal settings for share permissions to aapropriate folders, one at a time, Vista suddenly started processing share permissions to all files within respective folders. Until now that hadn't happened ! I have done absolutely nothing else than starting all over again several times doing excact the same settings time after time. After this ASv6.5 started and loaded weather. RC started and worked from my clien computer with sound and everything - until ASV6.5 broke down with a frozen WideClient after a couple of minutes. I then looked at the server ini and everything seemed to work very nice in the beginning, giving 34 frames at maximum, but of course 0 at the end. However, I noticed one more thing in the ini as follows: ********* WideServer.DLL Log [version 6.78] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 03/11/09, Time 10:18:40.300: Server name is xxxxxx 95628 Initialising TCP/IP server 95628 Initialising IPX/SPX server 95628 IPX/SPX socket() failed [Error=10044] Socket type not supported 95628 Failed to start IPX/SPX Server 95628 Initialising UDP/IP server 96595 Broadcasting service every 1000 mSecs 98124 Incoming connection Accepted ok (skt=10208) TCP 98358 Connected to computer "KONTORET" running WideClient version 6.787 (skt=10208) TCP 717433 Error 10053: client socket disconnected at Client: removing (skt=10208) TCP What does the error messages in bold, cursive letters mean ? Is this normal messages or does they tell something is wrong with the connection ? Regards, Carl EDIT: I have now run FS Smooth and AI Separation on the WideClient. This worked fine 4-5 minutes and then FS got disconnected and WideFS was frozen. As with the AS and RC WideFS says it's connected, however it's also frozen at the same time FS gets disconnected.

Ok thanks Pete, the more I read about this the more I suspect that I have bought the wrong version of Vista. I asked spesifically about networking capabilities between XP and Vista with the retailer, but obviously not specific enough. If I should manage to set up a acceptable network and permissions for my client applications then I will come back and tell how I did it. There may be some others experience the same problem as I do. Regards, Carl