26 minutes ago, John Fields said:

Hi, everyone,

I've downloaded the 0.4.4.3-test3, but it seems it's the previous version test2 instead.

Greetings

 

 

 

Hi, OK. It now seems to be working, sort of, for me. I see LSFG x2 shown all the time whether I have it turned on or off. I will test some more.

Edited January 11, 20251 yr by Harrier77

I know this is not the intended operation of MSFS 2024 with this app, but I have the following observation. I started the sim with the app running, and the sim setting is FG on. Lossless scaling is running but not activated. When loaded into the sim the app reports LSFG 2X rather than FG. The FPS value looks to be correct for FG. Just for fun I then started LSFG on top of the sim's FG and the app reported FPS drops to a no FG value, but the actual FPS is much higher. Here are the numbers: with FG running FPS 82, with FG+LSFG x2 FPS 52 but lossless scaling is showing FPS 52/102. This seems to show that when lossless scaling is started it uses the pre FG FPS for it's multiple ignoring FG in the sim which would seem to be correct; however, the app only reports the sim non FG FPS not the lossless scaling FPS.

I then set the sim for FG off, but with lossless scaling running but not activated. The app reports the FG FPS rather than the non FG FPS? The app also reports LSFG 2X even though it is not running. When I activate LSFG the FPS changes again now showing correct values. Here are the numbers: before activating LSFG FPS 82 (native FG is off so the FPS should be nearer 40), after activating LSFG I see 38/76.

It looks like the app is confused about what is controlling the FPS: no FG, native FG, LSFG, or native FG + LSFG. I am probably asking way too much from the app, but I am getting the best results by combining native FG with LSFG x2; it's just that the app does not report the FPS correctly in this instance therefore it's no good running it. Anyway, I hope this all makes sense.

 

1 hour ago, John Fields said:

Hi, everyone,

I've downloaded the 0.4.4.3-test3, but it seems it's the previous version test2 instead.

Greetings

 

 

 

Sorry, I stated the wrong test version here. It is test2, not test3, and is the first time test 2 has been posted.

9 minutes ago, Harrier77 said:

I know this is not the intended operation of MSFS 2024 with this app, but I have the following observation. I started the sim with the app running, and the sim setting is FG on. Lossless scaling is running but not activated. When loaded into the sim the app reports LSFG 2X rather than FG. The FPS value looks to be correct for FG. Just for fun I then started LSFG on top of the sim's FG and the app reported FPS drops to a no FG value, but the actual FPS is much higher. Here are the numbers: with FG running FPS 82, with FG+LSFG x2 FPS 52 but lossless scaling is showing FPS 52/102. This seems to show that when lossless scaling is started it uses the pre FG FPS for it's multiple ignoring FG in the sim which would seem to be correct; however, the app only reports the sim non FG FPS not the lossless scaling FPS.

I then set the sim for FG off, but with lossless scaling running but not activated. The app reports the FG FPS rather than the non FG FPS? The app also reports LSFG 2X even though it is not running. When I activate LSFG the FPS changes again now showing correct values. Here are the numbers: before activating LSFG FPS 82 (native FG is off so the FPS should be nearer 40), after activating LSFG I see 38/76.

It looks like the app is confused about what is controlling the FPS: no FG, native FG, LSFG, or native FG + LSFG. I am probably asking way too much from the app, but I am getting the best results by combining native FG with LSFG x2; it's just that the app does not report the FPS correctly in this instance therefore it's no good running it. Anyway, I hope this all makes sense.

 

Yes you are asking too much of the app. The app does not account for more than one flavour of FG running at the same time.  LSFG is considered to be running even if you haven't activated it as there is no way to detect it is actually running.

Run either in-game FG or LSFG but not both at the same time and the app will detect things correctly. If you do choose to run multiple flavours of FG, the app will still work but you will need to work out how that affects your target FPS versus displayed FPS by yourself and adjust accordingly.

