vgbaron

Sorry - let me clarify Gear lights work as expected On annunciator panel only Parking Brake is illuminated. Other lights are on the AP. I understand about support - if you say your lights are working, I'll check my system and also contact the script provider. Thanx John!

Hmm. Just to be sure, I disabled all addons in community, using the 7.2.5a version, downloaded the bravoleds.lua again. Gear and parking work. All AP lights work except for IAS and ALT. Only Parking Brake is lit in annunciator. if I disable lua script - no lights visible at all so I believe they are running. Vic

Can anyone confirm that after SU5 update both the hidBravobuttons and the bravoleds lua scripts do not work. Actually hidBravoleds doesn't work at all but bravoleds works partially - the ALT light on the AP doesn't light and only one item in annunciator panel is lit. It appears everything WORKS, just the lights not lit. Vic

Thanx John!

This has happened several times but not all the time. On normal shutdown of the sim, FSUIPC fails to unload from memory. The last line in the log indicates a LUA error . Any thoughts on how I may fix this? Thanx, Vic logs.zip

Will do Pete. At this point, it's only a 27 second increase in load time over "fastlaunch" so it's not a show stopper. Thanx for your help, and John's Vic

Well, I've narrowed it down with some success Replacing instdir and setting admin run on FSUIPC7, TIR and the msfs.bat file did not work. Setting flightsimulator.exe run as admin - same ctd so - restored and took ownership of exe.xml, FSUIPC7 and TIR - run as was set on both. Set run as on flightsimulator,exe started program from the MS Flightsimulator desktop shortcut - worked perfectly Tried it from the msfs.bat file with instdir intact - ctd set up a shortcut with just the fastlaunch cmdline entry - ctd run flightsim shortcut again - worked So it seems that I can not use the fastlaunch command in this instance. Tried the fastlaunch command with FSUIPC7 removed from exe.xml - worked just fine IF flightsimulator.exe was NOT set to run as admin.. I'll try some other combinations and see if I can narrow it down but running w/o the fastlaunch option works fine. Vic

I'll give that a shot tonight. Thanx John! Vic

I'll keep tinkering on and off but no joy so far. MSFS set as admin - shortly after initial screens - CTD - no entry in event viewer. Tried running it directly from the msfs icon - same. Didn't try it w/o FSUIPC entry in exe.xml file - will have time tomorrow. Adding TrackIR to exe.xml - wouldn't load with FSUIPC7.exe set as admin - it doesn't load with MSFS - no errors - just doesn't start FSUIPC on a lark, I added a trackir entry to the msfs.bat file - loads perfectly along with FSUIPC - only issue is I have to manually end it. in case I didn't mention it - it's a MS Store install to my F: drive not the default. I'll keep tinkering just on principle.. ]Vic

I'll also remove everything from the community folder in case some add on is affecting the loading. I looked at the event viewer but no relevant entries. I'll play a bit, if all else fails I'll throw TIR in the exe.xml file - probably the easiest solution. I'm just curious as to why the permissions conflict. Thanx for the help - Vic

ok, thanx John. I'll play around with it. If it's working for you then it's something in my configuration. I'll try to hunt it down. Vic

Hmmm - ok this is with 7.04 on w10 pro if I set run as admin in compatibility for FSUIPC7.EXE - msfs loads perfectly but FSUIPC7 is not loaded if I set flightsimulator.exe to run as admin in compatibility - there's a flash when FSUIPC7 tries to load and then sim CTD if I remove run as admin from both - FSUIPC7 starts and I get 740 error on TrackIR.

Thanx guys - I'll play around with it. I was unaware that 7.04 used the exe.xml. Vic

