Pete Dowson

Well there shouldn't be any difference as long as you aren't using any global values. Didn't you manage to get the Module name and address for the CTD you were getting, so i could look and see if I could nail that one? ext.run("C:\Prosim\ProSimMCP\ProsimMCP.exe") -- does not work.?? Strings in Lua, same as in many other languages, use the '\' character as an escape, to allow non-graphics to be included, like "\r" for return, To include a real '\' you need two of them for each, i.e. \\. ext.close("ProSimMCP") -- does not work.?? As documented, ext.close needs the handle returned by the ext.run function, not the program name . Please do check the documentation if you get an error as the explanation is often there. event.offset("5034"), "UB", "MCP") -- Offset "5034" is assigned by Prosim AC gate. Which works. You've got two many ')' characters there -- the first is not wanted. Pete

That SIM1.DLL is indeed the same one I have for SP2. So there's something else odd somewhere. Can you please paste the whole of the FSUIPC log, not just the one line, please. Pete

I've moved this from the FAQ subforum, where it won't get answered, to here, the Support Forum, which is the proper place for support requests. What version of FSUIPC4 are you trying to use? What Installer version? In all recent versions different email addresses for FSUIPC4 and WideFS7 have been accepted. Only very old versions need them to be the same. However, the NAME part must be identical in both cases. Maybe you've spelled your name differently? Note that the current supported version of FSUIP4 is 4.929 or later. Pete

But you still have Controllers enabled in FS? The hat is assigned automatically (by default) to Pan View in FS, but this is listed in its Buttons/Keys table, not its axes table, for some odd reason. So check there -- in fact test if it works in all directions there. And note that if you haven't actually disabled controllers in FS then it can (and may have already) automatically reassign axes and buttons. It is for this reason you are advised to either assign all in FS or all in FSUIPC, not a mixture of both. Pete

I really don't know any way you can actually stop PAN VIEW from moving the view in all 4 directions, it is just a simple built-in FS facility. All FSUIPC will be doing is sending the control with its value to FS. Does panning work in FS if you enable controllers in FS? It should be the same. Also check for conflicts -- you did try assignments in the Button & Switches tab before. You need those deleted. If you aren't sure what to do, show me the Axes and Buttons sections from your FSUIPC4 INI file. Hmm. Test your panning without EZdok running to see if that's interfering -- you can close it as it is a separately running EXE file. Pete

As the Offsets Status documentation tells you, it is not effective for writing. You have to use the regular FS controls. Seems you are not referring to FSX documents? The FSUIPC4 offsets status document is the reference for FSUIPC4. Changes from what version to what version? The changes documents normally accompany the interim update in the downloaded ZIP. For main releases there can sometimes be a Changes document accompanying the full Installer in the downloaded ZIP, but that's only true if the History documentation is not fully up to date. The History document embodies all the changes and along with the rest of the FSUIPC documentation, including of course the offsets list, is installed in your FSUIPC Documents folder (as stated in the Installing and Registering document). Pete

Well, as far as I know that's the only cause of the log entry. In 4.928 FSUIPC would still not have patched the entries 9even with Lua) but it simply didn't log it -- an omission on my part. If you think your SIM1.DLL is correct please do send it to me for checking (ZIP it and send it to petedowson@btconnect.com). I'm using Acceleration so mine will be different in any case. Pete

Nevertheless, the registry entry still exists for FSX. Nothing is going to "invent" that for you, it is there, present in the Registry as I showed. And why did you do all that? There is absolutely nothing in the log to indicate anything wrong at all with your P3D installation nor FSUIPC4 being installed into it, as I said Yes, but you selected P3D when asked for the location of FSX, that is all. Sice you don't have FSX you shouldn't have selected anything, just aborted that part. However, it doesn't matter at all. FSX.EXE is not going to be found because it isn't there. As I said, the cleanest thing to do to fix your system is to remove the redundant entries in the Registry pointing to a no longer existing FSX! The prompt would have asked you to find FSX.EXE. You don't appear to have read much of my last reply and log anyalysis at all. :sad: Yes, it has correctly installed FSUIPC4 into P3D, as it had done the previous time and as shown in the Log. The installer would not say anything until and unless you press a button on that screen. It cannot edxit at all just when checking an option. Of course they are, and it is only one error. You appear not to even bother to read things. It asks you to locate FSX.EXE, not Prepar3D.exe. Why don't you read what it says? You most certainly have NOT removed the Registry entry which says you have FSX installed ... please go and re-read what I told you last time! You seem to have ignored most of it! What is the point of my giving you a blow-by-blow analysis if you ignore it? In my opinion, so-called registry cleaners do more harm than good. The entry you should some time remove is found in one of these places: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 or HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 You have a parameter in the former, I think, called Setuppath or maybe, less likely, Apppath -- or even both. It is pointing to: "E:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\" It isn't doing any real harm except for confusing the hell out of you, it seems. Regards Pete

