Pete Dowson

Yes of course. SimConnect is independent of FSUIPC, and FSUIPC actually uses SimConnect for many things. You'd only buy WideFS if you wantred to run FSUIPC-using applications on a separate PC. You don't need it for SimConnect applications. Pete

I'm afraid I cannot fix SimConnect problems. But your message at least provided more information. As noted earlier in the thread I could not reproduce it, but then I was not given sufficient information, and the OP, a "garyhall2530" took the huff and left here with a sercastic comment, making me ignore the thread subsequently. In particular you said: Why would you use FSUIPC's winsd smoothing in DWC mode? DWC mode gives ActiveSky absolute control over the winds in any case, so it can do the smoothing itself. The only use of FSUIPC wind smoothing is for localised WX station weathers which set conflicting winds and the bugs in FS's weather engine mess up during interpolation. I think it gets a sign wrong somewhere, or uses a cos instead of a sin, etc. Would the actual altitude be 16384 metres by any chance? i.e. 53,753,28 feet? Because if so it would indicate something being stored in a signed 16-bit word and going negative. Not that this helps me -- I've certainly checked for any altitude dependency in the FSUIPC smoothing actions, and there is none -- the altitude isn't a factor in any part of it EXCEPT for avoiding the smoothing of surface winds if the SimConnect "on ground" flag is set (i.e. even that doesn't use altitude, only the "on ground" flag, put in offset 0366). Also, if there were such a problem in that code it should affect the winds no matter who set them and in what mode. The FSUIPC smoothing is a "hack" which hooks a call from the Weather DLL into the SIM1.DLL and changes the winds being set at the aircraft before they are actually implemented. The way they get set doesn't come into it. It's a mystery, but i don't know how I can help and I don't really know why it becomes a problem in DWC mode where smoothing shouldn't be needed in any case. Regards Pete

Which Paul is that? Can you point me to the helpful answer? Pete

Sorry, I don't really understand this bit. What is "Windows Problem Reporter" and how does it interact with a running program which is quite happy? Nor me. How does this relate to the Windows Problem Reporter? Pete

Ah! Sorry, I failed to notice this in the original Installer log you posted: FSUIPC will not run if it beleives itself to be corrupted, which is what it assumes if the signature doesn't check. If you right click on the FSUIPC4.DLL itself, select Properties - Digital Signature, then select the Simflight signature and Details, it should say the signature is okay. if it doesn't then either it isn't a good copy, or, more likely, your Windows installation isn't running the required decryption and signature checking services. You aren't stopping some default Windows services running, are you? Googling Windows error finds things like "Trust verification failed" and "The certificate was explicitly marked as untrusted by the user.". The FAQ subforum contains a couple of threadsa which might help. see One solution for "My signature check fails on the installed FSUIPC4.DLL. (Error 80092026)" and Help with FSUIPC4 code signature problem Again, apologies for not noticing this error earlier. Regards Pete

sorry, I am completely unable to explain any more simply than saying what I said. Bit 0 is the bit worth 1, bit 1 is the bit worth 2, and so on., Each higher bit is worth twice the previous one, so the top bit in a byte, bit 7, is 128. how else can I explain it? Try a simply maths course. Try 2 x 2 = 4, 2x 2 x 2 = 8 ... etc. It is that easy, really! surely much easier than learning how to use flight simulator at all? Pete

The settings are saved in the FSUIPC INI file and reloaded each time. How are those being lost? It makes no sense! Did you write-protect that file, or are you deleting it? Look at examples. There are many provided in the FSUIPC Documents folder along with the documentation, and the User Contributions subforum here provides more. Regards Pete

What exactly are the symptoms? No Addons menu, or just no FSUIPC entry in it? Still no FSUIPC4 log? Are all of the other DLL entries running and working? i.e. FsPassengersX A2A Feel AccuFeelMenu FeelThere ERJX Helper FSCopilot Try, temporarily, renaming that DLL.XML, so it is ignored, and re-run the FSUIPC4 installer. If that works then there's some sort of conflict with one of those other Add-ons. If it still doesn't work, and/or those other add-ons don't load, then you have a problem with the SimConnect installation. That gets very complicated ... Pete

The only way short of doing some Lua plug-in programming is to assign the same controls to both "press" and "release". Encoders send a sequence on "on" and "off" signals. Assigning to both will double the speed. There's a drawback, though. It might be difficult to get to the exact value you need to set. Regards Pete

