Pete Dowson

Delete the complete [Axes] and [JoystickCalibration] sections from your FSUIPC5.INI file. Well, someone else did it for you then? they appear to be very deliberately made settings. They couldn't possibly have been made by accident or even fooling around! I strongly suggest you at least peruse the FSUIPC user guide and even check the pictures there before messing with things "unitentionally"! Incidentally, there's absolutely no way whatsoever for the use of the mouse macros you created could interfere with any controls other that whatever those mouse macros were attached to. The axes interaction would have all been due to both P3D and FSUIPC controlling the axes. Pete

Thanks. You said this: but that plainly is not the case. You have throttles assigned AND calibrated in FSUIPC. Not only that, but you have actions assigned to the throttle movements on the right-hand side of the assignments facility: [Axes] PollInterval=10 RangeRepeatRate=10 0=0X,256,D,9,0,0,0 -{ DIRECT: Throttle1 }- 1=0X,BR,0,0,65966,0,65967,0 -{ DIRECT: Throttle1Entering=THROTTLE1_DECR, Leaving=THROTTLE1_CUT }- 2=0Y,256,D,10,0,0,0 -{ DIRECT: Throttle2 }- 3=0Y,BR,0,0,65971,0,65972,0 -{ DIRECT: Throttle2Entering=THROTTLE2_DECR, Leaving=THROTTLE2_CUT }- The axes are not only trying to control the throttles normally, but you've also assigned "throttleN decr" and "throttleN cut" controls to then as well, both at the idel position. Also, you evidently have axes enabled in P3D. So your throttles will be acting there independently of what you set FSUIPC to do. For axes you MUST either assign all in FSUIPC or all in P3D. If you assign in FSUIPC you must disable controllers completely in P3D. It is your choice. The macro files are merely normal mouse macros and cannot interfere unless P3D operating those switches has such side effects. Pete

If this is really the case you must have some hardware or USB driver interaction. And "thrashing" isn't really like "jittering", surely? And just "touching" the sidestick, not moving it as previously stated. Having two completely different descriptions of the problem isn't much of a help really. Saying it only started happening after you created these 'macros' implies that all was well with the sidestick before then. Is that so? Anyway, we can't possibly advise without seeing your settings. Please show or attach the FSUIPC5.INI file, a Log file (FSUIPC5.LOG) and the macro files (.mcro). Pete

When pressing ALT+F to get the FSUIPC window up don't you see a menu bar with File MSFS Assignments Options Log Add-ons WideFS Help showing? The Assignments is where you do assignments and there are selections for Axes, Buttons & Switches & Key Presses. If you don't see all of this then you haven't registered the program! You might also peruse the documentation, which you'd find useful. but the Assignments window you'll get is pretty much the same as those you would have used in previous versions. Pete

That's part of the Data received from the 777X (and available in the offsets as showing in the FSUIPC offsets list for the 777X (mapped to offset 65BF. But like all of the mapped PMDG offsets it is read-only. 69632 is the base of the control Events as defined here, in the SDK: #define THIRD_PARTY_EVENT_ID_MIN 0x00011000 // equals to 69632 So, you need to find the event you need to use, in the list, and add whatever it says against that to your 69632. Didn't the tutorial you refer to tell you any of that? There looks to be 3 separate Events, called "Transfer Switch". i assume they do the job. For example: #define EVT_COM1_TRANSFER_SWITCH (THIRD_PARTY_EVENT_ID_MIN + 526) So, for COM1, add 526, exactly as it says. The transfer switches are, I think, the same as the "swap" buttons on the radios which swap the Standby and Active frequencies. Most radios don't allow you to change the active frequency directly. You change the standby then do the swap. Pete P.S. This belongs in the Support Forum, so I've moved it.

Don't Honeycomb and some Saitek devices have more than 32 buttons? I assume they would also be used with P3D? And of course a proper test would be for its proper use even on 32-bit only devices, to make sure no errors have been introduced. So maybe the beta test was seen as aiming only at >32 button users, so others didn't bother. Or perhaps, like on most Forums, lack of problem reports may just be because there haven't been any. Not sure there's any justification at present for removing the changes. If you're worried about making it the main release. Maybe keep the previous one available for folks to revert to if they think they need to, on the (hopeful?) assumption they report the problem, of course. I'm use it here and I have no problems, but apart from testing with vJoy I don't have any devices with >32 buttons. Pete