If the currently loaded aircraft matches an existing profile, then that's it ... you already have one! If you want to separate that specific aircraft from a profile you already have it assigned to, you will have to exit FS and edit the INI file to delete its name from the [Profile. <profile name>] section in which it is listed. This is easy enough, but it isn't included in the on-line dialogue window because it is a rarely needed action and would overcomplicate the user interface for normal use. Pete

What flight simulator are you using? What version & update? What was your previous version of FSUIPC? The change in 4.929 is that it checks that the frictions data is default before hooking to it. If you are using an already patched version of SIM1.DLL (which some folks are), then, for safety, FSUIPC will not allow further changes. The previous versions also did a similar check -- the main change is that it now logs a failure. Pete

It is definitely not a good idea to "Kill" plug-ins if you can possibly avoid it. Depending on what that plug-in is doing it can cause hangs and crashes. I've attempted to eliminate them all, but I can only do so for the ones I can actually see or get details of -- with a CTD you should have all the details, the module name and the offset. So I can look at that. But it still remains problematic. In order to allow the plug-in so much freedom over what they do there is a lot of time spent not IN the Lua interpreter itself, where a termination request can be quickly detected and acted upon, and in order to Kill the thread a forceful "kill thread" call to Windows is used. If this occurs in a critical place elsewhere, outside of the Interpreter, it can have unwanted consequences. As I said, I've tried to interlock all of the places where this is the case but it is a never-ending task. I'll look at yours when I have the details, but i don't guarantee anything. I suggest that you modify the Lua plug-in to instead terminate itself on a flag being set, or, better using the event system. Did you set the option for a separate log? Pete

It sounds like you didn't "uninstall" it but simply deleted it? The uninstaller should remove the Registry references. That is why I said to paste the log into a message, as I see you have done. The log actually shows that your Registry still says you have FSX installed: Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... It seems that you simply deleted FSX too, without uninstalling it? This is why you get a prompt asking you to point to where FSX is: INSTALLATION FOR FSX: SetupPath="E:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\" Checking version of the FSX EXE: Couldn't obtain Version Info! Asking user to find FSX.EXE ... Then, oddly, you "oblige" by pointing it to P3D!!! Why? User identified path: "C:\Program Files (x86)\Lockheed Martin\Prepar3D v2" Checking version of the FSX EXE: Couldn't obtain Version Info! Asking user to find FSX.EXE ... User aborted attempt to find FSX. Installation failed. Why not just abort the FSX install inn the first place? What are you trying to do here? Really you need to edit the Registry again and remove the installation details for FSX. I'm surprised you don't get problems with other installers. However, the installation for P3Dv2 proceeds successfully. Why do you think it doesn't? See: Looking in registry for Prepar3D v2 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"SetupPath" ... >>> OK! FOUND Prepar3D v2! <<< ... ... INSTALLATION FOR Prepar3D v2: SetupPath="C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\" Checking version of the Prepar3D v2 EXE: ... Version 2.1.9936.0 (Need at least 1.0.677.0) Checking compatibility with installed SimConnect: Found SimConnect build 60905 (Original) Found SimConnect build 195 (ESP Orig) Found SimConnect build 61242 (SP1 May07) Found SimConnect build 61259 (Acc/SP2 Oct07) Checking if there's already a version of FSUIPC4 installed in: C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL ... No previous valid version found. Prepar3D v2 Modules folder created okay! Okay -- installed FSUIPC4 into "C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\BillofFlagstaff\AppData\Roaming" Now finding \Lockheed Martin\Prepar3D v2\Prepar3D.CFG for all users, including this one ... Found Prepar3D.CFG in "C:\Users\BillofFlagstaff\AppData\Roaming\Lockheed Martin\Prepar3D v2\Prepar3D.CFG" Now checking DLL.XML ... ... No previous DLL.XML found, creating new one (for FSUIPC4 only). Now checking for a SimConnect.XML file ... ... No SimConnect.XML file found. This is okay. ... "Modules\FSUIPC Documents" folder created okay! Now installing the Prepar3D SimConnect interface for FSUIPC4 into the "Modules" folder: Installed "SimConnectP3D2.dll" okay Now installing additional files into the "Modules\FSUIPC Documents" folder: Installed "FSUIPC4 User Guide.pdf" okay Installed "FSUIPC4 for Advanced Users.pdf" okay Installed "FSUIPC4 History.pdf" okay Installed "List of FSX and P3D controls.pdf" okay Installed "FSUIPC Lua Library.pdf" okay Installed "FSUIPC Lua Plug-Ins.pdf" okay Installed "Lua License.pdf" okay Installed "Lua Plugins for VRInsight Devices.pdf" okay Installed "LuaFileSystem.pdf" okay Installed "Example LUA plugins.zip" okay Installed "Offset Mapping for PMDG 737NGX.pdf" okay Installed "FSUIPC4 Offsets Status.pdf" okay =========================================================== So, apart from your FSX pointer to nowhere, what is the problem? Pete

