Pete Dowson

Ah, that partly explains it. When you install FSX-SE without a prior edition of FSX, it installs to look like FSX. If it thinks FSX is already installed, it installs as FSX-SE. Your first install would have looked like FSX to the second. Always uninstall between install attempts. Mind you, it doesn't really explain why the later one (looking like FSX-SE) was in the normal place, Steam\steamapps\common, whilst the original, looking like FSX, got into SteamLibrary\steamapps\common. Unless you chose such a place. Pete

Sorry, no. That's very odd. Are you going to the right folder? Look at the FSUIPC4 log file, it will show the correct folder path in the entry starting "FLT UNC PATH = " or similar, right near the beginning. It is P3D which actually saves the files. FSUIPC merely generates a filename and sends the request. Pete

Well you certainly have Steam and SteamLibrary, presumably both with files in, including Steamapps\common\fsx. the Registry says they are both their, one labelled as FSX the other as FSX-SE. FSUIPC4 installed into E:\SteamLibrary\steamapps\common\FSX\Modules, so if you don't boot from there it certainly won't run. You actually have FSX as well? In which folder. Both registry entries, the one for FSX and the one for FSX-SE point to (different) Steam folders. Surely you don't have FSX in one of those two? Yes, I think you need to uninstall both copies of FSX-SE and probably try to do the same for FSX, if it is uninstallable. Else it might need some registry editing. How did you arrive at this mess? Pete

Just use an entry in the [Programs] section of the INI file. See the section entitled Programs: facilities to load and run additional programs on page 38 in the Advanced Users guide (it is also listed in the Contents). Pete

The DLL.XML only contains IVAP's entry. None for SODE. So I don't know why oyu are seeing one but not the other. I suspect you are getting the DLL.XML from the wrong place, as FSUIPC's Installer certainly added it to this one: C:\Users\Max\AppData\Roaming\Microsoft\FSX-SE\DDL.XML But maybe your FSX-SE isn't loading this. The line: in the Installer log indicates that, though you have both FSX and FSX-SE registered as installed in your Windows registry, they are both FSX-SE. Furthermore you appear to have TWO distinct installs of FSX-SE, and I think you are loading the wrong one. the two are in these folders: .. >>> OK! FOUND FSX! <<< ... SetupPath=E:\SteamLibrary\steamapps\common\FSX ... >>> OK! FOUND FSX-SE! <<< ... SetupPath=E:\Steam\steamapps\common\FSX See? You have files in "SteamLibrary" AND files in"Steam"! A bit of a mess really. Try loading the other one. Pete

Interim versions are found in the Download Links subforum above. They are the DLL only, no installer. You still need to run the latest installer first. Interim versions are supplied to fix or assist with certain bugs or other user needs. A full installer version is only released when made necessary, usually by a Sim update (as in the relatively frequent P3D releases). Why do you think that has anything to do with FSUIPC? First off, a correction. SimMarket do NOT have any versions at all, only a link to the latest installer, which is also available here. The Download Links section will tell you what interim versions do for you differently. FSUIPC uses SimConnect. It's the main interface used by most add-ons since FSX and applies to P3D too. There's a recent entry in the FAQ subforum describing FSUIPC and SimConnect relationship. Pete

Actually, The fact that this may be of interest to others has led me to put a copy back into the FAQ subforum...., for future reference. Pete

MOVED FROM FAQ SUBFORUM (Please always post support questions to the support forum. The subforums are repositories for reference data) Almost all by asking SimConnect to supply it. (Before FSX, FSUIPC had to get the data from all sorts of places in memory, found by research and disassembling parts of FS). SimConnect is a part of FS, built into the code, and written by the same guys who wrote FS. How's it not going to have access and knowledge about everything? After all, they had the source code! The "SimConnect.dll" installed with FS is NOT SimConnect itself, it is just the library of functions, and all of them communicate with the code inside FSX -- either by TCP/IP protocols or by named pipes (or memory sharing, much like FSUIPC with external applications. Local variables are variables local to the code of specific Gauges, accessed through the Panel interface using names preceded by L: The term "offset" referes to the number of bytes from the first one in an area of memory which contains all the data extracted by FSUIPC and made available to its client applications. Similarly to receive data written by those clients to act upon. The model derives from methods invented by Miicrosoft in FS95 and FS98 days, and originally referred to locations in an FS module called "GLOBALS.DLL" which was its repository of data used throughout the Sim. As FS developed, and started to use C++ and Object Oriented methods, these all disappeared into their different modules and became effectively sealed off from each other. FSUIPC then had to try to find itall and collect it back into its own equivalent of that "GLOBAL" area. By doing this throughout all the versions of FS from FS98 to P3D (including CFS1 and CFS2), it maintained forward compatibility for many applications -- which was the prime objective. FSUIPC uses SimConnect for about 99% of its needs. I had assumed that gradually all applications would use SimConnect directly, rather than go via FSUIPC, and many do. But some still use FSUIPC a lot, and it has other uses for things like assignment and calibration, so it keeps being maintained after all these years. Pete

Sorry, the message isn't from FSUIPC. I don't know what it means about "FSUIPC sdk" as there's no need for anyone except programmers to have or use the sdk. I didn't even know IVAP used any part of FSUIPC. I think you need their support. Pete

Sorry, I've no idea. I don't know anything about either. Pete

