Pete Dowson

Last reply till 28th -- just on my way to Sri Lanka. How are you starting that DynamicFriction? If you start it with "LuaDebug ..." then it does the same as using the Debug/Trace Lua option. "STOP" on the Logging tab only affects the main internal logging options. Pete

What subforum? Who says that? There are several subforums in most forums -- see the list at the top of this one. They include Announcements FAQ - answers to Frequently Asked questions Download Links - latest versions of all my programs and other goodies here User Contributions - lots of useful stuff there But if you have a problem with FSUIPC or WideFS then you are in the right place here. But you need to give more information. "Waiting for clients" is normal for the Server when it is waiting for connections, and "Waiting for connection" is normal for the client when it is waiting for FS. Have you referred to the WideFS user guide? Try looking at the section about configuring your network. There are logs produced both by the server ("WideServer.log" in the FS Modules folder) and client ("WideClient.log" in the WideClient folder on the client PC). Those will help reveal any problems in connecting. I'm afraid this is my last posting here until I return on February 28th. Off on holiday in the morning. It might be a good idea to post details of your problems, with the contents of the log files pasted in, in a new thread with an appropriate title, because no one else is going to look at one called "lost key". If you make the title explicit then maybe someone else will be able to help you whilst I'm away. Pete

FSUIPC always makes a log! If any Lua contains bad lines the Lua will terminate and FSUIPC log will show the Error! Have you never looked in the FS Modules folder. Look now. See the FSUIPC4.LOG file? For line-by-line logging of the Lua plug in you just set the option for this in FSUIPC's logging tab. This must be done BEFORE starting the Lua, so either restart it afterwards with an assignment to a key or button, or restart FS after setting the option. The Lua program cannot control how fast you turn the rotary!!! I don't understand "making the encoder turns very slow in the same speed". By all means experiment. Are you saying you get results, but just not differnt ones for fast and slow? I thought you said itjust didn't work at all? Pete

Sorry, I've no idea. Have you tried logging? Did you look at the FSUIPC log to see if there were any errors? Does it actually get the device? What did you edit apart from the Vendor and Product names? Is that Lua otherwise the very latest one, installed by a current version of FSUIPC4? Pete

Right. The load problem is definitely not FSUIPC4, it is the SimConnect bug, which Microsoft knew about but couldn't find a full fix. It was much much worse in the original FSX RTM version. They applied a fix in SP1 which helped in 99% of cases but didn't clear it up completely. It is a timing problem between different threads and they never found a way to isolate it. I can say this for sure because that offset, 0x0001DBB5, is the entry point to FSUIPC4 from SimConnect, a function called "DLLStart". It is the call from SimConnect to that entry point which is causing the crash, probably because the DLL has been loaded once, checked by the Windows "Trust" system (which SimConnect always uses even though the prompts which occur in FSX were removed in P3D), and probably then unloaded and is being reloaded as the time another thread in SimConnect tries to call it. So, I can't actually do anything about it in my code as it doesn't get that far. Pete

The FSUIPC error log actually shows a successful load, starting at 235 System time = 11/02/2015 20:03:51 and being normally terminated, with P3D closure (not crash) a couple of minutes later! 92719 System time = 11/02/2015 20:05:24, Simulator time = 15:56:57 (19:56Z) 92719 *** FSUIPC log file being closed Minimum frame rate was 41.3 fps, Maximum was 46.8 fps Minimum available memory recorded was 2147Mb Average frame rate for running time of 12 secs = 44.7 fps Memory managed: 9 Allocs, 9 Freed ********* FSUIPC Log file closed *********** The crash data from Windows doesn't relate to that successful load and is later: Date: 11/02/2015 20:38:54 But since no log is produced it suggests FSUIPC was either not loaded, or barely so (the Log is started pretty much iimmediately FSUIPC receives the startup call).. )However, at least this time you provided the main information needed, the offset: Faulting module name: FSUIPC4.dll, version: 4.9.3.9, time stamp: 0x54d9e947 Exception code: 0xc0000005 Fault offset: 0x0001dbb5 I'll have a quick look to see if that tells me anything, but meanwhile you need to determine what the difference is between the successful load and the subsequent unsuccessful one. Maybe something is left set strangely? Maybe it only works correctly on a clean PC boot? Unfortunately I'm away from this evening for over two weeks, so it is doubtful I can solve it beforehand. There are (so far) no other similar reports and judging by the AVSIM P3D forum there are quite a few folks using it. I have it installed and working fine on two different systems, but I don't have Windows 8 or Windows 10 so I'm a bit concerned that maybe your Pre-Release operating system is involved.(as I see mgh suggests). BTW I see that FSUIPC regards Windows 10 as just another version of Windows 8. not that it will make any difference -- FSUIPC assumes Microsoft keep Windows backward compatible. However, I'd like it to be logged correctly, so can you tell me what the full version number is of that Windows build? Is it another 6.n increment or have they moved on to 7 or more? Pete

