John Dowson

As it looks like it is not getting AI data from FSUIPC anyway, there is nothing I can do. Even if it was getting AI data from FSUIPC, there is nothing I can do at the moment as there is currently no way to get multiplayer/group aircraft data via SimConnect. I still think your best bet is to use something like JoinFS or similar. If that (or a similar program) is still buggy and/or under development, they will hopefully get around to fixing those issues at some point - if these issues are being reported...!

How does AivlaSoft's EFB2 get its traffic information? knowing that would help.... FSUIPC's traffic tables just show the AI traffic as received from the FS and there is no way to receive multiplayer/group traffic, unless they have also been injected as AI traffic... John

You should always use letters to prevent possible issues when the joy ids change, that is why this is now mandatory. I will update the documentation, as I said. Thanks, John

@kingm56Sorry for the late reply - missed your post for some reason... I am not sure what you mean.... offset 0x3110 is a general facility for sending events/controls to the FS. You can't read them as there is nothing to read - you write to them to send any control to the FS, including PMDG custom events, which I believe use the Rotor Brake control (with the parameter indicating the actual control/event to be used) in the MSFS version. Why do you think that you cannot send these PMDG events using this offset? They are the same as any other event... John

No - you should not run the sim as admin, or FSUIPC7, unless you have a need to do so. All programs communicating to MSFS should be ran at the same priority level, so if you are running MSFS without admin privileges, make sure FSUIPC7 is also ran without admin privileges. Ither than that, I have nothing more to say on this issue that I haven't already said (many times...!_...please see the following posts: Read those posts and check your EXE.xml. If that file is in the correct format and in the correct location then I have no idea why MSFS is not starting FSUIPC7. You can go back to the older method of having the MSFS.bat file start FSUIPC7 - details on how to do this are in those posts I referenced. I will create a FAQ topic on this issue and put all relevant information there....when I get time! John

I don't think it is possible to get information via simconnect on any other aircraft apart from the users' aircraft and AI aircraft at the moment. However, if the multiplayer aircraft are injected into MSFS as AI aircraft they can be seen. I believe some programs such as JoinFS do this. See the following thread: https://forums.flightsimulator.com/t/vatsim-ivao-lnm-etc-all-need-their-simconnect-injected-aircraft-to-show-labels/362824/73 John

I've checked this and it is not possible. I will enquire about this with SimMarket. John

Maybe also worth checking the MSFS assistance options - maybe the copilot is setting this...

Done.

Strange issue...no idea if it is related to FSUIPC. Can you please activate logging for Events and Buttons & Keys, and produce an FSUIPC7.log file showing your issue, than attach that as well as your FSUIPC7.ini file and I will take a look - the log file may be large and need zipping. You can do this with the logging console window open, and see what events/timestamps you see when this occurs, which may help identify the cause. John

Yes, I would have thought you would get the discount price. However, don't have any control over SimMarket's discount pricing policy, but I will see if I can add a discount if you have previously purchased FSUIPC4/5/6 in a bundle, if possible... John

Just checked and it looks like I removed this ini option ion FSUIPC7 but have forgotten to remove it from the documentation. Too many people were having issues with Joy id changes as they weren't using the JoyLetters facility, so I originally just change the default from No to Yes. However, as many users transferred there ini files from other FSUIPC versions, this was still not being set so I decided to remove this option altogether but forgot to update the documentation. This option really isn't necessary. If you want to change the original letter assigned, just do this before you make any assignments and then reload/restart. I will update the documentation to make this clear. John

Why don't you just try the trial license, available in a thread at the top of this forum. It has currently expired, but I will be generating a new one a bit later today. If your VRInsight devices are serial devices, see appendix 3 of the Advanced User guide 'Handling VRInsight serial devices in FSUIPC', together with the separate document Lua Plugins for VRInsight Devices. John

That file is deleted when you uninstall, and will be created (in-the-fly) the next time you run MSFS. It is automatically generated once connected to MSFS. John

Yes, sorry - TrafficStallTime cannot be set to a negative value, my mistake. Set this to 2 or 3 seconds (or higher) if using traffic data. If not, it doesn't matter. Hmm. Maybe that is the case - I will check. However, I think that profile specific luas should be started/auto-run when you start FSUIPC with an aircraft already loaded. However, they won't start until the lvars/hvars have been received. I will check this - but next week now, I'm off tomorrow and back next Thursday, so I will check then. Ok, thats good to know, thanks. John

What has FSUIPC got to do with any of this? And what does C1, Vr and V2 actually do? FSUIPC is aircraft agnostic - it just sends controls as you have assigned for that aircraft. The controls for many MSFS aircraft, especially add-ons, can be aircraft specific, and in the case of the FBW A320, version specific. Take a look at the MobiFlight HubHob resource (https://hubhop.mobiflight.com/presets/) and you can see what is available for the different version of the FBW A320, and also the Fenix A320 and the Asobo 787. You will see that the controls you need to send are quite different for each aircraft. In FSUIPC, you need to assign the correct control for each aircraft (using profiles). I know nothing about FDC Live Cockpit - you will have to consult the documentation or support forum for that program to see how (and if) it needs separate configuration for different aircraft or versions. John

I know why you say this - FDUIPC can be used with any HID joystick type devices, as well as other devices like GoFlight and PFC devices using specific drivers that we provide. You don't need to use lua if yoy don't want to, although it may be necessary for non joystick type HID devices. FSUIPC does not have any facilities for talking to IOS devices. If its only GPS data that you require, then it may be possible then you may be able to configure FSUIPC's GPSout facilities (see User Guide) to provide the correct data for that program from a USB acting as a standard serial device on the FS PC. Otherwise, there may be additional programs to help with this (e.g. WingX). Alternatively, there is a websocket server/interface also available, and any web pages written using these dacilities should be accessible from a web browser on any device. There have been several questions on using ipad with FSUIPC before, maybe check some previous posts - here are a couple (version of FSUIPC and the FS dont matter here as the FSUIPC facilities are the same): There is also a utility (FSXFollow) that allows connection but using WideServer: By the way, you posted in the User Contributions sub-forum where it states NOT for support requests. I have moved your post to the correct forum. John

I will update tomorrow.

That is very strange...that version has been released now as 7.3.6. There was only one change and I can't see how that could effect that... Please download and try the latest release. If you get the same issue, activate logging for Lua Plugins and set Trace logging for the WAPI (in your FSUIPC7.ini)) and show me the log file as well as the lua script.

Do you have AutoAssignLetters=No in the [JoyNames] section?

Got me sad because I´ve spend €60+ and now own a plane that I can´t fly. That is unfortunate...they should make it clear that the aircraft cannot be controlled externally from MSFS. Many home-cockpit builders will have the same issue. Maybe try asking for a refund... Thanks for the update. John

I have also updated the dll - please find attached.FSUIPC_WAPID.dll I will release this version shortly. Thanks got your help with this. John

Ok - so this also indicates the issue is/was with the WASM/WAPI. That would be good, thanks, After you have done this, you can disable the WASM and uninstall it again if you like. Not an issue keeping it installed/running, but may as well remove to save resources if not using. John

Hi @aurel42 I found an issue in the WAPI (WASM interface) code that can cause FSUIPC7 to crash in certain circumstances. This is fixed in the attached version if you would like to try it (with the WASM enabled). John FSUIPC7.exe

@Fragtality Could you try the attached version please. I've also attached the updated WAPI library (and header - not sure if you need this) for you to use to rebuild your client (zipped). Let me know how it goes - attach the trace logs again if any issues. Thanks, John FSUIPC7.exe FSUIPC_WAPI.zip