2 hours ago, fakeflyer737 said:

Is anyone using this with trackIR and getting terrible input lag ? 

As I mentioned in my previous post, I get a tiny input lag when using TIR, I wouldn't say terrible but it's definitely noticeable and annoying. Apart from that annoyance, the app works perfectly! 

57 minutes ago, AnkH said:

@Cpt_Piett what does the MSFS engine do when using this RTSS frame limit? Does it render 30 FPS and doubles it to 60 due to FG? Because if I set a 30FPS limit in NVCP, MSFS will render only at 15FPS to end up with the 30FPS limit (as indicated when using Dev Mode FPS overlay). But your numbers indicate, that you also do not achieve 30FPS on heavy scenarios, dont you? "46 FG-FPS" tells me, that you only get 23FPS on KJFK with 100% AI traffic, correct? So what does your 30FPS limit then do? 

30 FPS is what I get in MSFS with FG. I actually get a bit more with 100% AIG traffic at KJFK, but I decided to lock at 30, which I should be able to get on average. 

With Lossless this is then doubled to 60. I could choose to go with x3 i.e. 90 FPS, but then I've set my monitor refresh rate to 60Hz (to get less screen tearing), and there's no point having higher FPS than that. 

The whole reason behind the FPS lock with RTSS is that it's much more smooth. The explanation is that the frame time consistency is much better - something that I talk about in the abovementioned video. Basically the frame time variation is much less - i.e. the difference between two consecutive frame times. 

TL;DR: I get the best result in terms of smoothness with FPS locked using RTSS in front edge sync. 

Edited June 14, 20241 yr by Cpt_Piett

53 minutes ago, Cpt_Piett said:

TL;DR: I get the best result in terms of smoothness with FPS locked using RTSS in front edge sync. 

Ok, maybe I have to try that once. Is it easy to setup? RTSS is anyway running already when I am using MSFS to have the FPS displayed correctly.

To make my question more precise: I now enabled front end sync in the RTSS settings, I put the value in the framelimit within the GUI but what number do I put in the scanline sync setting in the GUI? The same number as for the frame limit?

Edited June 14, 20241 yr by AnkH

Ok, now the sim totally freezes as soon as I move the drone some feet around. Switching window instantly brings it back, then it freezes again. Until the scaling of MSFS is lost. I need to stop playing around I guess... 

20 hours ago, Alti said:

i have to correct me here: its the first program on Steam, i own now, thats able to run without Steam client. just verified also now and wondering about that.

I was also surprised. Normally the SteamClient will pop up.

1 hour ago, AnkH said:

Ok, now the sim totally freezes as soon as I move the drone some feet around. Switching window instantly brings it back, then it freezes again. Until the scaling of MSFS is lost. I need to stop playing around I guess... 

That is exactly what I encounter with this app

6 minutes ago, guenseli said:

That is exactly what I encounter with this app

Add me to that list.

9 minutes ago, guenseli said:

That is exactly what I encounter with this app

Add me to that list.  I also lose my mouse pointer.  The only way I can get it back is to Alt-Tab out of MSFS and back in.  Then the vicious circle repeats itself. I m back to the 3xxx series FG mode and AutoFPS for now.  I've lost a days worth of flying trying to work through this.

Edited June 14, 20241 yr by fppilot

2 hours ago, Cpt_Piett said:

30 FPS is what I get in MSFS with FG. I actually get a bit more with 100% AIG traffic at KJFK, but I decided to lock at 30, which I should be able to get on average. 

With Lossless this is then doubled to 60. I could choose to go with x3 i.e. 90 FPS, but then I've set my monitor refresh rate to 60Hz (to get less screen tearing), and there's no point having higher FPS than that. 

The whole reason behind the FPS lock with RTSS is that it's much more smooth. The explanation is that the frame time consistency is much better - something that I talk about in the abovementioned video. Basically the frame time variation is much less - i.e. the difference between two consecutive frame times. 

TL;DR: I get the best result in terms of smoothness with FPS locked using RTSS in front edge sync. 

