Pete Dowson

Right. In that case it sounds like something that gauge is doing. Is that gauge running at the time you try to load another flight? If so I am guessing that the gauge is stuck in a loop and not allowing the new flight to be loaded. Is this "vasFMC gauge" the same one you mention above as the "upper ECAM gauge"? If so then this confirms that there is a problem with that gauge. The install log doesn't tell me anything about FSUIPC running. I needed to see the FSUIPC log file. However, it sounds like that won't help much either. Is this vasFMC / upper ECAM gauge payware? Do the authors offer support at all? You might need to ask them for help on this one. If it is a freeware package and I can download it someplace then I could try it here for you. But I cannot really support nor fix other folks software, so the most likely way to move on this would be for you to contact them and, if they need help resolving it, they could contact me to discuss what is happening. Regards Pete

Er ... there should be no need! The ZIP file contains the Installer program and a PDF entitled "Installing and Registering FSUIPC". Surely that's enough of a Hint? Do you really need ANOTHER document in there saying "READ THE OTHER DOCUMENT FIRST". There is no Installing and Registering document INSTALLED, only the full user guides and other things. If you'd bothered to read the Installation guide you'd have seen all this explained. You don't have to look far when it was in the ZIP next to the program you extracted and ran! Where else do you expect me to put it? So nothing is using FSUIPC4 for anything? I thought you installed it because some add-on requested it? Just downloading it does nothing at all. You copy it into the FSX modules folder, exactly as it says next to the place you clicked to download it. That's what explanations are for! As I said."See if there are FSUIPC4.INI and FSUIPC4.LOG files in the FSX Modules folder." You seem to be ignoring or skipping over a lot of stuff put here to help! :-( you have Windows Explorer set to hide the full filenames from you, for those file types it things it knows. You should really change that or you will have problems with lots of addons. Explorer folder options, uncheck "hide file types" or whatever it is called. Anyway, an INI file is a type of "config settings" file. All CFG and INI files will list like that. And a LOG file is a type of text file. Yes, it's best to paste text files like logs into messages. Anyway, since FSUIPC is evidently running I don't need to see the Install log. Maybe the run-time log (FSUIPC4.LOG) would tell me something, but it is doubtful. If you are not running anything that needs to use FSUIPC, and you haven't purchased and registered FSUIPC4, then FSUIPC4 is really doing nothing at all, it is just sitting there receiving information from SimConnect (part of FSX). The only time I've known any crash happen just by receiving data from SimConnect is when there's a faulty weather file or bad WXSTATIONLIST.BIN file. This causes the crash in WEATHER.DLL, not in FSUIPC, and would happen in the same circumstances if anything read the weather. This sort of corruption can sometimes arise if you use the FSX default real weather downloads, because it seems these are not checked adequately by FS and can arrive corrupted from the website. The only way I could tell that is by getting you to make a SimConnect. logfile, but i think that is beyond your capabilities for now. If you've not used the real weather downloads since you installed FSX then it's not likely in any case. A way for you to check would be to delete all of the .WX files from the Flight Simulator X Files folder in your Documents folder, and also the WXSTATIONLIST.BIN file from here: C:\Users\Art1\AppData\Roaming\Microsoft\FSX Then run FSX. Next time you download real weather the latter file will be rebuilt. Regards Pete

