kaha

January 13

It happened again, here's the log file.

January 13

I did not iconify the window. However, I hadn't coded a wnd.close for the terminate event. I did that now and will see if it happens again.

In the screenshot you can see which "Restart" I did. Also I attached a screenshot of the event viewer.

I will

January 13

Sometimes FSUIPC just quits without obvious reasons. John, this is just to let you know, it doesn't happen frequently. Here's what I did this time:

- startup the sim (and automatically FSUIPC)

- load Icon A5 and do some assignments and checks in FSUIPC

- go back to Main Menu

- load Carenado C182RG

- do several starts and landings

- go back to main menu

- start another flight with the Carenado C182RG

- did a "Restart" when 5 minutes into the flight.

After the restart FSUIPC was not running anymore. I attached the logfile.

Karl

FSUIPC7_prev.log

January 10

Ok, thanks.

January 10

Yes, the function is there, I implemented it. But why does it report then that there are still open COMs?

January 10

John, from this I assume the script that still has open COMs is HIDSwitch.lua and all other scripts don't?

   610765 Killing aircraft lua Autos....
   610765 Lua threads being terminated:
   610765       7 = "C:\FSUIPC7\L_Teensy.lua"
   610781 Waiting for lua threads to process termination event....
   612968 LUA: "C:\FSUIPC7\L_Teensy.lua": killed
   612968       8 = "C:\FSUIPC7\L_Throttle.lua"
   612968 Waiting for lua threads to process termination event....
   615171 LUA: "C:\FSUIPC7\L_Throttle.lua": killed
   615171       9 = "C:\FSUIPC7\L_Mixture.lua"
   615171 Waiting for lua threads to process termination event....
   617359 LUA: "C:\FSUIPC7\L_Mixture.lua": killed
   617359       10 = "C:\FSUIPC7\L_Prop.lua"
   617359 Waiting for lua threads to process termination event....
   619546 LUA: "C:\FSUIPC7\L_Prop.lua": killed
   619546       11 = "C:\FSUIPC7\HIDSwitch.lua"
   619562 Waiting for lua threads to process termination event....
   619984 **** DevCom read/write threads still running - will exit anyway but could cause issues...
   620296 **** DevCom Read thread terminated
   620375 LUA.11: HidSwitch ends.......
   621765 LUA: "C:\FSUIPC7\HIDSwitch.lua": killed
   621765 Stopping WAPI (as MSFS in main menu)...
   621890   [INFO]: SimConnect_Close done

Would you need the .lua script?

FSUIPC7_log.zip

January 10

Thank you!

January 10

Ok, as soon as it happens again I will send the log.

January 10

Today I made two flights with the Shorts 330.On the second flight I got error messages:

"**** InputEvent received but not known: ....." in FSUIPC.log

and

"...Error sending Input Event 'LIGHTING_GLARESHIELD_1'" in the log of my lua script.

The errors about input events are in regard to interior lighting. I did not change anything in my script, the errors just came unexpected. I then exited to the Main Menu and made another flight with the Shorts. Everything worked again.

I attached FSUIPC.ini, FSUIPC.log and the log of my lua script.

Karl

Karl_InputEvent_errors.zip

January 9

Sometimes lua scripts that reside in the [AUTO] section of the .ini file keep running when the flight is ended and I go back to the Main Menu. This happens since recently only, maybe introduced with version 7.4?

Is there a reason for it?

January 3

Thank you, John.

January 3

Alos, I cannot get "Pan Heading" working on an axis.

January 3

On 1/2/2024 at 11:46 AM, John Dowson said:

You can use the external quickview presets:

For other external quickview controls, you would need to either define your own preset, or assign a key combination to the control in MSFS and then assign to this key combination in FSUIPC.

John

For some reason I struggle to get it working. For all 8 external quickviews I see the same camera view from behind the aircraft.

January 2

Thank you John. I'm on a flight right now but will use the new .exe then.

Karl

January 2

23 minutes ago, John Dowson said:

