Jump to content
The simFlight Network Forums

John Dowson

Members
  • Posts

    10,836
  • Joined

  • Last visited

  • Days Won

    209

John Dowson last won the day on March 12

John Dowson had the most liked content!

Profile Information

  • Gender
    Male
  • Location
    Spain

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

John Dowson's Achievements

Grand Master

Grand Master (14/14)

  • Well Followed Rare
  • Reacting Well Rare
  • Conversation Starter Rare
  • Very Popular Rare
  • Dedicated Rare

Recent Badges

508

Reputation

  1. You need to use the lvars, not the standard FS controls. The easiest way to do this is to use the available presets. Check the Select for Preset box, click the Find Preset... button, and navigate to the Black Box->AnalogBaron presets, and under Electrical you will see the following presets: LEFT_ALTERNATOR_OFF LEFT_ALTERNATOR_ON RIGHT_ALTERNATOR_OFF RIGHT_ALTERNATOR_ON Try assigning to those. However, looking at the calculator code for those presets, it looks like the *_ON ones are toggles (but not the *_OFF ones) for some reason. You can either use those or define your own presets. Alternatively, you can add the lvars BKSQ_alternatorSwitch_R and BKSQ_alternatorSwitch_L to free/spare FSUIPC offsets and assign to the provided offset controls to set/clear the lvars via the offsets. John
  2. First you have to be aware that the flight load/save/auto-save functionality provided by FSUIPC completely rely on the functions provided by the MSFS SDK, namely the SimConnect functions SimConnect_FlightLoad and SimConnect_FlightSave (as well as SimConnect_FlightPlanLoad). Although the SimConnect_FlightLoad function is documented as working, the SimConnect_FlightSave function (as well as the SimConnect_FlightPlanLoad function) is still documented as 'NOTE: The current status of this function is NO ERROR, NO RESPONSE.', which is Asobo's way of saying that this function is still not 100% working/reliable, It has been this way since release. Therefore the saving and loading of flights is still not 100% reliable, although some users have reported more success with this than others (maybe aircraft dependent). If it is not working, I cannot do much about this - you can try raising a bug request with Asobo, but they may reject this if the flight file is generated by the SimConnect_FlightSave function as they are already aware of issues with this. Flight files generated by MSFS2020 itself and those generated by external apps (using SimConnect_FlightSave) should be compatible/the same, but this may not actually be the case at the moment. You could try loading the flight file via FSUIPC7 (File -> Load Flight) to see if that makes a difference. You can do this either when in the World Map, or when you already have an aircraft loaded and ready-to-fly. John
  3. Yes. Up to you. There are hundreds of add-ons that use FSUIPC, some the freeware version and some the registered/paid version. I cannot comment on any such software - you need yo contact the developer. John
  4. But as I keep telling you, FSUIPC and the PFC driver have nothing to do with your RSG equipment, and I cannot help with this as these devices are not supported by FSUIPC. No problem. John
  5. Can you please try the attached version which has been reported to have fixed this issue. Please let me know if it works for you. John FSUIPC7.exe
  6. That is nothing to do with FSUIPC - I hope that is not in the FSUIPC Launch.Addon section... This is because they are mot written - you add them only if/when needed. There are two new ini parameters that you can add to the [General] section which control the delay between sim detection and trying to connect: DetectToConnectDelay - defaults to 5 seconds, used when FSUIPC7 is started manually DetectToConnectDelayAuto - defaults to 60 seconds, used when MSFS starts FSUIPC7 (i.e. when the '-auto' command-line argument is present No problem - thanks for testing this for me. The issue seems to be that MSFS does not send the required events when you try to connect obtain a connection too early during its initial loading period. I don't understand why I cannot reproduce this here though, very strange... John
  7. Then read that! As it says in that post, I don't know what NMEA/GPS sentences Foreflight is expecting - you need to ask them. It is a facility provided by FSUIPC to send out GPS data to the network for use by 3rd-party programs. If Foreflight is using this feature, they should let you know how to configure this in FSUIPC. This feature is configurable in the AutoSave/GPSOut tab of FSUIPC4 and is described in the FSUIPC4 User guide starting on page 10. But i do not support Foreflight, only FSUIPC, I do not know how to configure FSUIPC for use with Foreflight, you need support form them, not me. John
  8. Your original EXE.xml was corrupt - it was missing an opening SimBase.Document directive. You have two other add-ons using this file - AFCBridge and Logitech MSFS plugin. One of these must have corrupted this file, I have added these back in the attached EXE.xml, so please use this to replace the one you are using: EXE.xml And again, what happens when you try to start manually, i.e. when you double-click the FSUIPC7.exe in windows Explorer? Do you see the FSUIPC7 splash-screen? Is an FSUIPC7.log file created, if so please show it to me (i.e. attach it). Also, please right-click on the FSUIPC7.exe and look at the properties, security tab. Is it blocked from running there? if so allow it to be ran. John
  9. Can you please try the attached. I have increased the delay between detection and trying to connect from 30 seconds to 60 seconds. There is also a new ini parameter where this can be adjusted if needed. John FSUIPC7.exe
  10. I know nothing about Foreflight or even if it uses FSUIPC - as the problem is with this software, I suggest you try their support first. John
  11. The FSUIPC PFC device drivers were written by Pete Dowson, my father. I support these to the best of my ability, but as I don't have any PFC devices my knowledge on these is not much more than what is provided in the documentation and available in existing support requests. These drivers have been stable for many years and are closed for further development, No, not for your issue with the RSG500. It is not, It only runs when FSUIPC is running (it is an embedded dll) and will have no affect on the RSG500. Not really - you need support from RSG for this device. John
  12. Definitely an issue with the latest version of FSUIPC7 - looks like the AircraftLoaded event is received with an empty aircraft name for some reason, so the PMDG threads are not being started. Probably a timing issue somewhere... It should be ok if you exit and then restart FSUIPC7. This problem also applies to the current release of MSFS. I have also added a fix in the attached version if you would like to try. I am also on SU15 now but looks like the beta switcher program isn't working as expected - it has overwritten my released version...hmmm I see there is also a new SDK (0.24.1.0). I will take a look at this and update ready for the release. John FSUIPC7.exe
  13. Can you try the attached please - and add back the '-auto' command line flag in the exe. Show me the FSUIPC7.log regardless of all is working or not please and I will take a look tomorrow (finishing now, orders from the wife!). John FSUIPC7.exe
  14. That is interesting....however, I suspect that it was reconnecting a lot at start-up as that will just reduce the initial stall time from 45s to 5s. Can you show me a FSUIPC7.log file please. I suspect that this is a timing issue between establishing a simconnect connection and requesting the data. I think I will remove this and add the delay between detecting the sim and connecting when auto-started, I will provide an updated version for you to test, probably tomorrow. 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.