John Fee

I quote your guide: 'The 256 is the increment and 16383 is the limit. This will give 128 steps between -16383 and 16383 inclusive (32768/256 = 128)....' The word 'steps' is how I got the wrong idea. I understand now that my interpretation was incorrect. John

Thanks. Am using x0BC0 as per the Advanced Users guide. I thought by reducing the number of increments/decrements this would make matters worse - dividing the same range into fewer, and thus larger, segments. Worth a try. I don't want to reduce button scanning rate if that's going to affect rotary buttons as well. Thanks again for prompt support. Hope all well with you. John

I'm using 'Offset SWord Increment/Decrement' to control elevator trim buttons on a yoke in both FSX and FS9 (Windows 7 x64). In the parameter box I set 256/16383 for increment and 256/-16383 for decrement. I allow the control to repeat when the (trim) buttons are held. My problem is that the resulting trim control is very fierce - it is as though the button was controlling the elevator directly and not just trim tabs. I don't know the correct word for it but I suspect the 'frequency' of signals sent by the button is very fast and that this gives an exaggerated effect. Could this be so? If it could be, is there a way of adjusting the rate at which the button sends its signals when held? Thanks. John

Thanks, Pete, This was exactly the information I needed. I hadn't tried offsets before - scared off by the terminology. I now have the most balanced trim function I've ever had in half a lifetime of using FSUIPC. I traced the original problem though. In the photo Button 24 points up at the green LED. This button is permanently active and in some way had become set to keypress 'Home'. This resulted in continuous trim inputs. I removed the key/button assignment - I hope permanently. I would like to disable this button but am not sure how. Just one thing, Pete, I've not set these trim offsets to be 'profile specific'. Does that mean that these settings are active for any plane unless over-ridden by a 'profile specific' setting? I wasnt' sure exactly what the User Guide meant. John PS I set up the same trim offsets in FSX :)

Pete I'm using FSUIPC 3.999w 12 Aug 2012 and FS2004. For longer than I care to remember I've been using FSUIPC button assignments to control elevator trim via a rocker switch on a CH Eclipse yoke. This worked very nicely until recently after I deliberately deleted FSUIPC ini. I've got everything back the way it was except for elevator trim up/down. Under Buttons and Switches, I assign 'Home' key for trim down, and 'End' key for trim up, but this produces erratic responses to the rocker switch. I have tried this with 'key press to be repeated when held', and not; and I have tried it with 'profile specific' checked, and not. I ended up re-enabling FS9 joystick and reverted to FS control. The upside is that I can now use the FS 'Hat' control. EDIT: This failed after a re-start and I was back to square one. I was getting full trim up or trim down no matter what I did. Is there something about elevator trims (they are axes after all) which makes them tricky to set up using FSUIPC keypress assignments? Or have I, as is often the case, missed something obvious? Thanks as always for your continuing development of FSUIPC. I've been following the FSX friction discussions with interest. John

Many thanks, Pete. Spot on as usual :) . John

Pete I'm running FSX with FSUIPC 4.839b in W7 x64. Forgive me if I missed this in the docs, but what parameters should I set for Traffic Zapall and Traffic Zapper in the Key Presses dialogue? I wish to be able to remove AI planes that are in my way on short finals, and also when they are about to taxi through me on the ground. So, a narrow beam with a range of 1-2 miles extending around 800ft QNH would seem about right. Having said that, your default values for most things in FSX usually fit the bill. I know I should not mix topics but I read a lot now on these boards about Lua. Is this a language the inquisitive but poorly informed sim pilot should learn? Best regards John

Problem solved. It was a livery problem. The JU52 profile was for one repaint only. I was doing my checking with a different repaint loaded. I'm not sure why this second repaint chose to be a DC-3 and not something else though. Thanks for help, Pete. As I suspected, I missed something obvious. Regards John

No joy, it is still doing it. It is convinced it's a DC3. FS9 is installed in the root directory for that very reason. All very odd, I admit.

No, I never tweak settings with FS running. I saved the .ini and rebooted each time. Will do.

Hmm...not so simple. I already tried removing the profile name from under DC-3. What happens is that when I then attempt to assign the JU52 profile it again shows as DC-3. [Profile.Junkers 52] 1=Junkers 52/3m D-ASIS 2=AC520 Pegasus [JoystickCalibration.Junkers 52] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No MapThr12to123=Yes FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=0 RudderTrimControl=0 CowlFlaps1Control=0 CowlFlaps2Control=0 CowlFlaps3Control=0 CowlFlaps4Control=0 MaxSteerSpeed=60 Rudder=-16190,-1355,1408,16192 Throttle=-16209,16383 PropPitch=-16380,16380 Mixture=-16380,16380 LeftBrake=-15104,16384/16 SlopeLeftBrake=5 RightBrake=-14848,16384/16 SlopeRightBrake=5 Throttle1=-15877,-9290,-5067,16216 Throttle2=-15694,-10003,-4829,16042 PropPitch1=-16035,-9760,-5926,16039 PropPitch2=-16384,-10082,-7382,16383 Spoilers=-16209,16211/16 Flaps=-16201,16383/16 Reverser=-16380,16380 [Profile.DC3] 1=Douglas DC-3 BEA 2=Junkers 52/3m G-AHOF //this line reappears under DC3 when I check profile specific and select Junkers 52 Presumably I am missing something obvious.

