Ron Attwood Posted Friday at 09:13 PM Report Posted Friday at 09:13 PM Is it possible that FSUIPC can 'forget' assignments? Or is 2024 controls system snatching then back by nefarious means? This is mostly keystroke assignments. As lovely as it is 2024 is..is..well, trying.
John Dowson Posted Friday at 09:44 PM Report Posted Friday at 09:44 PM No, FSUIPC will/should not "forget" or lose assignments - they should all be stored in your FSUIPC7.ini file. What can and does happen sometimes is that your device GUIDs can change, and then FSUIPC recogognises it as a new device and your old/original assignments wont be available. This can sometimes hapoen on windows uodates, or possibly when reconnecting a device to a different hub (although less likely in this case). Another reason assignments can seem to be missing is when using an aircraft with a different livery, and not using aircraft substring names in your profile section. In either case, show me / attach your FSUIPC7.ini and .log files and I can take a look. John
John Dowson Posted Friday at 10:00 PM Report Posted Friday at 10:00 PM Sorry - if its key assignments it cant be related to GUIDs. Set logging for Buttons & Keys for the lig file, and try an assignment that isnt working, i.e. "forgotten". If its an assignment to an lvar or preset, it could be the WASM has crashed....
Ron Attwood Posted Friday at 11:58 PM Author Report Posted Friday at 11:58 PM My God! I've just looked at the log file. Who'd guess that so much went on under the bonnet? FSUIPC7.log FSUIPC7.ini
John Dowson Posted Saturday at 09:49 AM Report Posted Saturday at 09:49 AM You did not set logging for Buttons & Keys (Log -> Buttons & Keys) as I asked for, so your log file tells me nothing. Please set this logging and try again, and also provide some information as to what is not working. You are also not using substrings for your aircraft profile names. This means that any variant you load will not match a profile that is not already in the profile, and so the assignments for that profile will not be loaded. When you add an aircraft to a profile (or crate a new profile), you should always edit the name added to the profile section to make it a substring that matches all variants. I have done this for you in the attached ini, so please download and use this one. John FSUIPC7.ini
John Dowson Posted Saturday at 10:01 AM Report Posted Saturday at 10:01 AM 12 hours ago, Ron Attwood said: This is mostly keystroke assignments. If you mean assignments to keys, then there are none of these in your ini file. Or do you mean button assignments to send key-strokes? If so, this also depends on the key presses also being assigned in MSFS. John
Ron Attwood Posted Saturday at 12:16 PM Author Report Posted Saturday at 12:16 PM Sorry. Yes, key strokes. I wasn't aware of the difference. I'll get on it. 😁
John Dowson Posted Saturday at 12:22 PM Report Posted Saturday at 12:22 PM 2 minutes ago, Ron Attwood said: Sorry. Yes, key strokes. I wasn't aware of the difference. I'll get on it. But, as I said, you have no key assignments (i.e. assignments to key presses/releases) in your ini file. Are you sure you have made some in FSUIPC? I have never heard or seen FSUIPC lose an entire key assignment section... You can also check (or send me / attach) your back-up FSUIPC7.ini file, from the backup-ini folder. This will contain your assignments as they were when you installed version 7.5.4. John
Ron Attwood Posted Saturday at 12:58 PM Author Report Posted Saturday at 12:58 PM Log set to Buttons and keys FSUIPC7.log These are from my .ini file. 8=HD,17,K80,24 -{Key press: lalt+P}- 9=PC,1,K50,24 -{Key press: lalt+2}- 11=RC,33,K69,9 -{Key press: lshift+E}- 12=RC,38,K81,9 -{Key press: lshift+Q}- 13=PA,1,K74,8 -{Key press: J}- 14=PA,2,K50,24 -{Key press: lalt+2}- 15=RA,7,K69,9 -{Key press: lshift+E}- 16=RA,9,K81,9 -{Key press: lshift+Q}- 17=RA,6,K87,9 -{Key press: lshift+W}- 18=RA,8,K83,9 -{Key press: lshift+S}-
Ron Attwood Posted Saturday at 01:12 PM Author Report Posted Saturday at 01:12 PM I think I know the problem. MSFS controller system makes a preset for EVERY plane I jump into. In the olden days my first job with a new sim was to disable all the controls. Then FSUIPC took care of everything. Never a problem. I'll leave you in peace and try to come to terms with 2024 'system'.
John Dowson Posted Saturday at 02:03 PM Report Posted Saturday at 02:03 PM Your log shows the button press sending the key presses and then these key presses being received back, e.g. Quote 17031 Button changed: bRef=0, Joy=2 (C), Btn=1, Pressed 17031 [Buttons] 9=PC,1,K50,24 17031 SendKeyToFS(00010032=[lalt+2], KEYDOWN) ctr=0 17047 Sending WM_KEYDOWN, Key=164 (LAlt) (Scan code 56), Ctr=4 17063 Sending WM_KEYDOWN, Key=50 (Scan code 3), Ctr=3 17078 Sending WM_KEYUP, Key=50 (Scan code 3), Ctr=2 17094 EV_KEYDOWN received: 0x32 (2) 17094 KEYDOWN: VK=50, Waiting=0, Repeat=N, lParam=0 (0x0), Shifts=4 17094 .. KeyDown received from FS but not programmed 17110 Sending WM_KEYUP, Key=164 (LAlt) (Scan code 56), Ctr=1 17125 EV_KEYUP received: 0x32 (2) 17125 KEYUP: VK=50, Waiting=0, Shifts=0, lparam=0 (0x0) 17125 .. KeyUp received from FS but not programmed 17219 Button changed: bRef=0, Joy=2 (C), Btn=1, Released So your button assignments to key presses are working. Note that your log also shows that you are trying things too early - around 5 seconds after FSUIPC was started, but it hadn't fully started until a couple of seconds later. You should give FSUIPC a bit more time before trying to control the aircraft via FSUIPC. 47 minutes ago, Ron Attwood said: I think I know the problem. MSFS controller system makes a preset for EVERY plane I jump into. In the olden days my first job with a new sim was to disable all the controls. Then FSUIPC took care of everything. Never a problem. I'll leave you in peace and try to come to terms with 2024 'system'. Ok, makes sense. Note you can also set logging for Events (Log -> Events), as well as Buttons & Keys, and also open the logging console window (Log -> Open Console), This would then not only show you what FSUIPC is doing, but what the key press is assigned to in MSFS (i.e. the event that it triggers). Anyway, good luck with MSFS2024...I don't use this much (still prefer MSFS2020 or P3D), but at least its a lot more stable these days... John
Ron Attwood Posted Saturday at 02:57 PM Author Report Posted Saturday at 02:57 PM 48 minutes ago, John Dowson said: Note that your log also shows that you are trying things too early - around 5 seconds after FSUIPC was started, but it hadn't fully started until a couple of seconds later. You should give FSUIPC a bit more time before trying to control the aircraft via FSUIPC Top tip. Also I never realised about the profile thing. If I got a new paint I'd have to point it to the appropriate profile. In the end I'd have l list as long as your arm of Comanches. 😂 Thanks for your time John. I expect I'll be back in the future with more 'insurmountable problems' 🙄 1
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