EisernUnion

Its a 'S:' Var I cant really help as RNP will be a myth forever to me .. despite im coding, im so bad in logical, maths etc... so i takes me ages to understand them (after drawing them ;)' And yes im sorry the MY-SWAP is just another RNP Script inside AAO as i had no idea how to write it inside the streamdeck profile or combine it to the rest of the key-down event ... as i said im bad on this 😉 MY-SWAP: (L:S_PED_RMP1_XFER,·Number)·2·+·(>L:S_PED_RMP1_XFER,·Number) Here are all RNP Codes used (they work for FENIX, i have no idea if they work on other aircraft as i fly fenix only) - The custom var used inside the streamdeck plugin is called MyFreq ... - when hitting the numbers, will be pre-stored on each of the 4 (COM1, COM2 Active | COM1, COM2 STBY) Buttons - Once on of them is pushed ("on button-down") the respective Code will be executed Key-Down event on ... COM1 ACTIVE S: (L:MyFreq, String) stod 1000000 * (>K:COM_STBY_RADIO_SET_HZ) '' (>L:MyFreq, String) 1 (>K:FENIX_A3XX_MY-SWAP) Event Value: 1 COM1 STBY S: (L:MyFreq, String) stod 1000000 * (>K:COM_STBY_RADIO_SET_HZ) '' (>L:MyFreq, String) Event Value: 1 COM2 ACTIVE S: (L:MyFreq, String) stod 1000000 * (>K:COM2_RADIO_SET_HZ) '' (>L:MyFreq, String) Event Value: 1 COM2 STBY S: (L:MyFreq, String) stod 100 * s0 '5' (L:MyFreq, String) schr 6 == if{ l0 0.1 - s0 } l0 dec2b16 (>K:COM2_STBY_RADIO_SET) '' (>L:MyFreq, String) Event Value: 1 The Plugin Settings look like this The middle Buttons are used to display the ACTIVE (green) and STBY (orange) Freq on the respective COM. Key-Down event is swapping them SWAP COM1 S: (>K:FENIX_A3XX_MY-SWAP) SWAP COM2 K: COM2_RADIO_SWAP Here is a short clip when using it

Axis and Ohs has a StreamDeck Plugin for setting Frequencies ... it uses a own variable (to "collect" all numbers and thereafter send this custom variable as a freq to the respective COM by use of RPN..) im using this for years. And the idea crating a variable and send it to the COM might be an idea as well for your purpose Added how it looks (customized by myself) Example to Set COM1 Active Dial your Freq, e.g. 123.150 will be the Variable1 (String) On 'Button down' e.g. 'COM1 Active' this RPN will be executed [The current active COM1 will be SET to COM1 STBY (to switch back) and the Variable1 will be set as Active] (L:Variable1, String) stod 1000000 * (>K:COM_STBY_RADIO_SET_HZ) '' (>L:Variable1, String) 1 (>K:FENIX_A3XX_MY-SWAP)

Hi, im not sure if the title is correct, but the issue i came across today is the following.... LRM needs FSUIPC to work... i noticed that random flights were not logged or even is noticed that im flying.... after posting the issue in the respective forum i thought it might be an issue with a not well closed connection when i close msfs2024 after the first flight because it looked like only those flights were not logged that i made on a 2nd, 3rd Session on a day .... after posting i checked FSUIPC and the idea was correct but it seems that FSUPIC is not well connected on those follow-up sessions... after "disconnect" and "connect" the 2nd line of L-VARS became visible (was not there before) and also LRM instantly noticed my GPS Position..... (i disabled event logging already 😉 FSUIPC7_prev.log FSUIPC7.ini FSUIPC7.log

My bad ... just edited my post ... Problem solved by myself... sometimes creating a post helps to reflect the issue and the thing around it.... WHY and WHAT has caused the DetectToConnectDelayAuto Value to change to the default value of 30... have not edited the .ini for months nor deleted it .... this msfs2024 drives me crazy.

As i wanted to get the L-VARS to check something i just noticed, the WASM Menu is missing .... i have not changed anything, noithing updated so far ... its not there anymore... the last time i used it was 1 or 2 weeks ago .... Any suggestion ? The WASM Module is loaded

yes, mine has the 1st Nov .... will reinstall and hope 🙂

I have the same issue since updating to 7.4.18 .. already followed any vcruntime troubleshooting guide, also the remarks in the readme... ; windows updates are paused, so there is nothing other updated in between... FSUIPC has crashed 2 times today, 5 times yesterday.... the reinstall of the vcruntime was done yesterday ... i have no idea what raises up this issue..... And @John Dowson : Its not the error about a missing VCRUNTIME140_1.dll ... its a memory access error Name des fehlerhaften Moduls: VCRUNTIME140.dll, Version: 14.40.33816.0, Zeitstempel: 0x7d65c186 Ausnahmecode: 0xc0000005 Fehleroffset: 0x00000000000111fb ID des fehlerhaften Prozesses: 0x0x733C Startzeit der fehlerhaften Anwendung: 0x0x1DB315041059C78 Pfad der fehlerhaften Anwendung: C:\FSUIPC7\FSUIPC7.exe Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll Berichtskennung: 396e3f8e-a1ba-4be6-b4fb-f29d5766bc6a Vollständiger Name des fehlerhaften Pakets:

Today is one of those days wasm module wont keep alive .... third msfs restart and silently dies ... like the last time we discussed this issue... it was running fine the last days since 7/27 .... nothing changed, nothing installed etc.... 20240813_FSUIPC7_prev.log20240813_FSUIPC_WASM.logFSUIPC7.log20240813_FSUIPC7.log

Hi, dont know what is going one since a couple of versions .... The WASM Module is quite unstable and "dies" to easy .... 5 Min within MSFS and it quits its service.

The current working is 7.4.13a, will replace it with b

Just a quick note: Since i started to log with the file you provided .... no crash happend.... i stopped creating trace logs now... crazy ....

ok... first flight done so far no error ... but.. will see....

Will make this changes and continue logging.... yes, it stops anytime later ... i have no idea when, today it was on the second leg after the first leg EDDH-LOWS at some point on the second flight from LOWS-EGNT. After arriving in EGNT i restarted MSFS and now im flying Touch and go's at EGNT, this msfs session is running for 1:16 min now and still everything is still working. Im thinking about how to monitor the status of the wasm module to notice the silent die of it and try to figure out if something else had i did at this time and might had an impact on it

Same as yesterday evening.... as i wanted to turn on landing lights at FL100 stopped working .... wasm debugger flagged it again as "dirty" and is not working anymore. FSUIPC7.log

First thx for your support .... Second: Stopped working again... .... recognized it when i was about to switch off landing lights, TO lights and didnt respond after touchdown ... touchdown was at 20:06:48z ... last entry in wasm log 19:54:41z ... (nothing happend, nothing noticed while on final... just after landing as the buttons not responded anymore) FSUIPC7.log FSUIPC_WASM.log might be nothing, but dirty sounds not so good at all ?!