kevinfirth

I'm sorry, I did try it and found it very useful, but stressful family situation meant I had little time to make any meaningful reports back. To your absolute credit you responded to issues and issued new versions faster than I was able to look at them sadly 🙁 perhaps it could be made as a hide/showable option in the future pls?

My app has updated to 0.5.2.0 However, I seem to have lost the threshold setting for spike detection? Was that removed please?

I don't have a problem seeing the aircraft at significant distances, but I do run OLOD at 1000

I concur with others that the landing gear issue has not noticeably improved. I'd be willing to demonstrate and work with the Devs if they want to make a serious attempt to tackle it. I was under the impression that @Kaiii3 and AIG had some dialog earlier this year but that doesn't seem to have resulted in any steps forward sadly. I just don't really understand how the engine culls individual sub parts seemingly by itself. I'd be happy to learn though. But if kaii and AIG can't figure out what of anything needs to be done e to models to make them work, I don't hold out much hope for divvy me!

Not far from staffs here yes. My postcode is DY11 5LU

To be fair, what's they've done is, I feel, mostly right. I'm able to run most things in most places with OLOD 1000, I'm only really noticing the undercarriage issue, nothing else. If they'd change that, bingo!

No problem! You can have it in a standard panel on the main screen, or on a second monitor, or networked through your phone or tablet. Use buttons when you want, speak when you want, it's inherently flexible. On the main screen or on a mobile device you will not lose focus and frame gen.

Anyone noticed if recent changes have impacted GAIST ships package visibility?

Not quite. While I happily concede there's a lot of info in there, I'm not seeing a great deal that can't be established from other sources within the sim. So my point I think still stands, in that it is possible to create exactly the knowledge based level of control you say is your objective, (and I agree!), but it doesn't HAVE to come exclusively from simbrief. You've chosen to go with that to begin with, and that's a perfectly valid choice, no quibbles. Don't overlook other sources of data though that might be slightly harder to access and make use of 🥰

Backing off the tests above showed that TLOD Base 70 was the absolute sweet spot, It started, and stayed at that level.. The trick appears to be to have settings that aim to achieve a 1% low at the fixed fps target level. Then switching to a less graphically intense scenario, but with those same settings.... TLOD base starts at 70, then rapidly increases to its x4 max, all super smooth. So, 3 things that come out of this for me. 1. Why wasn't AutoFPS upping TLOD in my first instance, when it had TLOD at 80 and spike detection hadn't activated? 2. When starting at TLOD Base max, why weren't those evident frame time issues detected as spikes? 3. For people like me, with powerful hardware, medium stress situations probably mean that we could go above Extra x4, would that be possible?

Yes this is already selected I've gone with TLOD Base Min 80 Extra x4 Start Max, with TLOD Top Max 1000 for settings That should a) produce a low enough base that I see no spikes in the heaviest possible scenario, b) give me up to TLOD 320 on the ground in medium stress situations and up to TLOD 1000 in the air and in low stress scenarios. All with OLOD 1000. Here's what happened: TLOD Base starting from low - zero spikes TLOD Base starting from high (320) - TLOD seems to be reduced partially for fps, but spike protection does not kick in, despite evident frame time issues. Wonder if this is because the spikes seem to be more prolonged and 'less spiky', more tabletop? So I backed down Extra to x2...to see the impact. As expected, TLOD Base started at 160 rather than 320. Spikes had a different profile, as again expected. Spike protection still didn't activate.

You're free to develop on whatever path you choose of course, but I'd question why you think simbrief is a higher 'source of truth'? It's just an automated pln import basically.... I'd agree your system has to understand intent, context, traffic, timing, sequencing, and the operational situation around the user, but simbrief doesn't actually give you any of that over a bare pln file....

Other ATC apps permit both freestanding flightplans OR Simbrief operations...

Here's a screenshot of the taxi-map app shown in the default MSFS2024 tablet. It shows: your aircraft position; stands/gates; taxiways; holding points (if specified) and the taxi-path ATC has given you. It is zoomable and draggable, and can be set to auto-centre and follow your aircraft location. This is a direct representation of the scenery that is installed on your PC. People with different sceneries may get allocated different taxi-paths as a result, because Vox reasons your path based on what's there, not what should be there in an ideal world. VoxATC calculates your taxi-path based on a complex set of inputs including aircraft weight, so you'll always be directed to taxi via a route that's suitable for your aircraft size. In development - the displayed taxi-route will be shown in different colours, dynamically updating to provide a clear visual indication of how much of that route you are actually cleared to follow at this time. - Holding points will be more clearly displayed in an appropriate visual colour scheme, so they can be quickly and easily distinguished

I've been able to reproduce the 'spiky' conditions in the same scenario as before. AutoFPS does detect these, and reduces TLOD, but when doing so it doesn't drop incrementally, but straight to TLOD Base Min - is that right? I've got it to TLOD 900, OLOD 1000, in drone cam view towards central london, 47Gb system RAM and 29 Gb of VRAM in use. All smooth, no stutters. From this I'd say the photogrammetry import code seems pretty solid by itself. Introduce an aircraft though and it goes to pot. So, I backed it down to TLOD 80, no stutters, AutoFPS doesn't up the TLOD to find the boundary?

