What is up with the optimization of this software

ditto...no vsynch

 

Your displayed image will then be 2, 3, 4, etc. frames behind what's truly happening.

 

Nonsense and nothing can change the fact this is how it is and DD`s dream world can not change this.

60hz LCD = 60fps = 16,7 ms
100hz LCD = 100fps = 10 ms
120hz LCD = 120fps = 8,3 ms
144hz LCD = 144fps = 6,9 ms

LightBoost 100hz @ 100% = 100fps = 2,8 ms
LightBoost 120hz @ 100% = 120fps = 2,4 ms
LightBoost 100hz @ 50% = 100fps = 2,3 ms
LightBoost 120hz @ 50% = 120fps = 1,9 ms
LightBoost 100hz @ 10% = 60fps = 1,7 ms
LightBoost 120hz @ 10% = 60fps = 1,4 ms

You guys have Stockholm syndrome and only thing I can say to you is, dream on baby drean on..................

 

So with cheaper wheel, blurry high refresh high latency 60Hz monitor and ugly no HDR I can still manage 1:48.5 no tow Italy in F3 Eve.





Good to know !@!


lol

 

You claims happen only in DD`s dream world and no other place.

 

hehehe



Wake up Spin stop dreamin' get ya' hand off it. !


lool

 

and.......
The OP is nowhere to be seen.
Seeing he has no interest in the answers its possible it is a paid blog by a competior game.
Still it allowed a few to get into a nice argument.

 

OP was here, check some posts back, he said his performance improved after several tweaks..

But the saga continues anyway, this is how we roll!

 

Think of pre rendered frames as a buffer. Obviously they aren't "pre" rendered because the future can't be predicted. What actually happens is it holds on to the image until it is a few frames old before displays it. This way if the GPU gets behind a little it has 4 frames before it is noticeable to the end user. But this causes big input lag. One frame on a 60hz monitor lasts 16ms. So 4 frames is 64ms. So the physics engine is running 64ms ahead in what you see on your monitor. So the reactions you make on your wheel are always going to be 64ms behind. Turn on VSync and the delay goes up even more.

I highly suggest people set pre rendered frames to 1, disable VSync and use Max Framerate in the player file set to something reasonable so you not rendering frame rates your monitor physically can't even display and simply generating a bunch of heat and also generating a lot of extra CPU load. Do some laps back to back before and after the changes and you will see the difference in your driving. Another way to see the lag real fast is to turn on the animated wheel in the cockpit. Then quickly turn your wheel left and right. You will see the animated wheel is lagged behind if you have pre rendered frames set higher than 1 and VSync on.

 

??????????? What?

 

Noel has it right and yes, DD is in a "dream world".

 

Slightly away from the question but pertaining to other posts in here................

Just to get something clear in my own head.................

If the game can do 100 fps with current hardware/settings.
But it's coming out of a monitor that does 60hz.
Now I understand that I will see on my screen only 60fps.
So regardless of monitor hz the screen will still display my game doing 100fps,just with some frames missing.
So somewhere within that 1 second my screen loses 40 frames.

Is this where input lag comes from?
And I assume this is where sync comes into play?

Is the 'argument' about whether to sync to your monitors refresh rate or not to sync?

 

Whatever always ends in squabbles. lool

All I said is I do better PBs with 120 fps then 60 fps.

What I tell lies. ?

Why does that bother anyone ?

You ain't got enough to do.

 

This has cleared the air on input lag, vsync and pre rendered frames, thanks Noel

 

Input lag comes precisely from using vsync, which forces GPU to buffer some frames to always keep in sync with monitor refresh rate. The solution I, Noel and others recommend is to skip vsync and set up frame rate limit to 60 (or as high as your PC can handle) in player.JSON file. This doesn't cause as much input lag as vsync (can't explain why).

 

I wonder if ISI can license the tech that Oculus uses for its Rift and Gear VR software. The software that pre-renders the image and then only changes the pixels that actually need changing as it is about to be rendered on the screen. This allows faster rendering and lower input lag. The time between the input (Wheel turns or pedal pushes) and the photon coming out of the monitor is significantly lower then standard. I cant recall off-hand what the tech is called.

 

Excellent advice for people who are actually looking for help.

 

Well whatever I run high fps

I have high CPU/GPU heat .....nonsense

I have high CPU load .......nonsense

If I ran higher graphics settings for eye candy in turn lowering my average to 60fps, you think that will help heat and load........how ?

Obviously you never ran any Mad Onion "custom" benchtests in your life ( tell me about heat and load ) lol

I run 60Hz 1920x1080 fullscreen windowed borderless mode, my average fps would be around 90

30fps is wasted and I am killing my PC ..........if you say so.


On top of that I can't see how I could hotlap any better with my favourite car/track combos, I would be a alien. lol

 

I think this answer belongs to my problem. Seems related.

 

DD I think you quoted the wrong post?