Pete Dowson

Duplicated post! Please see other answer! Pete

Offsets are for programmers, and the PMDG assigned ones are only for read-outs to show on displays. All the PMDG controls are simply numbers sent by assigning your switch to <custom control> and inserting the appropriate PMDG control number. Those are listed in the PMDG documentation (in their SDK folder), not in mine. If you can't figure that part out, you really need to address this to folks in the PMDG support forums. I don't use any PMDG products and don't currently have ready access to their SDK. Sorry. Pete

I've no idea what the "Pro 2016" is I'm afraid. What does it have to do with FSUIPC? You do really need to explain more if you have a question for me. BTW version 4.948 is superseded by 4.949. I only supply and support the latest version. And please entitle your threads by something more meaningful than just "Peter". That is really listtle help in a Support Forum which is referred to by many users. Pete

Well, without any information, such as at least one of the Logs of when it didn't appear, I'm afraid I've not got a clue. Sorry. Maybe some conflict with another add-in. It would be useful to know more so the problem can be narrowed down -- maybe a new bug in SimConnect which should be reported to L-M. But with no info there's no point. Pete

No. It'll be a false positive I should think. Withrecent versions of FSUIPC4 you shouldn't really need to use JoyIDs, as I've now built code into FSUIPC4 to do similar things, assign IDs where none can be found in the REgistry. Pete

The Installer log shows a correct install. By the sound of it you don't have an install problem. The more relevant log is the run-time log "FSUIPC4.LOG". However, it sounds very like the dialogue window is somehow occurring BEHIND your FSX window (which will go black in any case). This is almost always a video driver problem. See if it happens in FSX Windowed mode (ALT + ENTER to switch between the two). If not then it is certainly related to the video driver setup on your PC. The FSUIPC dialogue is a standard Windows dialogue and should be drawn over the full-screen FSX, but sometimes drivers get full screen mode wrong. Pete

Sorry, but you don't need to "run" FSUIPC. Once correctly installed it simply rns as part of FSX. Perhaps you could explain exactly what it is you are doing when you get this "black screen"? FSX has ALWAYS changed to a black screen when showing a SimConnect-requested dialogue box. Is that what you mean? Please ALWAYS state the actual version number of FSUIPC when asking for support. Pete

Okay. That checks out and the details and key work perfectly. Sorry, but he is most certainly making a mistake. Get him to copy and paste instead of trying to type it all in. As I said, ALL THREE ENTRIES must be exactly right! Pete

What is "the latest version"? Do you mean 4.948g? If not please update. FSUIPC doesn't change on its own, its setting are remembered and do not change by themselves. If your hardware is changing it sounds like you have faulty hardware or connections. Note that P3Dv3 also appears to ave a number of bugs in this area -- see the reports on the P3D client support forum at L-M. Hopefully most if not all of these will be fixed in version 3.1, due soon. Using any sort of migration tool will likely make FSUIPC's Installer go wrong, and could fool FSUIPC itself into doing the wrong things -- depending what the migration tool does. FSUIPC is very specific to each version of FSX and P3D and will not work correctly if it is fooled into seeing the wrong version. Dirt, temperature variation, hardware problems, bad connections, and dual assignments (i.e. in FS/P3D and in FSUIPC). Pete

Re-installing "many times" makes no sense, as it is only doing the same things each time. Reinstall when a new version is released. Please check that yuo have the very latest -- 4.948g. If not please first download it and install that and check again. We need to determine whether it is being loaded but just failing to connect to SimConnect, or not being loaded at all. So look in the P3D Modules folder and see if it is generating an FSUIPC4.LOG file or not. If so, show it to me please (paste its contents into a message). If it isn't then something is going wrong at the SimConnect loading stage. Did you run any of the SimConnect installers? Many add-ons will want either the SP1 or SP2 legacy SimConnect installs -- see your P3D \ redist \ Interface folders for these. The SimConnect installers asre the "SimConnect.msi" files. Just double click them to install. That is a P3D3 bug. Please see the thread pinned to the top of this Forum. The problem is supposed to be fixed in P3D 3.1, due for release soon. Pete

