John Dowson

Why don't you just try? If you try yourself and post if you have errors, you are more likely to get a response. Try something like: That will be called 5 times a second, and will change the value in offset 0x66E2 to match your criteria (i.e. values in the other two as-of-yet unspecified offsets are > 10000 then 1, else 0). Replace the ? with the correct offsets/types you are reading. Still don't know what those are. Can you see how that works? Also, note that you can use ipc.log to log a message, which can help you to debug and also see how your lua is working.

@ricktana Your EXE.xml is correct, and if its in the correct location I have no idea why its not being picked-up by MSFS and used. I don't have time to investigate MSFS anomalies. sorry. If you want to investigate further, ask on the Asobo forums why the EXE.xml file isn't being picked-up. Please report back if you find anything. John

No. For the last time, this is auto-generated. Just leave it alone. Why are you quoting the user manual at me? Ok. Which offsets? What do they hold? If you want to do this for two offsets, then depending upon how quick you want your offset to change, there are different methods you can use. The easiest way is just to use a timer (event.timer). In the timer, read the offset values, do the comparison and then write your value when needed. The second would involve to event.offset functions, each monitoring one of your 'read' offsets, and setting a global flag when your condition is true. Each offset function should then check both global flags, and call write to your offset if your condition is met. There are plenty of lua examples, both included with FSUIPC7 and available in the user Contributions sections here. I suggest you take a look at some. I really haven't got time for basic lua lessons, sorry. Just look at the documentation and examples and try things out.

Ok, thanks. Unfortunately as you aren't installing the auto-start component, the log doesn't tell me what type of install it thinks you have. If the installer thinks you have a steam install for some reason and its an MSFS install, it will crash when tryint to create the EXE.xml as the required folder doesn't exist. You could test this, by manually creating the folder: <USER>\AppData\Roaming\Microsoft Flight Simulator Then run the installer again, select to install the auto-start component, and see if it works. If so, you can then move the EXE.xml created in that location to the MSFS install location (and remove any folders you created). I'll update the installer to log the install type regardless of whether you opt to install the auto-start component. I have also had one (or maybe two) other confirmed reports of the installer not correctly detecting the install type. Can you also let me know the locatin of your MSFS UserCfg.opt file - is it in $LOCALAPPDATA\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt ? Otherwise, this is what an EXE.xml looks like - replace the FSUIPC7.exe path with your own (highlighted in bold): John

Why? As I said, just don't touch that section. It is managed by FSUIPC - leave it alone! Why did you change it? What are you trying to read? You use the read function corresponding to the data type of the data held in the offset you want to read. Please see the lua documentation for event.offset, in the Lua Library document. Also, take a look at the example lua files provided - there should be a zip file containing examples in your FSUIPC documents folder.

Whats the issue? The log shows your lua is running ok. However, you are reading from 0x67E7, which is in a reserved area. Are you sure thats correct? Other than that, your lua is running ok - it will just run and exit. If you want to keep it running, and update an offset when another offset changes, you probably want to ne using the event.offset function. Then the lua thread will keep running, waiting for that offset to change, and then calling the event function, in which you can write to your other offset. If thats not what you need, then maybe activate the lua on a button or key press rather than have it auto-started. Don't write the [LuaFiles] section. This is constructed automatically from the lua files (old/removed and new) and shouldn't be manually changed. Just add your luas to the [Auto] section when you want them auto-started. John

The install log is written at the end of the installation process, so if it crashes no install log file is generated. Could you show me your install log for this please. Maybe it thinks you have a Steam installation? Yes, but I've no idea what at the moment. It won't be, if the EXE.xml file has not been created/updated. You can try manually creating the xml file if you like. Otherwise, you can go back to the old way of starting FSUIPC7 with MSFS, via the bat file. There is another post with the same issue, and there are also instructions on how to update to start FSUIPC7 from the MSFS.bat file (but make sure you use the correct replacement for INSTDIR, your installation folder): John

Very strange...but glad its now installed and working. Thanks, and enjoy the rest of the weekend as well, John

@giosuepirozzi Your EXE.xml also looks fine. Can you check the location is correct (see my previous comment for details). If the EXE.xml file is correct, and in the correct location, I do not know why it is not being picked-up by MSFS. You could go back to the old method of starting FSUIPC7. To do this, open the MSFS.bat file located in your installation folder, and change these lines: to

Please download and try the following installer: http://www.fsuipc.com/download/Install_FSUIPC6a.zip It will still display the message, but you can continue to select the P3D version you wish to install into.

Hi Thomas, And you ran P3D at least once after installing (or re-installing) the client? If there are no P3D registry entries, it won't detect your P3D installation and won't install. I'm not sure why you haven't got the registry entries. I will look into this... In the mean-time, I can update the installer to maybe ignore this, and proceed to the selection of the P3D versions to install into (rather than aborting).

