Pete Dowson

FSUIPC version 4.974 is for P3D3 and FSX. It won't run in or even install into P3D4! None of my software programs use .NET framework. I expect you have an Addon which needs to talk to FSUIPC, but you don't have it installed or running. You need to install FSUIPC5. i don't know why you say you have FSUIPC 4.974. Pete

Okay. that shows nothing is ever seen by WideServer. So the client frames requesting connection are being blocked. Maybe previously you made an exception in your firewall for Wideclient or P3d and moving the latter has nullified that? Test with the firewall disabled. Pete

What's error 12? That isn't an FSUIPC message. Where do you see it? You need to provide more inofrumation. You are using P3D4 -- but which version? Are you using FSUIPC? if not, why are you posting here? If you are, the FSUIPC5.LOG file is needed (from the P3D Modules folder). Error 12 is probably being reported by one of your add-ons. check those. Pete

The folder of the Sim is irrelevant to WideFS. WideFS doesn't use any folder access to operate. The FSUIPC log isn't relevant at all. The important file there is the WideServer.Log. The WideClient log just indicates either that WideServer either is not active or that the IP Address obtained is incorrect: 2356 Server = DESKTOP-6AFUHUP 2371 Trying TCP/IP host "DESKTOP-6AFUHUP" port 8002 ... 2371 ... Okay, IP Address = 192.168.0.11 23416 Error on client pre-Connection Select() [Error=10060] Connection timed out I need to see the WideServer.Log as that will indicate whether the client was ever seen. Pete

What you are saying is that the iFly 737 doesn't obey the usual simulator controls. "G" doesn't operate the Gear? What is the "horizontal stabilizer trim"? Do you mean elevator trim? If so don't the normal trim up/down controls work (default assignment: NUM 1 and 7 keys)? Does the aircraft come with any documentation telling you how to operate these things. i would have thought that for such essential controls they would stay with the normal assignments, otherwise many many add-on devices won't be directly usable with it. When you ask such questions it would be helpful if you would mention which simulator you are using and how you are actually trying to do such things. Pete

I don't think so. There are a lot of settings which can't be read programmatically. Looking through the Sim Vars I can read from SimConnect, the only one applicable to flap failure is "FLAP DAMAGE BY SPEED" which I don't read at present. That probably isn't what you want, and there's no separate Left/Right variants. In any case many airliners have inboard and outboard flaps, and of course leading edge ones. Not sure what the flap fail options actually fail. I suppose you could change the flap setting by one notch and see if the flap readbacks change, returning the flaps after, but that would have a noticeable affect of flight, i would have thought. Pete

So why did you post your questions at the end of an older thread about FSUIPC 5.13 key settings? You are lucky I found your posts. I've split them off into a new thread with a more appropriate title. It is nothing to do with registration, so you must be making an error. Just purchase the Registration at SimMarket. The information is provided to you in the documentation -- refer to the User Guide. It's on page 3. You seem to have repeated all of the first post in the second, so I shall bypass the repeated part. The values you are reading are NOT characters, they are each 32-bit integers already! Why did you think they would be chracters? To start with, 4 bytes would then only accommodate yp to 9999 meters, nowhere near adequate! You read them into an ordinary numeric variable. Take care to treat the fraction part as unsigned. Really you should treat the whole 8 bytes as a single 64-bit integer (int64). It will be 2^32 too large if you want meters, so copy it to a double and divide it by (65536.0*65536.0). Pete

With multiple controllers like that you'd do much better to assign letters to the entries in the JoyNames section, as described in the Joy Letters chapter of the User Guide. Or set AutoAssignLetters=Yes if you don't mind them being called A, B, C ... I would use Y for Yoke, T for throttle, R for Rudder, and so on. You can do with before running session and FSUIPC will automatically change the 0, 1, 2 assignments to the assigned letters. Just deleting the INI file does that. Then you'd need to re-do all your assignments and calibrations, and re-set any other options you use. Alternatively, either delete or correct all of the entries which appear wrong. Deletion and reassignment in-sim is probably safest if you are not sure. The Direct method is more efficient, and offers some axes not otherwise available. But some aircraft don't like that method for some controls as it bypasses their own interception -- for example, throttles for some PMDG aircraft. The "to sim" method is identical to assigning in the simulator's assignments. So, try the "direct" method to start with, but switch to the "to sim" method if you get any problems with specific axes. It doesn't matter if you mix them. One exception: to get the steering tiller / rudder blending action offered by FSUIPC, both axes should be assigned "direct" and both calibrated. It may work the other way, but it is more problematic. Pete Pete

