jsmarko3

Yep, that fixed it. I moved the livery names to the right .ini file and everything started as it should. Thanks for the help with all this, I'm on my way now!

Oops, that one is 100% user error. No, FSUIPC didn't do that, I did. It created the profile files but left that in the ini and I said "why is this still here?" and moved it. That would probably explain why it seems like it forgets I have profiles at all. I'll fix that and give it a try. Sorry!

Hi John. Attached is another log file, as well as my adjusted INI file and the MD82 profile I'm working on. The profile is identical to the CRJ one with the exception of the livery name and the specific lua script called. Again, it doesn't seem like FSUIPC is reading the profile INIs with UseProfiles=Files. I am, however, starting FSUIPC after MSFS is running when testing this (mostly). It auto starts with the sim, however as I've been making changes I have been closing it and then restarting it. I do run it as an administrator; I need to run MSFS like that for several add-ons. I assume FSUIPC usually starts as an admin since the sim is launching it, but when I manually close and reopen it, I make sure to choose run as administrator for that reason. I just switched back to my old INI file (and renamed my Profiles folder, otherwise it keeps setting UseProfiles=Files), and it works like a charm, so something about reading profile files is funky for me. The one thing I will remember to do is to set up the profile files again BEFORE I start the sim, I'll let you know if that works so maybe the problem is with me restarting FSUIPC while everything is running. FSUIPC7.ini FSUIPC7.log MD82.ini

Hi John, I was indeed modifying the ini files while it was running, so that could be the cause. I'll give this new version a try and go back to using profiles and see what happens. Is this an installer, or a replacement for the exe?

Thanks for all the help John. I would have thought that using individual files would be the preferred method so as not to clutter up the main ini, but since I don't have much at this point it would be easy to change back over. If you're thinking if deprecating that functionality, I can do that going forward.

John, Sorry for taking up so much of your time with what should have been a simple issue. I believe I have finally solved it. It looks like there might be a problem with UseProfiles=Files, or maybe how I had them formatted. FSUIPC looks like it would create profiles as files ok, and maybe even update them, but it doesn't seem to want to load them when it starts fresh. I was noticing, based on my inability to read that offset I had set and opening the button binding window, that when I would start a fresh instance of FSUIPC it was not loading the CRJ profile. I say fresh instance because when I made changes to the script, ini file, whatever, I would close FSUIPC and reload it, unsure what it does and doesn't auto detect. I promise I wasn't trying to run it multiple times. I have put the few lines that were in the CRJ.ini file in the FSUIPC.ini file and removed UseProfiles=Files and not only can I monitor the offset, but now the simvar is being properly updated as well. Works like a charm and PACX is now registering the proper seatbelt sign values based on the seatbelt sign switch in the VC. I am attaching my files (I can include the log if you would like it, but it's currently still running while I tinker) in case they help debugging UseProfiles=Files, or the more likely case where it's a formatting issue on my end. FSUIPC7.ini CRJSeatbelts.lua CRJ.ini

I think I'm having profile issues for some reason. I've tried monitoring the offset I still have set in my CRJ profile, A000 for the CRJ seatbelt var, and I don't see that being updated despite seeing the LVar change when I repeatedly List LVars. I tried running the calculator code and monitoring offset 341D which was unaffected. PACX did change it when the boarding doors were closed, so that is the correct offset/variable. I have PACX change it automatically during critical portions of the flight until I figure this out, but just in case that was somehow interfering I turned it off. Still no effect. I did try rewriting the lua script using writeOffset instead of execCalcCode, but with the fact that I'm not sure my lua is running and/or having profile troubles, that didn't surprise me. EDIT: Alright, now suddenly the A000 offset for the CRJ seatbelt sign variable is reading appropriately, maybe now the lua script will run. I did have to reinstall the CRJ, maybe the profile was corrupted. EDIT2: Nope, not working again.

I'll give that a try and report back. Last night I did try dropping 1 (>A:CABIN SEATBELTS ALERT SWITCH,bool) into the Exec Calculator Code window under the WASM menu and that didn't have any effect, unsure if that means anything.