Why have you posted this THREE times? I'm not answering all three! Er, left and right brake axes are SEPARATE axes, not the same. They cannot possibly show on "opposite sides" (whatever that means -- opposite sides of what?). Please explain exactly what you've done and what you mean. Didn't you read the Installation and Registration document included in the ZIP with the FSUIPC installer? It tells you exactly what gets installed, and where. Perhaps rather obscurely, the documentation is in the "FSUIPC Documents" folder, in the Modules folder where FSUIPC is installed -- i.e. the 'installation folder'. Pete

Well. did you accomplish it yet? 1. Run FSX, get to flight mode 2. Go to Add-Ons / FSUIPC menu 3. Select Axis Assignment tab 4. Operate the hat till it is seen in the window at top 5. Select 'Send to FS as normal axis' 6. Check one of the 4 assignment lines 7. Press the drop-down arrow to get the list -- It is in alphanumeric order 8. Find and select Pan View. 9. OK out. If you want pictures please check pages 41-43 in the User Guide. This is surely all pretty simple stuff even for beginners? The above 9 steps accomplish what I meant by telling you to "assign to Pan View" in my much earlier reply (the part you sadly missed or ignored), and that sort of simple statement has been enough for most folks coming here for help. I'm sorry it didn't work for you, but perhaps if you could find time to look further at the User Guide you'd be better off as I'm sure you could find answers more efficiently and effectively that way. It is actually written in normal English, not "technicalese", and has been enhanced over the 15 years to answer all sorts of "beginner" questions. The only possible reason it might appear "daunting" is simply that there's a lot of things you can do. FSUIPC is a toolkit. The manual tries mostly to explain what the tools do rather than how to do specific things, because there are an almost unlimited number of things which can be done. Think of trying to provide a manual for everything you can do with a simple set of household tools -- you don't, you just provide operating details for the tools themselves. Pete

So you got no answer? It didn't help? By "if you tried" I honestly thought you would have actually read my previous reply where I said to assign to "pan view". The "pan view" control is only listed in the FS controls list, not in the direct to calibration list, so you only had to look and you'd have found it in the correct list. I really don't see why pointing that out is such a dreadful thing for me to do! It was later in your message I actually saw that you didn't read my previous reply properly and hadn't even seen (or had ignored) the advice to assign to pan view, so perhaps the earlier comment became inappropriate. However, I reply serially. perhaps you could forgive me for that in the circumstances. Also perhaps I have a different view of what good support entails. Support doesn't just mean providing a crutch, it also means helping folks to help themselves. Some folks need more help than others, as seemed obvious in your case. Others apply themselves a little more and so don't need it so much. If you think trying to get folks to help themselves more is patronizing then I feel sorry for you, and I'm surprised is isn't something you experience more of... May I respectfully suggest you peruse more of this Forum and see just how much support I give to FSUIPC users, and how it varies enormously from very detailed to just plain references to documentation. Different answers for different folks in different circumstances. And all this despite the fact that FSUIPC itself is now 15 years old. Many products have support withdrawn in much less time despite still being sold. And, except when I'm away, i not only support folks within minutes (ok, a few hours if I'm asleep of course), but also take on suggestions and add facilities requested by folks where these can be accomplished without jeopardising stability. I really do try my best and find it very upsetting when I encounter folks with your attitude. Luckily this isn't too often, else I would have quit long ago. I'd have more time to fly my simulator then. Pete

By "the initial stuff" I mean all of the lines in the file from the very start. You took the file and extracted part of it to show me even though you "only ran it for a few seconds". Why remove any of the lines at all? FSUIPC deliberately includes lots of information about where it is, what it is, what FS is and so on, so I can help when folks submit logs. Well, the answer would be obvious if you tried, because the PAN VIEW command is not one which is subject to calibration and is therefore not listed in the "direct to calibration" option. PAN VIEW is an FS control and is in the FS controls list. Er, how about Pan view, the one I explicitly told you to assign to and the one you were misusing in the Buttons & Switches section? ;-) I know you are a beginner, but you do need to read the answers, please. Okay? ;-) Pete

