Pete Dowson

Yes, I had assumed you were assigning in FSUIPC, but what method are you using to assign the axis? There are at least three ways -- FS controls Axis elevator trim set or Elev trim Set, and 'direct to FSUIPC' Elevator trim. Tell you what, to cut this exchange a bit shorter, why not enable axis logging in FSUIPC, push the trim forward (nose down) then pull it back (nose up) -- make sure you get this order so I can interpret the log correctly, then show me the log. best also to show me your settings (FSUIPC4.INI file). Make sure you do it with a default aircraft, of course. Pete

I also use EZCA so it isn't a specific incompatibility between that and FSUIPC. Neither are dependent on each other either. Try loading EZCA.EXE after FSX has fully started. You could even have FSUIPC load it. Pete

Well, don't do both. The favoured method is by the REV checkbox in calibration, but you MUST re-calibrate after changing that. Either of these does actually invert the values sent to FS. i.e. -16386 to +16384 becomes +16384 to -16384. There's no way that cannot be inverting the trim, so I think there's something else going on. You failed to tell me how you are assigning the axis. It sounds very much to me as if whatever you are doing is simply bypassing these options. Pete

Perhaps if you've still got the original flight file I could try it here. Of course it may well be inter-related to other settings, but, you never know. Regards Pete

Well something is preventing FSUIPC from sensing that the sim is ready to fly. It isn't receiving the aircraft name from Simconnect to start with. The only time I've seen this before was with P3D v1.0 when it was started with the SIM in PAIUSED mode. That's because FSUIPC has started anything yet. It is waiting for something which isn't happening, as I say. Several things to try to get more data: 1. If the SIM is paused, unpause it and see if that helps. Then make sure your startup flight doesn't have it paused. 2. Go into FS's Flight menu and select a different flight and/or aircraft. See if that makes it start. 3. In case it's some problem with the default flight or default aircraft, try changing it. Rename or delete the flight: \\ALPINEPC\Users\Owner\Documents\Flight Simulator X Files\default.FLT Let me know the results. Just look in the log to see if you get a "Starting everything now" message. No need to keep posting more logs until I ask. Regards Pete

I don't understand why you'd think that. Are you moving the wheel continuously whilst panning around? I assumed the only likely time you'd move it unintentionally what when you initially pressed it. If you don't continually move it, then the modification I have made will ignore the initial movement. It works fine here, but please yourself. I don't understand why you bothered to ask for some change in the first place now. Pete

Sounds like a corrupted install of FSX Acceleration. But I need more details to determine what might be going on. When a program crashes there will be details in the Windows event logs. Check the Applications log in the event viewer. Give me all the details -- module, offset, error code. Additionally, show me the FSUIPC4 log file for the attempts when it crashes, and also the whole of the Install log. both logs will be found in the FSX Modules folder. SimConnect doesn't create an Addons menu until something asks to add an entry, so what entries are already there? Maybe it's a clash with some other add-in you have? Regards Pete

Okay, I see you closed FS around 50 seconds after it loaded its default flight. Why? What was on the screen then? The thing is, FSUIPC doesn't think you are ready to fly yet and so hasn't started any of its additional services. When it does that is will have these entries in the log: (this is just an example from my system. Note that this is a full 3 minutes after starting, 2mins20secs after it loaded the default flight): 182022 Aircraft="Boeing 737-800 Paint2" 182068 System time = 31/01/2014 15:03:40, Simulator time = 15:01:20 (15:01Z) 184096 Starting everything now ... Pete

If there's no log produced by FSUIPC4 then it isn't running. If there's an FSUIPC4 log, but no WideServer log then FSUIPC is running, but WideServer is disabled. Please clarify. Pete

Which two options have you tried, exactly? And how are you assigning the axis (there are several ways to assign axes). Pete

