Jump to content
The simFlight Network Forums

John Dowson

Members
  • Posts

    13,301
  • Joined

  • Last visited

  • Days Won

    271

Everything posted by John Dowson

  1. Sorry I am a bit late to this one... Looks like you have solved your issue thanks to @target11 so I won' t read this in detail, but there are a few points you should be aware of: 1. The change UseProfiles=Yes --> UseProfiles=Files just makes FSUIPC use separate files for profiles. Without this. you can still use profiles (unless you set this option to No) - there is no change in the profile functionality. The Profile folder is only created once this option is set to Files. 2. The Ignore axis button is just used in the assignments panel, it has no affect when the axis panel isn't open. If you don't have a profile for an aircraft, the general [Axis] section will be used. Also, be aware that if you, for example, create a profile-specific [Axes.xxx] section for an aircraft, but not a profile specific [JoystickCalibration.xxx] section, then the general [JoystickCalibration] section will be used. So, if you want to assign an axes for a specific aircraft in MSFS rather than in FSUIPC, not only do you nee to create an empty profile-specific Axes section, but you should also create a profile-specific calibration section and remove/reset the calibration for each axes assigned elsewhere. If you don't do this, FSUIPC will still calibrate the axes assigned elswhere. 3. I am surprised that you need to set this option. I haven't looked at the ATR yet (I will do later), but you shouldn't really need to change this option if assigned to the correct axes control and with the No Reverse Zone option checked/unchecked as appropriate for yout throttle and aircraft. I will take a look at this in the ATR later. John
  2. There is no offset for battery 2, If using the A320neo. you could try adding the simvar ELECTRICAL MASTER BATTERY:2 to a free FSUIPC7 offset as an unsigned byte (UB). Detail on how to do this are on page 34 of the Advanced User guide. Otherwise, list the lvars and see if any of those hold the battery state, and if so you can use that.
  3. Ok, thanks for the update Leo. I was going to look into this today and that has saved me some time! Cheers, John
  4. The license has been updated, valid until 1st June 2023. John
  5. Try the attached version, 7.3.21a - add ShowSplash=No to the [General] section of your FSUIPC7.ini file. John FSUIPC7.exe
  6. There is a lua script available for this in the User Contributions sub-forum: The script should work in MSFS for the audio callouts, but the display facilities currently won't work unless they are using the Wnd library, which I doubt. You should also be able to disable the display facilities, or create your own lua from this.
  7. I am not sure I fully understand your issue - it would help if you could attach the lua file that is causing this problem, as that would be where the solution. if any, would need to be applied....
  8. Ok, that is the FSUIPC7 splash-screen. That is always displayed when FSUIPC7 is started, so that you know its running, as it starts and sits in your system tray. You cannot turn this off at the moment, but I guess I could add an option to do this. But I don't see why this is an issue, and if disabled, there would be no indication that FSUIPC7 had been started. If this really is an issue for you, I can add an ini file option (in a future release) for this to be disabled.
  9. No, they shouldn't conflict as only one (the first match found) will ever be used. Just makes things a lot easier, and by using aircraft substrings, the same aircraft with different liveries will also match, and so saves you having to add an aircraft to a profile when you are using a different livery. Looks a lot better/cleaner, with one profile for the PMDG 737/777 and 757, and another for the PMDG 747. Note that you were previously also assigning the steering tiller to the same axis as the rudder (which is common) but only in some of your old profiles, You may want to consider addung this back to both of your current profiles.
  10. But why would you want to do this? Why do you have several profiles for the 747? You only need separate profiles if the controls/assignments are different - they should be the same in all 747 variants, so you should only need one profile. Usually you would add an aircraft to an aircraft profile rather than creating a new profile. And rather than adding each livery, you should change the names used in the profile section, so if you change: to then that would match all 747-8 aircraft, or you could change to to match all 747s, and you can even add the 757 as that looks to be the same: There are slight differences in rudder/steeringtiller assignments, but I would have thought this should be the same for all 747 variants... Similarly, you probably only need one profile for the 777.
  11. As I said in my previous post, if you don't want to see the splash screen, don't use or even install the desktop icon, by deselecting the checkbox on the end of the installation process. All the desktop icon does is start MSFS and display the splash screen for 30 seconds or so while MSFS is starting. FSUIPC7 does nothing with start menu's, so if that is bringing up a splash screen then something else is doing that. You can easily create a desktop shortcut to just start MSFS if that is what you want to do.
  12. You have one Community folder, under R:\FS11\Community\. The C:\Users\alhar\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\ folder is for the Community apps read/write storage area. These different locations are explained in the WASM section of the Advanced User guide. I don't have any experience with the Volocopter - I loaded it the first time (or maybe second) to look at your throttle question. I don't know much, if anything, about this aircraft. Getting warm here - outside temperature in the shade is 25C, and feels a lot hotter in the sun.... Have some gardening to do later, but I will wait until 7pm or so when its cooler...! Glad its now working. Cheers, John
  13. Check any anti-virus software you are using (including WindowsDefender). I cannot see any reason that it won't run unless it is being prevented somehow, especially as you were able to re-run it previously. Also reboot first, just in case that helps.
  14. The screenshot says its version 4.934, so you need to update. If FSUIPC is crashing on start-up, then this is normally due to a corrupt weather file. Try disabling weather by setting NoWeatherAtAll=Yes to the [General] section of your FSUIPC4.INI file. If this solves it then either your wxstationlist.bin file is corrupt, or one of the .wx files saved with scenarios is bad. To resolve this, delete all of the .WX files from your FS Documents folder (where your flights are stored), and the file "wxstationlist.bin" in your <user>\AppData\Roaming folder for FSX. If that doesn't solve your issue, please show me/attach your FSUIPC4.log file, and also your InstallFSUIP4.log file if this issue only appeared after updating. Why won't it run? What error do you get? If it ran previously, I can't see why it won't run again, You can try re-downloading the zip file, unzip it (don't run it from the zip file) and try again, And there is no need to delete any files.
  15. This happens every now and again, but I am not sure why it happens to this version and not the previous version... If you can report this to McAfee, they should be able to check the file and once confirmed it is virus free they can add an exception so that it passes. Thanks for reporting. John
  16. You assign to an axis in the left-hand side of the axes assignment tab (This side to send an axis value) : The right-hand side is to send specific controls/presets when entering/leaving axis ranges, and the axis value is not used (This side to send button controls). The Select for preset checkbox applies to both sides. It is positioned there as I initially only intended this to be used on that side, but as a side effect it can also be used for axis values, such as in this case. There is only one Community folder used by MSFS...I think you mean you are using the addonlinker program to control what is there.... John
  17. What do you mean by this? Please give details. How are you doing this? What do you mean by "another 747"? Can you please attach your FSUIPC6.ini file so that I can see your settings. Also a log file showing your issue would be useful, with logging for Events and Axis controls enabled. The log file will probably be quite large so will need compressing/zipping. John
  18. Before anything else, please make sure that you are using the latest (and only supported) version of FSUIPC, which is 7.3.20. If not, please update first and try again, and then attach the log files if the Volocopter throttle isn't working.
  19. Can you please attach the full log files...and its the FSUIPC_WASM.log file I need to see, with Debug level logging, not the FSUIPC_WASMIF.log. I don't even know why you have that file - under normal conditions, the WASMIF/WAPI should log to the FSUIPC7.log file. Where did you find that file? And only set logging for Events in FSUIPC7 (and no other logging), and also set Debug level logging in the WAPI as well.
  20. Just checked that throttle preset in the latest update and that is working fine here - please show me your FSUIPC_WASM.log file. As for the AP/Garmin in the Volocopter, I am not sure what that is (is it even a Garmin?)...I am not sure if it is possible to control this from external applications at the moment... John
  21. If the problem is with FSUIPC7 not running, please see the README.txt or the Installation and Registration guide - you will need to update your VC++ redistributables to the latest combined package. Otherwise explain your issue with FSUIPC7 if that is the problem, or contact the support for your smartcars program. I can only support FSUIPC, not the programs that use it. And please take care to post in the correct forum for the product you are using. I have moved your post to the FSUIPC7 support forum. John
  22. The SU13 update has just dropped, so I will get back to you after I have updated and checked things (tomorrow sometime). In the mean-time, can you activate Debug level logging in the WASM and show me/attach your FSUIPC_WASM.log file, as this will show what is being received and applied in the sim. See the WASM section in the Advanced User guide if you don't know how to do this. So do I - this is normal in the Volocopter. Different events are continually send for many MSFS aircraft. You can stop these being logged by using the DontLogThese ini parameter, preferably in your Volocopter profile. Again, see the Advanced user guide for details. Or you can safely ignore these. John
  23. I can't really help if using PM - you should try PM support. Having said that, your issue seems to be similar to this (very old, but still valid) post: You can also try logging: set logging for Events (non-axis control) and also offset monitoring for the PM APU offsets (560F, 5624 and 5625). If you keep the logging console open (check Send to console window), you can then see what events (if any) are being used and how those offsets change when you operate the switch on the PMSystems screen. You can then try and duplicate that behavior. This is quite common for spring loaded switches - they only have one (single direction) or two (dual direction) buttons. If you need to send another value to an offset (or a control, or whatever assignment) when it springs back to the central position, then this should be assigned to the button release of the 2 buttons for the non-central position. Pete retired several years ago now. Cheers, John
  24. For the Garmins (if they are functional/working in the Volocopter), both Asobo and WT, you can use the MF presets that are also included in FSUIPC7. You can use the MF HubHob site to search for the relevant preset:
  25. @Oodi MenakerSorry for the delay. Could you please test the attached dll: FSUIPC6.dll Thanks and regards, John
×
×
  • 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.