Yes, you are confusing Joy Letters, which will now be used in FSUIPC, with the ID numbers in the Registry, which FSUIPC needs to use internally, when dealing with the Windows facilities. FSUIPC refers to the [JoyNames] section to translate the letters into numbers and vice versa. That's why both entries are there for each controller. With Windows updates or movement of the USB connections, the ID numbers may change but FSUIPC can relate them to the letters by comparing Names and GUID values. Pete

The 25kHz spaced versions of the COM frequencies are provided in the original frequency offsets, 034E and 3118. The full frequency, allowing for the 8.33kHz spacing mode, are provided in offsets 05C4 and 05C8 respectively. They are 32-bit integers with the frequency in Hz, so allow for any spacing. It seems that the software you are using is reading the wrong offsets for an 8.33 capable display. Pete

Ah, well done! Some of these uninstall programs are pretty useless. Anyway, it is evidently useful to have that data logged initially, so tomorrow I will make 5.125 the main current release. Thanks, Pete

You have Windows set to hide file types, so you aren't seeing the .log and .ini types. Please refer to the section Finding and Editing files relating to FSUIPC and WideFS on page 6 of the FSUIPC7 User Guide. The .ini file is simply labelled as "Configuration settings". The .log would be a "Text Document" like the one for the Installer. Youdon't seem to have one for FSUIPC, which implies that it has not yet been run. Pete

Thanks Roman. I'd forgotten that there are camera views defined in the aircraft.cfg file! Pete

It depends very much on the aircraft, really. You could try a macro file using a sequence of View or Pan controls. Work out how to do it on the keyboard then do the same thing with macros. After all all the keys will only result in assignable controls being sent. Use FSUIPC event logging to see what they are. Or perhaps it could be made a camera view -- if it isn't already. Look at your Cameras.cfg file (in the AppData\Roaming folder for the sim). Those camera views assignable to controls have a "HotKeySelect" parameter. I think the number assigned there denotes which VIEW_CAMERA_SELECT_n controls selects it. If it's a Panel then the PANEL_n control should work -- but I think the "n" has to be defined in the aircraft's PANEL.CFG file. Those are the controls sent for Shift+n. On my VFR cockpit I have a toggle lever for Left and Right views. The "off" position is set to select the default forward view but with the cockpit panel part lowered right down so its top is where the top of my hardware panel it. But for the Left and Right views I used a combination of two Pan controls, one panning left and the other panning down, so the view swung around and raised a bit to to compensate for the lowering of the main view. That system is powered off at present, but if you are interested in such a way I can show you what I did next time I power it up (maybe later today, but more likely tomorrow). Mind you, this was with P3D5. i don't know if the same facilities exist in FSX-SE, though they probably do. Pete

