abennett

They're not absolutely working if the Fenix.GqlGateway is not showing up in Volume Mixer

I am not getting these announcements at all, because this Fenix.Gqlgateway does not appear in my Volume mixer in Windows.... Somehow I don't think it is starting when I run the Fenix. I have reinstalled twice, and everything else is working as normal but this seems not to. If anyone has any ideas it would be most appreciated. Thanks

Yeah I turned on the PA knob on the pedestal. Just get no sounds. I think somehow the Fenix.GqlGateway application (this is the application that actually plays the sounds, they don’t come from the sim) just isn’t playing sounds. I think those that have them working will see this in the windows volume mixer, it’s just not there for me.

Anybody else not getting the Cabin Announcements? Yes it’s enabled in the EFB, and yes I have turned on and up the PA knob. I don’t hear them in the cabin either… Many thanks.

Presuming with custom auto OLOD unchecked, this app will do nothing with OLOD and it will just be always at what I set it in the sim?

No CTDs from your app here either.

I was getting CTD with 737 every single flight in the beta without fail. I noticed that using the swapper thing left a rogue file lying around as well as the two dll files. I removed this, and was able to complete a flight with the PMDG. Maybe a coincidence, but I was getting a CTD every single flight, and then was able to complete one after removing. I might try one more this evening and see if it crashes again but it’s already gone 1am!

I would be interested to know if those experiencing CTDs have used the DLSS Swapper utility. I'm sure the majority won't have used it, but there may be some that have.

Yeah this bug is a pain. I get it whether using either of these apps or not, just always there. Asobo should really prioritise this. With the advent of FG so many are using DX12 now and it’s pretty bad that it results in this.

Sorry I was typing my reply, and this was posted whilst typing and I didn’t notice!! Thanks for the clarification. Of course not that you need anyone’s approval, but that seems to be great to have both options basically and sounds like something I’d be really happy with!

Thanks for this, I don’t see an option on the right for the TLOD changes on ground, so I’m assuming that leaving the TLOD Min on Ground/Landing, unchecked, in essence means that the TLOD will change on the ground…? So a bit of a nomenclature change? And leaving this unchecked also will mean the application will remain fully automatic and not target TLOD min at 1000ft AGL on descent etc?

Is it still possible to have how it was in the previous version or is that gone? It worked perfectly for me just having it change TLOD on the ground and setting a minimum and max TLOD and letting the app do the rest… I may have missed something/misunderstood, but this seems basically just like the Dynamic LOD rather than Auto. There you set what the TLOD should be at 0 AGL and then it slowly changed up to whatever you set it. When I load into the flight why would I want to be at my minimum TLOD if my FPS are above my target? I’m just reducing the visual quality when I have headspace for a higher TLOD. Similarly, why would I want to be at my minimum TLOD at 1000ft AGL when descending if I am getting way more FPS than my target? I’m just reducing visual quality for no reason again. In my opinion the previous auto version was perfect and simple. When you were below the FPS target it would reduce and when you were above it would increase, all within your desired max and min TLOD constraints. I really think this is so much better, than forcing me to a lower TLOD when I might not want it.

Just given it a whirl around ini KJFK in the Fenix. Working beautifully, not a single stutter and kept really nice visuals at 90fps!

Done a bit more testing, for me at least, with that latest version, with the TLOD changes on ground ticked, it is only on the ground that TLOD changes are made, and not when in the air. And when it is not ticked, no changes at all to TLOD are being made.

But you said here the app would work down to the TLOD minimum. Do you mean it would work down to the minimum only if you were below the target FPS? I wouldn't want it to work down to the minimum if I was above the target FPS... Also here, why is the TLOD staying at 340, I am well above the target FPS and consistently above it, but TLOD is stuck.

Hmm, I'm not sure it isn't best just as you had it before, to be able to set your target FPS and let the app do the work. I am happy to set a minimum of 50 TLOD, but if I am above my FPS target and therefore could be at TLOD 100, I would rather be at that. Seemingly with this, it would reduce me to 50 TLOD anyway. Then it has essentially just become the same as the other version where one set stuff by AGL. The great thing of this version was that you could set your minimum and maximum, but it would keep your TLOD as high as possible if above your frame rate...

Absolutely awesome as ever Reset. I can't stress enough how amazing you have been, both in what you have actually coded, and how you have dealt with the community. You have always been so clear in communicating what you are working on and why, you have been open to suggestions, discussed them and taken some of them on board. It's been a joy to be part of this little journey even just reading the posts and making a few replies. Thank you so much.

Yeah this is why I think it would be better if that app could always change the TLOD. I started the flight at 50 TLOD which is too low for my system but hey, I'd rather have it super smooth. It gradually increased to 400 on the way up with zero stutters and the sim looking great. I had set FPS target to 60. In descent and approach it just stayed at 400 the whole way as I was above 60 fps, but once I had landed, taxied over to the gate, etc., I was stuttering a fair bit, but because the TLOD can't change on the ground it was just stuck at 400, which was a bit too much for my system in the Fenix and a 3rd party airport to keep 60 fps at 400 TLOD.

You are doing just simply amazing work here, so many of us are so grateful. Once it is an option for this auto version to still change TLOD even when you are on the ground it will be just perfect for my use. A little question, is it possible to set max TLOD above 400, as you can in the usercfg, or is it limited to 400 as in the in-sim graphics options?

I think you set it the target you want inclusive of FG and the all sorts it all out in the background. It’s been working that way for me anyway.

Thanks @Cpt_Piett @Reset XPDR Might it be possible to have disabling TLOD changes when on the ground optional? Certainly in my case the TLOD I would like to use on the ground varies according to the amount of traffic around, as well as the airport and aircraft in question of course.

Can we use this auto edition without uninstalling the other version?

Thanks for taking on board my point about the frame gen and when msfs is not in focus. Looking forward to giving this a go

I guess I’ll just give it a try and see what happens. But it sounds like as it is, as soon as FG stops running because MSFS isn’t the focused application, it will reduce the LOD to try and get the same FPS as I was getting with FG running.

Yeah I think this would be better. For example I would probably set something like 30 native knowing I’ll then get 60 with FG. And then id still be happy with it at just 30 fps and keeping the LODs when I’m on another application. This would be better than setting a target of 60 with it taking FG into account and then every time I click on second monitor or a different program it chopping the LOD to have to get twice as many FPS to get the target of 60 without FG helping it. Hope that makes sense!