Then either you bought FSUIPC4 instead of FSUIPC3, or your friend is making a mistake. The registrations are automatically generated and will not be wrong. If you want me to check here I need the SimMarket order number. Do NOT post any other details. Pete

You posted this Support request in the FAQ subforum, where it was ucky I noticed it. Please alway put support requests into this, the Support Forum. Either you purchased a key for FSUIPC4 (FSX and later) by mistake, or he is making a mistake Every part, all three entries, must be EXACTLY as shown in your SimMarket account, letter for letter, number for number. Pete

Yes, in other words externally to the actual plug-in. If you change ipcPARAM inside the same plug-in, it doesn't generate another event for that plug-in. However, assigning "luavalue" is an external source of change for the parameter, so should work fine. Er ... you mean you were only setting it the once, in the same plug-in? Yes, that's one way. But possibly easier altogether, if you only need up to 256 values, would be to use LuaToggle with flag numbers 0-256 and event.flag to provide the number -- instead of ipcPARAM. Since a toggle is ALWAYS a change, you need not assign anything to the release. There's no point in compiling it as it is only loaded the once (I assume you are loading it via the [AUTO] facility in the INI file, or possibly from ipcREADY.lua?). Any event-based Lua plug-in stays resident once loaded unless it terminates itself or uses event.cancel to remove all outstanding event detection. Pete

You must NOT have controllers enabled in FS if you are assigning in FSUIPC. You evidently have dual conflicting assignments. Either assign in FSUIPC or in FS, not both. In FSUIPC a POV hat can be treated as a set of 4 or 8 buttons (according to the device) and you can assign two of those to the elevator trim up and down controls in the drop-down assignments list. Those assigned in FSUIPC will show in the axes tab (or buttons & switches for buttons) when you move/press them. FSUIPC cannot show you what you've assigned in FS -- use FSUIPC or FS, not both! FS assignments are NOT stored in the FSX.CFG file. Just go into FS options/ controls and make sure controllers are disabled. Pete

Sorry, I cannot support such old versions of FSUIPC! Version 4.853 pre-dates P3Dv2 by years. How on Earth do you expect it to work, let alone install? The earliest supported version of FSUIPC4 is 4.948. The current version is 4.948g. Please ALWAYS check that you are up to date before requesting support. There are Subforums at the top of this Forum which tell you all you need to know. Pete

Well, the fact that things have changed ON THEIR OWN as well is certainly starting to point to corruption and possibly hardware problems. Sorry, but there it is, and I've really given you all the advice I can. Check with Virtuali support about BGLMANX errors reporting SimConnect. I've never heard of that one. ALL SimConnect.DLL modules contain the export "SimConnect_Text" so I definitely think that's a corruption in your system, and changed since before this latest report of yours. Pete

So, is it from BGLMANX.DLL? Maybe you need to check with Virtuali support? Another thing comes to mind. Many reports of "stackhash" errors seem to identify overclocking or other hardware problems as a typical cause. Maybe something in the hardware is starting to fail. Certainly memory corruption is the cause of "stackhash" errors and could certainly also result in very strange errors like your missing Simconnect function one. Whether memory corruption is caused by software going wrong or by hardware is a difficult one to determine, but certainly something to investigate. Pete

From what? i.e. what program, exactly, gives such a message, and when? There's no such message in FSUIPC for sure, and FSUIPC is not dependent upon that function -- it uses it if it can, but doesn't really care if it isn't there. However, "SimConnect_Text" is a standard part of SimConnect, so if your SimConnect.DLL installation has it missing then it seems your FS installation is corrupted. Maybe this is why you are getting problems? Maybe you need to re-install. First I expect you could try installing just the SimConnect's (at least the SP1 and SP2 versions would be needed by most add-ons). Pete

You only ever buy it once. You can always download FSUIPC from wherever you first got it -- i.e. the Schiratti page as linked to from the purchase page on SimMarket. Or else, please do notice there are SubForums here, and one in particular called "Updated Modules". There you will find the latest versions of all my FS-related stuff. Then you simply run the Installer. No need even to re-register, just say "not now". (I never understand how folks miss all the important stuff placed right at the top! :sad: ). Pete