Which Nvidia driver version do you use? First time I installed lossless scaling I was using 555.99 and had lots of issues and also with the fps that is shown in RTSS, sounds like you have the same as you say RTSS shows 30 fps and dev counter too with FG on. Now that I have reverted back to 552.44 everything has been working far better.

I have an 4080. I set my monitor to 120Hz. FG in sim on. RTSS front edge sync to 60 fps. Lossless scaling set to x2. Using HDR special K.

This are the numbers shown: dev counter 30 fps, RTSS 60 fps, fps counter of Lossless left top corner shows 60/120. 

So 30 fps sim, FG makes it 60 and lossless makes it 120hz. Frame time graph linear and very smooth. The one only thing I dislike a bit is the increased input delay. I tried several other fps limit and vsync combinations, but it was nowhere as smooth comfrmed by the graph as with front edge sync RTSS.

I've not previously been inclined towards getting a 4090. Not been bothered by FPS per se, smoothness is what I want and my 3090Ti has been pretty smooth for me and given me around 40 fps in most situations. Same thing with the other various frame generation tools - I really don't want to tweak like that and I've not been convinced by all the pro and con debates I've seen here. But I've been following this thread and it sounded like a simple enough thing to test out so I did.

Actually very impressed, at least so far after just a few short flights. My large HDR monitor is set at a 60 limit (although it has Displayport and theoretically can do 120 it only seems to want to work via HDMI at 60), and so I've capped the sim at 30 and it all seems incredibly smooth. And I guess that as the sim itself is now only doing about 2/3 of what it's capable of natively (this is all at ultra plus and 4k btw) it should be able to maintain this relatively easily.

I will experiment some more, and try out things like JFK/EGLL plus AI full on, but I am likely to remain a convert, I suspect, even if it does violate my "leave it alone and don't tweak" rule.

It certainly gets my recommendation.

This is just bloomin amazing! Throughout loading and pushback with GSX, 50% FSLTL traffic, cloudy weather, everything on ultra and getting 45fps and beautifully smooth! This is the best money I have spent on simming in ther 15 years I've been flying! 😃

I want to give the tool a 2nd chance:
it gives me more frames, yes it did,
but extreme stuttering when paning around.
also i lost the mousepointer.
ant the last try, the screen freezes. i have to stop the LS-Tool to see my working MSFS again.
so still i am happy with my 60fix fps and did not run this tool with MSFS.

it works great for GTA, OMSI, TrainsimClassic, and also in F1-24
 

double post

 

Edited June 14, 20241 yr by Rocky_53

This is just bloomin amazing! Throughout loading and pushback with GSX, 50% FSLTL traffic, cloudy weather, everything on ultra and getting 45fps and beautifully smooth! This is the best money I have spent on simming in ther 15 years I've been flying! 😃 FYI, I switched off Gsync, set monitor refresh rate at 120hz, set Vsync and set frames at 50% in sim.

Edited June 14, 20241 yr by Rocky_53

3 hours ago, AnkH said:

Ok, maybe I have to try that once. Is it easy to setup? RTSS is anyway running already when I am using MSFS to have the FPS displayed correctly.

To make my question more precise: I now enabled front end sync in the RTSS settings, I put the value in the framelimit within the GUI but what number do I put in the scanline sync setting in the GUI? The same number as for the frame limit?

No need to do anything other than set the FPS, enable frame time limiter then front edge sync. No need to enter anything in scanline sync. 

1 hour ago, Eef said:

Which Nvidia driver version do you use?

I’m on 555.85. IslandSimPilot warned against updating to the latest, so I guess I’m waiting for the next one. 

Started a flight from Hamburg to Düsseldorf which is not as scenery-heavy as KJFK-KDCA. I locked FPS to 59, used x2 which gave me 118, had monitor refresh rate to 120Hz. Sim was much more responsive and snappier, almost no input lag and not much tearing. It probably helped that the mainthread was not about to die…

Everything was fine and dandy until I started experimenting at FL240, turned lossless on and off, and suddenly display went black. Had to reset the PC…

Edited June 14, 20241 yr by Cpt_Piett