Pete Dowson

Where on Earth did you read that "I must to write in FSUIPC.INI the string : ASNwxRadarPath = C : \ Prosim737 "? That's nonsense. It's only part of what you must write!! You don't need "experience in the simulation"! You only need to read what is written properly! I assume you don't even know what a file name is? Prosim needs a FILE. You only told FSUIPC a path -- there needs to be a FILENAME in the parameter which tells it the name of the file you want. It is a Prosim matter, not FSUIPC. All FSUIPC needs to know is the path and filename. You are in the wrong place. FSUIPC is not written specifically for Prosim, it produces radar files for any application, and it is up to the application what it should be named and where it should go! Look properly in Prosim support. There's a long thread you need to read to the end: http://prosim-ar.com/forum/viewtopic.php?f=13&t=8971 Pete

The log is in the Modules folder as is everything else to do with FSUIPC. With a Toggle switch you should still not use hold or repeat! Program both press and release to use the same control, that's all. Pete

Buttons, as opposed to switches, are on when pushed and off when released. If you assign a button to a Toggle control you need to only program the 'press', NOT both press and release! And you obviously don't want it held or repeated! If it still turns back off then you probably have conflicting actions -- for instance, through not disabling controllers in FS. You can use FSUIPC's event logging to see what is going on. Pete

Switches and buttons can be programmed to use macros if you wish, of course. Pete

You'd need to program a Lua plug-in for any outputs, but FSUIPC should see any inputs -- i.e buttons and switches. Pete

This is more a question for the PMDG support forums than here. I would guess that the parameters for most of the PMDG added controls (events) are just Mouse Flag settings -- usually just one bit in the 32 bit value, better expressed in FSUIPC in hex, as in x20000000 for bit 29. If you know how to do it with the mouse, then it's only a question of setting the correct mouse flag to do the same. I am away from my PC until late Monday so I cannot really help with that more directly, but it might be worth looking through some of the entries in the User Contributions subforum, above Pete

You haven't referred to the Prosim instructions about this, or read the threads about this in the Prosim support forums? You not only need the path, it must include the filename too, whatever Prosim needs. It isn't dictated by FSUIPC. BTW I moved your post to the Support Forum. You mis-posted to the FAQ subforum instead! Pete

Hmmm. Are sure it isn't some other add-on opening the console? Or maybe you have a Simconnect.ini file enabling it? There's only one console per Process, and if it's opened everything uses it including FSUIPC's log. It is definitely unlikely to be FSUIPC unless that option is not truly being turned off. Check the console parameter in the FSUIPC.INI file, change it there if necessary. Pete

No, it cannot be done without the client application being changed to also use the different class name, because the one it uses normally is the same as FSX's. Why not run the MCP program on the main VS PC? Pete

Yes, GFDIO is supported. See the list of GF devices in the GFD library section of you Lua Library reference document. Pete

Just had time to check here before leaving. Why post everything twice? Sorry to disappoint you, but you are most certainly running GSX, not FSX-SE. There is no sign of any FSX-SE installation showing here. Everything above confirms this: The registry: Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... SetupPath=C:\FSX\ No sign of DoveTail Games or an FSX-SE install. The folder C:\FSX contains FSX.EXE Acceleration edition: INSTALLATION FOR FSX: SetupPath="C:\FSX\" Checking version of the FSX EXE: ... Version 10.0.61637.0 (Need at least 10.0.60905.0) Checking compatibility with installed SimConnect: Found SimConnect build 60905 (Original) Found SimConnect build 61242 (SP1 May07) Found SimConnect build 61259 (Acc/SP2 Oct07) Build 61637 is most certainly FSX Acceleration, NOT FSX-SE. FSX SE's first release was build 62607 and the current version is 62615. The run-time FSUIPC4.LOG confirms this: fsx.exe version = 10.0.61637.0 Reading options from "C:\FSX\Modules\FSUIPC4.ini" Running inside FSX on Windows 7 Also, however, I notice that the log is dated over a week ago: 234 System time = 07/04/2016 20:47:11 Is that when you last tried? Are are you fishing out old files to show me? If you removed FSX how are they still there? The log also shows everything working fine, and most certainly also with the FSUIPC4 entry in the Add-Ons menu. BTW your FSUIPC is out of date. The oldest supported version is 4.949h and there's also an interim update 4.949n available in the Download Links subforum above. When you've found more current files please show me those instead of these apparently old ones. I'm afraid it will definitely not be till Monday evening earliest I shall see them now, however. Incidentally, the DLL.XML file you posted above is missing all of its new line codes, making it very difficult to read and check. Next time can you please try to retain the original format. I don't know how you lost the format -- maybe a poor text editor? Even Notepad should retain the formatting. Pete