I think you'll find that's the normal Windows check for you to confirm whether you think it installed properly or not. Windows has no idea one way or the other. so you didn't even look at the Installation guide included in the ZIP, the one which tells you what to do? Yes, the log is the same one which was displayed in front oof you, live, whilst the program was installing, and all the other files are those listed for you in the Installation guide which you didn';t bother to read. If there is no "Add-Ons" menu, the right-most one in the normal FS menu when you are ready to fly, then there is a problem with your installation. That is very unlikely. There are lots of possible reasons an FSX installation might crash. Without any other information I couldn't guess. Certainly, depending on the add-ons you run, the UIAutomation problem is one of them. Others often revolve around video driver problems, bad scenery files, bad terrain files, and so on. You'll need to supply more information. There is nothing at all in anything FSUIPC does which has ever been able to cause a crash to desktop. However, by all means update the FSUIPC4.DLL to the latest, so you are running the same one as me -- it is version 4.661 and it is available in the Download Links subforum here. To check if FSUIPC is even running, you should do several things: 1. See if there is an AddOns menu, and if so whether FSUIPC is listed in it. If not, then FSUIPC is not even loading and running. 2. See if there are FSUIPC4.INI and FSUIPC4.LOG files in the FSX Modules folder. If not then FSUIPC has never run. If there is a LOG there, show it to me. If these show that FSUIPC is not running, then show me the Install log and I'll tell you how to work out why. Regards Pete

Just remove the FSUIPC.KEY file from the FS Modules folder. If there's no KEY file it isn't registered, and if there's no INI file then it has never been run. Are you going to tell me there's no LOG file either? Because one of those is also always produced when it is run. There is absolutely and definitely an FSUIPC.KEY file there then. Maybe you are running Explorer with the folder option set to hide known extensions from you? When you uninstall a program with its uninstaller it doesn't remove files you added, only its own. You would have had to delete all the folders too after the uninstalling. Note that there is nothing stopping you re-registering. You don't need to unregister in order to register. Just enter new registrations when the FSUIPC installer offers you the option. Regards Pete

I'd need more information: especially the version number of FSUIPC, and a sight of the FSUIPC log file from the Modules folder. There is nothing FSUIPC is doing whilst FS9 is loading scenery. In fact it is not even able to get any time to run as FS keeps it all. What percentage does the progress bar get to? Does it say scenery, autogen, textures, traffic or what? Maybe it's actually got to 100% and would therefore be on the point of starting? The only interaction it might perform would be responding to requests from applications using it. Maybe one of those is instigating something which clashes with whatever is being loaded? Can you do a process of elimination, removing each possible FSUIPC client program or add-in? What additional DLLs apart from FSUIPC have you got installed in the Modules folder? Does it still hang without this "vasFMC" running? What is this "gaugewaring" thing you mention, and can you remove that to check? Dr. Watson? Does that still exist? BTW if you are not using at least version 3.98 I don't want to know. Even if you are you might want to first try version 3.989w, from the Download Links subforum here. Then at least you'll be using the same version as me. Regards Pete

