Pete Dowson

Very very strange. "FSUIPC4.dll_unloaded" ...? What's that, I wonder? "versión: 0.0.0.0," Pretty old! I never made a version 0.0.0.0 the first FSUIPC 4 was 4.0.0.0. The location of the error, 6100F75F is also very suspicious. I'm still thinking that this is the SimConnect problem, and you need to refer to that thread I mentioned in the FAQ subforum. You could try the FSUIPC4 loader, as mentioned in that thread. Also, as a test, try renaming this module: PMDG\DLLs\PMDGOptions.dll so that it doesn't load. I don't know if your PMDG aircraft is fully up to date, but there were some early versions of PMDGoptions which somehow clashed with SimConnect's subsequent loading. Finally, get a SimConnect log of an attempt to run FSUIPC4 (i.e. tell it to load) -- there's a FAQ thread for that too. Regards Pete

Sorry, but I've never heard of Smartcars. If you run FS "as administrator" then you have to run everything "as administrator" but you should really not do that with either. Re-installing FSUIPC only purs the same files back in the same place. It accomplishes nothing really. Without more information I'm afraid I cannot help at all. You don't even say what version of FS you are using. I need that, plus the version number of FSUIPC, plus the FSUIPC Log file from the Modules folder, just as a start. Doesn't this "Smartcars" have a support site? It's their message. Pete

Why post a picture from 4.852? Have you referred to the thread "FSX fails to run after ..." in the FAQ subforum? Because if there's no log then FSUIPC4 hasn't even been run, ever. So it's a problem in Simconnect which is usually overcome by persistence, as stated in that thread. Please also check for FSX errors listed in the Windows event viewer (Start/Run-Event viewer- Windows Logs=Applications, Red error emblem on the left, FSX as "source". Get me the details from one of those, if that's the last "problem" you had. Pete

But the first log most definitely doe show that FSX terminated normally. There is no way FSUIPC can complete it's log ad provide its performance summary if you delete FSX forcibly via the Task Manager. Perhaps you really mean that you send FSX a close message (like clicking on the X close icon in Windowed mode, top tight), rather than end the process? If this is what you mean then in fact FSX was still running and maintaining the good frame rate I mentioned. Maybe it is the graphics which are frozen? Try some things: 1. Run in Windowed mode, and if it appears to have hung see if the buttons on the title bar do work. 2.Display the frame rate or other things on screen via Shift+Z. See if they also freze or continue to change. 3. Try without LINDA. I see that plays a prominent part in your system, but try just for once. It may help narrow things down. I'm wondering it it is due to a safety interlock on Lua plug-ins, which I think LINDA uses profusely. Apart from LINDA, do you have any Lua plug-ins being loaded via [Auto ...] sections in the FSUIPC4.INI file? (Perhaps you could paste the INI file in a reply here -- it may help). Regards Pete

Sorry, I can't support WidevieW, and FSUIPC doesn't have anything to do with graphics rendering in any case. Maybe WidevieW uses SLEW or Pause mode on its clients? That might explain it. Ask at WidevieW support. Regards Pete

Not much, really. It's a crash in DirectInput. Are you using buttons or joysticks on that PC? Does PROSIM use any? Looks like some sort of incompatiblity. If you don't use WideFS to send button presses to FSUIPC for assignment there, try simply stopping WideClient scanning devices -- put "ButtonScanInterval=0" into the main [Config] section of the INI file. Regards Pete

Not without more information. You posted an Install log and the DLL.XML, neither of which is particularly useful for this. Is the an FSUIP4.LOG file in the Modules folder? If so, paste the please. If not then FSUIPC4 is not even being loaded, so it is probably the simconnect timeing problem -- see the relevant thread in the FAQ subforum about that. As for the "sever problem" crash, can you please provide that actual details. They identify what it may be due to and are always needed. Pete

If the FSUIPC calibration tab sees your "axis" then it is assigned already, because the calibration tab does NOT process axis inputs, only the controls they are assigned to. In the axis assignment tab you move the axis to get it recognised. Profile assignment is premature when there's nothing there. Regards Pete

What is this file to be "copied and pasted into the Modules file of FSX"? The FSUIPC installer creates the Modules folder and installs the files you need. Please tell me what "file" you mean. What does not work at all? FSUIPC? If it "does not work at all" how are you able ro "configure the buttons"? What buttons are you trying to use, and what are you assigning them to do? What plane are you using? A default plane or an add-on plane? Test on default planes first. Many add-ons need their own special commands. You do not choose aircraft in FSUIPC. You choose aircraft in FS's Aircraft menu. All of the FSUIPC documents are provided and installed in the "FSUIPC Documents" folder withing the FS Modules folder! I'm afraid there's no Spanish translations at present. There are some French manuals, if that's any good. Otherwise the only Spanish help might be found via the old thread: http://forum.simflight.com/topic/59312-instructions-in-spanish/ Regards Pete

I don't want to see a photo. You need to describe exactly what you did, how far it got, and then give the crash details -- not just "error of FSUIPC". You also need to version number of FSUIPC, and the log file from the Modules folder, and a list of add-ons you are using. Regards Pete

I think you must have a motherboard problem, then. Pete

FSUIPC always creates an INI file. If there is no INI file and no LOG file in the FS Modules folder, then FSUIPC has not been run, at all! I think you must either be looking in the wrong place, or you have Windows hiding filetypes from you (as recommended NOT to in the FSUIPC documentation). In this case the file will probably appear to be "FSUIPC" or "FSUIPC4" with type "configuration settings", whilst the log will be a "text" file. Pete

