Resource icon

Tracks Spa Francorchamps (2 Seasons, DRS) 1.20

Login or Register an account to download this content
Hey Patrick, i found a little bug. The car in pitlane is always shadowed, but there is no shadow on track. Can you reproduce that ?

Tested with V10 at 2.00 PM. When i drive at 4.30 PM its ok...
 
Last edited:
I only now did a couple of laps in the FReiza and i find the tarmac here doesn't interact with the tires in exactly the same way as on default tracks. Namely, the sense of road contact/resistance when turning is not the same as on default tracks. The car is more sensitive to my steering in puts, the steering is faster and lighter and there is not the same amount of progression. It feels as though i'm using a higher steering lock/sensitivity, but i'm not.

Due to this i find the quality of driving experience is not as good as on default tracks imo.
Overall grip is ok, just the grip progression when turning is not the best. The sense of tire ''bite'' and traction is missing compared to default tracks. Notice the same ''issue'' on Eastern Creek as well.

What do you think, Patrick ? Anyone else feels the same about it ?
 
Hm, did some more testing now and it doesn't feel that much different, really. Don't know what it was...
Something didn't load up properly or smth. Or just because i don't drive Reiza a lot..
In any case, when it drives like it does today, it's fine. :D
 
This track ran well in my league race yesterday. Except with the tire compound limitations it made it so we could not change to medium tires in the Formula V10 when pitting. Just sharing info so you guys know. :)

CompoundsAllowed=3,1 // A max of 4 compounds can be included in this parameter - first number is the prime
 
Yeah, I like to keep your content as-is so new people can join our league.
Perfect, I didn't think the restrictions were really necessary anyway.
Thanks much to you and your team! :)
 
Hi - I get the dropping to windows then back into game issue a few people reported with this track. Does it on the new version too.

I get this error in the Windows Application Event log as it triggers:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 141
P2: ffff838156ad1310
P3: fffff80896a57d80
P4: 0
P5: 10f0
P6: 10_0_14393
P7: 0_0
P8: 256_1
P9:
P10:

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20160904-1809.dmp
\\?\C:\Users\jamie.Rodders-1\AppData\Local\Temp\WER-5065640-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER504C.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_4649bd6c67a90a67c9c571b8c8d4ec4f9e97a1_00000000_cab_216d504c

Analysis symbol:
Rechecking for solution: 0
Report Id: 61b2ce51-72c2-11e6-89ef-08626627b0be
Report Status: 4


The this when it goes back into game:

Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 7d8cd993-695a-4195-a1b4-5fd41108f2e8

Problem signature:
P1: 141
P2: ffff838156ad1310
P3: fffff80896a57d80
P4: 0
P5: 10f0
P6: 10_0_14393
P7: 0_0
P8: 256_1
P9:
P10:

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20160904-1809.dmp
\\?\C:\Users\jamie.Rodders-1\AppData\Local\Temp\WER-5065640-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER504C.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_4649bd6c67a90a67c9c571b8c8d4ec4f9e97a1_00000000_cab_245569cf

Analysis symbol:
Rechecking for solution: 0
Report Id: 61b2ce51-72c2-11e6-89ef-08626627b0be
Report Status: 0

Looking into what it means and what might cause it but wanted to pop it up here and see if anyone with the skillz has an idea what it could be?

Cheers.
 
Also spotted a System event log error a second before the App one:

Display driver nvlddmkm stopped responding and has successfully recovered.

So some sort of display driver related issue. I'll try rolling back to earlier versions and let you know how it goes.
 
Tried a few different driver versions and tweaked a number of graphics settings but no success so far. There is no obvious pattern to it. Sometimes it doesn't happen for 15 minutes, sometimes several times in a few minutes. Ran GPU-Z analysis up until the point I get the driver crash and the only anomaly is the GPU load spiking to 100% as the crash happens - otherwise my GPU is cruising and the game is running generally flawlessly

Some info below if it helps anyone with ideas as I'm desperate to get racing on Spa. :(

Windows 10 64 Bit
980Ti
i5 4690K @4.5GHz
32GB Ram
3440x1400

Cheers.
 
@RodneyS

I doubt that the issue is track related (not impossible that's true). Many others have used the track without issue. Recent changes in the update are not likely to be the cause.

That said I would keep looking for problems with your hardware and / or system software. You would not be the first person to have some defective hardware causing weird grief.

If you like you can download an older version from the "Version History" tab above to use as a comparison.


EDIT. One more idea is DDU http://www.guru3d.com/files-details/display-driver-uninstaller-download.html

I have had some issue with Nvidia drivers. I am using win7x64 and removing the old driver with DDU then install the new driver as a fresh install works for me.
 
Last edited:
Back
Top