Thanks. So it's a similar problem with my SimConnectP3D2 needing the 100 version DLLs. I'll work out a solution for that too. Pete

Yes. Does the FSUIPC4 log file show that the AM is correctly applied? Are you sure you have the latest version of FSUIPC4 installed? (4.949n is the latest interim update). Pete

Please show me the FSUIPC4.Install.LOG, and also see if there is an FSUIPC4.LOG in the Modules folder. I'd like to see that too if so. You can paste the contents of these text files into a message here. I can't help without information, which is why logs are produced to show what is going on. If there is no FSUIPC4.LOG file then FSUIPC4 is not loading, which probably means there's an error in the DLL.XML file. Some other program installers do seem to make a hash of that. You'll find it in the same folder as your FSX.CFG or FSX-SE CFG file (depending on whether FSX-SE installed as stand-alone or as side-by-side with FSX because it thought FSX was still there). Once I have the Install log I can tell you exactly where to find the DLL.XML file. Unfortunately I am away over the weekend, back Monday evening, so please forgive any delay. I will try to check in over the weekend but I won't have access to my PC for that, only my iPhone. Pete

Aha! What's the DLL filename for that? MSVCR150.DLL? Maybe it's the same with my SmConnectP3D2.DLL. It apparently needs MSVCP100.DLL and MSVCR100.DLL. Perhaps I should package them into my installer too, just in case? Or maybe I need to get VS 2012 and re-build with that -- I see P3D needs MSVCP120.DLL and MSVCR120.DLL. I didn't really want to have to fork out for a new version though :-( Pete

So is it something related to the process (P3D rather than FSX) it is being loaded into? Curiouser and curiouser ... Pete

Some folks using FSUIPC4 on P3D also have the problem with my own SimConnectP3D2.dll, which the FSUIPC installer places in the Modules folder for loading and using as its SimConnect interfacr because P3D2 and P3D3 do not install an FSX SimConnect themselves. This is why I've had to have a pinned note at the top of this forum, to advise those suffering how to install an FSX version. I've never found out why Windows reports that the DLL cannot be found. It is very very annoying and I can appreciate your frustration. Unfortunately, since I don't understand how it can possibly happen I have no answers. I wish I did. It doesn't happen on any of my Win7 systems, and there are plenty of Win8 and Win10 users for which this is okay too. So, if you do find the reason and/or a solution, please do let me know. I'm wondering it is is related to dependencies in the module concerned -- i.e. missing other DLLs which it relies upon. In such cases, however, I would have expected a different error. Maybe it's being mis-reported by Windows? There is a free program called "Dependency Walker". Perhaps you can use that to check if Saitek.DLL needs something you don't have installed. http://dependencywalker.com/ Pete

Sorry, I don't know. FSUIPC only reports the error returned by Windows -- the text too. I'm always suspicious when things are installed in the Windows' Program Files folders, because those are protected. See if it works when you run P3D in administrator mode. Also right-click on the saitek.dll itself and look in Properties to see if it may be marked by Windows as access denied. Windows sometimes does that for some reason. Finally try putting the DLL somewhere else, outside of Program Files, and see if that works (you'd need to change the Lua program too to address it properly). Pete