The amount of free memory, in kb, is already updated every 10 seconds in the offset 024C 32-bit integer). You could display it easily with a Lua plug-in, or, if you wish, try to overwrite something readable by gauges -- but most such are not writeable. Incidentally, I don't really understand why OOMs are such a problem for some folks. There must be some really bad add-ons about with memory leaks. I've only ever had an OOM once, and that turned out to be a memory leak in one of my own private drivers. Regards Pete

Why not simply interpret ALL of the buttons you are using, in the Lua plug-in, and action them there? There's no point writing stuff to an offset just to read it back. All your plug-in wants to do is set values for NAV/COM frequencies based on buttons being pressed. Right? Make it all self contained. Pete

You are entering something wrong then. All three parts (name, email, key) must be EXACTLY right. If you still have the FSX installation, just copy the FSUIPC4.KEY file from its Modules folder into the P3D Modules folder. Pete

Hmm. This log shows that FSUIPC is continuing, that there is no "hang". If FSX was hanging then you could not get a normal close down, as you clearly have here: It was evidently running well for 11 minutes with an average frame rate of 25.4 fps. Where are these "hangs/freezes"? Perhaps you need to describe more fully what you actually see, because if FSX freezes forever the only way out it to use Task Manager to teminate it. Then FSUIPC doesn't finish nice and tidily like this. Your log with 4.864 doesn't look a lot different, execpt that you've changed aircraft more. Regards Pete

Well, not entirely. To start with you are using an unsupported version of FSUIPC. Version 4.91 is the earliest supported version for FSX. But the log does clearly show that FSUIPC isd working fine, and is most certainly not responsible for "hanging" your FSX. It continued okay and terminated normally, and FSX was running okay for nearly 8 minutes with an average frae rate of 22.9fps. So, it looks like that DBS program is messing you about. That message "FollowMe service initialised and ready" intrigues me. The only program I know which uses that is the one by Daniel van Os which was discontinued in 2011. The interface in FSUIPC4 was mainly to allow the as yet unreleased Version 5 of Radar Contact to get taxi routes generated by Daniel's FollowMe. It actually looks like RCV5 will never appear either, so the code in FSUIPC4 is really pretty redundant -- I should probably remove it. What I don't understand is what DBS's software is doing with it -- or are you actually running Daniel's "FollowMe2"? Regards Pete

No, it must be a ZERO! Did I type an 'O'? Ouch. Sorry. It should always work -- the event is automatically triggered when the Lua is loaded as well as when the offset changes. Regards Pete

Yes, if you've deleted them already. Be sure to go into Butto and Axes tabs and see if you can assign anything. Pete

The joystick interface being used in the Lua functions you are using only recognises 32 buttons. The later 64-button capabilities of DirectX were too late for FS and FSUIPC cannot risk using a later version. The HID facilities built into the Lua COM library would be a better way altogether for you. Please check it out. If doesn't use DirectX, but a direct USB link, much as a joystick driver might.There's a HIDdemo.lua example in the Lua stuff installed in your FSUIPC Documents folder. Offset 0350 is clearly documented as being 2 bytes, so 2 x 8 = 16 bits. "writeDD" is clearly documented as writing a 64 bit signed integer. So how do you work out getting 64 bits into 16? Look through the list of functions for the 16-bit unsigned value (wrteUW). It doesn't look anywhere near correct. The representation is hexadcimal (what's known as "BCD" -- binary coded decimal). Try using FSInterrogate and viewing the sort of values there. You seem to be trying to concoct something in decimal. For hex the multipliers would be values like 4096 (1st digit) , 256 (2nd), 16 (3rd) and 1 (4th). Don't forget the first digit (1) is omitted). Pete

Just caught this before leaving ... Could you now just try slipping the 4.913a DLL in (download: FSUIPC 4.913a). Maybe it was something to do with the older files. Else, if there's something only changed between 4.90 and 4.91 it might be easier for me to locate. Back Sunday or Monday ... Regards Pete

No, you don't need a new registration if you have a valid FSUIPC4 registration. A lot of folks have been having problems with joysticks on Windows 8. It doesn't appear to be anything to do with either FS or FSUIPC (and it's mostly the same in both), but I have read that some have found it better with FSUIPC axis assignment. I've no idea why that should be as both FS/P3D and FSUIPC use the same methods. Regards Pete

No idea, sorry. there is nothing FSUIPC will be doing when you "exit" a flight. Why do you do this when you can just go direct to the Aircraft menu and choose another aircraft? FSUIPC will of course be checking your INI file for different Profile or Aircraft Specific settings when you change aircraft, but this is straightforward and is done all the time. Maybe there's something screwed up in your INI file? Also you seem to report contradictory symptoms -- you say FSX is "crashing" but then you say it is "not responding". Those are two very different things. If it is crashing there will be a crash report -- check the Windows event viewer, application logs, for the error details. More information is needed please -- the INI file, the LOG file, the crash details, or at least clarification of what is actualy occurring. Regards Pete

What file are you copying to the FSX folder? Sorry, I don'ty understand the relevance of a file to your question! I think there must be something wrong with the translater, because this isn't making any sense. There is no option to choose and aircraft in FSUIPC options. Pete

But the Registry "EXE Path" entry for FS9 clearly says it is installed in "C:\Users\AguAcer\Downloads\FS9\FSUIPC", so the repair obviously didn't work. Your registry is evidently bad (how?), and you may need to delete the entry for FS9 manually. Regards Pete