Adamski_NZ

Phew!! This is turning out to be a 1,000pp non-fiction novel LOL! Apologies to all our forum guests! I really appreciate the time you've put in to explaining how things actually work (as opposed to me guessing how they might work) ;). Now that I have some very clear instructions I will try and stay out of your hair (!!). :)))

OK - thanks for your detailed instructions. Things are set up as in your screenshots (and AutoFPS is set to open/close with MSFS). I think I see what the problem is: the Custom Path. I think I need to set that path to my custom location for only the AutoFPS addon. I expected that the updater would simply follow the symlink - but it doesn't. As it stands, that last screenshot implies that it should be set to your regular Community folder - the path to which is stored correctly I've just re-run the installer, setting the custom location to my externally linked location - and got the prompt about making sure its enabled via Linker (and then the prompt about removing the old symlink) - which is good. Maybe it's just semantics/terminology, but I find it a little confusing: the external location for the widget is not my Community folder. OK ... I'm still not getting it right (arrrrgh)! After setting the custom folder, I re-ran the installer - with the widget enabled via Linker. I got the same warnings as before - but the existing symlink was deleted, so I had to recreate/re-enable it via Linker. Why can't the installer simply follow the existing symlink to the custom folder (and not delete it)? This is how I think it should work (tell me if I'm wrong!!): Path set in AutoFPS to the normal/regular Community folder. 1) No symlink or Widget found, so create it there (in the Community folder). 2) Existing symlink found: follow the link and update the old widget files (in the external/non-community folder). I hope I've explained that properly!!! ;)

AutoFPS Widget update: Forgive me if I'm simply doing things wrong. I can't seem to get the hang of auto-updating the widget (main app is absolutely fine). 1) Because of [the understandable] file-locking when I update in-sim, the widget is set to update on the next AutoFPS launch ... except it doesn't. 2) If I grab the latest from GitHub, the installer/updater doesn't follow the symlink to the external folder (I link to it with Addons Linker). Instead, it deletes the symlink and places the widget in my Community folder. I then have to move it to its usual (external) location. What am I doing wrong? As xzever (above) has said ... I rarely use the widget (as the main app works perfectly), but I'm intrigued all the same. What's the correct procedure if you're using Linker (for manual and in-sim updates)? It's trivial, really, but it does give me another opportunity to thank you again for such an indispensable addon :)

Wow - that's quite a find! Thanks for the heads-up :)

Wow! There really are some clever people out there!!! I already had ReShade, so this fix was easy to add: it works!!

Me too. Surprisingly little frame rate hit - even when run with Airside at a relatively busy airport. The only downside is that you now want to see FSLTL models have door animations ... something that probably would have a drastic FPS hit.

Despite the complexity of having just too many addons going at once, I'm really enjoying the activity that ApronLife gives us. I often do the complete GSX PAX/payload load in real time so just sit back and watch. If you have [the excellent] AutoFPS, you can temporarily tweak the LOD values while you watch the show, bringing them back to something more acceptable when you want to taxi & take-off.

It's all getting a little complicated. I have GSX Pro, BATC, FSHud and now "Airside" ... all of which integrate with AI in some way (though I only use FSLTL for the aircraft models). To add to all that, payware airports seem to vary a lot with their GSX ground track/paths. Some freeware GSX profiles help to iron some of these out, but it's become a bit of a nightmare.

I really like it - but I had to dial back the settings a fair bit. Not because of a frame rate hit, but because multiple vehicles were crashing through each other and running down ground crew all over the place LOL! While GSX is great, apps like ApronLife really highlight badly laid out vehicle/object paths in the airport you're using.

Hey! I'm the kind of guy that likes the Trislander, the Wilga ... and [drum roll] the Airtruk!! Beat that if you can!

All good - many thanks for the reassurance! :)

Just a thought ... my last update occurred when AutoFPS started automatically on MSFS launch. I've always understood that it's not a great idea to enable/disable addons with MSFS running. I have the widget symlinked by Addons Linker. a) Does updating the widget whilst active in MSFS cause any issues? b) Does it [even] update to the new version if the existing/old version is in use (files being locked etc.)? I've not experienced any problems, but just wondering ;)

We're going for a World Record!! Seriously though ... I'm not sure what your problem is. Tremendous feedback from the developer of one of the best MSFS tools out there - with loads of helpful submissions from the users. What more would you want?

Fantastic stuff! I just wish your expertise could be mirrored by the Asobo devs: the whole top menu toolbar thing is a GUI disaster.

I'm wondering if this may be something that could be achieved with FSUIPC. It can do some pretty clever stuff (but don't ask me how!). I Googled "open close any window with FSUIPC" ... You can open and close specific in-simulator user interface windows or panels in flight simulators using FSUIPC by assigning a button or key press to the PANEL ID SET control with a specific window/panel ID parameter, or by utilizing a FSUIPC Mouse Macro or Lua script. [1, 2, 3] Also - I've seen some addons being integrated with the EFB - which is always available via the TAB key. That might be a more elegant solution, but might be hard to code <??>.

Excellent - many thanks! UPDATE: RC3 installed with no problems. Also: I never had the font size cutoff thing, but just to say my window remains perfect with RC3 :)

Is there any way (when in-Sim or in the app) to see the current version of the widget - or if it needs updating?

Pleased to report RC2 works well on my system! The widget indicator works as advertised. Wow - this addon has come a long way :)

https://flightsim.to/addon/115328/taxi-cam-msfs-2024-pfd-taxi-cameras Nice idea, but very buggy (read the comments above). I won't even dare test it at this stage.

I occasionally get problems with Flowpro - either starting incorrectly (logo always visible @ top right) or not working at all. Usually, this is because I'm messing about with freeware mods. The fix (for me) is to simply re-run the FlowPro installer. Only takes seconds. Check you have the latest version while you're at it.

Thanks for the info :) ... is it working OK for you? Many people are reporting frequent CTDs and/or having to go through the whole tweak process all over again.

Cleaned up ... and installed Test8 from the Github page. The widget was active (via Linker) ... result ... PERFECT!!!!

Very interesting ... but I'd like to have clear instructions on how to remove all the tweaks cleanly in case it doesn't work.

Wow - we've sure added a layer of complexity! Yes - I follow what you're saying ... makes sense. I just had a repeat of the scenario with Test7, so repeated what I did with Test6. I wonder whether the widget should be made into a separate installer (that can only be run when MSFS is not running) <?>. BTW: For Test7, I had the widget enabled in Linker (symlink in Community) and the Test7 installer wiped the existing symlink, then created the new files in Community (which I then had to move). Maybe the contents of the symlinked folder should be cleared, rather than deleting the whole folder <?>. Hope this helps.

I have a couple of things to report on my update to 0.5.40-test6 from the previous (test) version: 1) The update tried to execute when AutoFPS fired up during MSFS startup (as per usual), then failed with some kind of error message - but I do remember it mentioning I should not have had MSFS running. So I tried re-running AutoFPS with MSFS closed: it fired up, but would not update. So I went to the Github page and downloaded test6 and updated manually. That worked fine :) 2) I generally try to keep my Community folder as clean as I can, so I move the widget to my utilities folder and link to it using Addons Linker. The AutoFPS installer seems not to follow the symlink that the Linker creates - and doesn't update the widget in its external location. I just delete the old widget files (and the symlink) and reinstall via the downloaded EXE. I'll see what happens with the next experimental test/update and make a note of what happens. Many thanks!