Could you try the attached version please:

FSUIPC7.exe 661.5 kB · 1 download

Sorry John, it works. I made a mistake with testing.

The .ini file is ok.

January 2

7 minutes ago, John Dowson said:

Could you try the attached version please:

FSUIPC7.exe 661.5 kB · 0 downloads

There's adifference to the old .exe: As long as FSUIPC is running the parameters show correctly in the Buttun Assignment window when changing to different switches. In the old version it showed zeros only. But after ending FSUIPC the .ini file stills is not updated, it still shows zeros.

January 2

3 minutes ago, John Dowson said:

I've just tried here and cannot reproduce this. Could you show me your FSUIPC7.ini files please and let me know which assignments are having this issue.

In [Buttons] its nr. 61 to 64. The corresponding .lua files are in the .zip together with the .log files which don't show an error.

Karl

Karl.zip

January 2

Thank you,

Karl

January 1

8 hours ago, ark1320 said:

I have just run into the same problem -- button Param values are reset to 0, but key assignment Param values are not, all with the same LuaToggle script. I tried turning off FSUIPC7 and editing the FSUIPC7.ini file directly (put in the Param values) and saving it. When FSUIPC7 restarted the Params had been reset back to 0.

Another user, using an exact copy of the same Lua script, and the same version of FSUIPC7 (7.4.1), does not have this problem.

Tried reinstalling FSUIPC7, didn't help.

Very strange.

Al

I also tried to edit the .ini file, but it getss reverted.

Karl

December 31, 2023

I cannot find controls for external quickviews for Button and Switch Assignments. Here's what I mean displayed in MSFSs control options.

THank you, Karl

December 28, 2023

27 minutes ago, LeoSchoonbroodt said:

Good for you, I stopped looking for a solution as i was flying another Heli.
Would you mind sharing your Code?
If you say you used a wrong parameter, i can only imagine 0 or 1 as parameter as it's an Inc and not a Set.

Test your input event with the button assignments and then take a look at the input events list from the log menu. Use this for the lua script.

In my example I use input event ELECTRICAL_Battery_1. Here is the lua script:

--[[

	Battery 1 for Caribou
	
	1 = on
	0 = off
	
]]

ipc.execInputEvent("ELECTRICAL_Battery_1", ipcPARAM)

Is your input event really named B:LIGHTING_PANEL_1_Inc? The input events I see in my aircraft don't start with B:

...
DHC4_ENGINE_Propeller_1<>
DHC4_ENGINE_Propeller_2<>
ELECTRICAL_Alternator_1<>
ELECTRICAL_Alternator_2<>
ELECTRICAL_Battery_1<;FLOAT64>
ENGINE_Throttle_1<;FLOAT64>
ENGINE_Magneto_1<>
...

December 28, 2023

Was my fault, works now. The reason it didn't work was that I used a wrong parameter.

December 25, 2023

On 12/24/2023 at 5:47 PM, LeoSchoonbroodt said:

...Still baffled why this ipc.execInputEvent("B:LIGHTING_PANEL_1_Inc", 1) doesn't work as the Input Event exists and i am using the syntax from the lua library.

I also cannot get it to work.

Karl

December 22, 2023

Also, sometimes the checkbox "Select for FS control" gets unchecked when looking at button assignments.

image.png.04cf75d7d2a87a5f5f7c2aeddb8a40b6.png

December 22, 2023

One strange thing: When assigning a lua script to a button the Parameter is not saved, it goes back to 0. Other lua scripts work. Renaming the script does not cure it. Not sure what's the reason. Here is a video (Dropbox link):

https://www.dropbox.com/scl/fi/aumkxe9n18ero2cl99eqo/FSUIPC.mp4?rlkey=oqxlh23b6fss1gglyvcto5uh3&dl=0

Anything I can do, John? Do you need any logs or anything else?

Thank you,

Karl

Profiles

Forums

Events

Gallery

Downloads

Posts posted by kaha

Important Information