How did you lose the folder? Are the other two versions there (60905 and 61242)? If you don't have the SP2/Acceleration version of SimConnect.msi (eg in the FSX SDK), then you may be able to download it from someplace, but I would guess that if Acceleration install/repair didn't re-create the correct folders/files then neither will the specific SimConnect installer. If that's the case it is some sort of Registry mess which I don't think is solvable, unless you can roll back to a better time. If not I can only think of two things to try: 1. If you do have the older folders, try using the "UseSimconnect" parameter in FSUIPC's INI file to select one of those. This is described on page 12 pf the FSUIPC4 advanced user's guide. 2. Failing that I think the only solution might be a Windows re-install. That's what I had to do in a similar mess -- one I created deliberately to see if I could write a program to fix SimConnect problems. Regards Pete

Partial logs don't give enough crucial information. Please always include all the initial stuff next time. Oh, and if you aren't using version 4.929 or later, please update now, as I do not support old versions. Now, onto your question. First, where are you finding any instructions for assigning to PAN VIEW in "Buttons and Switches"? Pan view is an AXIS control! If you want to use your Hat to get specific views the old way you use the Pan left/down/up/right etc controls, as per the example on page 32 in the FSUIPC User Guide. That example originally dates from FS2004 where there was no alternative. The FSX specific example (the second one there) only uses Pan view with parameter -1 in order to reset the view to forwards. In FSX it is far better to use Pan view as an axis -- assign your Hat to Pan view. That's all you have to do -- do this in the Axes tab, NOT the Buttons & Switches tab! I didn't watch the video you linked to (no time), but if it is telling you to do things the wrong way you should comment back to the author on that. Pete

Are you running the Installer by right-clicking it and selecting "run as administrator"? Because having installed P3D in the protected Program Files folder you must do. Obviously it doesn't need to find FSX. If you still have a problem I need to see the Install log to see why. It sounds like either your Registry entries are incorrect or you've renamed Prepar3D.exe as I know some folks do in order to "fool" installers which aren't aware of P3D. You can paste the log into a message here. If it isn't being saved into a folder (because it cannot create a Modules folder) you can still use the "File -- Save" entry in the menu in the window showing the progress. Pete

It is the way the built-in FS facility works. When you choose pushback, turn to left or right, it moves back straight for one aircraft length before it starts turning. FS has ALWAYS done this, as far as remember (back as far as FS98 maybe). I suppose it is designed to allow you to select the direction directly, with the aircraft just moving out enough to clear the parking positions to either side. Pete

Are you sure they are operated by Key Events? I've never seen any for cabin heat or cabin vents, for example. Cosmetic buttons and switches which don't actually do anything won't result in events being sent because there's no need. Additionally many add-on aircraft do their own thing, not using built-in simulator-defined events. You often need to find alternative ways to control them, which is why FSUIPC provides the "mouse macro" system, which works with C/C++ compiled gauges to actually call code directly, if possible, and also "LVars" (Local Panel variables) which can be set by FSUIPC macros. You might also find information for your add-on aircraft in the User Contributions subforum, where many solutions have been found and published. Pete

You really need to get the problem sorted out with Saitek. FSUIPC can give you more flexibility and more accurate calibrations, but it would cost you money and you would be disappointed if it didn't fix the issue, which I suspect it can't. I do think it is something to do with values in the registry which can be fixed relatively easily once you know how, but I am not a Saitek user and cannot help directly. There will be people on the Saitek forum who can help with Saitek matters. That's why there are specific forums for specific products! ;-) Pete

Not sure why you've posted this here. If you were using FSUIPC to calibrate then maybe I could help somewhat, but perhaps not a lot -- the problem you describe is typical of Saitek installations and I think it needs a registry hack to fix. But you'll need to go to Saitek's forum for the details as I don't have them. Pete

Really? The log always has a title with the version shown, like this: Installer for FSUIPC4.DLL version 4.929 The first line in yours was Parameter"AppPath" which would be a few lines in, at the earliest. and your log finished with a ""not found" line, which would never be the case. I don't have a site. The Schiratti site is certainly up to date -- its links actually point to the versions here in the "Download Links" subforum, where I maintain download links to all my programs and documents. Regards Pete

How? Do I have to join or something? Why not email me at petedowson@btconnect.com? Pete