Scott B Posted February 5, 2017 Report Posted February 5, 2017 (edited) I've been using the registered version of FSUIPC for several years now and very much appreciate it. Thank you. I envy your brain. I've recently upgraded from 4.955c to 4.961 and found that my physical rotary encoders will no longer operate the A2A Cherokee and Commanche virtual Com1 & 2, Nav 1 & 2, AP, or ADF knobs. I do not fully understand FSUIPC and couldn't solve it reading the advanced manual (probably overlooked or not understood). If I revert back to 4.955c, all my physical rotary encoders work perfectly to operate all A2A radio knobs. Nothing has changed or no updates were applied to A2A aircraft. It doesn't seem to matter if I assign the Lvar to a physical rotary encoder or a simple joystick button (or keyboard key for that matter). The A2A virtual radio knobs etc. rotate properly using the mouse wheel. The issue doesn't seem to effect the Xponder at all. But if my physical Xponder rotaries are assigned to operate the virtual A2A radios, they again cease to function. And even more strange, if I rotate the A2A radio knobs with the mouse wheel several turns clockwise, for example, then a joystick button can be used return the A2A knob counterclockwise that same number of revolutions before it stops, at which time it completely ceases to function clockwise or counterclockwise. This is part of the Com 1 macro, for example: 16=L:Com1FreqInnerKnob=Inc 17=L:Com1FreqInnerKnob=Dec And here is the associated "fsuipc.ini" entry (using a simple joystick button): 2=RA,11,CM1:16,0 -{Macro 01 A2A 180: L:Com1FreqInnerKnob inc}- 3=RA,10,CM1:17,0 -{Macro 01 A2A 180: L:Com1FreqInnerKnob dec}- Again, ver 4.955c with the same entries works perfectly. I can add parameters to the above entries and make it work (like 100 or 1000 along with -100 or -1000) but I'm not sure that's proper. This is likely something I've overlooked and is probably simple but, it has me stumped. Apologies in advance. What am I missing?? Thank you Scott Edited February 5, 2017 by Scott B
Pete Dowson Posted February 5, 2017 Report Posted February 5, 2017 1 hour ago, Scott B said: Recently upgraded 4.955c to 4.961 and found that my A2A Cherokee and Commanche rotary encoders will not operate the virtual Com, Nav, AP, or ADF knobs. I do not fully understand FSUIPC and couldn't solve it reading the advanced manual (probably overlooked or not understood). If I revert back to 4.955c, all my physical rotary encoders work perfectly to operate all A2A radios. It may be that the GUIDs associated with your devices are wrong. I recently fixed an error in FSUIPC whereby the GUIDs were not being correctly used to identify devices, as they should always have been. If there are some old incorrect entries in the [JoyNames] section of your settings, the FSUIPC4.INI file, then it may be that the current correct GUIDs are now associated with old joystick letters or numbers, so your assignments are ineffective because they are expective a non-existent device. I'm not sure what changes the GUIDs -- probably a Windows update -- a change of Windows version -- or of PC. And that could have been any time since you had those devices and started using FSUIPC for assignments. It should be easy to fix, and I'll show you if you show me your FSUIPC4.INI file. Pete
Scott B Posted February 5, 2017 Author Report Posted February 5, 2017 Thank you sir. I tend to keep a close eye on my config files including fsuipc4.ini with ExamDiff and back them up regularly before upgrading. I only see a few entry differences after upgrading to 4.961 and none appear to involve the joystick GUID's, for what that's worth. This process has served me well with previous upgrades all the way back to 4.929. I've attached my streamlined fsuipc4.ini file. It only reflects a Logitech joystick. Still, this streamlined version will not work with ver 4.961 yet it does work with 4.955c. I couldn't attach the fsuipc4.ini file that contains all of my usb board and macro entries because the file size exceeds the attachment limit, and it seemed like too much to copy/paste. But let me know if you want the whole enchilada! Scott FSUIPC4.ini
Pete Dowson Posted February 6, 2017 Report Posted February 6, 2017 10 hours ago, Scott B said: I only see a few entry differences after upgrading to 4.961 and none appear to involve the joystick GUID's, for what that's worth You misunderstood. It's the check INSIDE FSUIPC which was corrected. The FSUIPC settings won't need to have changed! 10 hours ago, Scott B said: I couldn't attach the fsuipc4.ini file that contains all of my usb board and macro entries because the file size exceeds the attachment limit, and it seemed like too much to copy/paste. Well it doesn't seem to deter others! You can use the <> button above to place the text into a frame with scroll bars where applicable. In the INI file you attached, the [JoyNames] section contains this: [JoyNames] AutoAssignLetters=Yes A=Logitech Extreme 3D 0=Logitech Extreme 3D 0.GUID={8CB99BC0-67B3-11E6-8001-444553540000} Is that your only device? No yoke or throttle or anything? That device does it all? Anyway, I think the problem is that the GUID for device A is missing. You need the section to read: [JoyNames] AutoAssignLetters=Yes A=Logitech Extreme 3DA.GUID={8CB99BC0-67B3-11E6-8001-444553540000} 0=Logitech Extreme 3D 0.GUID={8CB99BC0-67B3-11E6-8001-444553540000} Try that and let me know. There are NO other chanes in FSUIPC which would affect your device's actions, only the GUID check. Pete
Scott B Posted February 6, 2017 Author Report Posted February 6, 2017 Hi Pete. Thanks. Here is the file using Ver 4.955c that works. In the following message, I will attach the file that does not work using ver 4.961. Scott FSUIPC4.ini
Scott B Posted February 6, 2017 Author Report Posted February 6, 2017 And here is the file that does not work using ver 4.961. Scott FSUIPC4.ini
Scott B Posted February 6, 2017 Author Report Posted February 6, 2017 7 hours ago, Pete Dowson said: Is that your only device? No yoke or throttle or anything? That device does it all? Anyway, I think the problem is that the GUID for device A is missing. You need the section to read: [JoyNames] AutoAssignLetters=Yes A=Logitech Extreme 3DA.GUID={8CB99BC0-67B3-11E6-8001-444553540000} 0=Logitech Extreme 3D 0.GUID={8CB99BC0-67B3-11E6-8001-444553540000} Try that and let me know. There are NO other chanes in FSUIPC which would affect your device's actions, only the GUID check. Pete I do have several other devices but for troubleshooting reasons, I plugged in one simple Logitech joystick and did a fresh install of FSUIPC 4.961 and found that it wouldn't work even with one device. I saw no reason to continue troubleshooting with all devices plugged in. I didn't manually remove that line in red above. That line wasn't there after a fresh installation. Thank you Scott
Pete Dowson Posted February 6, 2017 Report Posted February 6, 2017 8 minutes ago, Scott B said: And here is the file that does not work using ver 4.961. Apart from recording the version of FSUIPC, the files are identical. I don't know why you are supplying them. You haven't even made the change I suggested. I do not need the whole file. That change is all you should need. 1 minute ago, Scott B said: I didn't manually remove that line in red above. That line wasn't there after a fresh installation. It doesn't get added by itself UNLESS you are starting from scratch with no letters allocated, in which case both lines will be added for each device with different letters for each one. You need to add the line yourself now. Pete
Scott B Posted February 6, 2017 Author Report Posted February 6, 2017 4 hours ago, Pete Dowson said: Apart from recording the version of FSUIPC, the files are identical. I don't know why you are supplying them. You haven't even made the change I suggested. I do not need the whole file. That change is all you should need. Are you saying the files I uploaded in my previous post doesn't contain the line you submitted in red? If so, I'm most certainly loosing my mind, in which case, I should stop posting. Since you don't need the whole file, below I've pasted the "JoyNames" portion of the "FSUIPC4.ini" file straight from my "C:\FSX\Modules" folder, which I tried again just now first using FSUIPC4 ver 4.961 (wihich doesn't work) and then ver 4.955c (which does work). And yes, apart from recording the version of FSUIPC (and maybe the history line), the files I uploaded in my previous post are identical. I posted them because I thought you'd want to see them and to demonstrate that only the "FSUIPC4.DLL" version changes while troubleshooting this issue, not the "FSUIPC4.ini" file, which I'm pretty sure contains the correct GUID entries you suggested. [JoyNames] AutoAssignLetters=Yes A=Logitech Extreme 3D A.GUID={8CB99BC0-67B3-11E6-8001-444553540000} 0=Logitech Extreme 3D 0.GUID={8CB99BC0-67B3-11E6-8001-444553540000} Anyway, ver 4.955c works great and all of your versions have worked great so I have no issues sticking with the older version as it does everything that I need (and more). After reading some posts on this site, it seems I've bypassed some upgrades anyway prior to 4.961, and never missed them. Thank you for your efforts and troubles. Scott
Pete Dowson Posted February 7, 2017 Report Posted February 7, 2017 2 hours ago, Scott B said: Are you saying the files I uploaded in my previous post doesn't contain the line you submitted in red? If so, I'm most certainly loosing my mind, in which case, I should stop posting. No, sorry, they were there. It was me. There's so many crash problems with P3D at present that I'm overloaded and rushing. Sorry. I also haven't slept properly for several days. So your problem isn't the GUID matching. I had assumed that because it was the mst recent change and I'm not aware of any other which could affect assignments. So, going back to the original problem reported, I need to get to the bottom of it. Is this the entire assignment list for device A or had you abbreviated it for me? [Buttons] PollInterval=25 ButtonRepeat=20,10 1=RA,0,C65588,0 -{BRAKES}- 2=RA,11,CM1:16,0 -{Macro 01 A2A 180: L:Com1FreqInnerKnob inc}- 3=RA,10,CM1:17,0 -{Macro 01 A2A 180: L:Com1FreqInnerKnob dec}- Does the brake assignment work? Does FSUIPC see joystick A properly -- does it respond to it in the Assignment tabs? Can you enable Button and Key logging in the FSUIPC Logging tab, please and use the above assigments and show me the results? Thanks, Pete
Scott B Posted February 7, 2017 Author Report Posted February 7, 2017 Thank you sir. I don't know how you do it! You need teams of people. Know that your program single-handedly transforms FSX into a breathing thing. That is the entire assignment list for device A (Logitech). It is not abbreviated. Keep in mind I'm only using this joystick to troubleshoot, with as few assignments as possible. Does the brake assignment work? I didn't check that. Nor did I check the joystick in the Assignment tabs. I've been tunnel visioned on the radio knobs and macros. I will enable Button and Key logging and post results. But at the moment I've been confronted with a different issue and can't get FSX to load. I will have to get back to you. It could be because I've been switching between FSUIPC versions so much. Edit: I will check event viewer for some info too. Hope you rest. Scott
Scott B Posted February 7, 2017 Author Report Posted February 7, 2017 A quick note: Event viewer is indicating tons of EZCA errors. I wonder if that could be the culprit? Scott
Pete Dowson Posted February 7, 2017 Report Posted February 7, 2017 And what happens if you tell Windows to go ahead and let FSUIPC load? That message box is often only a warning because of a previous crash, not one in this session. Off to bed now. Pete
Scott B Posted February 7, 2017 Author Report Posted February 7, 2017 Well, the first time I clicked "yes" and told Windows to let it load, FSX just dissappeared and didn't complete it's launch and almost simultaneiously another smaller window popped up indicating an error that I now can't remember the details of. Sorry, I know that's not helpful, and probably not clear. The second time I told Windows No to not load FSUIPC and FSX failed to complete launch again, I think. The third time I think FSX launched normally after clicking "no". I then deleted the FSUIPC.dll file from Modules, and removed the FSUIPC entries from the Trusted part of FSX.cfg. Rebooted the PC. Then I used your installer to install ver 4.961 (I left my *.key and fsuipc4.ini file in place). After that, I launched FSX fourth time and it launched normally, after I agreed to "unknown publisher" and "Trusted Module" normal to FSX of course. I've never seen that other window before though, that I recall. Again, that's probably not very clear or helpful. Anyway, FSX is back up and running with FSUIPC Ver 4.961. FSUIPC does see the joystick properly and responds to it in the Assignment tab and Calibration tab, and in the virtual cockpit as well. The brake assignment works fine although I may change that to something easier to visualize. But for the log below, I left it as is. The radios knobs still will not work unless, as I described in my original post. I rotate the knob a few revolutions with the mouse wheel first. Then the virtual radio knob will respond to the joystick button but only by reversing those same number of revolutions... then it stops. Text is getting fuzzy... Thanks, Scott ********* FSUIPC4, Version 4.961 (1st February 2017) by Pete Dowson ********* Windows 10 Pro 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0) fsx.exe version = 10.0.61637.0 Reading options from "C:\FSX\Modules\FSUIPC4.ini" Running inside FSX on Windows 10 Module base=6B250000 User Name="Scott " User Addr="" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired 78 System time = 06/02/2017 21:00:56 78 FLT path = "C:\Users\Scott\Documents\Flight Simulator X Files\" 78 ------ Module Version Check ------ 78 acontain.dll: 10.0.61637.0 78 api.dll: 10.0.61637.0 78 controls.dll: 10.0.61637.0 78 fs-traffic.dll: 10.0.61637.0 78 G3D.dll: 10.0.61637.0 78 language.dll: 10.0.61637.0 78 sim1.dll: 10.0.61637.0 78 visualfx.dll: 10.0.61637.0 78 weather.dll: 10.0.61637.0 78 window.dll: 10.0.61637.0 78 ---------------------------------- 109 Trying to connect to SimConnect Acc/SP2 Oct07 ... 140 FS path = "C:\FSX\" 796 ---------------------- Joystick Device Scan ----------------------- 875 Product= Logitech Extreme 3D 875 Manufacturer= Logitech 875 Vendor=046D, Product=C215 (Version 2.4) 875 Serial Number= 875 ------------------------------------------------------------------- 1015 LogOptions=40000000 00000001 1015 ------------------------------------------------------------------- 1015 ------ Setting the hooks and direct calls into the simulator ------ 1015 --- CONTROLS timer memory location obtained ok 1015 --- SIM1 Frictions access gained 1015 --- FS Controls Table located ok 1015 --- Installed Mouse Macro hooks ok. 1015 --- Wind smoothing fix is fully installed 1015 --- G3D.DLL fix attempt installed ok 1015 --- SimConnect intercept for texts and menus option is off 1015 --- All links checked okay 1015 ------------------------------------------------------------------- 1031 SimConnect_Open succeeded: waiting to check version okay 1031 Trying to use SimConnect Acc/SP2 Oct07 1031 Opened separate AI Traffic client okay 2796 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 2796 Initialising SimConnect data requests now 2796 FSUIPC Menu entry added 2828 C:\Users\Scott\Documents\Flight Simulator X Files\Fsuipc Cherokee Troubleshooting.FLT 2828 C:\FSX\SimObjects\Airplanes\A2A_Piper_PA28_180_Cherokee\PA28_180.AIR 15171 User Aircraft ID 1 supplied, now being used 38718 System time = 06/02/2017 21:01:35, Simulator time = 09:02:27 (14:02Z) 38859 Aircraft="Piper Pa-28-180 Cherokee" 42890 Starting everything now ... 44062 Advanced Weather Interface Enabled 51375 KEYDOWN: VK=83, Waiting=0, Repeat=N, Shifts=0 51375 .. Key not programmed -- passed on to FS 51468 KEYUP: VK=83, Waiting=0 55671 Button changed: bRef=0, Joy=0 (A), Btn=11, Pressed 55671 [Buttons] 2=RA,11,CM1:16,0 55671 Repeating flag set: bRef=0, Joy=0, Btn=11 (RepeatDelayCtr=1) 55828 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=11, (RepeatOk sets 2) 55828 [Buttons] 2=RA,11,CM1:16,0 55828 Repeating flag set: bRef=0, Joy=0, Btn=11 (RepeatDelayCtr=11) 55859 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=11, (RepeatOk sets 2) 55859 [Buttons] 2=RA,11,CM1:16,0 55859 Repeating flag set: bRef=0, Joy=0, Btn=11 (RepeatDelayCtr=11) 55890 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=11, (RepeatOk sets 2) 55890 [Buttons] 2=RA,11,CM1:16,0 55890 Repeating flag set: bRef=0, Joy=0, Btn=11 (RepeatDelayCtr=11) 55906 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=11, (Result 4) 55906 [Buttons] 2=RA,11,CM1:16,0 55937 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=11, (RepeatOk sets 2) 55937 [Buttons] 2=RA,11,CM1:16,0 55937 Repeating flag set: bRef=0, Joy=0, Btn=11 (RepeatDelayCtr=11) 55953 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=11, (Result 4) 55953 [Buttons] 2=RA,11,CM1:16,0 55984 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=11, (RepeatOk sets 2) 55984 [Buttons] 2=RA,11,CM1:16,0 55984 Repeating flag set: bRef=0, Joy=0, Btn=11 (RepeatDelayCtr=11) 56015 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=11, (RepeatOk sets 2) 56015 [Buttons] 2=RA,11,CM1:16,0 56015 Repeating flag set: bRef=0, Joy=0, Btn=11 (RepeatDelayCtr=11) 56031 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=11, (Result 4) 56031 [Buttons] 2=RA,11,CM1:16,0 56046 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=11, (RepeatOk sets 2) 56046 [Buttons] 2=RA,11,CM1:16,0 56046 Repeating flag set: bRef=0, Joy=0, Btn=11 (RepeatDelayCtr=11) 56093 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=11, (RepeatOk sets 2) 56093 [Buttons] 2=RA,11,CM1:16,0 56093 Repeating flag set: bRef=0, Joy=0, Btn=11 (RepeatDelayCtr=11) 56109 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=11, (Result 4) 56109 [Buttons] 2=RA,11,CM1:16,0 56125 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=11, (RepeatOk sets 2) 56125 [Buttons] 2=RA,11,CM1:16,0 56125 Repeating flag set: bRef=0, Joy=0, Btn=11 (RepeatDelayCtr=11) 56171 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=11, (RepeatOk sets 2) 56171 [Buttons] 2=RA,11,CM1:16,0 56171 Repeating flag set: bRef=0, Joy=0, Btn=11 (RepeatDelayCtr=11) 56187 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=11, (Result 4) 56187 [Buttons] 2=RA,11,CM1:16,0 56203 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=11, (RepeatOk sets 2) 56203 [Buttons] 2=RA,11,CM1:16,0 56203 Repeating flag set: bRef=0, Joy=0, Btn=11 (RepeatDelayCtr=11) 56234 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=11, (RepeatOk sets 2) 56234 [Buttons] 2=RA,11,CM1:16,0 56234 Repeating flag set: bRef=0, Joy=0, Btn=11 (RepeatDelayCtr=11) 56265 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=11, (RepeatOk sets 2) 56265 [Buttons] 2=RA,11,CM1:16,0 56265 Repeating flag set: bRef=0, Joy=0, Btn=11 (RepeatDelayCtr=11) 56296 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=11, (RepeatOk sets 2) 56296 [Buttons] 2=RA,11,CM1:16,0 56296 Repeating flag set: bRef=0, Joy=0, Btn=11 (RepeatDelayCtr=11) 56312 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=11, (Result 4) 56312 [Buttons] 2=RA,11,CM1:16,0 56328 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=11, (RepeatOk sets 2) 56328 [Buttons] 2=RA,11,CM1:16,0 56328 Repeating flag set: bRef=0, Joy=0, Btn=11 (RepeatDelayCtr=11) 56375 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=11, (RepeatOk sets 2) 56375 [Buttons] 2=RA,11,CM1:16,0 56375 Repeating flag set: bRef=0, Joy=0, Btn=11 (RepeatDelayCtr=11) 56390 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=11, (Result 4) 56390 [Buttons] 2=RA,11,CM1:16,0 56406 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=11, (RepeatOk sets 2) 56406 [Buttons] 2=RA,11,CM1:16,0 56406 Repeating flag set: bRef=0, Joy=0, Btn=11 (RepeatDelayCtr=11) 56453 Button changed: bRef=0, Joy=0 (A), Btn=11, Released 57015 Button changed: bRef=0, Joy=0 (A), Btn=10, Pressed 57015 [Buttons] 3=RA,10,CM1:17,0 57015 Repeating flag set: bRef=0, Joy=0, Btn=10 (RepeatDelayCtr=1) 57156 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (RepeatOk sets 2) 57156 [Buttons] 3=RA,10,CM1:17,0 57156 Repeating flag set: bRef=0, Joy=0, Btn=10 (RepeatDelayCtr=11) 57203 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (RepeatOk sets 2) 57203 [Buttons] 3=RA,10,CM1:17,0 57203 Repeating flag set: bRef=0, Joy=0, Btn=10 (RepeatDelayCtr=11) 57218 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (Result 4) 57218 [Buttons] 3=RA,10,CM1:17,0 57234 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (RepeatOk sets 2) 57234 [Buttons] 3=RA,10,CM1:17,0 57234 Repeating flag set: bRef=0, Joy=0, Btn=10 (RepeatDelayCtr=11) 57265 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (RepeatOk sets 2) 57265 [Buttons] 3=RA,10,CM1:17,0 57265 Repeating flag set: bRef=0, Joy=0, Btn=10 (RepeatDelayCtr=11) 57296 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (RepeatOk sets 2) 57296 [Buttons] 3=RA,10,CM1:17,0 57296 Repeating flag set: bRef=0, Joy=0, Btn=10 (RepeatDelayCtr=11) 57328 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (RepeatOk sets 2) 57328 [Buttons] 3=RA,10,CM1:17,0 57328 Repeating flag set: bRef=0, Joy=0, Btn=10 (RepeatDelayCtr=11) 57343 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (Result 4) 57343 [Buttons] 3=RA,10,CM1:17,0 57359 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (RepeatOk sets 2) 57359 [Buttons] 3=RA,10,CM1:17,0 57359 Repeating flag set: bRef=0, Joy=0, Btn=10 (RepeatDelayCtr=11) 57406 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (RepeatOk sets 2) 57406 [Buttons] 3=RA,10,CM1:17,0 57406 Repeating flag set: bRef=0, Joy=0, Btn=10 (RepeatDelayCtr=11) 57421 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (Result 4) 57421 [Buttons] 3=RA,10,CM1:17,0 57437 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (RepeatOk sets 2) 57437 [Buttons] 3=RA,10,CM1:17,0 57437 Repeating flag set: bRef=0, Joy=0, Btn=10 (RepeatDelayCtr=11) 57453 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (Result 4) 57453 [Buttons] 3=RA,10,CM1:17,0 57500 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (RepeatOk sets 2) 57500 [Buttons] 3=RA,10,CM1:17,0 57500 Repeating flag set: bRef=0, Joy=0, Btn=10 (RepeatDelayCtr=11) 57515 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (Result 4) 57515 [Buttons] 3=RA,10,CM1:17,0 57546 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (RepeatOk sets 2) 57546 [Buttons] 3=RA,10,CM1:17,0 57546 Repeating flag set: bRef=0, Joy=0, Btn=10 (RepeatDelayCtr=11) 57562 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (Result 4) 57562 [Buttons] 3=RA,10,CM1:17,0 57593 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (RepeatOk sets 2) 57593 [Buttons] 3=RA,10,CM1:17,0 57593 Repeating flag set: bRef=0, Joy=0, Btn=10 (RepeatDelayCtr=11) 57625 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (RepeatOk sets 2) 57625 [Buttons] 3=RA,10,CM1:17,0 57625 Repeating flag set: bRef=0, Joy=0, Btn=10 (RepeatDelayCtr=11) 57640 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (Result 4) 57640 [Buttons] 3=RA,10,CM1:17,0 57671 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (RepeatOk sets 2) 57671 [Buttons] 3=RA,10,CM1:17,0 57671 Repeating flag set: bRef=0, Joy=0, Btn=10 (RepeatDelayCtr=11) 57703 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (RepeatOk sets 2) 57703 [Buttons] 3=RA,10,CM1:17,0 57703 Repeating flag set: bRef=0, Joy=0, Btn=10 (RepeatDelayCtr=11) 57718 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (Result 4) 57718 [Buttons] 3=RA,10,CM1:17,0 57734 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (RepeatOk sets 2) 57734 [Buttons] 3=RA,10,CM1:17,0 57734 Repeating flag set: bRef=0, Joy=0, Btn=10 (RepeatDelayCtr=11) 57781 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (RepeatOk sets 2) 57781 [Buttons] 3=RA,10,CM1:17,0 57781 Repeating flag set: bRef=0, Joy=0, Btn=10 (RepeatDelayCtr=11) 57796 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (Result 4) 57796 [Buttons] 3=RA,10,CM1:17,0 57812 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (RepeatOk sets 2) 57812 [Buttons] 3=RA,10,CM1:17,0 57812 Repeating flag set: bRef=0, Joy=0, Btn=10 (RepeatDelayCtr=11) 57843 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (RepeatOk sets 2) 57843 [Buttons] 3=RA,10,CM1:17,0 57843 Repeating flag set: bRef=0, Joy=0, Btn=10 (RepeatDelayCtr=11) 57875 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (RepeatOk sets 2) 57875 [Buttons] 3=RA,10,CM1:17,0 57875 Repeating flag set: bRef=0, Joy=0, Btn=10 (RepeatDelayCtr=11) 57890 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (Result 4) 57890 [Buttons] 3=RA,10,CM1:17,0 57921 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=10, (RepeatOk sets 2) 57921 [Buttons] 3=RA,10,CM1:17,0 57921 Repeating flag set: bRef=0, Joy=0, Btn=10 (RepeatDelayCtr=11) 57953 Button changed: bRef=0, Joy=0 (A), Btn=10, Released 59187 Button changed: bRef=0, Joy=0 (A), Btn=0, Pressed 59187 [Buttons] 1=RA,0,C65588,0 59187 Repeating flag set: bRef=0, Joy=0, Btn=0 (RepeatDelayCtr=1) 59187 FS Control Sent: Ctrl=65588, Param=0 59343 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=0, (RepeatOk sets 2) 59343 [Buttons] 1=RA,0,C65588,0 59343 Repeating flag set: bRef=0, Joy=0, Btn=0 (RepeatDelayCtr=11) 59343 FS Control Sent: Ctrl=65588, Param=0 59375 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=0, (RepeatOk sets 2) 59375 [Buttons] 1=RA,0,C65588,0 59375 Repeating flag set: bRef=0, Joy=0, Btn=0 (RepeatDelayCtr=11) 59375 FS Control Sent: Ctrl=65588, Param=0 59390 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=0, (Result 4) 59390 [Buttons] 1=RA,0,C65588,0 59421 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=0, (RepeatOk sets 2) 59421 [Buttons] 1=RA,0,C65588,0 59421 Repeating flag set: bRef=0, Joy=0, Btn=0 (RepeatDelayCtr=11) 59421 FS Control Sent: Ctrl=65588, Param=0 59453 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=0, (RepeatOk sets 2) 59453 [Buttons] 1=RA,0,C65588,0 59453 Repeating flag set: bRef=0, Joy=0, Btn=0 (RepeatDelayCtr=11) 59453 FS Control Sent: Ctrl=65588, Param=0 59468 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=0, (Result 4) 59468 [Buttons] 1=RA,0,C65588,0 59500 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=0, (RepeatOk sets 2) 59500 [Buttons] 1=RA,0,C65588,0 59500 Repeating flag set: bRef=0, Joy=0, Btn=0 (RepeatDelayCtr=11) 59500 FS Control Sent: Ctrl=65588, Param=0 59515 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=0, (Result 4) 59515 [Buttons] 1=RA,0,C65588,0 59546 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=0, (RepeatOk sets 2) 59546 [Buttons] 1=RA,0,C65588,0 59546 Repeating flag set: bRef=0, Joy=0, Btn=0 (RepeatDelayCtr=11) 59546 FS Control Sent: Ctrl=65588, Param=0 59562 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=0, (Result 4) 59562 [Buttons] 1=RA,0,C65588,0 59593 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=0, (RepeatOk sets 2) 59593 [Buttons] 1=RA,0,C65588,0 59593 Repeating flag set: bRef=0, Joy=0, Btn=0 (RepeatDelayCtr=11) 59593 FS Control Sent: Ctrl=65588, Param=0 59625 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=0, (RepeatOk sets 2) 59625 [Buttons] 1=RA,0,C65588,0 59625 Repeating flag set: bRef=0, Joy=0, Btn=0 (RepeatDelayCtr=11) 59625 FS Control Sent: Ctrl=65588, Param=0 59640 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=0, (Result 4) 59640 [Buttons] 1=RA,0,C65588,0 59671 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=0, (RepeatOk sets 2) 59671 [Buttons] 1=RA,0,C65588,0 59671 Repeating flag set: bRef=0, Joy=0, Btn=0 (RepeatDelayCtr=11) 59671 FS Control Sent: Ctrl=65588, Param=0 59687 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=0, (Result 4) 59687 [Buttons] 1=RA,0,C65588,0 59718 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=0, (RepeatOk sets 2) 59718 [Buttons] 1=RA,0,C65588,0 59718 Repeating flag set: bRef=0, Joy=0, Btn=0 (RepeatDelayCtr=11) 59718 FS Control Sent: Ctrl=65588, Param=0 59750 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=0, (RepeatOk sets 2) 59750 [Buttons] 1=RA,0,C65588,0 59750 Repeating flag set: bRef=0, Joy=0, Btn=0 (RepeatDelayCtr=11) 59750 FS Control Sent: Ctrl=65588, Param=0 59781 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=0, (RepeatOk sets 2) 59781 [Buttons] 1=RA,0,C65588,0 59781 Repeating flag set: bRef=0, Joy=0, Btn=0 (RepeatDelayCtr=11) 59781 FS Control Sent: Ctrl=65588, Param=0 59812 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=0, (RepeatOk sets 2) 59812 [Buttons] 1=RA,0,C65588,0 59812 Repeating flag set: bRef=0, Joy=0, Btn=0 (RepeatDelayCtr=11) 59812 FS Control Sent: Ctrl=65588, Param=0 59828 Button held, flags=X05, repeat set: bRef=0, Joy=0 (A), Btn=0, (Result 4) 59828 [Buttons] 1=RA,0,C65588,0 59859 Button changed: bRef=0, Joy=0 (A), Btn=0, Released 66453 KEYDOWN: VK=83, Waiting=0, Repeat=N, Shifts=0 66453 .. Key not programmed -- passed on to FS 66546 KEYUP: VK=83, Waiting=0 68062 KEYDOWN: VK=83, Waiting=0, Repeat=N, Shifts=0 68062 .. Key not programmed -- passed on to FS 68203 KEYUP: VK=83, Waiting=0 68781 KEYDOWN: VK=83, Waiting=0, Repeat=N, Shifts=0 68781 .. Key not programmed -- passed on to FS 68875 KEYUP: VK=83, Waiting=0 69828 KEYDOWN: VK=83, Waiting=0, Repeat=N, Shifts=0 69828 .. Key not programmed -- passed on to FS 69984 KEYUP: VK=83, Waiting=0 70937 KEYDOWN: VK=83, Waiting=0, Repeat=N, Shifts=0 70937 .. Key not programmed -- passed on to FS 71031 KEYUP: VK=83, Waiting=0 76156 Sim stopped: average frame rate for last 32 secs = 54.5 fps 76156 Max AI traffic was 0 aircraft 82375 System time = 06/02/2017 21:02:18, Simulator time = 09:02:59 (14:02Z) 82375 *** FSUIPC log file being closed Minimum frame rate was 44.4 fps, Maximum was 62.3 fps Minimum available memory recorded was 2630Mb Average frame rate for running time of 32 secs = 54.5 fps G3D fix: Passes 10997, Null pointers 0, Bad pointers 0, Separate instances 0 Maximum AI traffic for session was 0 aircraft Memory managed: 25 Allocs, 25 Freed ********* FSUIPC Log file closed ***********
Pete Dowson Posted February 7, 2017 Report Posted February 7, 2017 5 hours ago, Scott B said: Well, the first time I clicked "yes" and told Windows to let it load, FSX just dissappeared and didn't complete it's launch and almost simultaneiously another smaller window popped up indicating an error that I now can't remember the details of. Sorry, I know that's not helpful, and probably not clear. The second time I told Windows No to not load FSUIPC and FSX failed to complete launch again, I think. The third time I think FSX launched normally after clicking "no". That sounds exactly like the occasional SimConnect "trust" bug as covered by the FAQ subforum thread. It does seem to take a few retries sometimes (according to reports. I've never reproduced it on any on many PC systems). Luckily all that nonsense was removed in P3D. 5 hours ago, Scott B said: The radios knobs still will not work unless, as I described in my original post. I rotate the knob a few revolutions with the mouse wheel first. Then the virtual radio knob will respond to the joystick button but only by reversing those same number of revolutions... then it stops. So, what is changing after those few revolutions? Certainly nothing in FSUIPC. I assume this, for COM1 for instance, is the total of what is being done in the Log above? On 2/5/2017 at 8:10 PM, Scott B said: This is part of the Com 1 macro, for example: 16=L:Com1FreqInnerKnob=Inc 17=L:Com1FreqInnerKnob=Dec If those L:Vars get written then presumably you should see an immediate effect? It might be a good idea to have the L:Vars displayed on screen in real time as they chhange, so we can see. You can do that by running the Lua plug-in "display vals" -- it's in the example plug-ins Zip file in your FSUIPC Documents folder. It may be that it is they aircraft which is responding incorrectly or late. Though I don't uinderstand why it would be different between different versions of FSUIPC as none of the code in any area to do with button interpretation has been changed, not for many many years. And the log certainly shows it responding to buttons okay. The L:Var requests are just that, requests via the FS PANELS.DLL interface. I'd add more logging if there was anywhere to add it, but all it does is call "get_named_variable" followed by "set_named_variable" -- and it does the same sequence no matter whether it's a Set, Toggle, Setbits, ClrBits, Inc, Dec, or Cyclic Inc. I could put a log message at the very point of sending those two commands to FS, but I'm not convinced that would help. Let me know what you think. If you want to try that send me an email on petedowson@btconnect.com. Pete
Scott B Posted February 7, 2017 Author Report Posted February 7, 2017 4 hours ago, Pete Dowson said: That sounds exactly like the occasional SimConnect "trust" bug as covered by the FAQ subforum thread. It does seem to take a few retries sometimes (according to reports. I've never reproduced it on any on many PC systems). Yeah, I've never encountered that before. 4 hours ago, Pete Dowson said: So, what is changing after those few revolutions? Certainly nothing in FSUIPC. I have no idea, sincerely. 4 hours ago, Pete Dowson said: I assume this, for COM1 for instance, is the total of what is being done in the Log above? If I understand you correctly, yes, I only manipulated the com 1 knob and the aircraft brake while logging. Those are the only buttons assigned. 4 hours ago, Pete Dowson said: If those L:Vars get written then presumably you should see an immediate effect? I do see an immediate effect with 9.55c. 4.955c. 4 hours ago, Pete Dowson said: It might be a good idea to have the L:Vars displayed on screen in real time as they chhange, so we can see. You can do that by running the Lua plug-in "display vals" -- it's in the example plug-ins Zip file in your FSUIPC Documents folder. That will take some time for me to learn. But I will try. Lua confuses me. I don't use Linda for that reason, not that it is necessary for this suggestion. I will look into the manual. 4 hours ago, Pete Dowson said: It may be that it is they aircraft which is responding incorrectly or late. Though I don't uinderstand why it would be different between different versions of FSUIPC.... This is probably an issue... in some way... with my system. I have difficulty explaining the issue. I made a video unlisted on Youtube that may help clarify, if you are interested. Considering that the code hasn't changed in FSUIPC, it almost has to be something related to my system. I'm not certain I have the discipline, or brain power to figure out why my setup and 4.961 won't work well together. 4.955c works so well, it feels like a waste of my time... and more importantly, yours. Again, thanks for your efforts. Scott
Pete Dowson Posted February 7, 2017 Report Posted February 7, 2017 8 minutes ago, Scott B said: That will take some time for me to learn. But I will try. Lua confuses me. There's nothing to "learn"! It's far easier that creating macro files and assigning them as you've already done. You only need to put the Display Vals.lua file into your FS Modules folder, go to the Keys or Button assignments tab in FS, press the "reload" button if your FS was running when you copied the file over (so it recognises it), then assign a key or button to "Lua display vals" in the drop down as you have for the macros. Then when you use that key or button the logging will start and it will display changes to LVars on screen too. If you want to stop it you'd need another key or button assigned to LuaKill display Vals, and use that. I now have a version of FSUIPC which can optionally log the L:Var aactions when you use those macros so we can see what happens. As I said, email me and I'll send it. Pete .
Scott B Posted February 8, 2017 Author Report Posted February 8, 2017 Thanks Pete. Your email sorted out the problem. I simply added an FSUIPC4 parameter limit of 1000000000 to the "L:Com1FreqInnerKnob=Inc" and -1000000000 to the "L:Com1FreqInnerKnob=Dec", as I alluded to in my original post and it works great! Thank you for your hard work! Please consider this issue solved. Scott
Pete Dowson Posted February 8, 2017 Report Posted February 8, 2017 8 hours ago, Scott B said: Your email sorted out the problem. I simply added an FSUIPC4 parameter limit of 1000000000 to the "L:Com1FreqInnerKnob=Inc" and -1000000000 to the "L:Com1FreqInnerKnob=Dec", as I alluded to in my original post and it works great! Okay, good. I'm still trying to work out what changed between 4.955 and now to make this act differently. It's strange. If it was a bug I fixed it most certainly should have been recorded, but I don't see it anywhere! Oh well. Perhaps I wasn't myself at the time! Pete
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now