7 minutes ago, Reset XPDR said:

Yes you are asking too much of the app. The app does not account for more than one flavour of FG running at the same time.  LSFG is considered to be running even if you haven't activated it as there is no way to detect it is actually running.

Run either in-game FG or LSFG but not both at the same time and the app will detect things correctly. If you do choose to run multiple flavours of FG, the app will still work but you will need to work out how that affects your target FPS versus displayed FPS by yourself and adjust accordingly.

Thank you, I thought so. I was just interested in seeing the results comparing native FG, LSFG, and both. From my limited tests so far I get the best results with both. I have adjusted the target FPS to a reasonable value and the app is working well.

0.4.4.3-test2 working great so far.  I've been trying out the new FPS Cap feature and it seems to be working as advertised.  My only issue with it is that it forces TLOD Base+.  I have the headroom with my FPS Cap to reach my max TLOD setting; however, on the ground I always have gotten panning stutters if TLOD was over about 80 or so.  Since the app is forcing TLOD to 200 on the ground, the panning stutters are pretty bad (this is the main reason this app has been the best thing since sliced bread for me).

My only request with the new feature would be to not force TLOD+ on the ground.  Otherwise, it is the exact feature I had been looking for.  Thanks.

31 minutes ago, rjack1282 said:

Since the app is forcing TLOD to 200 on the ground, the panning stutters are pretty bad (this is the main reason this app has been the best thing since sliced bread for me).

You could try expert settings and set TLOD base as you wish. 

31 minutes ago, rjack1282 said:

0.4.4.3-test2 working great so far.  I've been trying out the new FPS Cap feature and it seems to be working as advertised.  My only issue with it is that it forces TLOD Base+.  I have the headroom with my FPS Cap to reach my max TLOD setting; however, on the ground I always have gotten panning stutters if TLOD was over about 80 or so.  Since the app is forcing TLOD to 200 on the ground, the panning stutters are pretty bad (this is the main reason this app has been the best thing since sliced bread for me).

My only request with the new feature would be to not force TLOD+ on the ground.  Otherwise, it is the exact feature I had been looking for.  Thanks.

+1 Here. Tested it and I also asked myself, is TLOD Base + intended to be forec "on"? I can´t eliminate the "check"

Just now, Cpt_Piett said:

You could try expert settings and set TLOD base as you wish. 

Yes. But the app will force due the cecked option "TLOD Base +" to set higher ground TLOD as TLOD Base. This way it is forced you are not able to have the TLOD Base value as at base (GND). 

10 minutes ago, mpo910 said:

+1 Here. Tested it and I also asked myself, is TLOD Base + intended to be forec "on"? I can´t eliminate the "check"

Ok I see. Currently testing the latest version. I think the forced TLOD Base + is intended. Release notes:

Quote

Added FPS Cap TLOD automation method, which is just a special case of Auto TLOD with TLOD Base + enabled and TLOD Top + disabled that is suited to FPS caps and is now more clearly identified.

 

I set TLOD Base to 50 and the app didn't force it higher. Am I misunderstanding something here?

If I use LS with autofps it is detected. But instead of 2x it shows LS 1x

3 minutes ago, flieger28 said:

If I use LS with autofps it is detected. But instead of 2x it shows LS 1x

test 2 fixes this

11 minutes ago, Cpt_Piett said:

I set TLOD Base to 50 and the app didn't force it higher. Am I misunderstanding something here?

My guess is the app senses that you have no headroom left to increase LOD with TLOD+

Edited January 11, 20251 yr by rjack1282

I started another session on the ground. TLOD Base set to 50 and the app adjusts it up to 350. This didn't happen on approach though. 

2 minutes ago, rjack1282 said:

My guess is the app senses that you have no headroom left to increase LOD with TLOD+

I had enough headroom for at least TLOD 200. 

Edited January 11, 20251 yr by Cpt_Piett