Pete Dowson

No, it doesn't matter at all, not in any Windows INI or CFG file handled by the Windows private profiling system like all my INI files and also FS CFG files. Pete

A photograph? What's the point of looking at a real aircraft panel if it is not implemented in FS? Since it seems the switch is not implemented in FS, you'd need to simply wire the switch to do what you want wth your own G1000 build. If you mean you want the FS G1000 gauge to come alive when you operate that switch then I think it would have to just switch on the main battery and avionics switches because otherwise how it the gauge to know to come alive? The only alternative, assuming you aren't building your own G1000, is to make your own gauge which does obey some switch, for which you could use a User offset. Regards Pete

You should simply state the problem. No way can FSUIPC change the brake axes when you simply disarm the autobrake. PMDG are fobbing you off. If you want me to look at it I need to know a lot more. Most things in the NGX do not use standard FSX controls at all, so I assume the same is true of the Autobrakes, and i have no idea what you are doing there, but if setting A/B = 0 applies brakes there's something wrong with that assignment or a bug in whatever is applying autobrakes. I suggest you use FSUIPC's logging facilities. First make sure your FSUIPC is up to date. The currently supported one on FSX is 4.91. Enable button logging and both normal and axis event logging, but Not until you are about to "vacate the runway and set AUTOBRAKE to zero ..." I suggest you get to that point, pause, enter the FSUIPC options and enable those logging items, OK out and release pause, do your thing, then pause and turn the logging off. If you don't do this there will be far too much logged to make head or tail of. I am away after tomorrow (Wednesday) till Tuesday next, so if you can't get back with this within a day it's going to have to wait. Regards Pete

FSUIPC is running if there is an FSUIPC entry in the FS Add-Ons menu. If by "wouldn't that of ..." you mean "wouldn't that have ...", the answer is not necessarily, if the file was corrupted before the part where the FSUIPC entry is added. Squawkbox3 on FS9 uses FSUIPC, but SB4 on FSX does not, it uses SimConnect. I can't do that without seeing it. You'd need to paste it into a message here. But first see if FSUIPC is actually running. Also tell me which version, and check the FSX modules folder for an FSUIPC4.LOG file. Paste that in a message if ithere is one. Pete

First off, a general comment on your code. It is extremely inefficient. The whole point of separating the build up of read/write requests from their processing was to reduce as much as possible the process switching and message queing. You should do ALL the reads and writes you want to do in a batch, then call the Process function, one Process call per cycle. On the question about G-Fprce, why are you reading the offset 11B8? The documented offset for G-Force is 11BA. You should check these things. Regards Pete

You simply read the byte or word or whatever and use the logic function And to test the bit. So the test would be: lights = ipc.readUW(0x0D0C) if logic.And(lights,2) ~= 0 then ... end I am 70 this month, but i'm always learning new things. It's what makes life interesting! ;-) Regards Pete

I am not aware of any standby battery simulation in FS at all. All of the possible FS controls are listed in the assignments dropdowns, along with a lot of extras added by FSUIPC. I've just looked at the default G1000 and don't see anything lablelled as another battery switch. How do you operate this standby battery now? If there is one it is probably completely local to the G1000 gauge and therefore probably only controlled by its graphic. Pete

I moved your Support question to the Support Forum so it can be answered. You posted in the "FAQ" subforum, which is a repository for information, not support. I don't know what "QAR" is, but why program it to wait for a button click if that is not what you want? Surely, as the programmer, it is up to you how you do things? It sounds like you are either not using the standard code supplied by the FSUIPC SDK, which includes a timeout on requests, or you are ignoring the error reports when the requests do time out. Well, all the programs I know of do so easily enough. Connection and Read and Write requests all include timeouts, and return errors upon no response. Simply take notice of the errors, wait a little while, ad try again. On a read/write error if the connection is not okay within a few seconds of retries, assume the connection is lost, close it and try reconnecting -- again with timeouts, short waits and retries. It is all simple error detection and correction. Regards Pete

No problem. Thanks for confirming. I'm uploading version 4.91 today, with an updated Installer and documewntation (minor changes only) as well as the free-standing DLL ZIP. This will then be the current supported version. Regards Pete

No. It works perfectly here and it was a very simple fix. I suspect you've not updated in the correct place. Turn on 'event' and 'button/keypress' logging in the Logging tab, test again, and paste the resulting log in a message here. Pete

I think you must have some sort of conflict going on, then. Go to the Logging tab and enable Axis logging. If you put FSX into Windowed mode temporarily, and enable the Console Logging option, you will be able to see exactly what is happening. The spoiler axis has always worked perfectly except for the on-the-ground auto action. There is nothis weird or different about it otherwise. Regards Pete

It is not FSUIPC supplying a detente, it is FS. The detente is the "ARM" position, and it operates over a fixed region of the % deployment of the spoiler. It sounds like you are trying to test this whilst on the ground. FS has a nasty habit of deplying 100% if you arm it whilst on the ground, as if you've just landed. There's no way with a continuous axis of moving smoothly from 0 to 100% without passing through the Arm region, so the ONLY way of calibrating or testing your spoiler axis is in the air. Regards Pete

It'll check and if necessary update both FSX and Prepar3D. Also ESP if you had that. You could register again, but if you are going to then copy your FSX modules folder over there's no need. The KEY file will get copied too. If you can wait till tomorrow version 4.91 installer will be available. I'm preparing it for upload now. Regards Pete

No "tutorial" is needed. Instrictions are in the Installation guide included in the main ZIP! Just run the FSUIPC4 installer. That will set up the DLL.XML file and so on. For your settings just copy the FSUIPC4.INI file over from FSX. There is nothing specific to FSX in the INI file. If you have macro files, Lua plug-ins and so on, copy them too. In fact there is nothing wrong with copying the whole FSX modules folder over. But run the Installer first to get things set up! Pete Pete

