Jazz

It creates a hideous blur effect when looking about that reminds me of being slightly drunk. With TrackIR I find it intolerable. I have noticed that game developers like to use it to mask poor frame rates. I switch that off whenever possible.

Rogue Flight Sim Dev of the Year 🎉

There is not a checkbox in FPS Cap mode to enable TLOD Base + but I assume that it's on by default which is why it exhibits this behaviour of trying to push beyone my TLOD Base setting? If that is actually what is happening then yes, that is exactly what I'm asking for. When I load into the sim with FPS Cap mode I don't want it to try and push my TLOD above my TLOD Base setting until I have taken off and flown above my ALT TLOD Base setting. Once above that it's great to have it do its thing. Inversely, I want it to be back at my ALT TLOD Base setting as I pass back through ALT TLOD Base. With the way I currently have this set up it would mean that I remain at a TLOD Base of 100 until my ALT TLOD Base altitude of 500ft when it can start pushing up my TLOD should the correct conditions be met. And the same in reverse when landing. I'm perfectly fine with it doing it's seeking thing for a minute when I load up as long as it does what it needs to do and gets the info it needs and then sets and sticks to my TLOD Base until ALT TLOD Base altitude. My personal concern with that is, won't that mean that it will limit more how far it will push the TLOD limit when in flight? As an example, if it would push up to 300 TLOD in flight now then it may limit it to 250 or something after such a tweak? Or would this only affect when on the ground? Does Hr+ affect the entire range of flight from ground to cruise or is it aimed at something more specific? I just what to clarify. From my testing it seems to effect the entire range which is why I'm concerned with that. I suppose though, that if more restrictions were placed on that and it did limit more then one phase then I could increase the TLOD Top setting to compensate for reduced TLOD in cruise? Would that be a correct assumption?

The thing is, buddy, this is not the answer because it solves one issue and creates another. If I use Auto TLOD with the + additional unchecked then it will indeed force the TLOD Base below ALT TLOD Base and that is great but then it creates a new problem when flying and that is that I have to have my TLOD Top set so low that everything looks ugly all the time because I may fly over an area such as London or New york. That means that most of my flight looks poorer than it needs to in order to have the headroom to fly over London without it turning into a slide show. FPS Cap mode gets rid of this problem because it's changing things on the fly according to what it sees my FPS doing. That means I can set it up so that it looks great when it can and drops it when it has to such as high demand areas and this works very well for me generally speaking when flying. It really impresses me. The trouble is that it doesn't seem to work well on the ground at the start of the flight and as I have said. It consistantly tries to push this far too far and after a min of it working it out I'm left with a figure far too high and this goes on and on until it eventually realises that it's wrong and drops it to the TLOD Base level anyway. This can take forever and normally is still going on during the preflight, start up and taxi and the entire time I have erratic FPS which is an immersion killer. The Auto TLOD mode has the checkbox '+ additional TLOD with good performance conditions'. What I'm suggesting is that we have a similar checkbox in FPS Cap mode that allows us to force it to always use TLOD Base below ALT TLOD Base. I'm fine with it being erratic for a minute while it does what it does but it needs to settle at my TLOD Base and not try to push this until I get above the threshold of Alt TLOD Base when it can go about it's adjustments to maximise the visuals without dropping the frame rate. If we had that option in that mode it would be the perfect mode as far as I can see. Is there any technical reason that this cannot be achieved? I believe that @rjack1282 is seeing the same problem as me and has suggested this or something very similar as a way to remove the problem. Anyway, it's your baby and I hope you are taking what I'm saying in the way I am intending it and not as a criticism. I think it's a great piece of work and I'm just trying to help you make it better and make my flying experience better.

That wouldn't be a terrible idea. However, can't there be a setting to force it to stick to TLOD base when below the Alt TLOD base? I'm not sure why it needs to push this at all below there if the user doesn't want it to. If it must then can't it run whatever process it needs to run to establish the data it needs before reducing down to the TLOD base number I have set. The fact is, in my experience the initial setting is just wrong. Whatever it thinks I can run at the beginning is almost always wrong and instead of being at the 60 FPS I have set and capped it drops to 50-55 as soon as I look around. Then I must put up with this until it realises its wrong. It's just an immersion killer and seems totally unnecessary. If it stuck to my TLOD base number of 100 it would always stay at my 60FPS setting with headroom. Is there a technical reason why this can't be an option?

I'm interested in how resource hungry they are. I expect the TDS to be more resource hungry but because I have not tried it I can't test and compare the 2. FPS is primary concern number one for me in flight sim. When I do get it I will compare the two in exactly the same conditons to see how it affects performance but am interested to hear from anyone that has done this themselves.

Is there any way to get it to always use the TLOD base setting when below the AT TLOD Base number when using FPS Cap? I currently have a TLOD Base setting of 100 but when I start the sim up it runs it's checks and it decides that my system can run 200. Sometimes more, sometimes less. Trouble is, it can't and I have to put up with jerking and micro pauses until it decides that it really can't and then defaults down to the TLOD baase setting of 100. My AT TLOD Base setting is 500 so I would assume that below 500ft it should always default to TLOD 100. This works fine when I'm landing but for some reason, when I load into the sim it tries to push it's luck when it really shouldn't. What am I missing?

I have a fully paid up premium PMS but since the Navigraph integration on the TDS I have been considering migrating. I believe that I will sometime in the next month. I'm most interested in the performance differences between the two.

No thank you. It's far better for the app to inform you that there is an update than to have to go searching around websites.

Sure, although, I'm not sure where this is going......how about a game of snooker? Do you play snooker on Shoooters Pool? It's like the flight sim version of snooker.

A little gushing, perhaps. Appreciated, none-the-less. The praise isn't for me, though. It's for the author.

I have been playing with this app today and I must say its a game changer. Had no need for it with 2020 but with my rig 2024 has been disappointing with the performance. I have only flown in 2024 with the A2A comanche and the performance when on or near the ground has been borderline. Enough to convince me that airliners were not going to be an option for me and my rig in 2024. Anything less than 60 FPS is not acceptable to me, especially with track IR. However, after spending a few hours with this today, I have managed to massively increase my graphics and maintain that 60 fps at all times. It's no understatment to say that it's a game changer. Why Asobo have not implemented this into the sim is mindblowing to me. It's so obvious and effective as to be an open goal. The fact that a hobbyist has done this work by himself makes me raise an eyebrow as well as to force me to doth my cap to the man. Thank you, Reset XPDR. MS2024 is looking much more enjoyable thanks to your efforts. It really is appreciated.

Correct

I've seen it alright and once I did it was turned off. It's as janky as it gets and almost all the ships look like the Cutty Sark. Never seen so many tall sailing ships. All identicle. Normal modern ships were rare and when they made an appearance were parked in totally stupid places. Half onshore, half off. It was a total immersion killer. That said, there wasn't any where I would expect to see it such as one of the busiest shipping lanes in the world like the English Channel. But then I would find 5 massive identicle tall sailing ships crammed on top of one another in tiny harbours. I think it fair to say that it doesn't work and when it pretends to work it looks absurd.

14 pages an not one comment regarding performance. Unless I missed it, which is entirely possible. How do the FPS compare to the Fenix? Anyone able to just compare the two at the same airport and settings?