Discussion in 'Technical & Support' started by 4thworld, May 4, 2017.
What car is it?
Not the case.
I tried again yesterdays beta ( just edited this, I tried latest beta thinking it was a new beta that had been released today) and the problem persists. The only difference is that launcher video settings shows my GPU (yesterday it didn't) Only today I have found that 32 bit version is working. Yesterday I didn't try but I guess that it would have worked. One never knows with this cumulative versions... once the train has left you can only get next one.
However in 32 bit version full screen issue persists. Alt Tab not working and rF2 gains focus all the time. I can guess devs are working so hard in order to solve the legendary ATI issue that rF2 regains focus instantaneously when trying to switch to another program. Remember that the idea was to be able to return to rF2 after using another application. If I cannot use other applcations I wouln't suffer from Alt Tab Issue.
I finally made Full Screen "properly" work!!!!
As I mentioned I had to use 32 bit mode since 64 bit crashes.
Once ingame I selected Nvidia Graphics from the available options. If I pick my GPU from the list, it won't scale to full screen.
In order to make it work sometimes I have to first "deselect it" by selecting my GPU and selecting back Nvidia Graphics. Beware also that sometimes in this process the interaction with the screen buttons will be acting like if it was a different resolution. Restarting rF2 solves it.
Regarding FPS, quite disappointing. The cumulative term cannot be applied to FPS evolution.
Will try to get time to do benchs, but from a first experience, the DOF in track cameras are KILLING my performance, putting down the PP to low, solves all the performance problems, vsync 60 fps locked all the time, is there an option to disable only the DOF?
I put a video here yesterday, on PP low I was able even to do a video with 60fps all the time...
With PP on ultra, on cockpit i can have 70-80, but as soon as i change to trackside cameras, FPS goes to 20!
i7 4770k 4.5ghz
evga gtx 980
1080p all on max, PP low for now
AA level 5.
AA above 2 just kills FPS . Still only 50% of DX9 FPS when 8 in DX9 and 5 in DX11 for me. Not able to use any of the PP and when escaping to PIts the replay window is only at 13FPS so relay is stuttering very badly.
CPU: Intel Core i7 3770 @ 3.40GHz, Ivy Bridge 22nm Technology
RAM: 12,0GB Dual-Channel DDR3 @ 798MHz (11-11-11-28)
Motherboard: MEDION H77H2-EM
Graphics: NV Surround (5760x1080@60Hz), NVIDIA GeForce GTX 970 (MSI), multiview enabled, frames capped at 60
my experience with the latest build. Tested in multiple race starts at Malaysia in the updated C6R and 12 AI, starting last:
- with the fullscreen issue fixed, there is less input lag, however still noticably more input lag than with dx9. I checked back-to-back numerous times.
- an improvement of GPU load/frames, yet still severe stutters when the GPU/CPU load is only around 30-60%. I hope the attached logs show this.
a huge thanks to Studio 397 for all of their hard work!
Humm, it seems we didn't get rid of those past chronical rF2 issues/crashes/errors yet, which is alarming...
With last patch performance is a bit better, but still get stutters here and there and Suzuka is still the worst track for stuttering...
I see that you are using a Logitech G27 Wheel, I have the same setup and can't seem to get the ffb to work correctly, would you be so kind as to let me know what settings you are using in the Logitech Profiler?
Worst performance with the latest build.
Resolution: 1920 * 1080, All to Max, 35 FOV
AA: Level 8 in DX9, Level 5 in DX11 (no PP)
Conditions: 1 full lap from the finish line to the finish line.
Build ID: 1818133
Aggressive Threading OFF
Please could someone answer above question, I have a feeling it's at the heart of my performance issues and maybe for others too.
It has nothing to do with it. Information shown is wrong but that does not affect performance at all.
k, it's just weird that I was getting 75fps, and then next time i loaded it, couldn't get over 40.
I've already posted this using the contact support form, but here is the condensed version:
Windows 10 64bit / Intel XEON E3-1245 / 16GB / Ancient underpowered AMD R270 2GB / SSD / Ancient Logitech Momo Black
Normally I can run rf2 using non-multi view to my triple 1080p monitors, with vsync using medium/level2aa/2x Anisotropic or can cap at 120fps in DX9 with medium/low settings. I typically run Assetto at similar settings, and iRacing I can run 4x/4x using DX11.
My test is to use DX11 updated content, and I didn't want AI or any other factors to be an issue.
1 USF2000 Car, Silverstone GT, Sunny, 0 AI
Initially I was getting 50% or so frame rate compared with the same settings on DX9
2017-05-04 15:01:20 - rFactor2 DX9
Frames: 7032 - Time: 30000ms - Avg: 234.400 - Min: 225 - Max: 246
2017-05-04 15:22:35 - rFactor2 DX11
Frames: 3456 - Time: 30000ms - Avg: 115.200 - Min: 102 - Max: 130
There was an increase in fps on 5/8
2017-05-08 13:09:53 - rFactor2
Frames: 4347 - Time: 30000ms - Avg: 144.900 - Min: 135 - Max: 162
and a tiny increase in fps 5/12
2017-05-12 10:51:19 - rFactor2
Frames: 4415 - Time: 30000ms - Avg: 147.167 - Min: 135 - Max: 164
So now I can come close to getting minimal settings to run, but especially if I try to use my tiples even the lowest usable settings will be only at 60fps or so.
GPU usage in cockpit was just 68% before a recent build, now its at 78%, but it did not increase fps. Memory usage is 1750 MB dedicated memory.
I am really proud that the devs have increased the fps this much. It will take a bit more to make it at DX9 levels.
The issue of Suzuka is that it uses a lot of VRAM, more than all ISI/S397 tracks, over 2 GB even at 1080p. So unless you have a 4 GB GPU, it's probably lack of VRAM, especially since the DX11 build uses slightly more VRAM than DX9.
Tonight's run I7 4770 24ram Sapphire rx480 8ram triples (5900x1080) eyefinity only. All graphics settings at max, but post set to None. DX9 about 108 FPS. DX11 about 98. USF2000 NOLA. I've noted this before but the log collector turns itself off after a minute or so.
That's the way it works. After pressing Left Shift + Space it starts recording until it gets sufficient recalled data. The higher the fps the less it takes to build the file.
It would be useful that when pressing Ctrl+F it would not only prompt how to start recording but instead of just saying "Recording", it would say "Recording. Wait until log is build. You can find logs under userdata/log"
Latest result (Build: 1818133, 13 May 2017)
I have i7 6700, 16GB RAM, AMD RX480 8gb (single monitor), No AI.
DX11 with partial cloud - between 105-134 Frames
DX11 with no Cloud - between 108-140 frames
DX11 with Overcast & Storm - between 85-118 Frames
***Was getting some stuttering when there was lightning (framerates on storm only dropped below 95 when
there was a lightning flash***
*** Also, the rain 'disappears' for about 30-40 metres in Turn 1. That would be track related, though***
Previous results (earliest result first)..
Silverstone in the GT500 (same settings):
DX9 - between 98-126 frames
DX11 - between 37-63 frames
DX11 with partial cloud - between 58-73 Frames (an improvement, but still would be slower in online multiplayer or with AI)
DX11 with no Cloud - between 96-123 frames (comparable to DX9)
DX11 with partial cloud - between 101-133 Frames (Still better than DX9 no cloud)
DX11 with no Cloud - between 107-139 frames (Better than DX9).
DX11 with partial cloud - between 103-131 Frames
DX11 with no Cloud - between 107-138 frames
My Results using Max AA DX 9 & DX 11 , Nissan GT500 and Latest Version of Silverstone 1.6
Some improvement since last build and with this updated version of the track.
Obbzy my latest update shows build to be May 12 after doing an update today am I missing the May 13 build somewhere?
Frames 9085 Time (ms) 60000 Min 126 Max 171 Avg 151
Frames 7189 Time (ms) 60000 Min 97 Max 139 Avg 119
Separate names with a comma.