Bits in a byte are normally numbered from 0 to 7, with bit 0 being "worth" 1 (2^0 = 1) up to bit 7 worth 128 (2^7 = 2 x 2 x 2 x 2 x 2 x 2 x 2 = 128). If you "found" "bit 7" is 0x40 (which is 64, hex 40 = 4 x 16 + 0 = 64) then whatever you are reading is numbering bits from 1 instead of 0, which is very non-standard. The FSUIPC SetBits and ClrBits controls allow you to set and clear one OR MORE bits all at the same time. The parameters for them are NOT "bit numbers" but numerical values providing the 'masks' (as they are called) of bits to be set, or cleared. So, as an example: x55 (or decimal 85), which = 0 1 0 1 0 1 0 1, means bits 0, 2, 4, and 6. So such a 'mask' will set or clear all those 4 bits. It is much more flexible (i.e. more powerful) to use masks in this way rather than bit numbers, which can only specify one bit. Please also see the FAQ on numbers, bits etc. Pete

Before it got that far did it take a while processing your scenery layers? If so then it is processing okay but failing to write the results -- probably because your FS folder is protected. Try running it "as administrator". If it didn't spend a while scanning then maybe you are not even running it from the FS folder? Oh, and make sure you run FS at least once first, else the scenery.CFG file is not where it should be. Pete

That looks okay. Certainly FSUIPC4 should load. If something then went wrong I'd need to see the normal Log or something else. What about the one you are using now? Note that the "old version" loads these other DLLs as well as FSUIPC4: FsPassengersX A2A Feel AccuFeelMenu FeelThere ERJX Helper FSCopilot BTW I seem vaguely to recall there was some conflict years ago between FSUIPC4 and FSCopilot. One thing to check is that the latter is up to date. It might be good to make sure FSUIPC loads AFTER FSCopilit. That can be done by moving this section to then end, just before </SimBase.Document> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> regards Pete

It's only another text file, like the Log you posted. Just load it into Natepad or whatever and copy and paste as I assume you did with the install log. Ah, that would explain the discrepancy between the DLL.XML and your Modules folder contents. Probably he changed it to stop FSUIPC4 loading. It it worked, why not use it? If it doesn't then it maybe just as bad as the current one, so post whichever one that doesn't work for me to look at and fix. Good. Then the problem is very likely to be a bad DLL.XML rather than something more serious preventing the Add-Ons-FSUIPC menu being added desptite FSUIPC running. An alternative to posting it here is to simply delete the existing one and re-run the installer, so that it makes a new one from scratch with only FSUIPC4 being loaded. This is okay if you have no other add-on DLLs being loaded. If you are not sure, don't do this -- the fact that you got a member of your VA to even look at it does imply there's something more you are using. It is often the other DLL installers which mess up the DLL.XML, not thinking that there might be others needing entries. Regards Pete

Yes, that's what I need to see, but you forgot to paste it into your message! It is not installed by the installer program, only provided in the ZIP (in case of specific difficulties). You must have copied that in yourself. It isn't a good idea to do things like that without at least knowing why. It is all clearly explained in the very short Installation guide, provded for you to read BEFORE doing anything! Anyway, it seems you placed the Loader into the Modules folder AFTER you ran the installer, as this shows: So, although it is currently not doing anything, please remove the loader from the Modules folder to avoid future confusion and problems. Also, please do read the little bit of essential documentation provided. It won't take long, really! It's a little odd that the installer found that there was no previous version of FSUIPC4 installed in FSX itself, yet there was an existing entry for FSUIPC4 in the DLL.XML file. How did that happen? Did you delete FSUIPC4 from a previous install? Was there no FSUIPC4.LOG file in the Modules folder? Regards Pete

There's the problem. FSX is not compatible with the later versions of that DLL. You can put the older one into the FSX main folder and it will use that instead. You'll find this problem and solution discussed on the AVSIM FSX forum, just search on uiautomationcore. Pete

There is no difference possible in FSUIPC between windows 7 and Windows 8. it doesn't use anything specific to either -- it cannot as it needs to run on everything since IXP, so I imagine what is up on your system. But bearing in ming that FSUIPC is a SimConnect application, it may be that your SimConnect subsystem is screwed up somehow. The Modules folder is not an original part of FSX, it is created by FSUIPC's installer. Nothing placed in there will run unless something else changes to make it run -- the FSUIPC4 installer adds the path to FSUIPC4 in the Modules folder by adding it to the DLL.XML file. Check that for other add-ons being loaded. I'm sure it cannot be specific to the 'Modules' folder, which is a misleading diagnosis. Try downloading the very latest interim update from Download Links subforum. And when you get a crash please find and supply the crash details. In the Windows error logging you will find the name of the module which crashed and the place within it. If it is in FSUIPC4 and you use the very latest (4.869) then I should be able to help a little more. Regards Pete

Ok, thanks! Pete