AdvDisplay hasn't been used or supported for years. The facilities are built into FSUIPC now. Please refer to the User Guide. Pete

This log shows to me that your Prepar3D installation is not correct. Certainly, the SIM1.DLL you have installed is not the one installed by the full install file provided by Lockheed Martin. If the version of P3D installed isn't one FSUIPC knows properly, then, yes, crashes will likely ensue. What version number, for instance, is the SIM1.DLL? Right click on it and select Properties. Please show me the FSUIPC4 Install log, also found in the Prepar3D Modules folder. Additionally I need the crash details provided by Windows. Pete

If there's no error logged for its loading, then no error was reported by Windows when FSUIPC asked for it to be run. So as far as FSUIPC knows it was successful. Are you sure it isn't still running invisibly? Maybe it isn't fully closing from before. Use Windows Task Manager to check the running Processes. Another thought. Maybe it needs to be run when FSUIPC and FS are ready. Try adding the READY option. One last check -- make sure the [Programs] section "at the end of the INI file" (as you say) is the ONLY [Programs] section! Pete

Well, unfortunately the crash information is missing the one crucial value I would need to really think anything: the module offset, which tells me WHERE in the program it crashed. Have you omitted it for some reason? Or doesn't it feature? If it doesn't that in itself is telling -- telling me the crash is happening before FSUIPC has actually managed to start. A description of how far the loading process of P3D proceeded before the crash is, of course, essential, so do you think you could tell me that too, please? Furthermore, the FSUIPC4.LOg file from the Modules folder, as far as it is produced, would help to see how far it got. If there is none, as well as no information about the crash place inside the DLL, then it would certainly indicate that this is the usual SimConnect timing glitch during DLL loading which afflicts a few quite severely but most not at all -- please see the FAQ subforum thread entitled "FSX fails to run after FSUIPC4 first installed", which although referring to FSX also, I'm sure. applies to P3D. On the other hand, if there is a log, there must surely be a crash location which you've omitted. Please find that, as well as pasting the contents of the log in a message here. Incidentally, I'm afraid that after tomorrow evening (Thursday 12th) I am away for over two weeks. Pete

Yes, it does. I have no control over the site you call "my website", it isn't mine! For up to date and correct information please always refer to the Download Links subforum here. Or of course, alternatively, you can read the Changes document included in the download! And as it is required that you keep FSUIPC up to date if you want support it is best to download any version later than the one you are using. Pete

Well FSUIPC can program keystrokes to button presses. Assigning keystrokes to keystrokes is rather odd, and I'm not sure it can work because the keystroke being sent will arrive back and interfere instead with the keystroke being read. Pete

Strange, then, because FSUIPC is usng the same Windows facilities as Prepar3D and other programs. It's all pretty standard. The only thing different in FSUIPC is that it uses the ID number assigned interbally by Windows. In the above case you have two devices on separate USB ports by the look of it -- IDs 0 and 1. You mention "throttle" in the singular, but FSUIPC is seeing two. Maybe you should show me the [JoyNames] section which FSUIPC gets when you have only one of the two devices connected -- one result for each, please. It looks like the Registry entries for the devices may be screwed up. If you are familiar with delving into the Registry with Regedit I could look up the areas you would need to check, and maybe Export for me to see. Pete

These values should be read as integers in any case -- they are 16-bit short unsigned integers! It would never work reading them as "strings"! Strings are numbers of ASCII characters, one character to an 8-bit byte! How do you think 4 hexadecimal digits can fit as 4 characters into a 16-bit value? BCD means Binary-Coded Decimal. The "Binary" part of that is the key. The value is a decimal value, but coded in such a way that each 4 bits contains one of the decimal digits you want! For example, the hexadecimal value 0x1895, has the decimal integer value 6293 but represents the frequency 118.95 (the first 1 is assumed). So you just read it and split off each group of 4 bits in turn. You can do that either by logical shifts and "Ands", or by repeated division by 16, taking the remainders each time. If you want the frequency as a string for display, use a formatting command to show it as hexadecimal. In C, using the standard library, that would be char result[7]; sprinf(result, "1%02X.%02X", value/256, value%256); The result of this in the example 0x1895 would be "118.95". I split the upper 8 bits from the lower so I could insert the decimal point. Pete

Aha! I'll need to remember that for any future problems like this! Thanks for letting me know! Pete

From late Thursday I will be off-line until about the 28th. Pete

Why not use Alt+Enter? Why use another key combination assigned to send a key combination? Pete