The ipcDebug facility has long been superseded by the "Trace/Debug" option in the Logging options tab. I doubt the facility to detect Events is built into ipcDebug. Please try using the built in trace/debug option which is far superior. Then let me see the log (or suitable extract) and your FSUIPC4.INI file, please. BTW, I assume "PMDGBaseVariable" is defined somewhere earlier in the Lua code? Pete

Well, I really don't know how to help. I can answer specific questions about FS. I know nothing at all about ETS. The first thing you need to do is study the API and see if you understand it. If not you need to study a lot more -- I doubt whether I can help clarify an API which I've never seen and know nothing about. If there is indeed an API for folks to make addons for ETS then there is bound to be a Forum and user group and other folks who've done such things. That's the place you need to be. Script? Not a program? Without seeing the API I would guess at least it would need a program written in perhaps C/C++ or Visual Basic. A "script" implies they are providing already and interpreter of some kind that any user could deal with, thus pretty much eliminating the need for the 'program' which you are thinking about. This is why I added the Lua interpreter to FSUIPC -- so that user's can construct their own add-ons by scripting. Reading a string of parameters as a 'script' is a matter of doing just that -- a program written to read files, line by line, and interpret them to do something. A program to interface to other programs is totally different. You need to decide how to commnicate with other programs. SimConnect in FSX does it by subscription -- client add-ons providing callback procedures and making calls via a Library (DLL) to request messages each time something changes. Some programs do it using UDP or TCP internet protocols. This requires you to learn about Networks and how to program them. FSUIPC talks to other programs using shared memory. FSUIPC waits for specific pre-defined Windows messages being sent to its Window procedure which identify uniquely the pre-defined memory space already opened by the add-on application, and requests and answers are then arranged by placing data in that memory and making further Windows message calls. All these methods require knowledge of assorted Windows APIs. If you aren't a programmer already you will need to become one. A program development system such as Microsoft' Visual Studio, at the very least. That gives you a choice of languages. I use C with some ASM. Most folks these days use C++, Visual Basic or C#. Pete

The V axis on the Rudder Pedals is the only input which is ever seen as changing. And most of the time that is flicking between 32768 and zero. All the other inputs are returning zero all the time. These are returns from standard API calls reading the joysticks via normal standard USB requests. Why they aren't working is beyond me, I'm afraid. I can only suggest uninstalling them (via the Device Manager in the Windows control panel -- uninstall including drivers, unplug them, then re-boot the PC and re-connect them. Windows should reload the drivers automatically. I really don't understand how they could be working in P3D, because I'm sure it must have to use the same interface. There are other steps you could try: 1. Ensure the controllers are actually disabled in P3D (not just unassigned) in case that is somehow interfering. 2.. Use JoyIDs to change the ID numbers, eg. from 0,1,2 to 3.4.5. 3. Check the Registry entry is correct and fix if necessary -- see the FAQ subfrum thread "Some Saitek axes only provide partial movement" Pete

Ouch! Version 4.939 pre-dates P3Dv3 by a long way!. It knows nothing about version 3 and all sorts of things will be going wrong -- I'm surprised it doesn't crash P3D during normal operation! Version 4.946 was the first to support P3D version 3.0. You need to keep up to date. The current version is 4.948g. Pete

Yes, that's what I get. That just means a memory corruption affecting the stack of the process. What module is identified? Pete

Try moving the BGLMANX.DLL entry to the end. i.e.this: <Launch.Addon> <Name>Addon Manager</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>bglmanx.dll</Path> </Launch.Addon> to just before this: </SimBase.Document> I see you have PMDG Options loading too. That often gave me grief too, but I don't use any PMDG add-ons now. BTW I don't think any of these problems can occur in P3D, because they removed that awful buggy trust checking system which FSX uses and which all happens BEFORE the FSUIPC module is even loaded! Pete