If you assign them in FSUIPC you really should disable them in P3D, unless you want odd things to happen and controls to become unusable! P3D doesn't need to "recognise there are joysticks" if those joysticks are being recognised and routed to it by FSUIPC! That's the whole point! That's how FSUIPC does things like calibration, reverse thrust, and adjustable response. Pete

Yes. But as I said, this does mean assigning in FSUIPC. I told you where where to find the reverser assignment just previously! In any case, in FSUIPC there is nothing stopping you having multiple controls assigned for the same thing -- for example folks with both captain and first officer control have a set each. When more than one axis controls the same Sim function, FSUIPC "arbitrates". It uses the one with the most deflection from normal. That works well. With reversers, of course you should bring the throttle back to idle first. With separate axes assigned to the apparently separate functions (throttle and reverser), FSUIPC will act on the last input seen, so operating the reverser whilst full throttle is engaged will result in rather sudden changes! 😉 As I said previously, it is best and safest to assign everything in FSUIPC and disable controllers completely in P3D. There's a checkbox for that in the last section. Merely unassigning axes may not be enough. If you don't need anything special from FSUIPC assignments, then you can do all the assignments in P3D instead of FSUIPC. But you need the reverser. No, the REV button just swaps the action of the input over, so that the max position acts like the min position and vice versa. it doesn't make a "reverser". Pete

Yes. As I said you can calibrate in FSUIPC wwithout assigning in FSUIPC. I don't think P3D has a reverser assignment -- but check. I think you will have to assign in FSUIPC for a reverser, which yould really mean assigning everything in FSUIPC and disabling controllers in P3D. you might get away with a mix but it can be precarious because of P3D's automatic assignmeny of axes (and buttons). Pete

For an axis as aseparate reverser you would need to assign in FSUIPC with the "Direct to FSUIPC ..." mode selected. Then in the drop down list you will find reverser assignments. When you calibrate you will probably want to check the REV button as full reverse is normally a pull right back, with full forward for it undeployed. Pete

You certainly have multiple assignments. There's really no way otherwise. The calibration section detects what is going into the simulator, NOT what thejoysticks or their assignments are doing. Measurements there could even come program a program or plug-in. If you'd like to attach your FSUIPC5.INI file I can check your assignemtns there, but from what you've said it doesn't sound likely to be anything there. Pete

You've not calibrated it properly then. Set the idle zone ("central zone") where you want it, not halfway! Follow the numbered steps in the calibration chapter of the FSUIPC user guide. Yes, there are checkboxes specifically for that in the calibration tab for the 4 throttles. Please do refer to the documentation! Pete

I'VE MOVED YOUR SUPPORT QUESTION TO THE SUPPORT FORUM. PEASE ALWAYS POST SUCH QUESTIONS TO THIS FORUM, NOT TO A SUBFORUM, IN FUTURE! You need to clarify. Do you want a separate axis as a reverser, or do you mean a reverse zone on a throttle lever? (Whether it's an X52 or any other axis doesn't matter. The methods are the same. An axis is an axis is an axis.) Pete

Sounds best to find out what LINDA is sending so you can do the same. Try enabling FSUIPC's event logging first, and see if it is sending commands. If it is using L:Vars then it is a little more complicated. You can get a list of those by using the List L:var control in FSUIPC's assignment dropdown, but to see then change, live, use the Log LVars Lua plug-in, one of the Lua Examples provided for you in the FSUIPC documents folder. Pete

No. You can calibrate no matter where you assign. You need to disable controllers in P3D if, and only if, you intend to assign them in FSUIPC. Assignment and Calibration are two different things. Assignment operates with the INPUTS from your controllers, calibration operates on the data being sent to the simulator. If you've no need for any special assignments, or any need to have them change for different aircraft, then just assign as usual in P3D. You can still calibrate in FSUIPC if you wish. Pete

