-
Content Count
5,344 -
Joined
-
Last visited
-
Days Won
2
Posts posted by steviejay69
-
-
11 minutes ago, 1512marcel said:I follow you, but most of these options already exist (driver call or selection) and the OP's question is about only changing the frontwing and not the tyres, which and I qoute @Tway only happened once in an insane number of 100% races. Me for one questions if this ever happened in real life and see no point adding such an option.
McLaren ran long in the Honda years (until Alonso insisted on going banzai on options at the start to race and lose places before retiring or being told to retire the car, or getting banged because he was trying to race with sub-standard equipment) so I would think the probability is high on those races and latterly the Williams being in a similar position at the back.
But both teams would take more hard tyre compounds and then have the spare sets to replace them in most permutations. But that doesn't happen when you take the balanced tyre choices on the tracks that use mainly soft and mediums (or the relative compounds when they were differently named).
So I agree, not many IRL representations of the situation being replicated, but the game throws it up as deliberately picking too hard a set of compounds gains nothing when car performance is equal (you don't want to stop unnecessarily, you don't expect to try to lose performance).
-
13 hours ago, 1512marcel said:Your being cynical right?
Probably not.
It's about the game being able to respond as a strategist might. You do get the strategy suggestion (usually mid-race if you have had some unscheduled stop or you run longer than recommended on one of the compounds) but the game sticks rigidly to a pre-determined strategy (unless you input a change of call as the driver). If you go beyond your scheduled stops it just cycles through your "least worn" tyres really, regardless of compound.
As someone who often tries 1 stop strategies, yes it is really rather dependent upon you surviving T1, Lap 1 and then generally as much of that first stint as humanly possible, and then getting a clean run avoiding traffic to get a good time advantage or make positions.
I think the game is almost fine as it is (WRT pitstops) but the addition of a 'keep' or 'stay' on current compounds should be a selectable call. We have the wing damage settable to Yes/No/Auto. so tyres Yes (selection) / No (keep) / Auto (to strat or least worn set) would be enough.
And give us the tyre selection option in the car in P and Q. If there is sufficient fuel for 2 laps with saving we should be able to override garage stops with hot stops.
-
1 minute ago, Overfl0w said:Yeah maybe it's the engine, now the game last longer but completely crashes after 4-5 laps and restarts. 😞
Other thing to realise is driver technology has totally changed. Even W8 did not exist before 2012.
-
Just now, Overfl0w said:At first I thought that but I can run F1 2019 at low preset in 1920x1080@144Hz, the same with the F1 2017 and 2018 games. This only happens to me with this games, but will try it and let you know if it works 😄
Remember the engine is very different F1 10-14 to F1 15-19.
-
I think you are being optimistic trying to run the game at 1920x1080@144Hz with a 2GB GTX660.
Try lowering the resolution, framerate to 60Hz and use the medium preset.
-
1 hour ago, thisdisplayname said:Thanks. I found the answer on a Microsoft forum - https://answers.microsoft.com/en-us/windows/forum/all/force-feedback-wheel-problems/1dbdffea-3744-4548-bfa5-32ad2f240310?page=5
So I tried that.
But now the pedals are reversed although in the Thrustmaster control panel they are the right way round??
Do you mean axis reversed (100% throttle with no input and 0% throttle with pedal 100%) or clutch/throttle swapped or brake / throttle swapped?
-
1 hour ago, thisdisplayname said:Just dusted off Formula 1 99 which runs on W10 64 bit quite happily. But my year 2000 approx wheel doesn't run at all.
https://support.thrustmaster.com/en/product/ffdrw-en/
Does anyone know if there are any divers/fixes out there?? By the dearth on the www and the Thrustmaster tech support, I guess it is time to recycle it via a bin?
Thanks.
Try installing the driver package in Windows Vista Service Pack 1 compatibility mode? If you can reach the Thrustmaster CP then there's a chance.
-
47 minutes ago, martingr1 said:See attached.
Also, latest crash dump below.
[01-04-2020 16:48:35] - ##################################################
[01-04-2020 16:48:35] - EGO dumper
[01-04-2020 16:48:35] - processId=632, threadId=27768, exceptionPointers=000000001453E3C0, buildId=614494
[01-04-2020 16:48:35] - ##################################################
[01-04-2020 16:48:37] - Suspending threads of process 632
[01-04-2020 16:48:37] - tempPath=C:\Users\marti\AppData\Local\Temp\
[01-04-2020 16:48:37] - dumpFilename = C:\Users\marti\AppData\Local\Temp\614494-20200401-164837.dmp
[01-04-2020 16:48:37] - offsetsFilename = C:\Users\marti\AppData\Local\Temp\614494-20200401-164837.off
[01-04-2020 16:48:37] - infoFilename = C:\Users\marti\AppData\Local\Temp\info.txt
[01-04-2020 16:48:37] - dredFilename = C:\Users\marti\AppData\Local\Temp\dred.txt
[01-04-2020 16:48:37] - hardwareSettingsInfoFilename = C:\Users\marti\AppData\Local\Temp\hardware_settings_info.xml
[01-04-2020 16:48:37] - hardwareSettingsConfigFilename = C:\Users\marti\AppData\Local\Temp\hardware_settings_config.xml
[01-04-2020 16:48:37] - zipFilename = C:\Users\marti\AppData\Local\Temp\614494-20200401-164837-0.zip
[01-04-2020 16:48:37] - 0x140000000: F1_2019_dx12.exe
[01-04-2020 16:48:37] - 0x7FFE421C0000: ntdll.dll
[01-04-2020 16:48:37] - 0x7FFE40AF0000: KERNEL32.DLL
[01-04-2020 16:48:37] - 0x7FFE3F180000: KERNELBASE.dll
[01-04-2020 16:48:37] - 0x7FFE3D300000: apphelp.dll
[01-04-2020 16:48:37] - 0x7FFE41600000: advapi32.dll
[01-04-2020 16:48:37] - 0x7FFE41850000: msvcrt.dll
[01-04-2020 16:48:37] - 0x7FFE40D50000: sechost.dll
[01-04-2020 16:48:37] - 0x7FFE409D0000: RPCRT4.dll
[01-04-2020 16:48:37] - 0x7FFE3F650000: crypt32.dll
[01-04-2020 16:48:37] - 0x7FFE3F4B0000: ucrtbase.dll
[01-04-2020 16:48:37] - 0x7FFE3F090000: MSASN1.dll
[01-04-2020 16:48:37] - 0x7FFE3B9D0000: amd_ags_x64.dll
[01-04-2020 16:48:37] - 0x7FFE2C910000: bink2w64.dll
[01-04-2020 16:48:37] - 0x7FFE416B0000: USER32.dll
[01-04-2020 16:48:37] - 0x7FFE41010000: gdi32.dll
[01-04-2020 16:48:37] - 0x7FFE3F150000: win32u.dll
[01-04-2020 16:48:37] - 0x7FFE3F7C0000: gdi32full.dll
[01-04-2020 16:48:37] - 0x7FFE40700000: ole32.dll
[01-04-2020 16:48:37] - 0x7FFE35580000: d3d12.dll
[01-04-2020 16:48:37] - 0x7FFE3F5B0000: msvcp_win.dll
[01-04-2020 16:48:37] - 0x7FFE412C0000: combase.dll
[01-04-2020 16:48:37] - 0x7FFE40140000: bcryptPrimitives.dll
[01-04-2020 16:48:37] - 0x7FFE0B030000: d3dcompiler_47.dll
[01-04-2020 16:48:37] - 0x7FFE41140000: oleaut32.dll
[01-04-2020 16:48:37] - 0x7FFE3A650000: dinput8.dll
[01-04-2020 16:48:37] - 0x7FFE3DD80000: dxgi.dll
[01-04-2020 16:48:37] - 0x7FFE40270000: setupapi.dll
[01-04-2020 16:48:37] - 0x7FFE3F460000: cfgmgr32.dll
[01-04-2020 16:48:37] - 0x7FFE25C70000: gfsdk_ssao_d3d12.win64.dll
[01-04-2020 16:48:37] - 0x7FFE3D1E0000: gpuopen_depthoffieldfx_x64.dll
[01-04-2020 16:48:37] - 0x7FFE3F430000: bcrypt.dll
[01-04-2020 16:48:37] - 0x7FFE3DC90000: hid.dll
[01-04-2020 16:48:37] - 0x7FFE419B0000: shell32.dll
[01-04-2020 16:48:37] - 0x7FFE3E5A0000: iphlpapi.dll
[01-04-2020 16:48:37] - 0x7FFE41900000: shcore.dll
[01-04-2020 16:48:37] - 0x7FFE3D030000: WINMM.dll
[01-04-2020 16:48:37] - 0x7FFE3F9C0000: windows.storage.dll
[01-04-2020 16:48:37] - 0x7FFE3F0D0000: profapi.dll
[01-04-2020 16:48:37] - 0x7FFE260B0000: VCRUNTIME140.dll
[01-04-2020 16:48:37] - 0x7FFE3F100000: powrprof.dll
[01-04-2020 16:48:37] - 0x7FFE3F080000: UMPDC.dll
[01-04-2020 16:48:37] - 0x7FFE40CF0000: shlwapi.dll
[01-04-2020 16:48:37] - 0x7FFE3CFD0000: WINMMBASE.dll
[01-04-2020 16:48:37] - 0x7FFE3F0B0000: kernel.appcore.dll
[01-04-2020 16:48:37] - 0x7FFE3F7A0000: cryptsp.dll
[01-04-2020 16:48:37] - 0x7FFE3DCF0000: dxcore.dll
[01-04-2020 16:48:37] - 0x7FFE41050000: ws2_32.dll
[01-04-2020 16:48:37] - 0x7FFE3EA60000: CRYPTBASE.DLL
[01-04-2020 16:48:37] - 0x5D340000: steam_api64.dll
[01-04-2020 16:48:37] - 0x7FFE15870000: tobii.gameintegration.dll
[01-04-2020 16:48:37] - 0x7FFE36370000: winhttp.dll
[01-04-2020 16:48:37] - 0x7FFE2B750000: wininet.dll
[01-04-2020 16:48:37] - 0x7FFE3BB90000: wtsapi32.dll
[01-04-2020 16:48:37] - 0x7FFE3B670000: xinput1_4.dll
[01-04-2020 16:48:37] - 0x7FFE3EE20000: DEVOBJ.dll
[01-04-2020 16:48:37] - 0x7FFE40860000: IMM32.DLL
[01-04-2020 16:48:37] - 0x7FFE08990000: gameoverlayrenderer64.dll
[01-04-2020 16:48:37] - 0x7FFE418F0000: PSAPI.DLL
[01-04-2020 16:48:37] - 0x7FFE2BC30000: inputhost.dll
[01-04-2020 16:48:37] - 0x7FFE3CB80000: CoreMessaging.dll
[01-04-2020 16:48:37] - 0x7FFE3B090000: CoreUIComponents.dll
[01-04-2020 16:48:37] - 0x7FFE3AF30000: wintypes.dll
[01-04-2020 16:48:37] - 0x7FFE3BA40000: PROPSYS.dll
[01-04-2020 16:48:37] - 0x7FFE3E0E0000: ntmarta.dll
[01-04-2020 16:48:37] - 0x7FFE3F960000: WINTRUST.dll
[01-04-2020 16:48:37] - 0x7FFE406E0000: imagehlp.dll
[01-04-2020 16:48:37] - 0x7FFE07740000: steamclient64.dll
[01-04-2020 16:48:37] - 0x7FFE37BF0000: VERSION.dll
[01-04-2020 16:48:37] - 0x7FFE25420000: Secur32.dll
[01-04-2020 16:48:37] - 0x7FFE3E890000: MSWSOCK.dll
[01-04-2020 16:48:37] - 0x7FFE156F0000: tier0_s64.dll
[01-04-2020 16:48:37] - 0x7FFE2C890000: vstdlib_s64.dll
[01-04-2020 16:48:37] - 0x7FFE3EF70000: SSPICLI.DLL
[01-04-2020 16:48:37] - 0x7FFE3D400000: uxtheme.dll
[01-04-2020 16:48:37] - 0x7FFE3E400000: rsaenh.dll
[01-04-2020 16:48:37] - 0x7FFE37A60000: cryptnet.dll
[01-04-2020 16:48:37] - 0x7FFE0A580000: nvspcap64.dll
[01-04-2020 16:48:37] - 0x7FFDE9F90000: D3DSCache.dll
[01-04-2020 16:48:37] - 0x7FFE3EFA0000: USERENV.dll
[01-04-2020 16:48:37] - 0x7FFE3D4D0000: twinapi.appcore.dll
[01-04-2020 16:48:37] - 0x7FFE3D850000: RMCLIENT.dll
[01-04-2020 16:48:37] - 0x7FFE36690000: nvapi64.dll
[01-04-2020 16:48:37] - 0x7FFE420A0000: NSI.dll
[01-04-2020 16:48:37] - 0x7FFE33EE0000: dhcpcsvc6.DLL
[01-04-2020 16:48:37] - 0x7FFE33EC0000: dhcpcsvc.DLL
[01-04-2020 16:48:37] - 0x7FFE3E5E0000: DNSAPI.dll
[01-04-2020 16:48:37] - 0x7FFE40890000: MSCTF.dll
[01-04-2020 16:48:37] - 0x7FFE3EE70000: WINSTA.dll
[01-04-2020 16:48:37] - 0x7FFE37C00000: nvldumdx.dll
[01-04-2020 16:48:37] - 0x7FFDFE570000: nvwgf2umx.dll
[01-04-2020 16:48:37] - 0x7FFE3DCA0000: gpapi.dll
[01-04-2020 16:48:37] - 0x7FFE075E0000: nvngx.dll
[01-04-2020 16:48:37] - 0x7FFE30170000: NvTelemetryAPI64.dll
[01-04-2020 16:48:37] - 0x7FFE36030000: DEVRTL.dll
[01-04-2020 16:48:37] - 0x7FFE35EF0000: drvstore.dll
[01-04-2020 16:48:37] - 0x7FFE37120000: SPINF.dll
[01-04-2020 16:48:37] - 0x7FFE07040000: nvngx_dlss.dll
[01-04-2020 16:48:37] - 0x7FFE0C820000: vulkan-1.dll
[01-04-2020 16:48:37] - 0x7FFE235C0000: nvngx_dlisp.dll
[01-04-2020 16:48:37] - 0x7FFE1ADA0000: NvTelemetryBridge64.dll
[01-04-2020 16:48:37] - 0x7FFE3C990000: dcomp.dll
[01-04-2020 16:48:37] - 0x7FFE3D820000: dwmapi.dll
[01-04-2020 16:48:37] - 0x7FFE2C100000: TextInputFramework.dll
[01-04-2020 16:48:37] - 0x7FFE35810000: iertutil.dll
[01-04-2020 16:48:37] - 0x7FFE41210000: clbcatq.dll
[01-04-2020 16:48:37] - 0x7FFE379E0000: MMDevApi.dll
[01-04-2020 16:48:37] - 0x7FFE37A90000: AUDIOSES.DLL
[01-04-2020 16:48:37] - 0x7FFE3D730000: resourcepolicyclient.dll
[01-04-2020 16:48:37] - 0x7FFE3B660000: CM.Windows.Gaming.Input.dll
[01-04-2020 16:48:37] - 0x7FFE3A870000: Windows.Gaming.Input.dll
[01-04-2020 16:48:37] - 0x7FFE05E60000: mssps.dll
[01-04-2020 16:48:37] - 0x7FFDEA1F0000: MSACM32.dll
[01-04-2020 16:48:37] - 0x7FFE05C00000: wmvcore.dll
[01-04-2020 16:48:37] - 0x7FFE0AAD0000: mfperfhelper.dll
[01-04-2020 16:48:37] - 0x7FFE14710000: WMASF.DLL
[01-04-2020 16:48:37] - 0x7FFE05AA0000: spsreng.dll
[01-04-2020 16:48:37] - 0x7FFE0BD30000: srloc.dll
[01-04-2020 16:48:37] - 0x7FFDEA210000: wdmaud.drv
[01-04-2020 16:48:37] - 0x7FFE3A2A0000: ksuser.dll
[01-04-2020 16:48:37] - 0x7FFE3B690000: AVRT.dll
[01-04-2020 16:48:37] - 0x7FFE2CDA0000: msacm32.drv
[01-04-2020 16:48:37] - 0x7FFDEA1E0000: midimap.dll
[01-04-2020 16:48:37] - 0x7FFE35AC0000: urlmon.dll
[01-04-2020 16:48:37] - 0x7FFE2BEB0000: Windows.UI.dll
[01-04-2020 16:48:37] - 0x7FFE05960000: dxilconv.dll
[01-04-2020 16:48:37] - 0x7FFE3E440000: DPAPI.DLL
[01-04-2020 16:48:37] - 0x7FFE268F0000: webio.dll
[01-04-2020 16:48:37] - 0x7FFE34000000: WINNSI.DLL
[01-04-2020 16:48:37] - 0x7FFE34DC0000: rasadhlp.dll
[01-04-2020 16:48:37] - 0x7FFE33F80000: fwpuclnt.dll
[01-04-2020 16:48:37] - 0x7FFE3E330000: schannel.DLL
[01-04-2020 16:48:37] - 0x7FFE0C020000: mskeyprotect.dll
[01-04-2020 16:48:37] - 0x7FFE3EB60000: ncrypt.dll
[01-04-2020 16:48:37] - 0x7FFE3EB20000: NTASN1.dll
[01-04-2020 16:48:37] - 0x7FFE0C370000: ncryptsslp.dll
[01-04-2020 16:48:37] - 0x7FFE3D880000: wer.dll
[01-04-2020 16:48:37] - 0x7FFE15D00000: aepic.dll
[01-04-2020 16:48:37] - 0x810000: sfc.dll
[01-04-2020 16:48:37] - 0x7FFE3A340000: sfc_os.DLL
[01-04-2020 16:48:37] - 0x7FFE30450000: Comctl32.dll
[01-04-2020 16:48:37] - 0x7FFE27A50000: NETAPI32.dll
[01-04-2020 16:48:37] - 0x7FFE3BC40000: DSREG.DLL
[01-04-2020 16:48:37] - 0x7FFE3BBB0000: msvcp110_win.dll
[01-04-2020 16:48:37] - 0x7FFE3A2B0000: XmlLite.dll
[01-04-2020 16:48:37] - 0x7FFE1CB10000: FlightSettings.dll
[01-04-2020 16:48:37] - 0x7FFE1DE50000: bcd.dll
[01-04-2020 16:48:37] - 0x7FFE26440000: netprofm.dll
[01-04-2020 16:48:37] - 0x7FFE265A0000: npmproxy.dll
[01-04-2020 16:48:37] - 0x7FFE0BF00000: Windows.Security.Authentication.OnlineId.dll
[01-04-2020 16:48:37] - 0x7FFE39910000: OneCoreUAPCommonProxyStub.dll
[01-04-2020 16:48:37] - Writing callstacks for threads of process: 632
[01-04-2020 16:48:37] - Thread: 13000
[01-04-2020 16:48:37] - Thread: 21928
[01-04-2020 16:48:37] - Thread: 20468
[01-04-2020 16:48:37] - Thread: 27244
[01-04-2020 16:48:37] - Thread: 33304
[01-04-2020 16:48:37] - Thread: 9484
[01-04-2020 16:48:37] - Thread: 12304
[01-04-2020 16:48:37] - Thread: 32116
[01-04-2020 16:48:37] - Thread: 15948
[01-04-2020 16:48:37] - Thread: 18848
[01-04-2020 16:48:37] - Thread: 12156
[01-04-2020 16:48:37] - Thread: 20864
[01-04-2020 16:48:37] - Thread: 2896
[01-04-2020 16:48:37] - Thread: 28524
[01-04-2020 16:48:37] - Thread: 8276
[01-04-2020 16:48:37] - Thread: 27768
[01-04-2020 16:48:37] - Thread: 27508
[01-04-2020 16:48:37] - Thread: 2476
[01-04-2020 16:48:37] - Thread: 5536
[01-04-2020 16:48:37] - Thread: 17840
[01-04-2020 16:48:37] - Thread: 27484
[01-04-2020 16:48:37] - Thread: 15820
[01-04-2020 16:48:37] - Thread: 29332
[01-04-2020 16:48:37] - Thread: 30160
[01-04-2020 16:48:37] - Thread: 7672
[01-04-2020 16:48:37] - Thread: 23768
[01-04-2020 16:48:37] - Thread: 11260
[01-04-2020 16:48:37] - Thread: 26676
[01-04-2020 16:48:37] - Thread: 19436
[01-04-2020 16:48:37] - Thread: 16332
[01-04-2020 16:48:37] - Thread: 2700
[01-04-2020 16:48:37] - Thread: 27796
[01-04-2020 16:48:37] - Thread: 1812
[01-04-2020 16:48:37] - Thread: 3128
[01-04-2020 16:48:37] - Thread: 27364
[01-04-2020 16:48:37] - Thread: 3036
[01-04-2020 16:48:37] - Thread: 30120
[01-04-2020 16:48:37] - Thread: 26008
[01-04-2020 16:48:37] - Thread: 18420
[01-04-2020 16:48:37] - Thread: 22192
[01-04-2020 16:48:37] - Thread: 27164
[01-04-2020 16:48:37] - Thread: 28876
[01-04-2020 16:48:37] - Thread: 10420
[01-04-2020 16:48:37] - Thread: 24548
[01-04-2020 16:48:37] - Thread: 21144
[01-04-2020 16:48:37] - Thread: 7636
[01-04-2020 16:48:37] - Thread: 33184
[01-04-2020 16:48:37] - Thread: 11136
[01-04-2020 16:48:37] - Thread: 32244
[01-04-2020 16:48:37] - Thread: 1608
[01-04-2020 16:48:37] - Thread: 33352
[01-04-2020 16:48:37] - Thread: 27104
[01-04-2020 16:48:37] - Thread: 4456
[01-04-2020 16:48:37] - Thread: 32120
[01-04-2020 16:48:37] - Thread: 18528
[01-04-2020 16:48:37] - Thread: 10236
[01-04-2020 16:48:37] - Thread: 15636
[01-04-2020 16:48:37] - Thread: 20520
[01-04-2020 16:48:37] - Thread: 18024
[01-04-2020 16:48:37] - Thread: 19616
[01-04-2020 16:48:37] - Thread: 5764
[01-04-2020 16:48:37] - Thread: 21240
[01-04-2020 16:48:37] - Thread: 20968
[01-04-2020 16:48:37] - Thread: 4320
[01-04-2020 16:48:37] - Thread: 13200
[01-04-2020 16:48:37] - Thread: 26952
[01-04-2020 16:48:37] - Thread: 21636
[01-04-2020 16:48:37] - Thread: 5236
[01-04-2020 16:48:37] - Thread: 13276
[01-04-2020 16:48:37] - Thread: 31272
[01-04-2020 16:48:37] - Thread: 27156
[01-04-2020 16:48:37] - Thread: 21920
[01-04-2020 16:48:37] - Thread: 20948
[01-04-2020 16:48:37] - Thread: 11072
[01-04-2020 16:48:37] - Thread: 29164
[01-04-2020 16:48:37] - Thread: 33428
[01-04-2020 16:48:37] - Thread: 29132
[01-04-2020 16:48:37] - Thread: 18472
[01-04-2020 16:48:37] - Thread: 26740
[01-04-2020 16:48:37] - Thread: 30832
[01-04-2020 16:48:37] - Thread: 33220
[01-04-2020 16:48:37] - Thread: 27748
[01-04-2020 16:48:37] - Thread: 18136
[01-04-2020 16:48:37] - Thread: 13216
[01-04-2020 16:48:37] - Thread: 26648
[01-04-2020 16:48:37] - Thread: 27044
[01-04-2020 16:48:37] - Thread: 6752
[01-04-2020 16:48:37] - Thread: 5228
[01-04-2020 16:48:37] - Thread: 29124
[01-04-2020 16:48:37] - Thread: 30008
[01-04-2020 16:48:37] - Thread: 31788
[01-04-2020 16:48:37] - Thread: 4604
[01-04-2020 16:48:37] - Thread: 21508
[01-04-2020 16:48:37] - Thread: 27556
[01-04-2020 16:48:37] - Thread: 32540
[01-04-2020 16:48:37] - Thread: 9836
[01-04-2020 16:48:37] - Thread: 23560
[01-04-2020 16:48:37] - Thread: 10036
[01-04-2020 16:48:37] - Thread: 12624
[01-04-2020 16:48:37] - Thread: 984
[01-04-2020 16:48:37] - Thread: 272
[01-04-2020 16:48:37] - Thread: 788
[01-04-2020 16:48:37] - Thread: 31288
[01-04-2020 16:48:37] - Thread: 25832
[01-04-2020 16:48:37] - Thread: 29964
[01-04-2020 16:48:37] - Thread: 26116
[01-04-2020 16:48:37] - Thread: 27912
[01-04-2020 16:48:37] - Offsets file can be found at: C:\Users\marti\AppData\Local\Temp\614494-20200401-164837.off.
[01-04-2020 16:48:37] - Writing DMP file.
[01-04-2020 16:48:37] - MiniDump can be found at: C:\Users\marti\AppData\Local\Temp\614494-20200401-164837.dmp.
[01-04-2020 16:48:37] - Preparing ZIP file.
[01-04-2020 16:48:37] - Resuming threads of process 632.
I would recommend the same as in the above post. Nvidia look like they might have released a not so great driver in 445.75
-
-
This applies to controllers too. If a controller can be used in the game control schema, it's input is registered. Analog(ue) sticks on console pads are notoriously jittery on raw inputs, so when you complain of your wheel veering hard left or right or the view being off it is your controller registering in game.
Unwanted or unused peripheral controllers can be disconnected.
e.g. if you don't use the shifter you can disconnect it. If you don't use the pedals they can be disconnected (I use a T300 with Fanatec pedals, nothing registers on the pedal inputs of the T300 because the pedals are in the box - and I used Logitechs before that).
-
1
-
-
On 3/27/2020 at 6:42 PM, steviejay69 said:I'd be in. My internet isn't working at 100% I might be laggy.
It's fixed. Thanks for the McLaren.
-
1 hour ago, V7k3ng said:Game still crashed after removing Aura
Removed Armoury Crate and all other ASUS software. Game still crashed
ME Driver/Firmware installers just error... not sure what to do there
I only have NVidia GeForce RTC2060 under display adapters
Intel Driver and support assistant will update my Bluetooth and Wifi Drivers - will do that now and retest tomorrow
Sorry, try this ME Driver and this ME Firmware (the last link the firmware was older, please unzip and run SetupME.exe for the driver, then once installed run MEUpdateTool.exe for the firmware). The driver is required first, it does not normally require a reboot but the firmware will require to be run on it's own and rebooted straight after.
The Intel GPU is not enabled in BIOS then. No worries if you're not using it (I did find it useful when using video editing and stream recording). The iGPU does have a hardware engine that can be assigned as the primary GPU in recording software like OBS. I do find my Ryzen CPU/AMD GPU is slower than the Intel CPU/GPU combo using a basic app like Easy Movie Maker. YMMV depending on your chosen software.
-
Check the position of the PS4/PS3 switch.
-
'Protected Folder Access' is probably turned on in Windows Security, because it sounds like the config file is write-protected.
-
On 3/30/2020 at 8:00 PM, WellsIII said:Also I have downloaded every single Thrustmaster setup from the workshop and none of them recognize the wheel when I go into my control settings.
Already tried:
reinstalling the wheel
updated all firmware and drivers for the wheel
the switch is set to ps3(pc) and not ps4 as it is supposed to be
Again this worked totally fine on iRacing but doesn't seem to work for F1 2019.
Driver package is 2020_TTRS_1 and firmware is v11. Assuming you are running Windows 10 64-bit version 1903/1909 with an Administrator account.
Install the above, do the firmware update, restart the PC. Check for correct operation in Thrustmaster CP. Set DOR to 360.
Delete hardware_settings_config.xml before launching the game.
Go into in-game settings and set controller scheme, remap as required, save as new scheme and play.
Which bit does it (or you) fail at?
-
1
-
-
54 minutes ago, Retnix said:Hello guys, I can´t play Formula one online since some weeks can someone help please ? I have Windows 7 and my error code is 1008:H.
You need to do what it says in the recommended posts. Or simply upgrade to Windows 10.
-
1
-
-
10 hours ago, 1512marcel said:@steviejay69, can you have a look at the included dxdiag file and share your wishdom.
@manutd1972 are you running from an Administrator account rather than a Standard account?
I will look at the dxdiag but my first suggestion / request is that you ditch Windows 8.1 for Windows 10. Like it or not, 8.1 is a cul-de-sac, it is on life support.Get the MCT and upgrade for free.
Ugh, after looking at the dxdiag, most of the drivers are from 2014, because that is the build era of that machine. Just....no. Reasonable CPU on a budget board in a mediocre system with a fairly hamstrung GPU. OK for internet and word processing for years to come, but gaming? No.
-
28 minutes ago, V7k3ng said:ASUS ROG STRIX Z390-E Gaming
Have just uninstalled Aura software and will test tonight. Will also do a test without the headset.
Update ME driver and ME Firmware.
If you remove the Intel VGA driver (if you have it enabled), so you remove driver software until 'Microsoft Basic Display Adapter' is shown in Device Manager, change Hardware|Device Installation Settings to 'No' and restart, you can install the latest DCH driver for Intel VGA.
Also uninstall Armoury Crate software (required for Aura) let's get this thing working then you can reintroduce software once you have a result. Any other ASUS utilities also, please.
ASUS support seems otherwise poor in the last six months. If you download and run the Intel Driver and Support Assistant you may receive updated LAN, IRST and (once installed) DCH VGA drivers via that mechanism.
-
2 hours ago, V7k3ng said:Hi
dxdiag attached (generated yesterday and sent to community(at)... with a bunch of other diagnostics and a crash dump)
I updated my BIOS to 1401 last night but have not played yet
Had my first in-race crash yesterday
Framerate capped at 120fps
Almost certainly going to be linked to your Aura lighting software - can't get the motherboard model from the dxdiag, can you let me know which it is please?
Second suggestion - can you test without the Creative Headset please? Use the Nvidia audio if you don't want to include the Nahimic audio.
-
2 hours ago, ratelaitor1 said:Im using an ASUS p8p67 B3 revision. Quite frankly I don't know what a dxdiag is. I'ts connected to the Usb 2.0 port directly to the mainboard. In other games like Assetto corsa I haven't had this problem. The ports are running EHCI as far as I know.
ASUS P8P67 B3 is quite an old motherboard. The USB 3.0 ports are clearly blue on the rear of the board and the only front USB 3.0 connector would be from the USB3_34 connector near the RAM slots. All the USB connectors at the bottom of the board are USB 2.0. USB 3.0 uses the NEC Renesas chip - you can disable it entirely for testing.
If you attest you are using only USB 2.0 then you have probably done all you can, save not plugging any other device into a matching connector. You have already said you have removed all other USB peripherals when testing.
Last UEFI BIOS rev is 3602 but uCode updates (Sandy Bridge 0x2F or Ivy Bridge 0x21) from KB4497165 if using W10 1903/1909.
-
56 minutes ago, ratelaitor1 said:Whenever I connect my wheel (Microsoft Sidewinder FFB) the game locks to 50 fps. Usually I would get around 150 frames. I have disconnected every other peripheral yet the problem persists. VSync is off, max fps and monitor fps set to 144. Just by disconnecting the wheel i get 144fps back.
I think this might be related to device polling. You should use V-Sync with a 144Hz display as it will probably be Freesync.
The Sidewinder wheel from what I can see is 98/XP-era hardware. It may be designed for USB 1.1 and although USB is designed to be backward compatible, there are often issues.
Your dxdiag will be helpful, but if you can try using the wheel in a USB 2.0 slot on the mainboard without any kind of USB hub or adapter, that would be likely to give better results.
Depending on what other peripherals you use, moving them around to separate device hubs may yield results. If all your USBs are 3.0 you could try switching to EHCI mode rather than XHCI. This will have the effect of making all the USB ports 2.0/1.1 compatible.
Try that and post the dxdiag. Many boards have an additional USB controller chip, so it's possible after looking at the manual I might be able to make some suggestions. Please ensure you post your mainboard name if it is not in the dxdiag.
-
19 hours ago, RoadkilleR78 said:I have an iMac with a radeon Pro 580 8GB.
I installed a new driver, the newset I've found is 19.30. It's just came out a couple of days ago. It seams ok, it solved most of my problems with graphic. But when I start the game it says that the driver is too old. It didn't says nothing with the much older driver 🙂
Tanks a lot!
The drivers you have don't follow the Windows release cycle. For any other Mac user, here is the Boot Camp driver page https://www.amd.com/en/support/kb/release-notes/apple-boot-camp
Since Patch 1.06 the recommended minimum driver release is 19.5.2
-
On 3/7/2020 at 1:26 PM, Petrowsky said:I have the exact same problem except I only use my wheel on PS4. People suggested reinstalling drivers and stuff, but I can't do that on PS4, can I? If I install the drivers from my PC, will it work on PS4 afterwards?
You could use PC mode (PS3) to download and update the wheel if there were any updates. AFAIK, the G29 as is is fully functional with consoles (PS4/PS3) and supported games.
PC users should use G-Hub to administer the wheel, provided they are also using Windows 10.
-
I think the issue is that for some reason the framerate soars in the cutscenes. These uncapped framerate surges are what does for the .exe in the end. Must be some timing critical sequence that goes FUBAR when it does.
Probably the same reason that game crashes are helped by limiting framerates or adjusting graphical settings.
But, I will wait for the dxdiag. A tag will get the quickest response @1512marcel 🤣
-
1
-
FPS lock to 50fps when using my wheel
in Technical Assistance
Posted · Edited by steviejay69
Waiting for merged posts.
dxdiag will be helpful. I have a feeling these machines are all using the Nvidia 445.75 driver, which I'm increasingly of the opinion is duff.