Okay, so it seems that your MSFS installation isn't recorded in the places I know about and which Makerwys is programmed to look in. Strange when it has been working for others, both MS store and Steam users. Unfortunately I didn't put enough logging into the code regarding finding the folders, so I've had to add it so I can see what is going on in your system. Please run this version (it won't do more than before except log where it is looking): MakeRwys.exe Then show me the Runways.txt file. (Make sure you don't have the older one open when your run the program). Could you show me your last FSUIPC7.log file please? that should give me a clue too. Pete

It is not seeing any MSFS installation at all. Was the display shown at the end saying anything, or did it just disappear? Pete

Did it make a "runways.txt" file (that's the Log) and/or a "scenerylist.txt" file? I'd need to see both please. Pete

Yes. If you already have this then the same registration code can be used. Pete

I still find this strange. I will look at the code to see how the offset is changed whilst in the button action scan. The two things are in the same thread and the scan of buttons to act upon is a loop with no chance of Windows messages being processed in the middle. SimConnect data arrives by message notification. So you can see the puzzle. I thought the only assigned actions which could do that were the offset controls themselves. [LATER] Yes. That offset is only being set when FSUIPC receives the value from SimConnect. It doesn't set it at any other time. So your result is weird -- I can't see how it can happen. Could you please try this: Before using any buttons, go to the Logging Monitor offsets facility and set it to monitor offset 208C as a U32. Also enable Button logging and Event logging. When things are settled down and you already to fly, press button 65,9. Show us the Log (or the parts of it relating to this offset and control). This may not show us anything useful as the Monitor operates only at (short) intervals, not between every action. But it may show something. If not some additional log lines might need to be temporarily inserted. Just set it specifically initially or when switching off. There are Button flag controls you can use and assign as you wish. Pete

Does MSFS even work on Windows 7? That's very surprising if so, since MS has stopped Win7 support. I think this is stated as the minimum requirement: Microsoft Flight Simulator 2020 requires, at minimum, a Windows 10 PC with either an Intel i5-4460 or AMD Ryzen 3 1200 processor, an Nvidia GTX 770 or AMD Radeon RX 570 GPU, 8 GB RAM, 2 GB VRAM, 150GB of hard drive space, and support for DirectX 11. FSUIPC7 is made for MSFS and so also needs Windows 10. Pete

I assume these lines are sequential numbers in your list and there are not 999 more assignments between them? That might have an influence. And check that 3041 actually being accepted. Those are really high button assignment numbers -- according to the documentation the allowable range is 0-2047. I suspect your second there is simply ignored (not being read). You can use the button flag facilities for this sort of thing. I assume that it is FSUIPC which is setting the offset immediately, because there is very little (no chance at least in previous versions of FSUIPC) for the SimConnect variable change being read and acted upon by FSUIPC in the middle of the button action scan, which is a single loop in the same thread. If FSUIPC is setting the offset at the same time as sending the value to SimConnect, you might as well change the button action to a simple toggle. 2041=CP(F-65,9)65,9,C67017,2 -{TURBINE_IGNITION_SWITCH_SET1}- 2042=CP(F+65,9)65,9,C67017,1 -{TURBINE_IGNITION_SWITCH_SET1}-

Further to my last replay, when you said: so, I ask you, please, where did you find the documents you referred to before: Those documents would have been installed in your Documents\FSUIPC7 folder, so your answers seem rather inconsistent and therefore puzzling. Perhaps you could elaborate? Not that, unlike the Installed documents, the controls list text file is generated when FSUIPC7 + MSFS are run. Pete

Drop-downs are part of the standard Windows dialogue system. All you need to do it type the first few letters and the list will move there. No. Controls are Events -- they are requests / commands to be sent to the Sim. Offsets are data repositories. They are not controls! Many but not all events will result in a change in the data being received. If you know what your control is supposed to do look for the evidence of it. As with FSUIPC6 before it, all of the FSUIPC7 document are automatically placed in a folder in your C:\Users\<user name>\Documents folder named after the version -- i.e. FSUIPC6 or FSUIPC7. The latest Beta is not supplied with an Installer, just a replacement DLL, so, of course, it relies on you having actually installed FSUIPC7 before. If you've never used the FSUIPC7 installer you are missing quite a lot of things! Pete

The full list is generated for you when you run MSFS with FSUIPC7. The latest version I have was generated (in my Documents\FSUIPC7 folder) and includes: 67059 ENGINE_MASTER_1_SET 67060 ENGINE_MASTER_2_SET 67061 ENGINE_MASTER_3_SET 67062 ENGINE_MASTER_4_SET 67063 ENGINE_MASTER_1_TOGGLE 67064 ENGINE_MASTER_2_TOGGLE 67065 ENGINE_MASTER_3_TOGGLE 67066 ENGINE_MASTER_4_TOGGLE Mind you, I am using the very recently released Beta version 7.1.0a, but I don't think it would be any different from the current latest release. The document to look for is called Controls List for MSFS Build 999.txt, but they also should be in the drop-down button assignmernts list. Pete

Sounds like that FSUIPC7.EXE is actually running. You need to terminate it (via "Exit"). If you can't get to its interface, use Task Manager. Windows Explorer just replaces files with the same name, just asking for confirmation. if you get another message instead of the confirmation request then you need to say what it is. Pete

Glad everything's now okay. For log files etc, rather than using Dropbox, if you ZIP such files you'll find they are small enough just to attach here. Might be a little quicker for you in future. Pete

Note that I amended my post whilst you were reading it! Pete