Corsair Hydro H80i V2 cooler. I think my temp stays much lower at present, but I'll check when it's under load. Pete

Aaaarrrrggghhh! The upgrade doesn't work! Takes several minutes, reboots, gets near 100%, then says it couldn't do it and that it's undoing it all! Checked with the suppliers and they confirmed there were issues with upgrading in situ, and that the only way was a re-install from disk or USB stick! Grrr. This means I'm back to square one, with another 48 hpurs work, minimum! :-( They did say they clocked it to their "maximum safe" level but I was welcome to try a bit more and it wouldn't invalidate the warranty (5yrs, worth having!). So, by system is going to be off for probably at least another week. Pete [LATER] Microsoft Tech Support have tried to do the upgrade too, and failed. They've escalated it and they'll cann me back on Friday (I'm out all day tomorrow). What a fiasco! You'd think this Windows stuff would be pretty smooth and advanced by now!

Ah, yes. That might explain it. They installed the Home edition -- I think most system builders use Home. All my Win7 installations are Ultimate. I figure one of the biggest differences for me has been the ease of getting networks uo and running properly. So, I'm just upgrading the Home edition of Wn10 to Pro at the moment. (You can do that in situ, from settings, it seems, using a Microsoft Store account). Not heard of that one. Is that above or below Professional? This is similar, but they set the clock for 4.4GHz instead. I was hoping for 4.6. It's with a 1080 video card and, yes, 3000Mhz RAM (but they put 16Gb in, which is a bit of overkill). However, I'm very pleased with the performance on the few tests I've done so far -- a lot faster than my ex-current one of 3 years vintage, even though that's clocked at 4.5Ghz -- but I might ask them what the problem was going higher than 4.4. Did you overclock it yourself? This is an Asus Z170 Pro Gaming mobo. Pete

I don't mind with AS16 because I run that on the FS PC in any case. But I'm using a Network of 6 PCs for my cockpit, and the SimConnect connection is used to at least 3 of those for applications such as Prosim737, ProATC/X and FS-FlightControl (or Aivlasoft's EFB -- I use them interchangeably). The setup's dead in the water if I can't make that work. I've never had any trouble between Win7 PCs or Win7 and XP. I know all the ins and outs of the SimConnect.xml and SimConnect.cfg files. There's something else going on here and it's driving me crazy. So, if you do have some suggestions, please, I'd love to see them! Pete

The problems I have are nothing to do with security, spyware, etc. And the Networking is fine for everything else - wideFs, shared folders, etc. It's onlt SimConnect over a Network Pete

Well, I can't get SimConnect working across the network between any of my other PCs (all on Win7 Pro) and this PC which is on Win 10 Home. That's the main problem. And it's crucial. Once that's fixed the other problems I can probably fix. `Pete

The only way I can work out why it isn't working is to test it on my own system. But I'm in the middle of rebuilding that at the moment on a new PC. Unfortunately the suppliers put Windows 10 on it (no choice offered) and that is causing me no end of headaches and loss of sleep. I've been trying to replace Win10 with Win7 (which I like a lot better and never had any problem with), but I'm having no success with that yet either. The booting of the Win7 installation needs USB drivers which I have but which it won't read! So, sorry, I've no idea when i can get you your problem. If you don't hear from me in a week, send a reminder. Pete

I see one error I made. See if fixing that helps. The '\r' in this line: mycopy = string.sub(mycopy,1,x) .. '\r' .. string.sub(mycopy, x+1) should be "\r" (i.e. double quote characters, not single. Sorry. I'm pretty distracted right now, overloaded with other things. Pete

Okay. It isn't crashing then. And it thinks it is displaying things. Additionally, changing the bit for window w2 (the FSX message window) won't affect the others, so I think something else is now wrong. Perhaps you should show me the Lua program, as it is now. Pete

Not the WideClient log. When you use plug-ins on WideClient they each make their own log, with their name. Pete

You are not reading all of my messages! The results you are getting means that the Lua program has crashed. I told you: "Always check the Log file (in the same folder) to see if any errors occurred. " Do that, please. Surely it isn't hard to find a file and look at it, even show the contents here so I can see why? Pete

No, it is a right mess still. You evidently aren't selecting the right option. You want this one: Actions menu -> Reset area and layer numbers and reorder the file Sorry, I don't know what you mean by this. If you mean the Runways.txt file, it logs all the data (and more) that it extracts from AFD files properly discovered. Pete

Since the addon scenery\scenery is always in the default part of the SCENERY.CFG file, naturally, with that part of your CFG file still being okay, it will always get scanned. The problem will be discontinuities in the numbering later on. I haven't got time to look at your SCENERY.CFG file yet -- probably not till the weekend -- but meanwhile use the Scenery Congi Editor to get everything all numbered in sequence. Then try to keep it that way. There are many other programs which would be affected by a numbering mess. I would be surprised if FS wasn't (I don't think FSX or P3D would like it) but maybe FS9 was different. I can't test that as I haven't had an FS9 installation for years. FSX is old enough (11 years now!). Pete

Does MakeRunways scan your missing layers now? MakeRunways uses standard Windows functions to read the file, so if there are syntax errors it will affect it. Pete

ZIP it up first -- it will be much smaller then. You can attach it to an email to petedowson@btconnect.com. Pete