Pete Dowson

Okay. I'm on holiday the week after next, so probably we are both back at the same time. :-) Pete

You have to think in terms of the way FS works, not a real aircraft, because FS's trim mechanism is NOT the same as a real aircraft's trim. Basically ALL three trim values available are additions, using the same units, to the control positions. So a trim offset of 100% (1.0 or +16383, depending which offsets you read) with an main control of 0 is exactly the same as a main control at 100% and the trim at 0, or both at 50% .... etc etc. Now think of what happens to a normal sprung gaming joystick or yoke. Hands off it goes to centre, 0 in both axes. The pressure is only being applied by the springs when you want it off-centre, i.e. a non-zero axis value. Trimming is just the act of transferring that non-zero value from the main control to the trim, so you can relax the hold and let it go back to its 0 position. Therefore, unless my reasoning is flawed somewhere (and I can't see that if so), the properly trimmed position is ONLY when the readout for the axis is 0. So you only need to read the diversion away from 0 in order to apply your pressure or movement or whatever. Regards Pete

But by definition a "required" vallue is an input TO the system, not a read-out FROM it. What, in your case, is providing the input? So YOU are setting the "trim required", so why not feed an extra output from your trim wheel or rocker switches or whatever to yout servo circuit? However, really only you know when you are "in trim" to the extent there's no pressure on the elevator axs of the control. With a normal home yoke or control stand which is simply spring loaded (so doesn't stay in different positions according to the trim) the central "hands off" position is when the input to the FS elevator control is zero. The trim value is then holding the aircraft's attitude in the desired "trimmed" position and will often be non-zero of course. So really the value you need is the FS ELEVATOR position, not the TRIM. When that is 0 you should be stable with hands off. Reading the TRIM position is surely not the relevant thing to do? Or maybe it's me not understanding? Regards Pete

Well, actually, I would rather not "let it lie", because I cannot support older versions and would like to know what this program is doing which is appearently now either not supported or become faulty. If you have contact with the author or the support folks for it I would like them to contact me with the reasons why so that they can be fixed if possible. Additionally, if or when GlobalSign do actually do as they threatened / promised to do in revoking the signature used on versions before 4.9 then it will affect everyone, as FSUIPC will simply refuse to work any more, complaining of corruption detected by a bad signature. They did say the revocation would occur within a matter of days, and that was weeks ago, so I don't know if it will ever happen, but still ... Regards Pete

Oh, right. Never done any scenery desgning so never looked there. I suspect this is actually implemented as a scenery action directly into the simulation, and not through the weather system if it is not reflected in any of the weather data which is provided. There's no mention of "thermal" types in any of the weather facilities. If you refer to the SimConnect part of the Core Utilities SDK you will see that all the information is provided in a sort of extended METAR string. There's no place for thermal data, and the METARs are in any case related specifically to defined weather stations. Requesting details for anywhere else simply gives an interpolation from the nearest three WX stations in a sort of triangulation grid. If this does affect the actual wind vectors at the aircraft then they should be seen affecting the X, Y and/or Z axis wind speeds at offsets "DC8, 2DD0 and 2DD8 respectively. But you will probably need to make sure FSUIPC's wind smoothing option were turned off the see it in the X and Z axes as this is where its smoothing takes hold. You may or may not see it in the vertical (Y) axis). I suspect that's because all of the offsets you monitored appear to be weather (from the weather.DLL) rather than wind effects (from the SIM engine). Regards Pete

The SDK contains both the FSUIPC guide for programmers and the FSUIPC4 Offsets Status List. If you install FSUIPC3 the former is installed into you FSUIPC Documents folder too, and if you install FSUIPC4 the latter is installed instead. The same applies to the list of FS Controls -- the List of FS2004 controls is installed in the FSUIPC Documents folder when you install FSUIPC3, and the List of FSX Controls is installed with FSUIPC4. You've only mentioned the FS2004 Controls list (quite "Looked under fs2004 controls with no luck") and the FSUIPC for Programmers document (quote "as per fsuipc for programmers document"), so it looks 100% as if you've only installed FSUIPC3, as neither of those are installed with FSUIPC4. How has that come about? Regards Pete

Sorry, but i don't really understand. What's a "weather trigger"? Are you setting weather in FS? Which version of FS? How are you setting it? Are you trying to detect wind or cloud turbulence -- the two are separate effects in FS. FSUIPC does contain logging facilities for weather, which you should use to ensure your weather program is doing what you want it to do. There is also the WeatherSet utility which will read the weather details for you. Pete

Well, I don't know of any problems afflicting other applications in such ways. Maybe Air Hauler was making use of something unofficial, or buggy, and that's been changed -- used for something, or fixed. I'm sorry, but without information about what it is doing that isn't wanted I can't help. If the developer looks at it and can tell me what is wrong I can take a look, of course. Pete

Hmm. Clean forgot about all those. They are obviously all part of the facility encompassing offsets 480 through to and including 4A0. I think those were added on request for someone who had some use, but I don't recally what they were for and I don''t know who uses them. Evidently, whatever the original application was, it didn't include Elevator Trim. Sorry. Anyway, you say they could be READ? It looks like they are meant only to be written, as values which may or may not have any effect according to bits in 4A0. Either way, I'm not doing anything more with FSUIPC3. If this is needed for FSX / P3D I could consider it for FSUIPC4. Regards Pete

