Pete Dowson

No, I don't know of any other way, and I don't think the Simconnect way is any good either -- that's why I gave up trying to provide it as an FSUIPC facility. I supsect there is a way if you hack into the code, as I think possibly Jean-Luc did for his RXP weather gauge -- he did that before the SimConnect facilitiy was available. Are you definitely using FSX with SP2 or Acceleration installed? I'm reasonably sure it didn't work at all before that in any case. Regards Pete

Sorry. I don't have the 747X so I can't even do a test. Hopefully others may help. Okay. So it would then only be a matter of keyboard focus? You just need to find the way to get the 747X's attention on the CDU. Regards Pete

Strange. i only have the MCP Pro I'm afraid, but maybe I can try treating it like an older MCP and see what I get. I've no time at present. If I don't post again before Friday, please post a remnder and I'll do it over the weekend. Regards Pete

Sorry, I don't know. It's by trial and error. I don't know of any other way. Most of the things you need to do with the CDU require a pretty full keyboard. I doubt if anything less will do. However, others may know a way. Have you checked in the User Contributions sub-forum? If someone has done it for the PMDG 737NGX it may well also apply to the 747X? Regards Pete

I think to do that you have to use a monitor program which hooks into the video display system, like those sed by VNC. It is fraught with problems, not the least of which dealing with the vast differences between full screen and windowed mode. No, it is not possible. There is no such memory where the image comes together except that in the video card. Images are built up through DirectX calls which build them in the video card memory using video card programming. Regards Pete

Sorry, I've really no idea. Obviously something got corrupted at some stage. But with your axes evidently only ever assigned in FSX, the stuff in FSUIPC for calibration was only able to work with whatever came through from FSX. FSUIPC4 only reads the joysticks directly when you assign in FSUIPC, otherwise all the calibrations are trying to do is modify the control values once FSX has received them and messed with them. It only rebuilds with everything reverting to default, with no assignments, no calibrations, no unusual settings. But in your case that was a good thing. In general one would only delete the troublesome area -- but your settings showed you only ever used FSUIPC for calibration, and then a little bit wonkily with assorted options applied rather haphazardly to different aircraft. Best to just start over, as you've now done. Regards Pete

Because it was replaced by the 3.998r version, of course. Just get the latest! Where are you seeing that? It is not available anywhere I know! It is several weeks old and was replaced by 3.998n then 3.998p before 3.998q. You should be referring to the Download Links subforum! Pete

Ah, mea culpa! Apologies. Pete

The problem is that the first part is event-driven -- i.e. it sits in memory waiting for something to happen, and does nothing until that happens, whilst the second part is in a never-ending loop testing for something. If you wanted them in one plug-in you'd have to re-write one or the other -- either to do everything in a never-ending loop, or to make everything event-driven. Really the best step is to keep both parts separate altotgether. Save then as two differently named Lua modules. As an example I'll call one of them A.lua and the other B.lua. Save both in the Modules folder. Now you can get them loaded in one of two ways. The first, using ipcReady.lua, is simply to make that lua load the others, as follows: ipc.runlua("A") ipc.runlua("B") That's it, all you need in ipcReady.lua. When you want other plug-ins to run automatically, add similar lines here with their names. The second way is to use the facilities to execute macros automatically. This is by adding an [Auto] section in the FSUIPC INI file: [Auto] 1=lua A 2=lua B Again, that can be extended as needed. Regards Pete

Is your MCP and MCP or an MCP Pro? I believe they are different. The Pro displays are handles by simply sending them the strings for dispay, whilst the older MCP (non-Pro) had to have the segments of each digit sent to it. Check the version of GFDev.DLL you are using too. there are many around. If you look in the Download Links subforum here you'll find the latest I know about, but also check the GoFlight website. Probably the only program you are using with uses GFDev.DLL is FSUIPC, so what that does may make the difference. In recent versions of FSUIPC (the latest is 4.758, also in Download Links) the location and version number of GFDev in use is shown in the Log, as follows (this is mine): 17453 Using "E:\FSX\Modules\GFDEV.DLL", version 2.1.0.1 Regards Pete

FSUIPC doesn't "support" specific add-ons by itself at all. It is an interface into FS. Where an add-on aircraft uses FS systems, then they are fully usable directly through FSUIPC too. Where an add-on does its own thing, those systems may or may not be accessible -- usually, if so, via either mouse macros or gauge local variables (LVars). With FS9 and before a lot of aircraft actually used FSUIPC offsets (including PMDG), but this is not so with FSX. I'm not a PMDG NGX user, but just check for yourself by using FSUIPC logging and operating the flaps. If you log events you may find it uses regular FSX controls, which you could use via FSUIPC too -- via offset 3110 if you need to use offsets. I do seem to recall seeing folks managing calibrated flaps for the NGX via FSUIPC so it must use regular FS controls, surely? and checking the innards of FSUIPC, writes to offset 0BDC are translated by FSUIPC into appropriate FS "FLAPS SET" controls, which should work -- but maybe it only likes AXIS_FLAPS_SETS? Regards Pete