But surely that is because it is bound to follow the actual value! Of course.It is not a delay in the operation of your device you nee, but an Autothrottle control software which works realistically. Surely that is in the choice of a realistic aircraft model, to start with? If you stick with iFly it seems you need to get them to sort it out. Or else ditch the add-on avionics and go with something like ProSim, SimAvionics or Project Magenta. -- assuming, of course, that they control the A/T properly. I think that you seem to be trying to treat the symptom, not the problem. Surely the levers should control the throttle value, not the other way around. And if there's no choice but to make it the wrong way round, the levers MUST reflect the actual throttle setting (else what's the point of them?) -- so, either way, it is the actual operation of the autothrottle you need to get sorted out, not how the levers act. Regards Pete

Yes. The method is by adding the delay parameter to the axis assignment setting in the INI file. Please see the Axis Assignments section in the FSUIPC4 Advanced User's guide. I must admit that I don't really understand what you are talking about though. Surely if you want to move the levers more slowly why not do so? You don't need to whack them up and down. If you are talking about autothrottle control by the autopilot/MCP as I assume you must be, then surely that is a matter of choosing a good realistic simulation? What are you using? The delay option on the axis I mentioned is actually probably nothing to do with what you want. The on-screen levers are only reflecting the actual value being set and used. I don't see how you'd expect FSUIPC to be able to prevent the FS autothrottle control setting whatever value it needed. I would think that will also be calamitous is trying to maintain correct set speed and pitch. Pete

Well, if there's no other answer I suppose I can provide an INI parameter which tells FSUIPC to ignore the actual EXE version number and believe something else. But it gets more complicated. Version 2.1 will be out soon, and that will have a different number which FSUIPC needs to check, because things move around. If you have a parameter to set it will have to have the full "true" version number in it, like 2.1.0.9448. Pete

Enrico Schiratti owns that page -- it is his collection of things related to my programs, as it clearly says. I have no control over it whatsoever. I do now seem to recollect that program, but it was written a long long time ago and will certainly not apply to FSX or FSUIPC4. You need to edit the FSUIPC4.INI file instead, adding the appropriate [Programs] section there. You can cut and paste that section from your FS9 version of FSUIPC.INI I should think. The FSUIPC4 Advanced User's guide does have a section about this too. Regards Pete

Yes, but you are asking about a program "run options.exe" which I'm afraid I don't know. Sorry, I think you may be in the wrong forum? Pete

What are you editing? Saving a file just saves a file. Nothing else is going to change it except you and your editor. Perhaps you need to be more explicit. I assume you are editing the FSUIPC4.INI file, before you run FS, and checking it again before doing so? FSUIPC4 itself doesn't alter the [Programs] section in any way. it is left exactly how you set it, so if it is changing it is you who is changing it! Pete

You simply assign the button you want to PTT on (press) and PTT off (release). That is it. nothing else to set, no WideClient parameters, nothing, exactly as documented! Pete

Whether WideClient connects is nothing whatsoever to do with its privilege level on the Client. Using "run as administrator" merely runs it with more privileges, it changes nothing else. And you should never need it -- better to run SB4 without "run as administrator" instead. It timed out waiting for the server in the FS PC, but it might have recovered when FS and FSUIPC were fully ready -- you terminated Wideclient only 3 seconds later, no time at all for a retry even! So why have you assigned the F12 key to send the PTT on and PTT off codes instead of the yoke buttons? You've not answered the questions at all. What on Earth are you using the F12 key on the FS PC for? and I know you are runninmg SB4 on the networked Pc. You said that at the start. That's what this whole exchange is all about! Roger Wilco references are to the standard PTT on and off messages which RW first established and which were copied in Squawkbox. It's a system where a program like FSUIPC or WideClient can send messages direct to SB (or RW etc etc) to handle PTT reather than mess about with keystrokes which are always problematic. Yes, exactly as I said! Why repeat this? What "error code"? You said something about "249" -- I don't know what 249 is. You said nothing about an error code! If there is no log then FSUIPC is not running. It always produces a log. If FSUIPC is not running you will get no connection, as you found! You seem extrremely confused. I'm trying to get answers to simple questions so I can help you, but you are misreading them. Pete