Since the only change between 4.90 and the previous version was the removal of the Signature, which is only checked on loading, I can't se how this can be related to FSUIPC. I think you need Air Hauler support to help. Regards Pete

Your question is a little confusing. Do you want the assignable control, or the writeable offset? Elevator control offset is at 0BB2 (just before the Aileron and Rudder offsets), and the elevator trim control offset is at 0BB2, just a little later in the list. Similarly you can find AXIS ELEVATOR SET and AXIS ELEV TRIM SET controls in the List of FS2004 controls, also just by searching for "elev". I think you need to find a new search program, because searching the PDF with either Foxit Reader or the Adobe PDF reader finds these things immediately! Pete

What's that "Local Disk" part? Surely you don't have your Program files folder in a folder called "Local Disk" on your C: drive? The original log you posted showed FS as being in C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X so why have you insertred that "Local Disk" part? Well of course. Why not simply delete FSUIPC altogether? You'd get the same result! Is "Razer Nostromo Keypad" a program, or a device? If it is a device, and has a bad driver, I suppose there is a possibility of it causing a hang in DirectInput when FSUIPC scans devices. I checked the link you provide. The Razer Nostromo Keypad driver appears to insert a bad Registry entry, which caused 4.90 problems when it scanned. This was fixed in version 4.902. We are now up to version 4.907. Perhaps you'd like to install that? It's only a matter of downloading the small Zip file from Download Links subforum and copying the DLL into your Modules folder. Pete

But programmed not only to repeat but to affect both COM1 and NAV1 standby and active, continually? Makes no sense. I'm afraid programming a button in FSUIPC cannot override a button programmed in FSX, and certainly cannot override direct control by a separate driver not using button inputs at all as this appears to do. Pete

All of FSUIPC's settings are stored in a Text file called FSUIPC.INI or FSUIPC4.INI. The format of the Buttons section entries is fully documented in the Advanced User's guide. Pete

The only possible cause I can think of is that somehow you got SimConnect classifying 4.90 as untrusted, so not to load it. Try deleting the entries in the [Trusted] section of the FSX.CFG, or maybe just put the latest version from Download Links into the Modules folder instead of the 4.90 main release so that it will ask again. Regards Pete

That surely cannot be the SimConnect.INI file you have created and saved!!! That is some binary file -- a graphics PNG file, like the picture you posted, by the look of it. This is going to take weeks at this rate! Start again, create a proper SimConnect.INI file as instructed in the FAQ thread I told you to go to, and make sure you put in the actual path to FSX rather than type literally "path to FSX". So far you don't seem to have done that simple thing. :-( Pete

Where is this button programmed, and to what? Pete

You posted a picture of the Properties of your SimConnect.INI file! Why? How's does that help me see inside it? Please stop posting useless pictures. If you want any assistance, paste the text fromthe relevant files in a message!! Pete

Please just paste the file here. It certainly looks wrong still, but as you say too fuzzy to be sure. An easy pathname to enter would be, say, C:\SimConnect.log to put the file in the C: root drive. The reason I prefer the Modules folder is that (a) I know it can be written to, some folders cannot, and (b) it keeps everything related to FSUIPC together. Looking at one of the Logs you supplied earlier, the path to the Modules folder would be: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Mofules making the file look like this: [simConnect] level=Verbose console=No file=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Mofules\SimConnect%01u.Log file_max_index=9 Is that what you set? If not, why not? Pete

No idea, sorry. You need a SIOC support forum. I've never used SIOC and know nothing about it. Is there documentation with it? I've always used Leo Bodnar's boards which are really easy to use as for inputs they emulate joystick buttons and axes which can be assigned directly. Regards Pete

You could have an L:Var which can be seen in FSUIPC, then have a Lua plug-in which reads that L:Var and write to the fuel offsets. Of course this needs a Registered install of FSUIPC too. Regards Pete

This is how PMDG implemented it. You have to send it controls ("events") to do things. You are confusing "Offset" and "Control". Controls are numbers sent to FS. Offsets are places in memory. NEVER mix the two, they are not the same in any way! FSUIPC offsets are 0-FFFF (0-65535 in decimal). Controls can be almost any number. If your "SIOC" device can only handle offsets you will have to make it set or toggle Virtual Button bits: see offsets 3340 and following. There are 288 bits available, allowing for up to 288 buttons. Then you can assign those buttons to controls in the normal way. Regards Pete

So, "K" means "KEY EVENT", as all of the controls have full names in the form KEY_XXXXX. Sorry, but the list of controls I publish is the complete list from FS itself. In FSX there is "FUEL DUMP TOGGLE", number 66651. I suppose you could try that number just in case, but it seems unlikely to be in FS9 as it isn't in the tables. Regards Pete

Please show me the INI file you used. I really find it hard to believe your system is that broken! Pete

Er, "path to FSX" isn't the real 'path to FSX', is it now? How is SimConnect going to write that file with such a bad pathname? Obviously you need to put in YOUR true path to FSX, not blindly copy the pro-forma file content! Pete