No, FSUIPC3 and FSUIPC4 are different products. Raise a problem ticket with simMarket if you are having any difficulties. Make sure you are using the same name and email -- maybe you have a different account now? Regards Pete

Oh, right. Confusing! You install them where you want them to run. Still best to use RunReady. The path must be wrong, then. Show me the actual Wideclient.INI file AND the WideClient.log file. Regards Pete

I don't know how you could miss it. The Download Links subforum certainly contains both. The entries for FSUIPC read as follows: The first link is just the DLL and a changes document. The second is the full works. This arrangement is always provided in that thread. I'm afraid that you didn't get any useful logging: It looks like you turned axis logging off but either never actually went back into FS flight mode to waggle the axes, or did go back but didn't waggle any connected axes. Natually, whilst in the options, such logging doesn't occur because the axes are not being put through the normal paths, they are only recognised for assignment and calibration purposes. Looking at the INI file, you have NO AXIS ASSIGNMENTS WHATSOEVER in FSUIPC. therefore if they aren't assigned in FSX, they cannot be used at all! That may explain the lack of logging -- FSUIPC cannot log axes which aren't doing anything. Secondly, look at the following, where I've simply removed everything but the calibrations. You have different calibrations, for the same devices, for loads of different aircrafgt. But some incvlude some axes, not others. All in all it is a mess. Can you tell me what you've been trying to do here? Additionally, in some places you enabled Filtering, others not. Why? Generally filtering is NOT a good idea unless you have really bad, dirty controls or a poor power supply. the only aircraft for which you have ailerons calibrated are: [JoystickCalibration.Cessna Skyhawk 172SP Paint1] Aileron=-16375,80,80,16383/8 -- Filtering enabled. Why? [JoystickCalibration.Airbus A321 Paint2] Aileron=-16380,-512,512,16380/16 Reverse enabled, but numbers show no calibration -- those are default numbers! [JoystickCalibration.Beech King Air 350 Paint1] Aileron=-16375,80,80,16383 Same calibration as the Cessna above, without filtering. Why have different calibrations for the same controls for different aircraft? I could understand some sorts of separate needs, like helicopters v aircraft, and fighters or stunt aircraft v airliners and GA. But not for these ordinary aircraft. you just confuse yoursel. If I were you I'd delete the FSUIPC4.INI file altogether and start again. But please do read a little more of the User Guide. And please think about assignments. Unless you assign your axes they cannot be used. Regards Pete

Odd because the same link is used in the Download Links subforum, where it works perfectly. Go there then. I was placed there at the same time as my last reply to you, three days ago. It's been available for over three days now. Use the subforum. Don't know why that link is different. Regards Pete

? Is RC4 in the most unlikely place as C:\FSX\RC4 ? ? Is this Run line in the [user] section of the WideClient.INI file? You should in any case use RunReady, not Run, as RCV4 wants FS running and ready to fly. ASE uses Simconnect with FSX, not FSUIPC/WideFS. Why do you say "Dunno how it s gonna work"? Pete

I don't see the delay as any sort of solution in any case. But the solution I suggested works 100% here. Yes. The FSUIPC interface is replicated by WideClient on the client PCs. That is exactly what it is for!! Pete

FSUIPC does not (cannot) treat any one axis different from any other except by user options. There's no way "aileron" assignment will get singled out for special unwanted treatment on FSUIPC's own initiative. Furthermore there's been no changes in how all this works for a long long time, and it is the same in FSUIPC3 and FSUIPC4. Before doing anything else, please update to the latest version -- 4.758 -- so we are both using the same one. No need to download the installer, just get the updated DLL and copy it in. Download Links subforum. It sounds as if you have something screwed up in your settings. Please, first, make sure controllers are all switched off in FSX (because any dual assignments can give the oddest results), Then paste your FSUIPC4.INI file here. You could also enable Axis logging in FSUIPC's logging tab, operate the ailerons and check the results. Again, paste the Log here if you want me to take a look. Regards Pete