Why do you have F12 on the FS PC assigned as well as buttons on the yoke? Are you using them both alternately or something?Obviously F12 on the FS PC isn't F12 on the networked PC. And you have to make up your mind whether you are wanting to send F12 to SB4 or try using it's Roger Wilco message capability, if that still exists. I can't help you that end, you need SB4 help or documentation. If you mean WideServer.DLL, it isn't used in FSX or P3D because it is built into FSUIPC4, as the documentation tells you. That is set to use F12 on the client PC, so you aren't using the F12 key you assigned on the FS PC? Only the buttons on the yoke? If that doesn't work it may be because SB4 is using a keyboard state/scan, and will therefore only respond to a real keyboard. Or it could be that you are running SB4 "as administrator" but WideClient normally, or vice versa. They must both be run in the same way -- probably best if you got WideClient to run SB4 for you. What's 249? Is that after you closed the client side, or when FS was closing down? It is after 20 minutes. Pete

Does LINDA use the comhid functions or simply the normal joystick button detection? In any case the handle is local to the thread which created it -- you'd either need to put you code into the Lua being run by LINDA, or get it to run call your Lua functions as an external module. Easier to simply use openhid in your own Lua code. With USB devices several programs can have them open at the same time, it isn't like the old serial port system. Regards Pete

You certainly don't want it repeating, on ON when pressed and OFF when released. With the SB comms window open in FSX, the tx light doesn't come on and I don't get the tx error sound that I do when pressing F12 on the machine running SB. Those assignments are for KeySends 1 and 2, not for PTT assignment. To link to those in FSUIPC you need to assign to KeySend 1 and KeySend 2, not to PTT. The whole point of assigning to PTT on and PTT off is to make it dead easy -- you need do nothing at all in WideFS for those (as it clearly says in the boxed text) -- assuming of course that the target program accepts standard "Roger Wilco" messages (as certainly SB3 did and also I thought SB4). You seem to have mixed up the suggested assignments for TeamSpeak, using normal KeySend assignments, and those for SB3/Roger Wilco. Pete

FSUIPC lets you assign to any built-in FS control, and also to some additional controls FSUIPC supplies itself. If you've installed FSUIPC (which you can do for free) you'll have all the information in a variety of documents in the Modules\FSUIPC Documents folder. Whether you can also control added switches and controls provided by an add-on aircraft or add-on avionics system really depends on how they are implemented. If they use FSUIPC offsets for their interfacing to FS, or use added FS controls, or even assignable keystrokes, then, yes, FSUIPC registration would be good for you. At the very least, for the Saitek device, you may find an add-on package called LINDA useful. For FSUIPC offset or button/switch assignment from a Networked PC you might need WideFS too -- unless that Aerosoft software is handling the Networking for you. (If needed, note that you can purchase FSUIPC + WideFS as a package cheaper than buying the two separately). Since I do not know the Aerosoft package I cannot advise further. I would hope that its documentation would tell you what you need. Regards Pete

No, not really -- how would it know which zoom level you wanted? The one originally loaded for the first view ever in the whole session, or what? Zooms are set by panel definitions and probably also saved flights. If you have a specific zoom setting you want to be able to set you could just use a button or keypress assigned to VIEW1 ZOOM SET with a suitable parameter which you'd need to calculate. A value of 64 is 1x, 128 is 2x and so on, so a 0.50 zoom would be 32. Meanwhile, I have implemented an option for a small delay before zooming starts, a bit like the delay you get on a keyboard before it starts repeating. If you'd like to try this before the next actual release let me know, and I'll upload it and provide a link. Regards Pete

I think the FSUIPC control you must be referring to is the one called "Key press & release". Correct? In the Advanced User's guide you presumably found this with the following part also present: (param is Keycode + 256*Shift code, or JsBk) This means the parameter can be the keycode (which as you found is 71 for 'G') plus 256 times the shift code (which as you also found, is 2 for Control). So, simple arithmetic gives 71 + (256 x 2) = 71 + 512 = 583. Alternatively, to save that hard sum you could use the "joystick/btton" notation, although it seems inappropriate for this control it still will work. JsBk means the letter 'J' followed by the shift code then the letter 'B' followed by the keycode, so: J2B71 Regards Pete

Ah, I see. I'll await the OP's response then before I do anything. Thanks, Pete