John Dowson

No problem... Also, if assigned to a momentary button (as opposed to a switch or sticky-button) and you only want 2 controls to be sent, you can assign one control to the press and the other to the release.

You can do this by either: - using a macro (see documentation on macro usage) - overloading your assignments via editing the ini- this is described in many other support requests, e.g. That is for FSUIPC6 but the procedure is the same for FSUIPC7. - defining a preset to send both controls and assign to the preset For issues and questions on MSFS/FSUIPC7, please use the FSUIPC7 support sub-forum - I will move your post. John

I have just done some tests as well, and setting the same cloud layer at 3000ft to 6000ft I see this for cirrus: 750719 46208 Monitor IPC:CE80 (U16) = 975 750719 46208 Monitor IPC:CE82 (U16) = 914 750719 46208 Monitor IPC:CE87 (U8) = 1 which changes to the following when switching to cumulus: 822422 46208 Monitor IPC:CE80 (U16) = 2133 822437 46208 Monitor IPC:CE87 (U8) = 9 so I am seeing a bigger difference for the cirrus which is way off... Checking in P3Dv5 - the upper altitude for cumulus is even more out: 73906 44992 Monitor IPC:CE80 (U16) = 3469 73906 44992 Monitor IPC:CE82 (U16) = 914 73906 44992 Monitor IPC:CE87 (U8) = 9 and Cirrus give the same as P3Dv6: 212172 44992 Monitor IPC:CE80 (U16) = 975 212172 44992 Monitor IPC:CE87 (U8) = 1 Not sure why the upper altitude mismatches the P3D value at the moment... Update: a 3000 foot thick layer of cirrus is either not possible in reality or very highly unlikely. The cirrus layers are usually very thin. I’m not sure what P3D actually does when you tried to set such values. My logging suggests that this is being reduced by P3D, but you seem to be seeing the correct value, which is strange... Also I think the upper altitude is calculated, not provided, so may not be a 100% match with the set value. But I need to go through the code and look at what is being received to generate these values. As I am not familiar with this section of the code, this will take me quite a while. I will look into this further when time permits and get back to you, but this may take a while... John

Yes - only log files from the current and previous sessions are available. No need to post it unless FSUIPC actually crashed. As I said, it was most likely an exception due to the MSFS crash, and then FSUIPC7 would exit gracefully. Just look at your log file to confirm this, and only post it crashed, i.e. no closing log statements, like the following: John

It doesn't/can't.... Can you show me/attach the A320 Mode.lua script - it may come from this assignment:

