Forum Discussion

macheerou's avatar
3 years ago

MULTIPLE BUGS ON LOW SPEC PC (EA WRC)

Product: EA SPORTS™ WRC
Platform:Steam-PC
Summarize your bug Various Bugs Found on Low Spec PC (DXGI error crashes, Poor Performance in Livery Editor, Wrong Class in an event bug, Graphical Glitches, Microstutters and Frame Drops, Late Calls by Codriver)
How often does the bug occur? Often (50% - 99%)
Steps: How can we find the bug ourselves? A. DXGI Error Crashes: The game often crashes after finishing a stage whenever you attempt to quit or start another event [Frequency: Often] B. Poor Performance in Livery Editor: The game lags too much when entering Livery Editor making livery editing practically unusable. [Frequency: Every Time] C. Wrong Class in an Event Bug: This happened to me once after the DXGI Error crash. I set up an event with WRC Class in Pacifico, followed with Group B in Mexico and Super1600 in Sweden. I did the WRC Class event with the WRC Builder Car and managed to finish the race just fine. After that I was able to select car for the next race (I selected Opel Manta). But the game then crashed with the DXGI error, and I had to restart the game. When restarting, I used the autosaved progress. While the event is now at Mexico, my car still stuck with the WRC Builder Car, while the rest of the opponents are still using Group B car (I noticed this when i finished the stage). This doesn't happen at the next event as my game didn't crash again and I was able to use the Super 1600 car just fine in Sweden. [Frequency: Seems rarely, this is my first time I encounter this bug] D. Graphical Glitches: Aside from stretched texture mapping issue that has been reported by many users, I also found a bug where a car door was improperly positioned during the cutscene at the start line before the start of the race. This happen upon a start line at Sweden (forgot which stage exactly) using the Fiat S2000. The door thankfully is correct when the race actually starts. [Frequency: Seems rarely, this is my first time I encounter this bug] E. Microstutters and Frame Drops (Underutilized balance of CPU and GPU usage): This has been widely reported by the communities but I just want to notify that this also happens on low spec PC. Several area where the frame drops and stutters most likely to happen is especially during start line (on most maps), and during in the middle or near the end of the race splits. Render Latency is also a big issue coupled with low CPU Utilization (Hovers at 35-45 percentage while GPU is at 99). Using ultra performance FSR drops the quality significantly but doesn't really gain performance because the CPU Utilization will spike up but the GPU utilization will become low instead. [Frequency: Often] F. Late Calls by Codriver I think this may have been raised by other members as well here, but the codriver sometimes call a corner very late making you missed some important corners. I think the timing for Important Corners (Sudden, Acute, Square, Hairpin, 1, and Chicanes) could be improved by some miliseconds to give more room. I already used the earliest call but they still call some of these corners very late.
What happens when the bug occurs? A. DXGI Error Crashes: The game will send you back to windows and the Unreal debug launcer will appear. On my case it says DXGI Error Device Removed. This Debug error usually means the GPU is removed in the middle of the game or improperly run, but I have used the latest possible NVIDIA Driver 546.01. This error occurs more often on previous drivers so the new drivers certainly help, but it still happen often. Mind you I'm using laptop that doesn't have NVIDIA Optimus technology so most likely this error is caused due to the computer automatically switches to iGPU temporarily during the downtime between the stages and this may have caused the game engine thinking that I removed the GPU mid game. This kind of error doesn't happen to me on other Unreal Engine games such as Assetto Corsa Competizione or Insurgency Sandstorm, as they managed to run just fine without error during downtimes. B. Poor Performance in Livery Editor: The game will freeze for a long time, and even the element that you select won't appear in the car. Not only in livery editor, but also lags so much when you try to change your driver number. C. Wrong Class in an Event Bug: I have explained in the previous point D. Graphical Glitches: I also have explained about this E. Microstutters and Frame Drops: Usually the frame freezes for split miliseconds before running fine again for awhile. The frame drops also quite significant as while I could attain normal FPS as high as 45 and 99% FPS at 30 ish, both FPS could drop into just 5-10 FPS at times during the stutter. F. Late Calls by Codriver The Late Calls caused me as a driver couldn't brake in time for important corners.
What do you expect to see? Improvement that mainly focuses on overall performance of the game first (A and E bugs) as priority before other bugs, because the crash is annoying as I had to restart the game multiple time, and the performance bugs are hampering the driving aspect (especially when you approach a corner and suddenly the game lags)

I would also like to state that the PC (Actually Laptop) specs that I currently use:
CPU: i7-7700HQ (4 Core 8 Threads, 2.8 GHz clock, 3.4 GHz All Core Turbo - 3.8 GHz Single Turbo Clock)
RAM: 24GB (16+8) DDR4 2400MHz
GPU: GTX 1050 Ti Laptop (NVIDIA Driver Game Ready 546.01)
Storage: Crucial MX500 1TB SATA SSD

While those configuration is actually below the Minimum Requirement Specs, I'm actually happy to report that I still able to play this game in a somewhat playable state (I only target 30 FPS at minimum). I use Low Graphics preset although I switch the Shader to Medium and the Texture to High (also I turn on fog + mirror at ultra low), Coupled with FSR at Quality Preset, 4x Anisotropic Filtering and Medium AA. Resolution is at 1080p.

On a good day when the game doesn't crash or does the stutters, It could attain up to nearly 60 FPS on best scenario (Less scenery and vegetation, clear sunny day) and on demanding scenario (Rain/Snow + Night + More Scenery), It could still attain 35-45 FPS. I think there is a bit more FPS to gain if I use external monitor to connect the game directly to GPU. But of course those amount of FPS only happens when the game doesn't stutter and if I don't run many apps in the background. I'm pretty sure it may be possible for Steam Deck to run this with similar performance or better than I do.

Great job Codemasters/EA for keeping the title playable for a low spec gamers, I'm hoping to see more improvement in the future.