I'm running version 3.999 in FS9. I set up a triple engined JU52 as a profile. When I load the JU52 and check the FSUIPC settings it shows as DC-3. Obviously, the same profile will not work for these two aircraft. I would do a fresh set up of the JU52 but I cannot uncheck the 'profile specific' box (greyed out). I guess I need to amend the .ini file but what to do exactly? Thanks. John

I tried it, Ed, but it didn't work. Since #21 I have mapped both my FSX (W7) and FS9 (XP) drives to my client. This has speeded up access. Also, WideFS opens automatically when connecting to FSX and FS9. I'm not sure why it does this but I like it :) John

Pete Joy! :grin: After much head-scratching and experimentation I eventually decided to take a look at the client PC registry. I should have done that sooner because the ASE paths to FSX and FS9 were in a mess. I fixed these, but still no joy.... Changed port from 500 to 4506 (supposedly unused) - success at last! Also, I had to rewrite the paths in the dll.xml to get the tools showing as you said. Nope. But I gotta admit this darned Simconnect thing very nearly had me beat. MS made a very big mistake when they passed you up, Pete. Thanks again for your help and encouragement. John

Ok. Just one last question. When you run FSX how many tools show in your Tools menu? I have only the OPT. I read somewhere that there are 3 in-game tools, OPT, Effects, and another. Regards John

Thanks again, Pete. You been incredibly patient. I resisted FSX for years because I have such a lovely FS9 triple monitor setup. Just recently I thought I'd give FSX a go. As far as I know the only program on my client which uses Simconnect is ASE. The others, various loggers and Radar Contact use WideFS. Similarly, FSKeeper uses WideFS I think, but I am not sure. It may seem a silly question but apart from running an addon program on the client, how do you know if/when Simconnect is connected? John

All checked again. Cut and pasted from your post. In correct places. I already copied to the client application folder. Not a dicky-bird! It just refuses to connect! I don't know where to go to from here. Regards John

WideFS connected! :grin: Simconnect still not, unfortunately. J

Pete Many thanks again. I modified the .cfg and .xml files. Still no joy, even with GRETEL instead of the IP numerals. Yes, simconnect.cfg is in the Client's Documents folder. I attempted to run ASE on the Client - just to see. Initially it could not find the FSX application. When I pointed the program to ../Roaming/Microsoft/FSX it loaded up a database. It produced weather but it did not transmit this to FSX. I wonder if the dual boot arrangement is causing problems. John PS More crossing. Will do as per #11. J

Thanks for #8 too, more crossing! I will try your settings. John

Pete Thanks for #6. My post crossed with yours 03.17. I have indeed two versions of the WideClient.exe. I've attached both pairs of .ini and .log files. Obviously this is a complete mess so I'm very grateful for your help. I also have a WideServer.ini and WideServer.dll included in the FSX version of the install. [Config] Port=8002 ;------------------------------- [user] Log=Errors+ ;------------------------------- Regards John WideClient_FS9.zip WideClient_FSX.zip

Pete Simconnect files attached. I included the .cfg (client) as well. Thank you for looking at these. Regards John Simconnect_John.zip

That's kind. I should have said that WideFS does not connect from the Client either. The server is waiting for connection....which is why I sent the first batch of files. It is not only Simconnect. As I said, I never had any trouble with WideFS and FS9. Used it for years and you wouldn't know it was there. If you think FSX's Simconnect is a triumph of software design, and a better way of connecting, I'm surprised. You must be one of very few. ;-) I have to admit that although I have read extensively I am still unclear as to the separate roles of Simconnect and WideFS in FSX. As I understand it, Simconnect is used by FSX to connect to addons such as ASE. Wide FS is used to control hardware from the Client, although this could more easily be done directly on the server machine. Maybe I am completely mixed up! I'll post the simconnect files to you later this morning. Thanks again. John

Pete Yes, of course I installed Simconnect.msi on the Client. There is every reason to install the SDK on the Client. In fact you have to do it to test the connection. The Server and Client SDKs must be the same version though. I ran out of ideas myself. Sorry to trouble you. Yes, obviously I am. I'll just go back to FS9, its a better program anyway. Thanks for your advice. Regards John