Well, I looked at the code for ipc.getdisplay and ipc.setdisplay, and it was easy enough (with what i've learnt about SimConnect in P3D4) to make them work for the "SimConnect Message Window", so these will be fine in the next FSUIPC5 release. The setdisplay one might turn out useful for you to get the window exactly where you want it. The ipc.setowndisplay will be identical in effect to uipc.setdisplay -- the title provided is ignored as unfortunately i can't change that. Pete

Which sim are you using? What sort of macro are you trying to create? Does the aircraft have keyboard short-cuts for the things you want to do? Have you investigated the possibility of using L:vars? Pete

Best and safest, really, is to disable controllers in P3d. You don't need to unassign anything then. And otherwise P3D may, as FSX used to do, automatically reassign things if it ever thinks the device is a new connection. Pete

Axis assignment is a completely separate section and action to calibration, so there's no way one will affect the other, though if you assign in FSUIPC "direct to FSUIPC calibration" then you should calibrate, otherwise the result may not be forwarded to the sim. The "ping" occurs when you try to set any value which breaks the rule of minimum <= centre values <= maximum i.e. left to right, bearing in mind negative numbers are less than positive ones. Just press the Reset button, then Set, and start again, watching where the numbers should go. Note that for aileron and rudder, for example, LEFT and RIGHT do NOT equate to MINIMUM and MAXIMUM. In its wisdom, Microsoft decreed that left aileron and left rudder were positive maximum values, and right were negative minimum. Calibration does several things for you, should you wish: 1. It ensures that both extremes of control surfaces and so one can be reached, which is not a given with many controls 2. It provides a way of ensuring the a central neutral position is exactly where it should be, physically, and, by using two values to define a zone, allows a little variation in that, so that a released control when it returns will always give a central result even if the values there vary somewhat, as they do due to spring tensions changing and temperatures or voltages affecting the readings. 3. It allows precise dead zones, like the central area, to avoid drastic aircraft behaviour from small nudges made by mistake, or, in the case of the rudder, to ensure toe brake operation doesn't also move the rudder. 4. It allows a variable slope which to be set which can make the controls less or more sensitive in the central zones whilst still not preventing the extremes being reached. Pete

If you mean they aren't setting or getting the size and position of the display window, then that certainly likely as I don't think I can do that easily. But I probably should be able to do it. t hadn't occurred to me. Sorry. I'll take a look. Pete

SetOwnDisplay was by a hack into FSX/P3D3. Wth proper new SimConnect facilities what that did is not possible (and I am NOT hacking into P3D4 code!). So "SetOwnDisplay" is now, in P3D4, the same as "SetDisplay". This should of course be noted in the Lua library document but on checking I see that the amendment I thought id put in did not make it to the end result, so I'm making a note to deal with that now ready for the next release. Sorry for the misunderstanding. That's strange and should certainly not happen. The display function isn't changed, and it certainly works okay normally. Can you show me the Lua plug-in so I can test it here? And see if it happens if you use SetDisplay instead of SetOwndisplay -- though any difference seems very unlikely as shey are effectively the same code. [Note: I though for compatibility it would be better to make those the same rather that just remove SetOwnDisplay from FSUIPC5] Pete

I don't think you can do exactly that (or at least not only that). but check the Advanced User's Guide. Look for the parameters ZapAirRange and ZapCylinderAltDiff. (Page 7). Since there are spaces in your path (eg in "PMDG 737 NGX") you need to enclose the whole path in "" so that it acts as one parameter. Else Windows sees each space as a parameter separator. Pete

You really need to read the whole thing as one 8-byte 64-bit number, then divide it by (65536*65536). (sorry, easier to remember 65536 that the max value of a 32 bit number). I don't know C# but it surely must support 64-bit values! If you must read them separately then treat the fraction as unsigned, otherwise you'll get propagation of the top bit as if it is a sign. BTW Calling 'Process' for each value you are reading is very inefficient. You should do all the reads and writes THEN call Process. The requests are then sent in one batch. Much more efficient. Pete