In my cfg file I have these two entries: Run1=CLOSE,"E:\FS-ATC-Chatter\FS-ATC-Chatter.exe" Run2=CLOSE,"E:\NaturalPoint\TrackIR5\TrackIR5.exe" I have both properties set to run as admin In 7.02 - all is good in 7.04 I get error 740 on the TrackIR entry. I run the fsuipc batch file as admin and do it the same all the time. Uninstalled 7.04 and switched back - no errors. Reinstalled 7.04 - error is back. Not the end of the world but is there something I am missing here? Thanx, Vic

Thanx Pete! I had forgotten about that, of course, that's what I did way back when. ANOTHER senior moment - they are coming faster and faster.......... Thanx again! Vic

Not a problem but curious. In V6 I had many profiles. They were in the Profiles folder with the a/c l;isting in the FSUIPC.INI file. Setting up profiles from scratch in v7 I see the profiles and the a/c list are contained within the INI file. Is this by design or have I forgotten about a setting to make the profilers external. Thanx, Vic

Tried again today setting up the Honeycomb yoke and all went well. Thanx Vic

Thanx Pete - In all my going back and forth I must have had FSUIPC running when I deleted the ini file. Vic

Turns out the stick was dying. All works well with the throttle alone but the stick created issues and now it will not even power up. Ran checks on USB ports - all ok - stick is dead. Rarely use the stick, mainly use the throttle as a switch panel so no big deal other than losing a day chasing down the problem. Sorry for the false alarm - FSUIPC 6 and 7 humming along nicely. Now I just need to reconfigure everything for the Alpha Yoke and in a month the Bravo quadrant. Thanx again Pete! sort of a related issue question - how do I start fresh with NO profiles and no assignments? I renamed the Profiles folder and deleted the fsuipc.ini file but when I started FSUIPC the profiles were restored. Any settings in the ini file were default. I just want to completely recreate the profiles for the new controllers. Vic

well, I know what's happening but not why. I looked closely at the GUID's and it seems the saitek x55 throttle and stick messes with the assignments. if I disconnect the x55 - all is assigned as expected, plug them in and it's a mash up. Same action in FSUIPC7 btw - The Alpha and the Saitek don't like to coexist on MY system. Has anyone reported a similar issue? Thanx, Vic

Just got HC Yoke and am starting install. Prior setup was CH Yoke, CH TQ, CH Rudders Saitek X55 (throttle & stick) all I did was swap out the CH Yoke for the Honeycomb. All controls are mapped thru FSUIPC. If the HC Yoke is connected, my rudders are not recognized. I've attached both INI files - something seems really strange with the joystick assignments. Using JoyID - all the assignments are correct but they don't match the ini file. Also I see TWO entries for Alpha controls. This is for P3DV5.1 - haven't tried FSUIPC7 yet with MSFS. edit: tried with and without honeycomb drivers - no change Any ideas? Thanx, Vic FSUIPC6.iniCHYOKE FSUIPC6.iniHCYOKE

Thanx John, that makes sense to me. Vic

Hi john - This question pertains to both FSUIPC6 and 7. Currently I have FSUIPC controlling all my hardware - CH Yoke, CH Throttle Quadrant, CH Rudders and Saitek X55. I have quite a few dedicated profiles that I use. This weekend I'll be receiving my Honeycomb Alpha Yoke ( Bravo TQ comes next month). What would be the easiest procedure to substitute the new Yoke in the profiles? I'm assuming I could create a basic profile for the yoke and cut/paste it in the various profiles or would I need to recreate the entire profile from scratch. Or, is there a more efficient way? Thanx, Vic

Don't get old John - sometimes you fail to see things that are right under your nose. All is well - apologies. Vic

I may have missed someone else reporting these but 1) I don't see either the name of the profile or the aircraft selected when assigning axes. 2) No visible save button after modifying profile. If I close FSUIPC and later reopen it with a new aircraft, when I select Profile Specific, I am asked to accept default assignments ( as usual) and then asked if I want to save the changes first. Does that mean they weren't saved upon exit? Had a few disconnects as others - trying the special version - so far so good. Overall FSUIPC seems to be working quite well Vic