barrykensett

Thanks for your reply Pete. Yes I worked from the manual when setting up FSUIPC and WideClient.ini., in fact I copied your settings in FSUIPC (Keysend variables 1 & 2. I used F12 on the slave computer so the text in the WideFS .ini file were the same as your example and with TeamSpeak in focus it all works. I then looked at the other topics you mentioned, not pretending to understand it all but the first stumbling block was starting the TeamSpeak program from WideFS which I gathered was necessary. I put the instruction to start TeamSpeak into WideFS .ini and rebooted but I got the error message WideClient couldn’t run Run1=C:\Program Files\Teamspeak 3 Client\ts3client_win64.exe(error740) I tried playing with the Focus commands but this didn’t work, not surprising because I was starting TeamSpeak manually because of the above error. Thr keyboard commands work perfectly so I am not speechless! Barry

I run P3D with FSUIPC on one computer and TeamSpeak amongst other programs on a services PC. I setup the PTT button on the joystick using the Keysend function. On the services computer I have F12 on the keyboard set to be the PTT in TeamSpeak. In WideFS.ini I set up the F12 key to work from Keysend.. it all works perfectly except that TeamSpeak needs to have focus; if any of the other programs on that PC (eg ActiveSky) have focus then PTT does not work. If I use the F12 key on the keyboard it works fine whether TeamSpeak us in focus or not. is there a trick to get over this? I have tried running TeamSpeak as admin. (a trick I learned in a similar situation) Barry www.a329sim.com

Thanks for your help Pete, I have spent some time tracking the problem and it is now fixed. Autostarting was an issue, the rogue was coming from a backup copy. I downloaded WideFS7 thinking it was not specific to Microsoft FSFS, in fact a friend uses that version satisfactorily. I could not however get it to auto start in the Widows start folder or by using FSFlight Control. It ran fine when started using the .exe. Using an older version of WideClient it auto starts and runs fine. Thanks again Barry

Been using WideFS for years but hit new problem I can’t crack. My FS setup is on three networked PC’s and has been working fine for years until I just upgraded one PC. PC1 is P3D and FSUIPC/Wide FS server, PC2 and PC3(just upgraded) both run Clent. I usually place the downloaded WideFS folder in Windows/Programs folder and the put a shortcut to WideFS.exe on the desktop. At one time I used to put WideFS in the Start folder but I find that these days I don’t have to do that, it puts itself there, very clever. I start all PCs and WideFS starts in PC2 &3 automatically waiting for P3D. Strangely the WideFS window shows in PC3 even though “visible no” is selected. When P3D starts up PC2 connects but on PC3 WideFS crashes. If I restart it from the desktop shortcut it connects and is then faultless for the rest of the night. Might appear minor but I have ADIRS software that crashes when WideFS goes out and never to return. I am using the latest download of WideFS but i also tried copying across the version and setup from PC2 which works perfectly but doesn’t on PC3. All three PC’s run Windows10. Any clues would be appreciated. Barry Kensett www.a320sim.com

I have successfully set up Com 1 radio tuning encoder by detecting encoder movement as a switch and used the drop down menu to assign Com 1 standby whole increase and decrease. When I try similar on Com 2 the menu shows Com 2 standby increase but no decrease. I can use the radio by always increasing so that the tuning "goes round again". Can anyone advise how I can get the decrease working for anti clock movement of the knob? Barry www.a320sim.com

Well I spent many hours setting up again and again, reading the manual again and again and I never got the aircraft to handle properly. It is far too twitchy to be realistic, it's as if the the aircraft has no inertia to damp down the movements. I then followed some tips on a couple of other posts on this forum and went the route of a lua script (based on "liar") to fool FS communicator that I am in fact flying FS9. It is now flying like a dream just like the olden days! The tiller is not working so am having to steer on the rudders at the moment so more work to do. I was worried in case this solution upset some other programs but they all still work, mostly I think they now use simconnnect rather than WideFS. Thanks for the time to post some tips Pete. Barry www.a320sim.com

Thanks for the reply Pete. The FS controllers are not enabled. I ran the log and noticed that there were no spurious inputs, I had made the wrong assumption there. I find that it is using the Delta function that is causing most of my problem, I had been using that in the belief that it sets up a null zone and I did this because I thought I was getting inputs in the neutral positions. However this was giving me the effect that when I moved the stick the movements were not smooth and proportional. I have now cancelled the Delta setting and things are a lot better. I will do some more experimentation and testing, your input has set me on a better track. Thanks again. Barry Www.a320sim.com

I have dual joysticks in my home cockpit which I can set up and calibrate in FSUIPC. For reasons I don't fully understand the handling of the aircraft is not good; if I fly FSX on the desktop with one joystick it is pretty smooth. In the cockpit however it has always been twitchy. I think one of the reasons is that there is interference between the two axes. If I disconnect one stick things improve but still not good. In similar vein I find that the steering tiller inputs are dreadful unless I disconnect one wheel and even then control is not smooth. I have tried amending slopes, I also set the minimum delta to give a null zone and I always cycle the sticks before use, I have even tried changing effectiveness in the cfg file. The only time I got smooth control was in the dark ages using FS9 and FS Communicator, the latter will not work with P3D. Has anybody anything to share on this topic? Barry www.a320sim.com

Daniel I want to do the same thing, I have looked through the LUA documentation but it is all Greek to me, I am too old I think. I have found the liar.lua and I understand that I put it in the Modules folder, in fact I have put it there and it is numbered in the config file so I have done something right I think. I have to put values in the script I presume, can you tell me what to do please? Barry www.a320sim.com

Further to above I have used FDT Simboards for some time but on moving from XP to Win7 I find that the driver loader is not accepted. Anyone any solutions? Barry www.a320sim.com

I use FDT boards and may be able to help. Barry www.a320sim.com

Pete From the AST forum I have been told that I should put 0x4602 into byte set and 220 (not hex)into parameter and it will work. I will give it a try. Surprised that you have not heard of AST software, it is very comprehensive and in my view better than PM for Airbus users. The support is much better too. Website is here http://www.airsimtech.eu/ I have no idea why they use 4602, I had assumed that they and you were hand in glove on that. If you are ever in the East Riding come and fly it. Barry

Pete Thanks for the quick reply, if you don't understand it either then I don't feel such an idiot. I will talk to AST but their main guy is away for a month, I'll try their forum. Just a few snippets for you, by AST I am referring to AirSimTech which is my suite of software similar to Project Magenta but more specifically tailored to Airbus. All of the internal variables in their SDK use Fsaddr 4602. I wanted to program another of the SDK offsets into my Flight Deck Technology (http://www.simboards.com/) USB card software, I gave them the 4602 offset and the relevant "SWID", they sent me back a line to paste into the config file for the board which works perfectly so somebody out there understands it. When I have more I will put it in here. Barry www.a320sim.com

I want to do something which I suspect is simple but I am an even simpler person and despite reading the manuals and the FAQ's I am stuck because I am a hardware man and the software jargon is all Greek to me. I want to program a switch to set off the fire extinguisher in my AST Airbus software. I have got the switch detected in SIOC and across my network to FSUIPC where I can detect the button. From the AST SDK I have an offset of 4602 and a SWID of 220 (whatever that means). I can select FS control and I get the drop down menu but I don't know what to do with it. I see bytes, Dwords, Swords but all I can use is the Fword which I am doing frequently. I tried offset byte set and put in x4602. I didn't know what to do with the SWID but tried it as a value x220. I then tried a flight, started an engine fire and pressed the switch but it did not put the fire out (I was not surprised!) Can anyone guide me on how to do it? Barry www.a320sim.com

Sorry missed the thread below Barry

Is it possible to detect a switch or button press to disable/enable a joystick? Barry www.a320sim.com

Thanks Pete, understand it now Barry

Could you clarify what happens when calibrating axes using multiple joysticks please. If I detect an axis by moving the control I can see which joystick and axis I am addressing. If I then go to the calibration page I do not see the joystick number which causes me to ask how it operates in the case of dual controls (Captain and First Officer). I presume that when I move from the axis detection page directly to calibration that I was calibrating that same joystick. Are two separate calibrations held for the two joysticks or is there one calibration for the function (e.g. aileron) which would be overwritten when I calibrate the other joystick for the same function? The problem arises over difficulty in maintaining the centre point calibration from one day to the next. Oh for one magic button that sets all the control centre points before flight! Barry Kensett www.a320sim.com

Thanks Pete, I sat on the naughty step for a couple of hours and then went back to the sim armed with your advice and all my controls are now visible and able to be calibrated in FSUIPC. I am hoping that having got all the controls working through the same software setup and with a bit of tweaking to create dead zones in the centres of travel that the "twitching" which started this post will go away. Time will tell. Barry http://www.a320sim.com

Pete Sorry FS Comm = FS Communicator. To recap on my objectives, because my sim is A320 I want to implement Fly-By-Wire; I am trying FS Communicator as this is the only software that I know of which does this. Also it incorporates the Airbus joystick priority handover feature with the proper warning lights. To save wiring and interface cards I re-allocate the throttle axis to nosewheel steering so that service physically goes wherever the sticks go. My rudder and brakes are a separate "joystick" Before I started to use Fs Communicator I had all the joysticks on the FS computer and set the controls up in FSUIPC and it all worked but as stated in the original post it was very "twitchy". In accordance with FS Communicator recommendations, the joysticks (sidesticks) are not now on the Flight Sim Computer. The roll and pitch axes go into Fs Communicator and via WideFS and FSUIPC to the Flight Sim (FS9) Because of the way I have wired things the tiller is not now on the FS Computer and is not handled by FS Communicator so I need to send that to the Flight Sim through FSUIPC. Initially I sent the rudder offset to the Flight Sim and that worked fine. I could not however use the tiller/rudder setup in FSUIPC as I could not "see" the axis. This is where your suggestion to use the PFC offsets looks to sort out my problem, if I can "see" the tiller and rudder axes in FSUIPC I can calibrate them. I missed the point about using values 0 - 127, I think I can sort that by setting the range in FS Communicator and will try that next. Thanks for your patience, I do try to read the manuals but there is a lot to read and a much of it I don't pretend to understand being a very old engineer, not a programmer. Barry

Pete Those offsets worked fine in that they appeared in FSUIPC as joysticks. I have put the rudder and brakes on the same PC as the nosewheel steering. I have carried out basic calibration in FS Comm, i.e extremes and centre for rudder and tillers, max and min for brakes. I then tried to set up in FSUIPC to get the steering and rudders separated. I went through the well trodden procedures but could not get a calibration to work, the input values did not look anything like the output valus from FS Comm and I could not get a centre point on either of the axes. Going back to FS Comm I put the steering and rudders all to 0BBA (rudder) and that works fine except that of course the two axes are both working at all times. The brakes calibrated fine. The sim is flying OK with the present setup but it would be nice to get the tiller to wash out, have you any more tips? Regards Barry

Found them in the docs for PFC.DLL. Will try them out. Thanks again Barry

Pete Thank you for those pointers, I think the mechanics are all OK as I have tried pulling them out one at a time (rudder and the two sticks) but I will double check. I do have a worry about the CH rudder and will be making a new set of rudder pedals soon. All plugged into motherboards. I have tried playing with the slopes but will have another play; I was trying to get a wider null zone. I did not know about the 3BA8 to 3BC6 offsets and have not yet been able to find them in your documents, can you give me a clue as this excites me? Thanks for your help. Barry

I have used two configurations using the steering tiller facility in FSUIPC, the first setup was with two joysticks connected to the FS sim PC plus one pair of rudder pedals. I disconnected the throttle connections in the joystick and plugged the steering tiller pots in there (easy short wiring job). The detection and calibration worked fine except that when taxying the aircraft twitches from side to side, not enough to make it unusable but very annoying as it does not follow a smooth track. I messed about with calibrations in FSUIPC but never managed to get it smooth. I think it is getting spurious inputs from somewhere and with so many controls in the game I am not surprised but I have tried to ensure through calibration that all controls "at rest" are properly zeroed. I am now trying out FS Communicator so I have two sidesticks connected to another PC which talk across with WideFS. Also I managed to get the throttle pots mapped to rudder as before but now I don't see the calibration options in FSUIPC (I presume this is normal using pots across WideFS?). By trial and error I found however that if I selected NW Steering in the axis calibration page and just clicked the centre point that the rudder came in as taxi speed increased so I thought I had cracked it, however the main frustration I still have is the twitching of the steering is just the same as before. I have of course calibrated everything in FSComm. FS communicator recommends Auto Coordination selected on and when I taxi and steer with the stick it is so smooth. This prompted me to try mapping the steering tiller to the ailerons but that messed the ailerons up. Has anyone else here had the "twitching" and managed to sort it? Barry www.a320sim.com

Worked perfectly, thanks again Peter for your patience. Barry www.a320sim.com