There are no offsets in any dropdowns in FSUIPC. Are you possibly just talking about FS controls, the same as those you can assign in FS itself? If you could explain (1) what it is your 737 OHD macro file does (why not paste it here), and (2) what you expect it to do with "any of the aircrafts in FS9", maybe I could help? If this OHD macro is concerned with the overhead, as it sounds, then as far as I know there are no default FS9 aircraft which implement much of the overhead system in any case. In the case of the lights, then FS9 does support several of the lights directly by controls. And although you mention "any of the aircrafts in FS9" in your earlier blurb you say "POSKY 737-832 aircraft only". You also seem to contradict yourself where you say on the one hand (and here I'm substituting 'controls' for 'offsets' so it makes some sense): but then you say: So one the one hand none of them work, and on the other hand they all work? It cannot be both, surely? Please explain what it is your talking about and supply a little information and maybe we'll see what is going on. At present I'm afraid I cannot make any sense of your question at all. Regards Pete

Outside temperature at your house, or in the sim world? If the latter then it sounds very much as if you have some additional simulation going on there representing freezing brakes. Are you by any chance using one of Thomas Richter's add-on programs, like the auto-brake enhancement? Or possibly the aircraft model you are using is more sophisticated than you thought? Regards Pete

Ian explained things well, but additionally i should point out that a little reading on your part, of the accompanying Installation document, would have surely set your mind at rest and allowed you to carry on happily. You would have surely seen the red banner pronouncing: You do NOT have to Register at this time. In this case simply click the Cancel button to continue. Pete

Right. So somehow, just adding the VRInsight port, the initial value of that "Show or Hide" option is "Hide" instead of "Show". Hmm. That isn't right. I'm glad we found a work-around, but I'll be sure to fix that before the next update is put up. Thanks for testing. I'll go see if the same thing happens in FSUIPC4 on FSX too. [LATER] Yes, same for FSUIPC3 and FSUIPC4. I've fixed it here and will upload the fixed versions in due course. Maybe next week. I've got some other stuff being tested too. Regards Pete

No you didn't! You started a new thread called "TQ and offsets", with no contextual information, instead of looking at the reply i sent in your original thread with a different title. And I replied in the thread you started on this, and I did so a few hours ago now. Why haven't you bothered to look? I provided the thread's title in my last reply here! There's no way I can remember all the details of all the questions folks post. you MUST either keep in thread, in which case the context is clear, or restate the whole question every time, which is obviously a bit daft. Pete

Hmm. stanger and stranger. Yes, i understood that. I just wanted to know who was displaying it -- FSUIPC or Advdisplay. Good. I don't know that option. That is what I referred to, the one in the FSUIPC HotKeys tab. Have you not used that at all? Please try it and let me know. Pete

If it is "switching on and off" without you touching anything, then either the unit is faulty, or you have a conflicting assignment somewhere. You can enable Event and Axis logging in the FSUIPC logging tab and see the events occurring in the log. You'll need to then search for the instigator. Regards Pete

You sent me an email, or are you referring to another thread here? [LATER] I just peered down the list of threads and see you are the instigator of one entitled "FSUIPC and assignments with TQ". Is that the question to which you are referring? If you don't stick to the thread, how am I supposed to understand what you are talking about? Checking that thread I see I am the last one to contribute to it. Don't you bother you read your own threads? Please stay in thread in future. There's no way I'm able to keep track of multiple questions fired out of context. The whole advantage of Forum support is in the thread structure. If you throw that way you lose most of the useful characteristics of such methods of support. Regards Pete

Er, where? In this Forum? Pete

You've not calibrated the toe brakes correctly, and are engaging them on occasion when using the pedals for steering. You need to leave a good null zone so you have to really press them to engage them. Pete

Hmm. Strange. I don't know how they are connected -- they shouldn't be. But this entry is not the operative part. Don't you have at least one other [VRInsight ...] section in the INI file? If so please show it to me. This "red window" is the one built into FSUIPC, isn't it? It isn't the one which is provided by the now defunct "AdvDifplay.dll" is it? (Check your FS Modules folder for that DLL). Have you tried assigning a keypress to the HotKey option to toggle the window on and off? If not, please do so, and try toggling it on. It may just be initialising hidden. Or possibily, if the VRInsight section you didn't show is running a Lua plug-in, that may be hiding it. Regards Pete

When you say you couldn't find such information, where are you looking? Did you try searching the Offsets table, in the SDK documentation, for "fuel"? You'll find lots of references, all explained. There are separate values for each tank, which you'd need to add up for total. If you are only concerned with FSX there is a total provided, too. Regards Pete

All offsets are listed in the documentation in the SDK. I can look them up, but so can you. I mentioned one of them, but you need to refer to documentation to see how to use them, and possibly use FSInterrogate (included in the SDK) to work it out. Why are you using offsets in anny case? The levers are normally operated by the FS controls I mentioned. It should be a simple matter of assigning the switches accordingly. Don't the suppliers of your quadrant offer any support? Regards Pete

Well they are certainly wrong, and won't do anything if the fuel levers are set to cut-off still, as they will be unless you set Mixture Rich. Please do see the FS help on how to start jet engines. The use of Mixture Lean and Mixture Rich to operate the start levers has been a feature of FS for as long as I remember, at least as far back as FS5 if not FS4. Yes, those are they. They are the Mixture Lean and Mixture Rich controls in FS. If you have to program offsets look up 0890 for Engine 1, etc. Regards Pete

You must calibrate it without using the detentes first. The flaps up position is always the one giving the output of zero. You need an area of the flaps lever movement all giving an 'OUT' value of zero. If you mean the starter levers, 3590 and 3594 are most certainly wrong. They are the fuel valves which are normally operated automatically by the system when you move the start levers from "cutoff" to "idle". The start levers are operated by the Mixture Lean (cut off) and Mixture Rich (idle0 controls in FS. Have you never used them to start a jet engine in FS before? Yopu are surely not one of those who relied on the simple auto-starting options in FS? ;-) Regards Pete

Hmm. Strange that a parameter I though would be ignored actually does something. That's interesting. Quite often the parameters are used to address different copies, but I can't imaging there being another AP altitude register. Maybe a bug in SimConnect. Regards Pete

You most certainly should not have to run anything "as admin". That gives the program "elevated administrator" privileges, which are the those which only installers need. If you run any part of your setup "as admin" you have to run all of the programs which need to talk to each other "as admin", because windows prevents programs of different privilege levels talking to each other. However, there should be no reason you have to run any of it like that. BTW it is not a good idea to append a new message to a 3.5 year old thread which ended with the diagnosis that the person was using an illegal (pirated) key, and saying you have the same problem! :blink: Regards Pete

There's no such thing as those offsets -- they are FS controls, not values in FSUIPC offsets. 65892 and 3 refer to FS controls, just like those you can assign in FS itself, or in the dropdowns in FSUIPC. They are not "offsets", which are the hexadecimal addresses of values in the FSUIPC data and range from 0x0000 to 0xFFFF (decimal 65535 max). FS INC and DEC controls do not take any parameter in any case. They just do increments and decrements. You might as well just send the 4 bytes for 3110. I cannot tell what is going on from the information you supply. Please use FSUIPC logging so we can see what's happening in FS. Enable event logging. You should also set offset 3110 as a "U32" for monitoring on the right-hand side of the Logging tab. Don't worry about the parameter at 3114 as that's not used in the INC/DEC controls in any case. Regards Pete

The terms "course" and "OBS1" refer to one and the same value, as long as you mean the pilot's side course. OBS1 is the course set for VOR1 or ILS1, and displayed on the pilot's side, whilst OBS2 relates to VOR2 or ILS2 and the co-pilot's side. There are no "separate" PFC offsets for FS values like that. There are only the FS values, which my PFC drivers use, just as any other software working through FSUIPC must do for aircraft implementations which use FS intrinsics -- as almost all do for basic radio values such as those. All of the FS offsets supported by FSUIPC are listed in the documents included in the FSUIPC SDK. If the Aerosoft 737 systems program is not handling the FS value for course then it is in error, and you should be seeking appropriate support from the author. However, I would be very surprised indeed if Andrew has such a basic and elementary value incorrect. He did, after all, also provide the original drivers for the Australian Aerosoft hardware cockpit "GA28R", representing a Piper Arrow cockpit, and that most certainly has it correctly shown. (I am fortunate enough to own one such cockpit -- i think they only made five in total!) Please double check what it is you think is wrong, and then seek appropriate support for the software you are using. Regards Pete

Assign the button to LuaValue <name of Lua> with the parameter as usual! That's what the LuaValue control is for! The Lua plug-in named must already be running, of course, otherwise this will do nothing. You don't need to use "if ipcPARAM == 10" because the value is provided as the parameter to the function. So it the function is function J41buttons(param) The value is the param is "param". This is actually the same as "ipcPARAM" AT THAT TIME, but another button could change that. Er .. event.param() is a function! It tells FSUIPC which of your functions to call when the parameter is changed (i.e set by the LuaValue control). Please do look at the examples using events. I don't think you understand them yet! Also please look at the definition of the event library functions. You will clearly see that there's no such thing as "event.param" without providing the function name as, foe example. event.param("J41buttons") and that there is no return value to this. It simply sets up that function to receive parameter values set by LuaValue. Pete