Jump to content
Christmas Period - Codemasters Staff and Support Read more... ×

steviejay69

Members
  • Content Count

    5,350
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by steviejay69


  1. 7 hours ago, RAFAGF said:

    It was reaching almost 80C and I stopped the stress test. Then I replaced thermal grease and now is stable around 65C. But the issues with F1 games still occurs. Artifacts at game Recore also appears but many other games are OK. Do you think there is permanent damage at my graphics card that can cause these problems?

    1976184200_ReCore23_04_202022_11_46.thumb.png.f26f8c3ac0944752b044258e37095d1b.png

    What kind of framerate are you running? The R7 370 doesn't support Freesync (your monitor allegedly does but I can find only a 60Hz refresh in the spec.)

    V-SYNC should be on and 60Hz (try 59Hz as well)? in-game.

    https://www.displayninja.com/freesync-monitor-list/

    Samsung C27F390FHC 27″ 1920×1080 VA 75Hz 48-72Hz No

    All things considered, the R7 370 is quite old. You've made the necessary mods, it is a DX11 card so maybe run the game in DX11 mode?

    (If it is F1 2018 it is DX11, unless you've opted into the DX12 beta - but that carries the 'Work In Progress' banner, even when you then use the DX11 mode.)

    The only other thing I haven't tested is the capabilities of the A320 chipset, all the AMD builds I've had are B450.


  2. 8 minutes ago, CroustiZ said:

    Hi, thanks for answering.

    I hoped... I removed my headset HyperCloud, I played and I crashed at lap 10...

    This is the rapport.
    Where did you see that the error codes was between amd gpu and the hyperx? maybe i could delete all files about the headset but I dont find them in my local disk.

    thank you....

    EGO Dumper.txt

    Quote

    +++ WER5 +++:
    Détecteur d'erreurs 1284965852182675754, type 5
    Nom d’événement : WUDFHostProblem
    Réponse : Non disponible
    ID de CAB : 0

    Signature du problème : 
    P1 : HostProblem
    P2 : HostTimeout
    P3 : 2
    P4 : 2.29.0
    P5 : 103
    P6 : 3
    P7 : 11b00
    P8 : ffffffffffffffff
    P9 : HID\VID_0951&PID_16A4&REV_0005&MI_03&Col02
    P10 : 

    Fichiers joints :
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER237C.tmp.WERInternalMetadata.xml

    Ces fichiers sont peut-être disponibles ici :
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_HostProblem_b3126c8280ac1a3a246e1674868ec141928b91c_00000000_0515b628-a06d-46e6-bb0a-d900484bab2a

    Symbole d’analyse : 
    Nouvelle recherche de la solution : 0
    ID de rapport : 0515b628-a06d-46e6-bb0a-d900484bab2a
    Statut du rapport : 268435556
    Récipient avec hachage : 79b4263ce632fc7f41d51da26fdb012a
    GUID CAB :0

    The driver won't be active without the dongle plugged in.

    The other crashes were in F1_2019_DX12.exe

    Quote

    +++ WER1 +++:
    Détecteur d'erreurs , type 0
    Nom d’événement : D3DDRED2
    Réponse : Non disponible
    ID de CAB : 0

    Signature du problème : 
    P1 : VEN_1002
    P2 : 26.20.15029.20013
    P3 : 0x887A0006
    P4 : 3
    P5 : F1_2019_dx12.exe
    P6 : 1.0.61.4494
    P7 : 
    P8 : 
    P9 : 
    P10 : 

    Fichiers joints :
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4F38.tmp.WERInternalMetadata.xml

    Ces fichiers sont peut-être disponibles ici :
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_VEN_1002_207e33ac691f7ea7b2add79093987e91cd217c6_00000000_9d9bb3a7-e42a-42d9-aad2-9f03aea215bd

    Symbole d’analyse : 
    Nouvelle recherche de la solution : 0
    ID de rapport : 9d9bb3a7-e42a-42d9-aad2-9f03aea215bd
    Statut du rapport : 100
    Récipient avec hachage : 
    GUID CAB :0

    Direct3D device removal.


  3. 4 hours ago, Crossy25 said:

    Hi Barry, it just says Thrustmaster TMX so not sure if thrustmaster tmx pro is or isn't? 

    AFAIK the TMX Pro is the same as the TMX but with the T3PA pedals rather than the 2 pedal effort.


  4. Oh yeah, can we please make the superlicence screen not be on TAB as it always goes in there when you SHIFT-TAB to Steam overlay. Annoying when in Multiplayer lobbies.

    Can we have the setup screen go left and right on the shifters (1,2), not on the buttons (10,9), like it used to?

    And when we are in the garage, can the brakes not be linked to up / down view?

    Can we also have a consistent enter / forward / accept on button 6 rather than jumping to button 4 irregularly?

    • Agree 1

  5. 2 hours ago, Fusobhz said:

    Yep, 2 values in TS-PC f1 file and 1 value on dictionary file.

    I'm not home now, but in f1 normal mode and with other wheel (like the R383) it works fine, the product id matches and no problem occurs.

    The problem is only with the F1 on advanced mode.

    Later when I get home I'll post these 2 screenshots, with f1 on normal mode (works perfectly) and with the R383 wheel (works perfectly to)

    But I can say that the 2 action maps files match with productid number on drivers, for sure.

    I'm not disagreeing with you, merely pointing out that the B696 ID is for the TS-XW, AFAIU.

    It's not abnormal for the device ID to change with the addition of a rim. The T300 I had only had one base ID, the Open Wheel Rim did not change it. The F1 Rim changed the ID when it was added to the T300 (the ID is different again for the T300 base when it's in PS4 mode - not applicable to you as it's a PC only wheel, the TS-XW will probably be the same, but won't be seen in the driver because it's not identified by the PC. It also didn't matter if the F1 wheel was in advanced or normal mode, but the driver did restart when changing, as the device description changed in Device Manager). The USBDeView shows my T300 as a disconnected device if I leave it in PS4 mode - incidentally that's T500 emulation mode for a T300, as it did for my old G920 before I installed the driver (it appeared in Device Manager as an XBox Driving Wheel or something might even have been XBox HID device, can't remember).

    I'm pretty sure the B68A device is correct. As TM's FFB driver hasn't really changed for a while (2017 I think), you could try going back to earlier drivers if you really wanted. It might be an error in the software itself (2019 had 1 release, 2018 had 1, 2 and 3, 2017 had release 1, 4, 5, 6 and 7. (I guess there's nothing to lose to see if the feedback works properly by installing these drivers; I guess uninstalling and installing 2017_TTRS_1 then going sequentially from there. At least while you wait for CM or TM to get back....

    https://www.dropbox.com/s/yk5dkaixdhylyzx/2019_TTRS_1.exe?dl=0

    https://www.dropbox.com/s/04v67mwos7xkok4/2018_TTRS_3.exe?dl=0

    https://www.dropbox.com/s/1nb5u3dtn5zqqup/2018_TTRS_2.exe?dl=0

    https://www.dropbox.com/s/zz12ar1adnufowd/2018_TTRS_1.exe?dl=0

    https://www.dropbox.com/s/ymmvzulyju3z6in/2017_TTRS_7.exe?dl=0 (I didn't have a T300 prior to this one, Station drivers have only the older Vista and 9x/XP versions that I don't. And I just recovered these from my old file history on Windows 10, I only normally keep the latest.)

    But I agree your actionmap change is probably correct to B68A.

    What happens if you disconnect the shifter TH8RS (or make sure it is in neutral)? Just musing as there was an issue with Logitech wheels misbehaving when the shifter was left in gear.


  6. 8 hours ago, Fusobhz said:

    tsf1.jpg

    See, to my mind it should describe the rim as Ferrari 'F1 Rim in Advanced Mode'. Fairly sure the T300 did this (I don't have the rim any more).

    But the T300 only had 2 IDs (B66E & B66F with the F1 Rim)


  7. I've been looking at the driver files and I'm not convinced the driver is even correct. Codemasters might be wrong but only because Thrustmaster might be (the driver is still headed $CHICAGO$ which is W98 (!) and the NT version has not been changed since NT 6.2 which is W8.0 (!)). In itself, it's probably not a biggy but the header should be $WINDOWS_NT$

    It seems the only value in it (TS-XX F1 ADVANCED) is for B696 which is with the TS_XW. 

    B68A is correct for the TS_PC and that's definitive according to how the driver is detecting.

    But TS_XW has B692, B693 (F1) and B696 (F1 ADVANCED). (Looks like I was well off with B692 ☹️ )

    TS_PC has B689 and B68A (F1). I think the driver isn't right and that's why B696 works like a pad because it's expecting the TS_XW firmware (and base).

    Gonna ask Thrustmaster to take a look too.


  8. You can change the Camera view by pressing C on the keyboard while playing. There is an equivalent button on the G29 but I can't find the mappings.

    There is a Camera View setting in the in-game options. Press ESC or Menu on the G29 and on that first menu Driving View can be toggled through the available camera options.

    Allegedly, T-Cam is an ASSIST and you should use COCKPIT 😉

    Edit: Unless I read your message wrong and your camera view is always looking back.

    Options: Stuck rear view button (keyboard,controller or wheel). Second controller (with analog stick) wants unplugging. Something wrong with the G29 (could be old LGS, try G-Hub).


  9. 2 hours ago, RAFAGF said:

    What tests do you suggest with Furmark?

    The thermal grease I have is GD900 I've been using at my CPU. Do you think is OK to use in GPU?

    Torture test. When the GPU temp is over 80C you should stop. Most cards should sit at 65C-75C under full load and not increase. They may fluctuate 1-2C but this will be the thermal throttling limit. Even a slow increase is bad. A quick one, get ready to stop the test and close down.

    Yes. I use MX4 for both. I've used it for years without issue. It would seem that there's maybe 1C either way between the two depending on which test you read. So it should be fine. It's more about how you apply it and whether you tighten the cooler (Heatsink/pipe and clean fans) properly. 

    Don't be stingy but don't slap paste everywhere. Tighten screws evenly and progressively. When they bite, there's no need to overtighten. A quarter turn, max. When you hit a stop, stop!


  10. I don't think the rejoin session feature is very useful. It basically encourages players to play with crappy connections, totally stuffing up the game.

    Also I don't think ghosting is helpful. If the lag was fixed by people not playing with ****** connections then players would know where the backmarker is. This would also help with the Blue Flags. The driver being lapped gets them waaay too early, fine if you are 12 seconds a lap off the pace but when you are racing and being lapped you need to be able to judge when the leader or lapping car is coming. This can make the difference in a lower points paying position between getting it right and using the lapping car as an aide or simply not getting a clean shot at a pass.

    Play with team audio and use the rear view, shout when you see the flag, when you are alongside and see if the two views tally. I'm not a betting man, but (clue) they don't.

    So in summary,

    1. Agree, observed EVERY time since last couple of patches. It wasn't in the game up until recently. You changed something. It will be in the detail that doesn't make the public patch notes.

    2. Agree, have seen. It's random in nature, sometimes it's fine, others it's exactly as described. A **** show.

    3. It happens in the menus as well as on track, setups disappear, weather changes, tyres end up being wrong. Frame rate limiter is often ignored after a graphics driver update. Cutscenes and the pits send framerates all over the place. Starting F1 2019, there is a dip observed every time (I use Steam FPS counter).

    4. Yeah the way the cars behave under AI control when the player leaves is UNSATISFACTORY. Cars veer back onto the track if they are retired from a standstill in the gravel way over by the catch fencing, and they're not ghosted. A retirement in the pitlane before the pitbox should put the car in the garage. Can you explain why they hit each other on the in lap after a session? Zero awareness, they all want the same piece of tarmac. This is also an issue in the AI logic. It turns in on you when the difficulty level is set so you can race it. Too slow and you can drive around it and win by laps. Too fast, well it's just too fast (this is too varied by track as well) I know humans can be specialists at certain tracks and have bogey tracks but how come I can beat the AI at 105 on some tracks and just eat fumes at 95 on others?

    5. Agree.

    6. Agree, if there was ever a case FOR ghosting, it's for AI in this situation (because you are AI controlled in the pits). Please fix it.

    7. Yeah, immersion and game breaking teleporting. Just watch a random 'IntoTheBarrier' vid on YT. There are aliens that are fast drivers and the "beam me up Scotty" types. Except it's that episode with the transporter malfunction and even Chief O'Brien can't fix it.

    8. Agree. There should be a cut off time for joining a session. If the 10 second countdown is on, it's too late. It can take at least that for connection bars to be resolved when everyone joins a lobby 10 minutes before the start.

    9. I have seen this posted in the forums. I haven't played enought to be really affected by it, but I would be ******. But, F1 2019 is ****.

    10. Ghost cars first appeared in F1 2013. So yeah, take your netcode revisions way back. You did fix it, during the game lifecycle! F1 2013 was the best game so far.

    11. Yeah, if there's one time you don't really want to be leading, it's when there is a full SC. And let's face it, Berndt has been working overtime since the last patch. Random.

    12. The delta pace is crazy wrong. Fix it. Yeah, penalties for cutting behind SC, penalties should be suspended (game can flag it but not count it as a penalty). What has not already been said about track limits detection? It's so broken. Rethink it. Regular is a stupid cutfest. Strict is randomly strict, then nonsensical.

    13. Also leaders if they don't get penalised by the randomness of the SC get bogged down sometimes and stuck in gear. It happened to me at Baku. Got swamped by people doing that under VSC (ignoring the delta under VSC ending). So twice I got ****** for being in front.

    14. Yeah to cap it all this is a misrule. And I'd like to add some overtakes under SC are penalised even when the person in front is told to hand the position back. He does and the car retaking gets an illegal overtake. Race Control, Codies. Have you heard of it?

    15. This is a longstander. The collision detection is like the track limits. Almost always plain wrong. What the hell is with that audio in that video?

    16. Haven't seen this one. But obviously wrong. People play more than me. I had 400 hours on F1 2017, I might get 200 on F1 2019.

    17. Well, if they're served by a stop-go they're not added to the times again (classically one year this was happening I think it might've been F1 2017) so aren't visible until the end. But then if they don't count (served), where is the issue?

    18. Nobody at Codemasters ever watched F2 or actually tested it I reckon. It's part brilliant and part bugged to hell. Pick the bugged to hell part out and I think people would just play F2.

    Good post @Bicarda

    • Like 1

  11. Simplest way is to backup the game and uninstall then reinstall from backup as it forces a first run that fixes the relevant runtimes. More inconvenient.

    You can't expect me to know every dependency of every bit of software? They're installed as you install programs, you've more chance knowing than me.


  12. 37 minutes ago, DarkFizz said:

    So do I need to reinstall every VC++ or I don’t really understand what to do. Can you explain it different?

    Select them and repair them, there should be an option when highlighting them in that Control Panel screen. If there isn't download them again from Microsoft.

    But it is better to have as few as possible really. Only necessary ones.


  13. 1 hour ago, DarkFizz said:

    Can’t find Microsoft .net Framework 4,5 (or later) in the uninstall/change.

    image.jpg

    Then it's likely to be one of the VC++ runtimes, you can see there are 32/64 and lots of versions (this is a MS mess unfortunately), for many older apps that prompt you to install older versions of runtimes I would ignore the request and only install the ones that; a) fail the install until you do download the runtime, b) don't work when installing without the runtime (the way to do this is uninstall, then reinstall and allow the runtime during the installation). Only caveat is, make sure you are running the latest version of the installer. Some installers are updated to not use the older runtimes but have been adapted to use the newer ones (just because the installer doesn't complain when you use it, not all of them check for newer or even are aware of newer runtimes).

    Once you get the Intel DSA working, I can see it will update quite a few versions of drivers. And Java is outdated since the 14th we have been on 8u251. 🙂

×