I am surprised that works... The problem is that the ipc.execCalcCode call will return almost immediately, but it will take a while for the updated lvar value to be received back by FSUIPC, so when you read the lvar value you will be reading its old value. You should add a delay before reading the lvar value (i.e. ipc.sleep(30)). But it would be better to just either: 1. Add the A:CIRCUIT ON:89 simvar directly to an FSUIPC offset using the myOffsets.txt file (see Advanced User guide), or 2. Add the lvar L:WING_DEICE to an FSUIPC offset using the [LvarOffsets] ini file section. The offset would then be automatically updated when a new/updated value was received. Calculator code is in RPN format (see https://docs.flightsimulator.com/flighting/html/Additional_Information/Reverse_Polish_Notation.htm), so try: ipc.execCalcCode("(A:CIRCUIT ON:89, Bool) (L:var_GlareshieldAnnunciatorTest, Bool) or (>L:WING_DEICE)") You could also maybe treat them as numbers and add them: ipc.execCalcCode("(A:CIRCUIT ON:89, Number) (L:var_GlareshieldAnnunciatorTest, Number) + (>L:WING_DEICE)")

Your press assignments are set to repeat - you shouldn't need this as the assignments are just updating an offset (no point in repeating this). So you can maybe change those assignments to a press rather than repeat, but this won't make much of a difference. Other than that, FSUIPC is behaving as expected. As I said in my previous comment, the offsets you are writing to are NOT controlled by FSUIPC, but are reserved for use by other systems. You need to look into what is using those offsets as it is that that should be sending the appropriate controls. If its the Sim-Avionics update that provoked this issue, I would have thought that the issue lies there somewhere. But you seem to be using offsets reserved for both Mark Hastings B777 Systems Simulator (5300-53FF) and Enrico's Project Magenta (5400-5FFF). How did you know which offsets to use - which software/document gave you this information? Maybe check that to see if its changed...

Strange how? Those are all a very long way away (not that that should matter)...have you set a very high or unlimited TCAS air range? Some of he VS values look very strange as well... I think I will make this setting the default, so you don't need to set that ini parameter. I will also update the latest beta release (see Announcements sub-forum) to this version in the next few days. John

Yes, MSFS has always given a lot of issues. By some reports, this can also be related to on-line activity. A few thinks to try: - switch to AI traffic if using live traffic, and maybe try some flights without traffic - turn off live weather if using that to see if that makes a difference - check for add-on conflicts - i.e. try the Simstaller tool from Parallel42 (free) - check the Asobo CTD reference for further tips: https://forums.flightsimulator.com/t/unofficial-reference-guide-to-ctd-solutions/442117 John

Yes, corrected in the attached version (version number unchanged at 7.4.18b). John FSUIPC7.exe

Can you try the attached version - please add AIAboveGroundLimit=1000 to the [General] section of your FSUIPC7.ini file. I need to go out now so haven't had time to test this version - please let me know how it goes and also attach your log file. I am also now logging the to/from ICAO codes, so should be able to see when/if that changes. John FSUIPC7.exe

I am not familiar with the New Weather Interface so not sure I can help at the moment, although I can look into this and get back to you (and maybe ask Pete about this). Are you writing to C800-CBFF to get the requested weather in CC00-CFFF? If so, can you show me how you are doing this.

No files attached,,,!

Done.

First, your log shows a couple of errors: This type of error is usually caused by a corrupt P3D client - please re-install this component and see if they go away. Ok, then can you please supply/ayyach a log file showing this issue. Activate logging for Buttons & Switches as well as Events. You can also monitor the offsets you are using. However, note that the offsets you are using are in an area with this description: i.e. they are reserved for these systems and are handled by them, not FSUIPC. Maybe check the offsets you are using are still valid after the update. John

That shows an exception in FSUIPC - did FSUIPC7 crash? Can you please show me/attach your FSUIPC7.log file from when it crashed. If MSFS CTD'ed, are there any windows events for this? If FSUIPC7 CTDs, this should not affect MSFS in any way, as it is a separate app. If MSFS CTDs, this can cause exceptions in FSUIPC7 (which will be reported in the windows events), but FSUIPC7 should handle this gracefully, and usually exits as it detects that MSFS is no longer running. Your log file would show if this is what is happening. John

Why not? Please show me a log file for this. This usually happens if you have the DetectToConnectDelayAuto ini parameter set too high, and are not waiting long enough for it to connect., If assignments to presets or lvars/hvars/calc. code stop working mid flight, this is usually a sign that the FSUIPC WASM module has crashed, You can prevent this by setting a WASM ini parameter to stop repeated scanning for new lvars - see MSFS have not made it easy for 3rd party developers. Everyone has different add-ons, different PC specs, different controllers, etc. FSUIPC should work pretty much out-of-the-box for most users. However, some initial configuration maybe needed If you have many add-ons and it takes MSFS more than a minute or two to arrive to the main menu state. But even then, FSUIPC will auto-tune itself - but you need to exit MSFS and restart once MSFS has arrived at the main menu AND FSUIPC has connected. Once toy have done the initial set-up/tuning, you shouldn't need to do this again. Auti-tuning will still monitor the connection, and if multiple connection attempts are detected, it will flag auto-tuning to be ran the next time FSUIPC is auto-started by MSFS. For this to work correctly, you need to make sure that you are still in the MSFS main menu when FSUIPC7 connects.

Yes - there weren'r that many updates between these versions, and nothing that could cause a CTD. The log file you attached ends after 80 seconds - so did P3D crash on start-up? Of so, that is usually a sign of a corrupt weather file. Try setting "NoWeatherAtAll=Yes" in the [General] section of the FSUIPC6.INI file to disable weather - if that fixes it, then you have a corrupt weather file which needs to be removed (see that FAQ entry I referenced). If thats not it, check the Windows Event viewer to see where the crash occurred, and maybe check the P3D forums for similar CTD reports.

Ok, although i don't know why you previously said 'The Workgroups are the same'! Once that is corrected, try again. If you still have issues, try setting the ServerName (or ServerIPAddr) and the Protocol - see the WideFS User guide, and also the WideFS Technical guide for troubleshooting network issues. Ok, but you need to sort this out - I can;t help with this... John

Please see the section Auto-tuning of initial start-up ini parameters in the Advanced User guide, and/or the following FAQ entry: No idea, Everyone suffers from CTDs at some point. It is up to you to determine the cause... John

Your log file shows that you didn't load an aircraft and get to the ready-to-fly state, and toy exited after 205 seconds... Apart from the first entry, the numbers are not in the correct position. Maybe the case also matters...try: John

Would be helpful if you attached your FSUIPC4.ini file, but it looks like its coming from an assignment (index 32, to button 8 on device 3) to a lua file, the one with index number 7.

Please respond to that questions - and all my questions. I cannot help if you do not respond. But with which axis? I can see entries for Ruder, Ailerons, Elevator and throttle. Lets try this again... First, choose one axis and let me know which. Then perform the same test, i.e. with logging for Axis Controls activated, just load your aircraft, and move the assigned axis through its full range and back again. Then exit FSUIPC/FSX, and save/copy/show me the FSUIPC4.log and FSUIPC4.ini files. Next, perform the second test. Do exactly the same as before, but change the reverse setting on the axis you are testing. Then exit anf show me/attach those two files again. i.e. two distinct tests, each with two files, trying one axis (and let ma know which!). This is FAR easier of you just look at the values logged in real-time...for example, this is what I see moving my throttle through its full range: i.e. the Param value foes from 0 to 16384 and back again. If I now go into calibration and reverse the axis: it now goes from 16384 to 0 and then back again. So the parameter values have been reversed. (Note the actual range depends on which axis control, but whatever the range, it should be reversed when the Rev checkbox is selected). John

Are you using the correct Active Sky dll (as_connect.dll) for the version you are using? Please check that first. Otherwise, weather CTDs are normally caused by a corrupt *.wx fille, so please check this - see If you still get crashes, please show me your FSUIPC6.log fo;e, as well as any crash reports for this in the Windows Event Viewer. Again, check that you are using the latest version of AS6 and have the correct AS dll installed (if using). I do not provide old and unsupported versions - I only move foreword. I doubt very much this has anything to do with the change from 6.2.0 to 6.2.1, but I have attached the 6.2.0 dll below for you to confirm. John FSUIPC6.dll

No, I cannot. What has this to do with FSUIPC? If your issue comes from an upgrade of the Sim-Avionics 777 flight model, why don't you raise this issue with them rather than here? I know nothing about the Sim-Avionics 777. If you have an issue with FSUIPC I can help, but I do not support 3rd party products/add-ons from other developers... If you have assignments in FSUIPC which aren't working, regardless of which aircraft you are using, then I need to see (attach not paste) your FSUIPC6.ini file (which contains your assignments), and also your FSUIPC6.log file, with appropriate logging activated (i.e. Buttons & Switches and Events (non-axis controls)) that shows what is happening. It could be something simple, such as an aircraft name not currently caught by a profile, or possibly a device GUID change that has made your current assignments obsolete. But I can't really comment without seeing your files. John