Anders Persson

Paul Just wanted to say a BIG THANK YOU for the great client dll you created. It is very good. Thanks a lot! :D

I personally found that the CH control manager is better way to calibrate the Yoke than using the calibration tool in Windows XP. Give it a try. You can always uninstall it if you don't find it good enough. The control manager is found at the CH homepage. But their site i very tricky to use. Things are hard to find (to use an understatement). Here is the link to the control manager: http://www.chproducts.com/retail/tech_cnager.html Good luck!

Now I've done it. I have tested the new fsuipc version (3.559) with WideFS 6.596 Everything went as expected = good! Thanks!

Success! :!: :!: :!: The new WideFS version did the trick! :D I started to try that and was going to test the new Fsuipc version as well but I wanted to do one thing at a time. With the new versions of WideClient and WideServer everything went just perfect. So I did not have to install version 3.559. Maybe you still want me to do that for some reason - please let me know if that's the case. :?: You previous thoughts were probably correct about some quirk and timing difference in the new WideFS version. GREAT job Pete! Thanks for your time and all good work. :D I'm really happy now.

Hmmlooking at what I actually wrote I realize that I'm not very clear. Let me refrase my self: My application is running on a a second computer connected to the FS computer via WideFS 6.510. Case 1 When I'm activating the menu bar (pressing the Alt-key and the menu gets visible) FS becomes frozen. My application on the second PC, however still, reads a zero value. Case 2 If I'm selecting the menu item "Aircraft|Select Aircraft" a dialog (not menu as I incorrectly wrote) is opened up. My application on the second PC reads a non-zero value. Case 3 If I'm selecting the menu item "Aircraft|Fuel and Payload" a dialog is opened up. My application on the secon PC reads a zero value. When I'm running exactly the same application on the FS computer and doing exactly the same activities I get a non-zero value in all the three above cases. FS computer: WinXP Home edition with service pack 2 Second PC: WinXP Professional with service pack 2 Please tell me if I'm not explaining my self well enough. Best regards.[/b]

Hi Pete Now I have done som testing with the offset 3365. I'm running FS9 in full screen mode and I'm having the menu hidden (I have to press the Alt-key to enter the menu) FSUIPC version 3.558 WideFS version 6.510 Now I'm getting a non-zero value from offset 3365 but only if I'm entering the "Select Aircraft" or the "View options ..." menu. The other menus gives me a zero value. However, once in a while when I'm leaving som of these menus I get a non-zero value for a short period. Pressing the Alt-key freezes FS but I still read a zero-value from the 3365 offset.

Just brilliant Pete. I'll test it as soon as I get hold of the new version and I will report back to you. Happy Holidays!

Great Pete, I'm looking forward to whatever the outcome may be.

Thanks for your very, very quick reply - impressive! I'll wait and see.

Hi Pete! I’m writing an application that will run on a second PC connected to FS via WideFS. The software needs to check if FS is “frozen” or not due to menu activity and I found that offset 3365 is exactly what I need. However, I do not get the non-zero values when FS is frozen. Instead I get zeros almost all the time. Once in a while the byte flickers and reads a value of 2 or 3 for a second or two, but it never stays at a non-zero value while FS is frozen. With monitor=3365,1 in the WideClient.ini file I could se that that WideClient receives a value of 3 for a short time (about a second or two). Here is a subset of the WideClient.log file: 110979 Monitored LAN data received: Offset 03365: 00 112151 Monitored LAN data received: Offset 03365: 03 . 112982 Monitored data read by app: Offset 03365: 03 . 113062 Monitored LAN data received: Offset 03365: 00 I also did a test running the application on the FS computer and had no problem at all with the offset. It gave me a non-zero value all the time I was in a menu or a dialog. I am not 100% sure that I’m not doing anything wrong here but since I only get incorrect values when running the application on the second PC connected to FS via WideFS I get the feeling that this might be an issue related to WideFS.

I just wanted to say thank you Pete for all your good work. To me, FSUIPC (and in my case also WideFS) is required to be able to do any serious flightsimming at all. So, Thank you Pete for all your good work

Hi Pete, I am definitely the one to thank you and I'm glad that I could be of at least some help to you. There is no hurry at all with the fix. I sure can wait. Just take your time. Regards Anders :D

Hi again Pete, I have done some further investigations regarding the spoiler axis peculiar behaviour. Here is a step-by-step documentation of what I’m doing. 1. I start of with a calibration of all the axes of my CH FlightSim Yoke USB. 2. Next I’m starting FS and assigning the spoiler axis to one of the Yokes levers I’m also the reversing the order of the axis. 3. Now I take off and while in the air I start to experiment. (Thanks Pete for your hint of not being on the ground – I have never thought of that before.) 4. The first test I’m doing is without having the spoiler axis being “set” by FSUIPC. All signals being bypassed FSUIPC. Now I have almost perfect functionality of the Spoiler. I can deploy it gradually and I can also retract them without any problem. 5. Next step is to enable the calibration functionality of FSUIPC. I press “Set” and set the minimum (-16193) and the maximum (16192) values. I am also closing the FSUIPC interface. 6. I check the FSUIPC.INI file and can recognize the following settings: Spoilers=-16193,16192 7. I return to FS and continue my flight. Now I’m getting the peculiar behaviour of the spoiler. I get some stutters but I manage to deploy it gradually but only “randomly” retract it to the unarmed position. The spoiler is jumping up and down when I’m getting close to the fully retracted position. 8. Again, I’m opening up the “spoiler” page in FSUIPC (page 6 of 8 ). The maximum value is now 512, not 16192 anymore. 9. I’m making a new calibration and I’m setting the maximum value to 16192. 10. I’m moving to the next page (7 of 8 saying: Reverser and other trims) and then immediately back to page 6 of 8 (Trim, spoilers and flaps). Again 512 is being displayed as the maximum value. It looks like FSUIPC is loosing the maximum value! Hope this can give you some info about what I’m doing and perhaps what’s going on behind the scene. Best regards Anders Persson

Hi Pete, Thanks for your quick reply and thanks a lot for FSUIPC I'm currently not in front of my PC with the FlightSimulator but I have some quick replies so far. (I have to come back later with som more facts thou) If you are refering to the "jumping back and forth". The answer is No. That's why I think this has nothing to do with FSUIPC but maybe a proper calibration through FSUIPC could eliminate it. That has been done. Yes, I did check the FSUPIC.INI file (should have mentioned that in the first post) and I can clearly see that the value is correct there. The correct value is beeing stored by FSUIPC. However, so far I have never got that value back when I'm returning to the "spoiler page". A quick thought. I have the axis reversed for the particular joystick level (fully up gives the minimum value and fully down gives the maximum value). Can that be part of the problem? Again, I have to come back to you with more facts and also all the steps I'm doing. So stand-by for some more info. Best regards, Anders Persson

I’m using FSUIPC version 3.21 and I’m having a CH Yoke USB. In FS I have assigned one of the joystick axis to the Spoiler and with FSUIPC I’m trying to calibrate that axis. I have no problem with setting the calibration values but every time I return to the “Joysticks” page in FSUIPC I always get the same maximum value of 512. The minimum value seems to be correctly “remembered” but never the maximum value. I could not find anything in the documentation about this, even tried to search this forum but with no success. Is this a feature or a bug? :?: I usually fly the PMDG 737NG and there is usually no problem for me to fully deploy the spoilers, however I’m having problems with retracting them. The spoiler level is “jumping” back and forth and can hardly settle at the fully retracted position. This is maybe not a problem that is connected to the FSUIPC but as try I would like to ventilate it here. Any suggestions from anybody would be appreciated. Best regards Anders Persson