FSUIPC cannot decide whether to load itself. In FS9 and before it is loaded by FS itself, in FSX and Prepar3D it is loadedby SimConnect as a result of an entry in the DLL.XML file. So, is this FS9, FSX or Prepar3D? What is the version number of FSUIPC please? Check the Modules folder in FS. Is there an FSUIPC log (or FSUIPC4 log) file? If so please close FS down then see if the log is current and show it to me (copy and paste it into a message.here). If this is with FSX or Prepar3D, then find the DLL.XML (it's inthe same folder as your current FSX.cfg or Prepar3D.cfg file). Copy and paste that here too. If that has been corrupted (and quite a few add-on installers seem to do this) then it can stop FSUIPC and other add-ons being loaded. Reinstalling rarely achieves anything as it is only replacing the DLL in the same place with the same DLL. Sometimes it can re-add FSUIPC to a DLL.XML screwed up by another installer, or even create a basic DLL.XML if the proper one has gone missing, but that's probably a long shot. Regards Pete

I'm lucky in that I use a projected display, seen through my cockpit window, and can't easily see the top of the screen, not without leaning forward and craning my neck up! I suppose you could always use Windowed mode and enlarge it enough so you could drag that part off the top of your screen. That would make menu access a bit awkward though. Regards Pete

Before memory problems get as far as a reported OOM, things start to go wrong in other ways -- memory corruption for example. Regards, Pete

No, not really. The FSX real weather download only unpades the WXstation list file. WX files are part of normal saved flights, and FSX always loads one initially even if you then don't use the weather so loaded. Files becoming corrupted on disk don't have to have originated with bad input data. Maybe just a glitch or interruption when writing, or in memory corruption somehow before writing. There are a number of bugs still in FSX which involve some sort of memory corruption (the G3D error crashes are one possible result of these). Just delete the WX file associated with the default flight, and don't load any other flights. See if you still get the problem. Pete

It's the other way around. FSUIPC is a gateway for information from FS. Linda has to monitor the information using the facilities FSUIPC provides. FSUIPC is passive, not active, and responds to requests. It doesn't initiate them -- that's the job of applications and Lua plug-ins. Regards Pete

Aha! That explains it. As you'll notice from the keycode list in the FSUIPC Advanced User's guide about page 15), 226 is not (was not) a normal key -- certainly not one I knew anythng about as a 'graphic' key. I've now obtained an updated list and find these extra keys defined since FSUIPC was first written (1999): VK_OEM_AX 0xE1 // 'AX' key on Japanese AX kbd 225 VK_OEM_102 0xE2 // "<>" or "\|" on RT 102-key kbd. 226 VK_ICO_HELP 0xE3 // Help key on ICO 227 VK_ICO_00 0xE4 // 00 key on ICO 228 I'll add these in an update for FSUIPC4. It'll be next week, though. I'm tied up now till monday. Regards Pete

On the UK keyboard that's the \| key. Assuming it gives the same Windows key code then FSUIPC must see it. In fact I think FSUIPC handles all known graphic keycodes -- see the list in the documentation. Go to http://whatthekeycode.com/ and press the key. Here the key in that position is 220. That works here, but of course is displayed as "\| key". See what number yours is. I cannot imagine it is a keycode not covered by FSUIPC's list, so I am pretty sure something else is capturing it first. Tell me the number. Regards Pete

Before FSX, Flight Sim always generated a flight called "Previous Flight" on closing, so that you could set that flight as your default and always start off where you left it. Because FSX didn't do this I was asked if FSUIPC could do it. and it does try to do it -- this relies on it receiving a call from SimConnect saying that it is disconnecting with enough time for a call back by FSUIPC to actually initiate the flight save before it is too late. This usually works okay, but i think if you "end flight" first there's no flight to be saved -- you've ended it! Weather DLL crashes are usually caused by faulty data in the WX file, or by a corrupt weatherstationlist.BIN file (the latter is in the same folder as your FSX.CFG file). You can try replacing the latter with the default, which I think you'll find in the FSX weather folder. Corrupted WX files are usually caused by faulty downloads of real weather by FSX, from the MS weather site. If it occurs even when you don't explicitly load a flight, the problem can be down to the WX file first loaded, as part of your default flight. It doesn't then matter if you change it or load another flight, the damage is done. Either change your default flight or find it and delete it's WX file. Since even a corrupted file cannot possibly have any affect unless it is actualy read back (any old rubbish can be written, it affects nothing if never read), I think your conclusions are incorrect -- unless you are actually loading the "previous flight" or have it as default. Certainly I think it likely that some flight you are loading has a corrupted WX file. That wouldn't make any difference if you are still loading flights. If when you are using ASE you are not loading flights, then that may explain it, provided the problem is not in the default flight. Regards Pete