hammerone Posted Monday at 03:42 PM Report Posted Monday at 03:42 PM Buonasera, ho un problema con la versione 7.5.0 riesco a caricare i profili aeromobili creati in precedenza con le versioni precedenti ma se voglio aggiornare un profilo per aggiungere funzionalità non me lo fa fare, premo un tasto qualsiasi e non viene rilevato. Ho provato a reinstallare FSUIPC con la versione aggiornata, funziona bene per qualche minuto e poi non rileva nessun tasto premuto. Con la versione precedente tutto funzionava bene
John Dowson Posted Monday at 04:13 PM Report Posted Monday at 04:13 PM 17 minutes ago, hammerone said: I can load aircraft profiles created previously with previous versions but if I want to update a profile to add features it does not let me do it, I press any key and it is not detected. I tried to reinstall FSUIPC with the updated version, it works fine for a few minutes and then it does not detect any key pressed. Presumably you have pressed the Set button, and the text in the key-entry box changes to PRESS KEY, no? And then when you press a key this is not detected - is that correct? Can you show me/attach your FSUIPC7.log and FSUIPC7.ini files please.
hammerone Posted Monday at 04:28 PM Author Report Posted Monday at 04:28 PM I did the same procedure I did with previous versions. I attach the 2 files FSUIPC7.log
hammerone Posted Monday at 04:31 PM Author Report Posted Monday at 04:31 PM The FSUIPC.ini file does not let me load it because it exceeds the total size
John Dowson Posted Monday at 04:39 PM Report Posted Monday at 04:39 PM 5 minutes ago, hammerone said: I did the same procedure I did with previous versions. Maybe, but as I don't know what you are doing, it would be helpful if you could answer my questions. Again, once you have pressed the Set button, does the text in the key-entry box changes to PRESS KEY? And then no key presses are recognised? And if you click on the PRESS KEY text box (to give it the focus) and try again, is it recognised then? 5 minutes ago, hammerone said: The FSUIPC.ini file does not let me load it because it exceeds the total size You can compress/zip it if its too large. Your upload limit will be very low as you are new to the forum, it will increase the more you post. I just want to check if you have any options set that may affect this, such as using a keyboard hook. John
hammerone Posted Monday at 05:01 PM Author Report Posted Monday at 05:01 PM Even compressed it is still too big If I go to Key Assignments it works for the keyboard and that's it. I have to assign the keys for Hotas Orion by Winwings. It's on Buttons and Switches that it doesn't recognize my key press.
John Dowson Posted Monday at 05:26 PM Report Posted Monday at 05:26 PM 14 minutes ago, hammerone said: It's on Buttons and Switches that it doesn't recognize my key press. Sorry but you are now confusing me. Are you now saying that it is not detecting button presses? What has this got to do with keys? Or what key press are you expecting to be recognised in the button assignments panel? Can you please be clear - buttons and keys are different.... If issue an issue with button presses, is this for one specific device or for multiple/all devices? Your log file does show some registry issues, but 8 devices are detected/acquired... I think you need to explain your issue more clearly if you want assistance... 22 minutes ago, hammerone said: I have to assign the keys for Hotas Orion by Winwings. Is that this device: Quote 1125 Device acquired for use: 1125 Joystick ID = 2 (Registry okay) 1125 2=WINWING Orion Throttle Base II + F18 HANDLE 1125 2.GUID={F9BCC310-1C46-11EE-8001-444553540000} ? Can you see the axes dor this device in the axes assignment window? 23 minutes ago, hammerone said: Even compressed it is still too big Then you need to use a (free) file transfer service... Also, please attach your FSUIPC7.JoyScan.csv file. I am finishing now for the day - I will check your files tomorrow now. John
hammerone Posted Monday at 05:27 PM Author Report Posted Monday at 05:27 PM the problem seems solved at the moment, the program did not recognize the Winwings MFDs, I disconnected them from the PC to try on the simulator without MFDs and the program works, I exited the simulator and reconnected the MFDs and now they are recognized, with the previous version I did not have this problem. Let's hope for the best that it does not give me problems again. Thanks for the support given
John Dowson Posted Monday at 05:32 PM Report Posted Monday at 05:32 PM It seems that you are having such issues as your registry is in a mess: Quote 1047 WARNING: Joystick ID 6 is duplicated in Registry 1047 WARNING: Joystick ID 1 is duplicated in Registry 1062 WARNING: Joystick ID 0 is duplicated in Registry 1078 WARNING: Joystick ID 5 is duplicated in Registry 1078 WARNING: Joystick ID 1 is duplicated in Registry 1094 WARNING: Joystick ID 9 is duplicated in Registry 1094 WARNING: Joystick ID 10 is duplicated in Registry If you can show me all 3 files (.log, .ini and .JoyScan.csv) we can correct this which should prevent such issues re-occurring.
hammerone Posted Wednesday at 09:47 PM Author Report Posted Wednesday at 09:47 PM Good evening, these days due to work commitments I have not been able to send you the files you asked for. Now I send you the 3 zipped files FSUIPC7.log FSUIPC7.JoyScan.csv FSUIPC7.ini
John Dowson Posted Thursday at 11:12 AM Report Posted Thursday at 11:12 AM These are the registry entries, with the ones causing issues in bold: Quote ,,, REGscanning completed N, x00, x06A3, x0763, Saitek Pro Flight Rudder Pedals (USB), -1, 3, 0, {NULL}, {D8437F80-3B77-11E9-8006-444553540000}, {D8437F80-3B77-11E9-8006-444553540000}, Y, Y N, x00, x4098, xBE04, WINWING F18 TAKEOFF PANEL, -1, 7, 0, {NULL}, {A10E72E0-8A9D-11EC-8001-444553540000}, {A10E72E0-8A9D-11EC-8001-444553540000}, Y, Y N, x00, x4098, xBC28, WINWING URSA MINOR CIVIL FLIGHT STICK R, -1, 0, 0, {NULL}, {B28BBB00-A07E-11EF-8001-444553540000}, {B28BBB00-A07E-11EF-8001-444553540000}, Y, Y N, x00, x4098, xBC28, WINWING URSA MINOR CIVIL FLIGHT STICK R, -1, 4, 1, {NULL}, {7B4F4CA0-A07F-11EF-8003-444553540000}, {NULL}, N, N N, x00, x4098, xBC28, WINWING URSA MINOR CIVIL FLIGHT STICK R, -1, 5, 2, {NULL}, {7B4F73B0-A07F-11EF-8004-444553540000}, {NULL}, N, N N, x00, x4098, xBC28, WINWING URSA MINOR CIVIL FLIGHT STICK R, -1, 6, 3, {NULL}, {7B4F9AC0-A07F-11EF-8006-444553540000}, {NULL}, N, N N, x00, x4098, xBB10, WINWING FCU-320, -1, 1, 0, {NULL}, {B28BE210-A07E-11EF-8002-444553540000}, {B28BE210-A07E-11EF-8002-444553540000}, Y, Y N, x00, x4098, xBEE1, WINWING MFD1-L, -1, 6, 0, {NULL}, {965EEB50-B268-11EE-8005-444553540000}, {965EEB50-B268-11EE-8005-444553540000}, Y, Y N, x00, x4098, xBEE1, WINWING MFD1-L, -1, 1, 1, {NULL}, {E2917330-B268-11EE-8006-444553540000}, {NULL}, N, N N, x00, x4098, xBEE1, WINWING MFD1-L, -1, 9, 2, {NULL}, {F60CF010-B268-11EE-8007-444553540000}, {NULL}, N, N N, x00, x4098, xBEE1, WINWING MFD1-L, -1, 10, 3, {NULL}, {F60CF010-B268-11EE-8008-444553540000}, {NULL}, N, N N, x00, x4098, xBEE1, WINWING MFD1-L, -1, 0, 4, {NULL}, {FB7A6730-B268-11EE-8009-444553540000}, {NULL}, N, N N, x00, x4098, xBE05, WINWING F18 COMBAT READY PANEL, -1, 8, 0, {NULL}, {2E778440-A47B-11EC-8001-444553540000}, {2E778440-A47B-11EC-8001-444553540000}, Y, Y N, x00, x4098, xBEE2, WINWING MFD1-R, -1, 5, 0, {NULL}, {3DBE5CA0-B269-11EE-800A-444553540000}, {3DBE5CA0-B269-11EE-800A-444553540000}, Y, Y N, x00, x4098, xBEE2, WINWING MFD1-R, -1, 1, 1, {NULL}, {EDD73A10-D0D9-11EE-8001-444553540000}, {NULL}, N, N N, x00, x4098, xBE62, WINWING Orion Throttle Base II + F18 HANDLE, -1, 2, 0, {NULL}, {F9BCC310-1C46-11EE-8001-444553540000}, {F9BCC310-1C46-11EE-8001-444553540000}, Y, Y N, x00, x4098, xBE62, WINWING Orion Throttle Base II + F18 HANDLE, -1, 9, 1, {NULL}, {A6289FC0-1C47-11EE-8002-444553540000}, {NULL}, N, N N, x00, x4098, xBE62, WINWING Orion Throttle Base II + F18 HANDLE, -1, 10, 2, {NULL}, {A69A7460-1C47-11EE-8003-444553540000}, {NULL}, N, N N, x00, x4098, xBE62, WINWING Orion Throttle Base II + F18 HANDLE, -1, 11, 3, {NULL}, {A69A9B70-1C47-11EE-8004-444553540000}, {NULL}, N, N To correct this, first takw a back-up of your refistry (using the Windows Registry Editor). Then unplug the following devices (without FSUIPC or the FS running!): WINWING URSA MINOR CIVIL FLIGHT STICK R WINWING MFD1-L WINWING MFD1-R WINWING Orion Throttle Base II + F18 HANDLE Then download and run (i.e. double-click it) this file: removeDevices.reg Reboot your PC, then re-connect those devices. Then run FSUIPC7 and exit, and show me those 3 files again. Everything should be ok, but I will check the files just in case there is an id or GUID change that may need correcting. John
hammerone Posted Thursday at 02:19 PM Author Report Posted Thursday at 02:19 PM Good morning I did as suggested, I'm sending you the 3 files FSUIPC7.ini FSUIPC7.JoyScan.csv FSUIPC7.log
John Dowson Posted Thursday at 02:47 PM Report Posted Thursday at 02:47 PM Looks like your Saitek Pro Flight Rudder Pedals weren't connected - are you still using these? Please try the attached ini - this shou;d correct things (your registry now looks good!). Connect the rudder pedals, if using, start FSUIPC7 and exit and show me the files again. John FSUIPC7.ini
hammerone Posted Thursday at 03:32 PM Author Report Posted Thursday at 03:32 PM Sometimes it happens to me that they do not activate, inserted the new ini file, now everything is fine. I attach the three files. Thank you very much FSUIPC7.ini FSUIPC7.JoyScan.csv FSUIPC7.log
John Dowson Posted Thursday at 03:42 PM Report Posted Thursday at 03:42 PM Yep - all looks good now! Cheers, John
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