Hi John, I took a first crack at a lua script to do the job, but I don't think the lua script is actually running. I have Lua Plugins and Log Lua Separately checked in the Log menu, but I'm not seeing anything other than the standard FSUIPC log. I use the Profiles as Files option instead of having it all in the ini file, so when it didn't seem to work putting [Auto] in the CRJ.ini file I tried putting [Auto.CRJ] in the main ini file, but that didn't seem to work either. I have attached the four relevant files in the hopes that something is obvious to you that it isn't to me. FSUIPC7.log FSUIPC7.ini CRJ.ini CRJSeatbelts.lua

John, Apologies, I believe I might have worded something incorrectly. Just in case this changes the direction I need to go, I am not trying to set anything in the CRJ. I plan on using the switch in the virtual cockpit to toggle the seatbelts, but this does not update the simvar. PACX reads the simvar, and thus cannot tell when I have the seatbelt signs on or off, so I'm looking to read the CRJ switch value and then set the simvar based on that. I am uncertain if it is trying to read the variable or an offset (not that I really understand the difference tbh), the only nugget I have to go on so far is this: https://forums.tfdidesign.com/index.php?/topic/5716-seatbelt-state-question/ To my untrained eye, it looks like he's setting the variable and not an offset, but it wouldn't surprise me if I'm wrong. I assumed I would need to set an offset, as I have tried LVar manipulation in the past (I acknowledge these are different things so the results might not be the same) and not had any results until I started using offsets, so I went digging through the provided offsets and found you have already assigned it 0x341D. I did find the above referenced topic on the A320 parking brake and will read it, and also that there is an example lua for the spoofing function included with FSUIPC. Regarding the documentation, yes, I have the latest version installed, or at least no more than 2-3 weeks out. I was asking specifically about download locations for it since I was hoping to do some reading while away from my PC, but the download link here on the forums here is what is dated January 2021.

Thanks for the pointer John. Oh boy, that's quite the mouthful, but I haven't cracked the lua portion of the manual yet so I'll take a look at that. It's not the aircraft that I want to use the simvar, though, it's an external app called PACX that reads that var to determine the seatbelt sign status. Is there an updated version of the manual available for download anywhere? I'll be away from my PC with my FSUIPC installation for a while but I'd like to start reading up on lua, and the link here on the forums is from January of '21, at least the advanced user guide was.

I've found that a lot of third-party planes for MSFS don't set the standard seatbelt sign variable, so PACX doesn't pick up on it. I'm trying to fix this using FSUIPC as the bridge between the LVars and the simvar, but unfortunately, I'm in way over my head with all of this. I'd like to think I'm a technical guy, being an engineer and all, but I must be lacking some very basic context on how this all works under the hood because I'm not understanding most of the advanced user guide at all. Tthe main problem: I'd like to set CABIN SEATBELTS ALERT SWITCH, a bool, which looks to already have an offset of 0x341D, based on the position of the Aerosoft CRJ seatbelt sign switch. The LVar for that is ASCRJ_OVHD_SEAT_BELTS, and it has three possible values: 2 for On, 1 for Off, 0 for Auto. I have successfully mapped it to an offset (UB0xA000) and I can read it no problem. At this point, though, I'm not sure what my next step would be. I don't want to assign it to a button or an axis, I would like it to update the simvar whenever the LVar is updated. I have had some limited success with other aircraft mapping axes to offsets to control things like oil coolers, but I don't see a way to just update one var from another. I could try assigning ASCRJ_OVHD_SEAT_BELTS just to 0x341D and see what happens, but given that it has values of 0, 1, and 2 I don't expect it to work very well. I have also discovered, from perusing here, the Mobiflight events list that comes with FSUIPC, and there exists a set for the CRJ, including some code for the seatbelt sign: 1 (L:ASCRJ_OVHD_SEAT_BELTS, Number) 0 == if{ 1 (>L:ASCRJ_OVHD_SEAT_BELTS, Number) } els{ (L:ASCRJ_OVHD_SEAT_BELTS, Number) 1 == if{ 2 (>L:ASCRJ_OVHD_SEAT_BELTS, Number) } els{ (L:ASCRJ_OVHD_SEAT_BELTS, Number) 2 == if{ 0 (>L:ASCRJ_OVHD_SEAT_BELTS, Number) } I didn't find the advanced guide very helpful in either deciphering what this does, how to use it, or if events are something I would want to use for this purpose. Given all of that, what path do I want to go down in order to do this seemingly simple task, and where in the documentation should I start? Thanks for any and all pointers. -Joe Markowski