By "stopped working" and "not detecting it", can you explain what you actually mean? Do you mean that the FSUIPC entry isn't appearing in the Modules menu at flight time, or even that the Modules menu isn't appearing either? I'll assume that's what you meant, for now ... That's okay. Is there an FSUIPC4.LOG produced when you run FSX? If so, please close FSX and paste the Log into a reply here. If there is a log it means FSUIPC4 is "being detected" and it is loading, but there's some problem with SimConnect which prevents the menu being created. If there is no log being produced, then SimConnect isn't even loading FSUIPC, so I'd need instead to see your DLL.XML file, which is probably corrupted. You'll find the DLL.XML here: C:\Users\nogutu\AppData\Roaming\Microsoft\FSX\ Show me that -- it is a text file, just paste it into a message. You can use the code parentheses (the <> button above) to retain the layout. BTW, is there a reason you are sticking with FSX SP1? You should really apply the SP2 update as well, as it fixes more things in FSX and makes FSUIPC4 run more efficiently too. Regards Pete

I don't think there will be many SimConnect programmers coming here. You might be better off in the SimConnect forum at AVSIM. But: I did try sing this facility once -- with FSX + Acceleration. It seemed to only ever return the 64 x 64 byte array all zeros but with rectangular areas filled with 0xFF's -- no other values, only 0s and 255's. And I couldn't really match what was there very well with what I saw in any case. I gave it up as being less than useful. If you can make it work I'd be delighted to know how. I only did it with ranges of 1 to 64 nms, in powers of 2. You are using 2 degrees, so 120 nm (in latitude anyway). And I had an alttude range of 2000 feet rather than your 9000. I don't know if these things makes a difference, but it might be worth experimenting. I think it only covers the area known as the "reality bubble" in any case, which would limit it to 80 nm from your location at max. Maybe you should try something smaller? (For radar on an ND set to something larger you could pad the far areas with guesses based on WX station readings -- programs like SA_WXR make their scopes using WX station readngs only). Check that the array size you get is 64 x 64, just to make sure it is actually supplying the data. And there's no need to "switch" on, or even check, the requestID if you only have one cloud state request -- the return of a SIMCONNECT_RECV_ID_CLOUD_STATE must be the one you asked for. Regards Pete

No, they are about a problem where, in full screen mode at least, some video drivers don't even draw the dialogue, so you get just a black screen, nothing else. The only things you do in the options dialogue is tell FSUIPC to go into Mouse macro making mode, and provide the file name for the macro file it will make, and, when you've finished making the macros, again to end that mode to let FSUIPC save all those macros correctly and make them available for assigning. To actually make each macro, after enabling the mode, you have to have the aircraft actually running, else how can you operate its switches etc, and see it working? The user guide section on this does explain all this. You seem to be skipping some paragraphs! Regards Pete

There are two ways to update. One is to run the latest Installer. This is advisable if your current version is a bit old with outdated documentation, because the Installer will provide updated documentation automatically. On the other hand if your current version is quite recent you can just download the ZIP containing the DLL and copy the DLL into the FS Modules folder. Check the Download Links subforum in this forum. You'll see several threads there providing different things. FSUIPC is in the Updated Modules thread. Read what it says and download the ZIP you need. Regards Pete

Well, it is the right file, but it shows that the version you are using is FSUIPC 4.50: which is well out of date, and totally unsupportable. I suspect something you've installed has overwritten your more up to date version. Please download the latest Installer from Download Links and use that. This INI file also shows that you aren't using FSUIPC for anything at all. It only has default settings. Have you purchased a registration or are you only using it unregistered, and, if so, what for? Regards Pete

No. And without knowing how you assign and claibrate throttles I'm none the wiser. From what you say all you've done is updated and registered FSUIPC. Are you actually using it for anything? If not it won't have much to do with your throttles. I don't think that aircraft uses FSUIPC either, but i'm not sure. Perhaps you can explain a bit more about what you are doing with the throttles? Regards Pete

The "explanations" need padding a bit with some hard data, really. You said I do not know of any autopilots on any aircraft for FSX which is any way use anything in FSUIPC to "accept" values like a heading or a vertical speed. Yet you say that, apparently just because of a change in the version of FSUIPC, no add-on aircraft will even allow you to change its heading or V/S? Yet, presumably, default ones do? There is absolutely no way FSUIPC can stop values being provided to an aircraft. It simply makes no sense. FSUIPC has no way to stop these things even if it was so stupid to want to! 4.70 is certainly not the latest. The very latest is actually 4.758, and 4.70 has been unavailable from any official place for some time now. Please take a look at the Download Links subforum where you will find full details of what is "latest". Well, assuming you actually USE FSUIPC for anything, all your "exact settings" are in the FSUIPC4.INI file, in the FS modules folder, which is the place where your "exact settings" are stored. If you don't know what you've used FSUIPC for or what you've set, just paste the contents of that file into a message here and I'll look at that -- it'd save you trying to remember. After all, you did also say and unless you are really using FSUIPC to assign stuff from these (unnames) Saitek controllers, I'm not sure how that statement can relate to FSUIPC either. Regards Pete