And you get no pop-up showing why it can't auto-start FSUIPC7? Your EXE.xml file looks fine. What was the location of this file, and what type of MSFS install to you have - MS Store or Steam? For Steam installs, it should be located under <USER>\AppData\Roaming\Microsoft Flight Simulator and for MS Store installs under <USERL>\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\ or <USERL>\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\ Can you verify the location is correct, and that the same folder contains your MSFS UserCfg.opt file.

After the path selection page, there should be a Choose Components page. Do you not see that? It is in the Choose Components dialog. This is not only strange but worrying as the installer does not download anything... If you re-installed, did it detect your original installation and uninstall that first? If so, that would have removed the registry entries. Can you re-download the installer and try again, and without selecting the auto-start component this time, to see if that makes a difference.

Ok, so FSUIPC7 starts without a problem, and its only the auto-start that is an issue. Does MSFS show any message giving an error or exception when started? Can you attach or paste the contents of this file please: C:\Users\Maurizio\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\EXE.xml

Your install log looks fine. What happens when you try to start FSUIPC7? i.e. by double-clicking the FSUIPC7.exe (no need to have MSFS running) What happens when you start MSFS using the MSFS icon? i.e. how you started MSFS before installing FSUIPC7 What happens if you start MSFS using the FSUIPC7 created desktop icon?

👍

Yes, as Pete says, you shouldn't do this. Re-install in a different location.

No, this sounds very strange! The MSFS.bat file does nothing but display the splash screen and then start MSFS. It does nothing else. What happens if you start MSFS without this (i.e. how you used to)? Installing FSUIPC7 will only affect your steam installation in one way: it will update the EXE.xml (located under $APPDATA\Microsoft Flight Simulator) to have FSUIPC7 auto-started with MSFS, if you selected that option during installation. Try just starting FSUIPC7 (double-click the FSUIPC7.exe) without MSFS - does that work? If so, just exit. Then try starting MSFS from Steam or using your old icon/start method.

Okay. Thanks for the update.

How are you assigning? Have you calibrated properly? Please see the User Guide, sections: THE EASY STEP-by-STEP WAY TO CALIBRATE YOUR CONTROLS - P38 CALIBRATING MULTIPLE THROTTLE, PROP & MIXTURE AXES TO "LINE UP" - P41

FSUIPC7 is np longer started from the MSFS.bat file, it is started from the MSFS EXE.xml, if you select that option when you install. What version of FSUIPC7 are you using? The latest version is v7.0.4. If you are not using this, please update. If you are using this version, and you selected to have FSUIPC7 auto-started with MSFS, you should either see a splash screen when FSUIPC7 is started, or an error message telling you that it cannot be started. If you see neither, then you did not select to have FSUIPC7 auto-started when you installed. So, please check you version and update if necessary. If you still have issues, please provide more details and, as a minimum, show me you InstallFSUIPC7.log file. John

Unfortunately not. This should be in the MSFS SDK documentation, but it doesn't say much on these things at the moment. This is the entry for TOGGLE_MASTER_BATTERY: KEY_TOGGLE_MASTER_BATTERY TOGGLE_MASTER_BATTERY Toggles main battery switch All aircraft Not very informative! Trial and error, as well as searching on the Asobo forums, are your best bet. You can have multiple assignments to a sign button or key press by commenting out the initial assignment (in your FSUIPC7.ini file) and then reload your assignments. You can then make your second assignment and click 'Ok'. Then, edit the ini again an uncomment your first assignment. Then go to the assignments panel again and re-load the ini. When you have multiple assignments to a button or keypress (you can have as many as you want) the assignment fields in the UI will be disabled and just show the first assignment. Alternatively, depending on the button type, if you just want two assignments, you can assign one on the press and the other on the release. Note that using multiple assignments is also typically used with either compound button conditions (where the action of the button is dependent on the state of another button) or offset conditions (where the action is dependent on the value in an offset). See the Advanced Useer Guide for details, starting on P19 Sequences, Combinations and Mixtures. John

No, this is not easy to do. Lvars are accessed directly via a function provided by the Panels.dll. Simulator variables come via a request to simconnect (where you have to set-up a data definition, a request, a group and priority, and finally request the item) and the value is received in a callback message in a different thread. There is also the added complexities of the types - lvars are all double (64bit floating point numbers), whereas each simulator variable has a specific type. This has also been requested before.

That's the location where the add-on.xml must reside if you want it "auto-discovered". As I said, its better to choose a different location for the actual installation folder. I have had one other report of the installer not creating a key file. but I'm not sure how this is possible. Installing in a different folder fixed it for the last user I think.

You are using v6.0.9. That is an old unsupported version. Please update to the latest release, v6.0.12 and try again, and post your .log an .ini if you still have the issue (not the _prev.log).