Sure, not having settings so high will eliminate the problem, but also leaves performance on the table. I have a strong rig and could happily back off settings in particular scenarios so as to avoid this problem. However, that sidesteps the ugly fact that I want to be able to use my PCs strength as much as possible and there IS some underlying cyclical interference in the game engine! This was always more about being able to isolate identify and remediate that base issue than 'just getting an ok flight'. I'm massively grateful to you for your willingness to attack this, and glad you enjoyed it! Thankyou!

I will at the weekend thankyou...

@Reset XPDR Work in progress maybe, but you're still miles and miles ahead of M$/A$obo in terms of addressing this particular issue, not to mention just superb functionality and transparency that bodyslams the in-sim 'dynamic settings' into the ground! 🤣

@Dialex props to you for your professional replies. You can't satisfy everyone all the time especially when they don't understand, or dont want to understand, the complexities involved.

Before you posted this I'd re-assessed and changed settings to TLOD Min 70, extra x1.5 😁 Understand completely, its easier for edge cases users like me to just limit settings themselves, I get it! Understood, thanks for the info! Independent tests without AutoFPS show the same cyclic rythym. I experience the same, just was hoping to see AutoFPS manage the increase in TLOD and stop at the point the the 1hx cycle inherent in MSFS2024 becomes apparent. I also reported this at: 1hz stutter caused by photogrammetry and TLOD - Bug Reporting Hub / Install, Performance & Graphics - Microsoft Flight Simulator Forums

I prefer traffic myself, but I can envisage a use case where someone wanted to practice RT procedures without having to worry about interference from AI at first.

You'll get the opportunity to find out shortly! It is a different approach to BATC, and I think its fair to say it will do some things better, and some things not so better! Whether either app is a better overall experience for any particular use case is up to you. 🤔 But this is a thread about BATC, so it's not appropriate to make comparisons here....

@Reset XPDR I have an issue with AutoFPS, that I'm not sure whether its me or the app. This is in the Fenix at EGLL Inibuilds with pretty much max settings. This image shows AutoFPS active and some metrics through rivatuner. Notice the frame-time spikes and the 1% and 0.1% lows, which are linked. Table of results with varying TLOD/OLOD values is below. TLOD OLOD 1% low 0.1% low 50 50 64 60 80 50 48 40 80 200 46 43 150 50 16 15 300 200 18 18 What this means in practice is that higher TLOD values specifically result in these approx 1hz frame-time spikes. That correlates with the fps drops, and results in stutters in the sim, destroying smoothness. The depth of the spikes, and the drop in 1% and 0.1% lows, scales consistently up to a point with varying TLOD values. Now, AutoFPS doesn't seem to care about this, and monitors fps values overall, thinks everything is fine and ramps up the TLOD, causing the stutters. [This is not evident at other airports I've tested, presumably because the TLOD load at those locations isn't great enough to have resulted in whatever causes the 1Hz cycling and the consequent frame-time and stutter problem.] Further tests reveal a correlation with photogrammetry on/off as well. High photogrammetry locations exhibit a much lower TLOD threshold for appearance of the frametime-spikes and resultant stutters. Questions: 1. Is the 1hz cycle related to AutoFPS? I've eliminated pretty much every other possible causality with no joy. 2. Am I using AutoFPS wrong to be getting this result? Would different settings eliminate or reduce this problem? 3. If not, could AutoFPS target 1% lows rather than the headline fps? Or photogrammetry? Many thanks for your consideration. Cheers K

Short answer to all these is no, yes, yes. (We will add Directs to the development list) This is a great juncture to mention the difference in operating modes. If you look back up a few posts, you can see at the top right the prompt/expert mode indicator. VoxATC will work in two different modes, which, as Ronseal will testify, do what they say on the tin. 1. Prompted mode - VoxATC will give you prompts for what would be an appropriate pilot input for that phase of flight. You don't have to follow these, but if you deviate from them too far, things might get complex. The menu button will give you a context appropriate list of options which you can select, and Vox will give you a prompt for the appropriate comms. 2. Expert mode - For hardy (or should that be foolhardy? 🤣) pilots, you can 100% rawdog the ATC experience. VoxATC will give you no prompts whatsoever, and you will have to wing it to the best of your ability. Get it wrong? Sorry, there's no help button... In expert mode you can say whatever you like, whenever you like, so brush up on your CAP413 uk pilots please... If you expect to be doing a lot of the examples above, expert mode will probably suit you best.

Claude cannot at the moment access Google Earth itself to map holding points - I tried! What you can do is drop your self created kml files containing an airport's holding points created in Google Earth to me over at our discord and I can AI generate bespoke xml files for VoxATC with that 😁 I've created an automated tool that will generate them this evening.