There's no way. It should be 0. Doesn't that work? I think this has already been reported to L-M as a bug -- but it might be a good idea for you to do so as well to reinforce this. The menu only accepts one keypress and there is no '10' key! Pete

Assign a key or button to "Wheel trim toggle". It's in the drop-down assignment lists. Pete

No easy way. Radio frequencies are not continuous and the numbers you get from an axis is not predictable enough. You would have been better off with a two way button. What you can do with an axis is assign to normal frequency increment and decrement controls on the right-hand side of the axis assignments tab in FSUIPC. Assign the increment control to the UP direction and the decrement to the DOWN direction, with the whole range selected for the action, and "repeat" selected. How well that would work I don't know -- you might find it changes them too fast to select a specific frequency, or conversely it changes too slowly and you run out of turning space on the knobs before getting to the minimum or maximum allowed frquencies. If you want to try, the cntrols to use would be COM radio whole inc COM radio whole dec COM stby radio whole decrease COM stby radio whole increase COM2 radio whole inc COM2 radio whole dec NAV1 radio whole inc NAV1 radio whole dec NAV2 radio whole inc NAV2 radio whole dec ADF1 whole inc ADF1 whole dec ADF2 whole inc ADF2 whole dec Pete

That shows a minimum of -16384 and a maximum of +16383. Do they show values in between as you turn them? If so, then, yes, they ARE Axes and you can assign them directly to any variable values (axes) in FS. They are pots exactly as fitted inside most joystick levers (though some times these are optical). If they only have those two values, the max and min, then they MIGHT be axes all the same, but configured in the driver to be digital axes -- on or off. That can usually be fixed. So, now we know they are seen in the correct place, what is the problem you have? Pete

Sorry, do you mean they show up as axes in the Axis Calibration tab, not as buttons or switches? Are they simple on/off buttons, or do they have a range of values or several different ones? If they look like axes it is because that's how the driver for them has defined them. What values are shown in FSUIPC for them? Pete

Did you try the FSUIPC User Guide, instaslled in your FSUIPC Documents folder? It's simple enough stuff. Assign as you wish, calibrate if needed. You don't mean "keys" I think, but controllers. Why didn't you disable the controllers completely in the simulator, then, as instructed in the user guide? You can assign in the sim OR in FSUIPC but NEVER both or you will get conflicts and other odd things happening. Just disable controllers completely in the sim if you want to assign in FSUIPC! Just delete the FSUIPC4.INI file in the Modules folder. ALL of your FSUIPC settings are in that file. Setting up profiles cannot cause conflicts. If you have conflicts you have forgotten to disable controllers in the sim. You've not set up the rudder in FSUIPC properly then. You'd need to tell me what you assigned it to and in what mode. For instance, if you assigned it in the mode "direct to FSUIPC ..." then you must also calibrate in FSUIPC. The control you assigned to may also matter. To assign to exactly the same control as the sim you use the FS control "Axis rudder set". Different add-on aircraft may need different treatment for best results. Just uncheck the "enable controllers" selection in the Options - Settings - Controls dialogue. It will be saved when you close down. No point. The whole point of using FSUIPC is to enable you do do more, not the same. You don't HAVE to assign anything in FSUIPC to use facilities like the calibration. The reason there are so many options is that FSUIPC is a set of tools, for you to use as you wish. If you only want something simple and straightforwards, why assign in FSUIPC at all? You can still calibrate there if you wish. The two things are separate. Calibration works on the FS control values NOT on the devices. Pete

No. I don't really know anything about sound and wave files. The code simply passes it all on to the DirectSound facilities in Windows. Have you tried comparing it to the ones which work using one of the sound editing programs like Sound Forge? These show you the actual channels and waveforms. Pete