Sorry, I don't know what this is about. Is there a question here for me to answer? Regards Pete

If what you are showing is the only [buttons ...] section,d and it is the active FSUIPC INI file, and you have either pressed the Reload button since changing the INI file or closed and reloaded FS, then there is no record of button 72,7 left and no way possible for FSUIPC to attribute any action to it! It cannot invent these things by itself, so it sounds to me as if you've changed the file and not told FSUIPC to re-read it by pressing the Reload button. Pete

But that IS the "actual" button entry!!! It is how a conditional button action is recorded. If there were another entry for the same button ythen the action it defined woyuld NOT be conditional!!! That is almost the SAME as this: 92=CR(+72,0)72,7,C66704,1 but without the Repeat action ® and without the condition that 72,0 must be pressed. Why would you want it to send control 66704 once when 72,0 is not pressed, but twice when it is pressed? If that is what you want, just at the extra line. If you want the conditional equivalent of "120=P72,7,C66704,1" you would have 120=CP(+72,0)72,7,C66704,1 i.e. the same as your line 92 but with 'P' for 'Press' instead of 'R' for 'Repeat'. Please please DO read the documentation which explains the format of button definitions, then when you mess around you might understand what you are doing. Okay? Correct, exactly as documented. The dialogue is only suited to normal simple programming. Once you start messing with multiple actions and conditions it is an INI file editing job. Pete

But it IS listed in the [buttons] section with the condition! You even highlighted it in RED: That IS the assignment to 72,7 with the condition on 72,0 being pressed included. What did you expect it to look like? You also have two assignments to 72,0, apart from its use in qualifying 72,7: The odd thing is that your conditional 72,7 assignment seems to be to "APU Starter" with a parameter of 1 (does that really do anything?), whilst releasing 72,0 does an "APU Off Switch". It looks to me that one might cancel the other. You say that but you need to realise that FSUIPC doesn't change by iteself, nor does your INI file setting. I've no idea what you mean to do with these assignments (they make no sense to me), but whatever it is if it changed then it is because you changed something. Regards Pete

FSUIPC4 applies wind smoothing to any weather, from anywhere, when enabled. I think this can be defeated as it is timing dependent, but not with normal weather programs which update weather at relatively infrequent intervals. I'm afraid I don't know REX Weather. The programs I use are either ActiveSky 2012 or OpusFSX. Both are excellent weather providers. First make sure you have wind smoothing enabled in FSUIPC. You shouldn't need to turn anything else on. If you are experiencing unwanted turbulence or variance you could opt to suppress those too, but that shouldn't be necessary. Second, check what options there are in REX Weather -- you don't want the weather yupdating too often. Every 15 or 30 minutes is certainly adequate. weather reports from the Internet won't be that frequent in any case. If there are still problems I can only advise you to seek help or opinions in the REX support forums. Yours surely can't be the only such experience? [LATER] I checked on the REX support site. This thread seems to say that FSUIPC does fix your issue: http://www.realenvironmentxtreme.com/forums/index.php?/topic/25279-wind-stable-but-no-turbulence-its-too-stable/ He has the opposite problem now, probably because he told FSUIPC to suppress turbulence too. There's also this thread: http://www.realenvironmentxtreme.com/forums/index.php?/topic/26225-massive-wind-shifts/ which implies there is a wind smoothing option in REX too, and an SP2 update which helps. Regards Pete

Good. thanks for confirming. Pete

I'm sorry, but I don't understand what you are saying. On the one hand you say you have a problem with the drop-down assignments list, but then you say you actually did manage to use it to assign things. Which is correct? What is the problem with the list? What is "ohd" (overhead display?) And if the problem is in assigning some things, why would wiring come into it? If you are actually saying it is a problem of your aircraft or FS not obeying specific FS controls, and not actually a problem with either the drop-down list or with making assignments, please provide more information. Which aircraft and which specific controls (by name)? FS itself does not have runway turnoff lights at all, so I assume you are using some additional controls provided by PMDG? Probably the PMDG aircraft uses separate autobrake implementation from FS as well. You can also check for yourself whether the controls are being sent correctly by going to FSUIPC's logging tab and enabling Event logging. If you are concerned instead about whether your switches or buttons are working, enable button logging. Operate the switches then check the FSUIPC.LOG file in your Modules folder. Regards Pete

The full install package on the Schiratti site downloads and unzips fine here. And consideriing it is THE main site to which everyone is pointed by the SimMarket purchase page and the ZIP file there hasn't been changed for nearly three months, I'm sure others would have reported a problem if there was one. I've just downloaded it and unzipped it myself successfully. I assume you did make sure you weren't getting a cached copy? Use F5 or Ctrl+F5 to ensure you remove cached copies. As well as the interim update 4.909 available in the Download Links subforum here, there is another copy of the full Install for 4.90. Did you not try that one? It is, in fact, a different file -- the one on the Schiratti site is "FSUIPC4.ZIP", a generic name so I can update the actual file without having to disturb the busy Mr. Schiratti, whilst the one on the Download Links subforum is "Install_FSUIPC490.zip". The contents of both are identical, however. Regards Pete

Well, yes, but what was confusing me, and still does, is why you are using key presses for buttons and not just programming the buttons directly. Regards Pete

Okay, I understand that part. Okay. i understand that bit too. This is where it doesn't make sense to me. You found the control for assignment, you said that already. Where does this "Ctrl Shift Z" come into it if you are using a joystick button? Can you elaborate on what you mean here by "I did not find choice"? Choice of the correct control to assign? Or what? Regards Pete

I don't know what the CRC Error it reports means, though. You'd need to ask PM. Regards Pete