Jump to content
The simFlight Network Forums

John Dowson

Members
  • Posts

    12,268
  • Joined

  • Last visited

  • Days Won

    250

Everything posted by John Dowson

  1. FSUIPC is not crashing - it is exiting as MSFS has crashed: You are also using an old and unsupported version of FSUIPC, 7.4.1 - the latest and only supported version is 7.4.2. Please update. I do not know why MSFS is crashing. Check your windows event viewer to see if there are any crash reports there, and check the Asobo forums for similar issues. I cannot help with MSFS CTDs. This is nothing to do with FSUIPC. John
  2. Yes, but you will not have access to the registered facilities - assignments. lua, etc I am sorry but I have no idea why the FSUIPC window isn't being opened. All I can suggest is that you try either verifying your FSX installation (easy with a steam install, not sure how to do this otherwise) or try tr-installing FSX. If you re-install, make sure that you also install SP1 and SP2. John
  3. What do you mean by this? So it looks like this is the software that is screwing up the registry, as that phantom device with no name but the same GUID as your yoke is now showing again. I am surprised it works with those files, as your B device is missing... You have two options. If its working, just leave it as is. Otherwise, you need to go through the whole procedure again (as we are back at the beginning), and then figure out why your 'joystick wasn't working correctly'. Maybe it needs calibration in the windows game controller panels. John
  4. There is the Pause (ms) control - from page 29 of the Advanced User guide: This works in the same way as any other control. Not 100% sure what you mean by 'I want to sleep for 750 ms between two button presses' though, as it is you who are pressing the buttons, not FSUIPC... If you overload your assignments so that multiple controls/events are sent on a button press, then you can use this control to insert a delay between the controls being sent. John
  5. To make multiple assignments to a key press, do the following: 1. Make the first assignment to the key press, as normal. Confirm, click Ok to close the key assignment panel, then re-open the key assignment panel 2. Open the FSUIPC7.ini file in an editor. Find the key assignment just made, then comment it out by placing a semi-colon (;) before the assignment line number and save. 3. In the key assignments panel, click 'Reload all keys'. 4. You can now make the 2nd assignment to the key press. 5. if you want to make more assignments, reload the file in the editor and do the same, i.e. comment out the assignment in the file and save, reload the assignments in the UI, and then make the new assignment. Repeat until all assignments made. 6. When all assignments are made, uncomment (i.e. remove the semi-colon you added) all the previous assignments and save. Do this with the key assignments panel in FSUIPC7 open. 7. Reload all keys again. You should now have multiple assignments to the same key press. The UI will only show the first assignment and it will be grayed-out/disabled. This indicates that there are multiple assignments on that key press, and you can no longer change this via the UI, only by editing the ini file. John
  6. No, it is NOT registered. But how? You say there is no FSUIPC window displayed. And as you are running an unregistered version, if it was displayed then the calibration tab would not be available in an unregistered copy. I am confused... And i can see/find no record of you having ever purchased a license for FSUIPC4. You purchased a license for FSUIPC3 on 10/10/2004. An FSUIPC3 license is NOT valid for FSUIPC4. You are therefore, and have always been, using an unregistered copy. If you think you have purchased a license for FSUIPC4, please let me know your order number. I do not know why you keep posting when you are not following my instructions. PLEASE do the following - if not, I cannot help you. 1. install the simconnect.dll for version 10.0.61637.0. This is the SP2/X-pack version. If you do not have this on your system, you can download from a link in this post: https://www.avsim.com/forums/topic/503093-simconnect-version-100616370/ 2. Download and install the latest VC++ redistibutable packages, both x64 and x86, available from https://docs.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist 3. Reboot then re-install FSUIPC4. 4. Run FSX/FSUIPC. Can you see FSUIPC in the Add-ons menu now? If so, does it open the FSUIPC4 main window? After performing ALL steps, any issues, please show me/attach both your Install FSUIPC4.log and FSUIPC4.log files. John
  7. This issue has been reported many, many many times, and the solution is both in the provided documentation and in hundreds of similar support requests. You need to update your VC++ redistributables. From the latest README.txt (not exactly like this in the current release though, as I have updated to make it clearer - not thatmany people bother actually reading the documentation or checking the forums before posting....): John
  8. There is already an option to have the window always open on start-up, controllable from Options -> Open On Start. This is et automatically when a new version is detected, so that the user is aware that a new version is available. I will not disable this feature. Just update when this happens - it only takes a minute or two. Then you will have to continue doing this until you update. The other option would be for me to display a separate pop-up box when a new version is available. But then you would have to acknowledge that message, just as you need to close the main window. Sorry, but I will not be changing this. I get too many support requests from folks using old versions, and not checking to see if a new version is available first. This feature is implemented this way to prevent such issues. John
  9. But why? Why do this? You should ONLY install the simconnect dll/msi that comes with your FSX installation. But it was previously working WITH FSUIPC...your issue was that FSUIPC is not registered, and that the FSUIPC main window was not being displayed. It would help both of us if you could just follow my instructions and report back... i am now confused about your situation. Is FSUIPC installed? is it registered? If it is not installed, please install. Any issues with installation (or if FSUIPC is not showng in the Add-ons menu after installation), show me the installation log. Can you register ok after installation? If you have problems with registration, let me know your FSUIPC4 order number so that I can check your registration details here.
  10. Thanks - all looks good now. Use the attached ini file and you should be ok. FSUIPC7.ini John
  11. You have this assignment on your alpha yoke that could be causing this issue: Buttons 12 and 13 are the master alternator switch on/off positions, so you will either be continually moving the eyepoint either down or left, depending on the position of that switch. Remove those assignments. John
  12. That preset is for the GTN750 from PMS50: Is that the one you are using? If not, that preset won't work. FSUIPC7 supplies the mechanism to send presets to MSFS. If you have any issues with particular presets, you should ask about this on the MobiFlight Discord server, on the MSFS2020 channel. That is the place to ask about MF presets. Check to see if a preset exists for the aircraft you are using for the function you want to assign. If not, try listing the lvars and also the Input Events, to see if anything looks suitable and try that. You can also try logging to see if anything is logged when you activate the button in the VC.
  13. I need to see the files with the devices connected.... However, it is interesting that the phantom controller is still recognised: This in the entry causing issues as it gets assigned the same GUID as your yoke (see my previous comment). You can try running the attached regedit file to remove this - just download and double-click it to execute. Once done, connect your devices, run FSUIPC7, exit, and then show me those files again. John removeDevices.reg
  14. Ok - that was the path for a steam install. Check your folders under your FSX installation folder and see if you can find any SimConnect.msi files. You need to install the one valid for your version, not the legacy ones (which you already have installed).
  15. Have you installed any specific drivers for your yoke? I ask as both hid and registry scanning are reporting the device twice (i.e. same GUID) but with different vendor (VID) and product (PID) ids: We can remove these entries and try again, but you will probably get the same result. If you have installed any specific drivers for your yoke and/or pedals, best to remove those drivers and let windows install/use the default windows drivers. Once removed, unplug your devices, reboot. Once done, run FSUIPC7 (not MSFS!) - just run then exit, and show me the 3 update files again - .log, .ini and .JoyScan.csv
  16. Your logs show a few issues, but FSUIPC4 is running and was still running when you attached the log...I think....was FSX still running? The issues are: 1. You are running FSX version 10.0.61637.0, but the simconnect library being used is 10.0.61259.0: To correct this, install the simconnect.dll for your version by running (i.e. double-click in windows Explorer) the following file under your FSX main folder: F:\Microsoft Flight Simulator X\SDK\Core Utilities Kit\SimConnect SDK\lib\SimConnect.msi 2. You are running an unregistered version, even though you are using a key file containing your registration details: I am not sure why this is - can you let me know your FSUIPC4 order number and I will check your details here. DO NOT post your key file or key details! Neither of these issues should prevent the FSUIPC main window from being displayed, although the interface will only contain a few tabs as it is running unregistered. I don't understand why the window isn't being displayed... Lets correct these issues first and see if that solves things... John
  17. Details will be in the FSUIPC7.JoyScan.csv file. If you attach that I can provide aa script to remove the entries, and you can see if they are registered correctly when re-attached.
  18. Please attach your FSUIPC4.log file....
  19. Maybe also check-out these posts on view control:
  20. Have you defined and saved the quickviews? If not, do that first. Otherwise, if you have issues with MobiFlight presets, you should report/ask about this on the MobiFlight discord server (MSFS2020 channel). However, I can take a look here, but will be later today or tomorrow - I will get back to you on this once tested here. Pan Heading has not worked since the release of MSFS2020. From the FSUIPC7 README.txt: John
  21. Do you mean that the FSUIPC main window is not displayed when you select it from the Add-on menu? Are you running FSX in full screen mode? If so, can you switch to non-full screen and see if the FSUIPC main window is hidden behind the FSX window. Also, please check the task bar - can you see FSUIPC there? Your installation log looks fine. Can you show me your FSUIPC4.log and FSUIPC4.ini files please.
  22. Hi Ray, as well as the total load weight/mass offsets mentioned by Luke, there are the total quantity fuel offsets: 1264 4 Fuel: total quantity in gallons (32-bit integer) Ok-SimC No 1268 4 Fuel: selected quantity in gallons (32-bit integer) Ok-SimC No 126C 4 Fuel: total quantity weight in pounds (32-bit integer) Ok-SimC No 1270 4 Estimated fuel flow at cruise, in pounds per hour (32-bit integer) Ok-SimC No ...and best wishes for the New Year to you both. John
  23. The problem seems to be with the name of your controllers in the windows registry - sometimes it reports a device name and sometimes it is empty. You need to correct for this (when it changes) in the [JoyNames] section of your FSUIPC7.ini file.
  24. How did it help? You seem to be having the same issue.... It seems the name of your devices is now missing from the registry. I have edited your ini again to use a blank name - see if this works. If not, you will need to clean your registry. Please don't add any new assignments until this issue is resolved. I have removed the ones you added to the yoke when it was assigned the joyletter C, as these are duplicates of assignments made when it had the letter B. FSUIPC7.ini
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.