FSUIPC doesn't care about how or where you change aircraft or airports -- except perhaps in the former case (changing aircraft) if you are using aircraft-specific or profiles which need to be reloaded for the changed aircraft. Changing airports is completely invisible to FSUIPC except for the resulting changes in things like Latitude, Longitude and Altitude, which arrive all the time in any case whilst you are flying. So my conclusion would be that it is because of another add-on which is either interacting with FSUIPC or is affected by the different memory arrangements which will occur with different versions. Either way thee's no way I can use any information about old versions. The current supported version is 4.939. If you use that and get a crash please check the Windows Event Viewer and see what the crash was -- the module name and offset. If it does say it is FSUIPC4 then I am interested and would like that information, plus the FSUIPC4.LOG, FSUIPC4.INI files from the FS Modules folder, plus a list of add-ons and add-ins in use or active inside FS at the time. You should start a new thread with an appropriate title when starting a completely new subject which is barely related to the thread you are posting into. Please do that if you do come back with relevant information. Thanks {ete

Didn't you so as I suggested and test that the FSUIPC mouse look worked using such an assignment to the FSUIPC facility, first, (i.e. rather than the middle button)? That would at least be a clue! I've not yet met a system whee the FSUIPC mouse look didn't work. It is only issuing standard FS controls, as I said. Didn't you do anything I suggested? Pete

I told you already. Read this again please, repeated from my last reply! If you want the equivalent of the tiller offset 3BC4 but for throttles, why not use of of it's neighbours (offsets range from 3BA8 to 3BC6)? There's a whole list of assignable axes there -- the 6 labelled "quadrant axis N" are the 6 axes left to right on a PFC quadrant eg spoiler,throttles 1-4 and flaps. Pete

It works fine here. Does it work with the mouse look enabled by assignment to the FSUIPC control to turn it on or off? If so then maybe you have disabled the centre mouse button for this facility? That's an option you would have had to set explicitly by editing the INI file ("UseMidMouseBtn=Yes"). Enable Axis and Event logging in FSUIPC's logging tab, temporarily run FS in Windowed mode and enable FSUIPCs console log. Then you can see the results, in terms of FS controls, of what you do. The Mouse Look facility uses "Pan View" axis controls for the view direction and "Zoom In/Zoom Out" for the zooming. Without any of the mouse options enabled on the Miscellaneous tab FSUIPC doesn't interfere with the mouse at all. Sounds like your FS is rather screwed up! Either use FSX or FSUIPC not both. If you disable controllers in FSX, which you MUST if you assign in FSUIPC, then the FSX mouse look facility is also disabled. No where. That isn't an option. You simply hold it down for 'on', release it for 'off', or else assign a button or keypress to the mouselook toggle, on or off controls, as you wish. If you need to use the centre mouse button for other things you need to do such assignments and set the UseMidMoseBtn=No pasrameter in the INI file (before loading FS). Pete

Note that FSUIPC version 4.939, now released, includes the same G3D crash fix for FSX-SE as included for FSX-MS. Pete

It must have both, unless you got FSUIPC4 illicitly, or through the Japanese dealer, or from Project Magenta? Or perhaps you have another SimMarket account in a different name or email address? I can't really retrieve it for you, either, without your real name and any email addresses you might have used. Pete

Well, I have no idea what is wrong with your system, but the only clues I see are that th three devices Registered in Windows all return the same Error: 188 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0763\Calibration\0" 188 Found correct joystick Id 0 188 ... and a "GUID" value 188 DirectInput8Create failed, return = 80040154 188 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_075C\Calibration\0" 188 Found correct joystick Id 1 188 ... and a "GUID" value 188 DirectInput8Create failed, return = 80040154 188 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0BAC\Calibration\0" 188 Found correct joystick Id 2 188 ... and a "GUID" value 204 DirectInput8Create failed, return = 80040154 The devices are identified because they are registered, as also shown in your FSUIPC4 INI file: 0=Saitek Pro Flight Rudder Pedals0.GUID={9E00CBA0-8535-11E3-8007-444553540000} 1=Saitek X52 Flight Controller 1.GUID={9E00CBA0-8535-11E3-8008-444553540000} 2=Saitek Pro Flight Yoke2.GUID={9E00F2B0-8535-11E3-8009-444553540000} I tried Googling the error number, but didn't really find much of any use. One thing you could try is this "fix" by honestly I can't see how it is relevant: http://www.microsoft.com/en-us/download/details.aspx?id=3988 When you say "can" do you mean "can't", otherwise that doesn't make sense? So, it looks like there's something screwed up with the device installation. Try uninstalling them in the Windows device manager unplug them first). Then re-booting and plugging them in again. If that doesn't work I think something is messed up in your Windows installation. Pete

Sorry, I don't know anything about using the mouse wheel for panels. Certainly it isn't anything FSUIPC does, as I said. Depends which parts, which options. Most generally changeable options in [General] are set in the FSUIPC settings dialogue. Assignments and calibrations can be reloaded with changes using the Reload button on the relevant tab. Pete