Still no reply on my ticket, its been 19 days
ok
idk anything else, sorry. I hope you figure out your issue soon.
it could be your ram or vram being taken up. do you run anything in the background? like google or other apps.
I also thought of that. But am upgrading my pc in the near future so maybe thatāll help ( probably ram i only have 16 gigs but 20 gigs of vram.
Itās game related. Iāve monitored everything, even with RivaTuner and it seems to be related to how the game writes to storage (saving). Every time Iād hit a prop the SSD would spike and an hiccup would occur. Deleting everything from BreakEffects.xml supposedly āfixesā the issue as itās directly tied to saving/sync. Lowering settings, changing resolutions, capping fps to different refresh rates, nothing works. Iāve tried running it on different drives and itās the same thing. Iām also using a 1TB 970 Evo Plus NVme SSD, so itās not exactly a slow drive. These hiccups also happen when completing seasonal objectives.
This also seems to be more prone to happen with the Microsoft Store version, reportedly. But Iām not sure about this.
One thing that Iām sure is that itās not hardware related, so you can stop bothering with that. Iāve reported this several times to the support team and they never cared, as usual. And itās not like I havenāt tried changing stuff under BIOS and monitoring temps and everything I could think of. My CPU canāt even be overclocked. Itās actually undervolted via Curve Optimizer (KomboStrike) and Iāve tried running it stock and the same thing happens. It also happened back with my previous CPU (Ryzen 5 3600). I also tried using the RAM fully stock and the same thing happens as well.
And this has been like this for me pretty much since the Rally Adventure DLC came out. I canāt even play it anymore because itās a stutter fest there. And itās a shame because I always found it extremely fun to smack onto stuff on Forza Horizon. And that map has a lot of it.
My Specs:
-RTX 3070
-Ryzen 7 5800x3D
-16GB DDR4 3600Mhz
-1TB 970 Evo Plus NVme (FH5 installation)
This was also my last guess so that is somewhat pleasing to know its not on my end.
Still this issue is there for 2 Years nearly so I will just hope for it to be fixed in FH6.
Do you mind if I send them your reply in my ongoing ticket?
Of course, be my guest. And if you need anything else from me, tag me. In fact, Iām gonna create another ticket regarding this as well. Maybe itāll increase the chances of them looking into this a bit more.
P.S - Iām aware that there are also a few reddit threads talking about this. I went to search for them but only managed to find one. But itās still informative, so Iāll leave the link down below for you to check out:
I just dont get why not every PC player is having these issues to my knowledge. It seems very weird, ive noticed that mostly players with newer systems and especially DDR5 RAM dont have this problem or just in very few cases. Could also be related to RAM capacity since we both have 16 GB of DDR4 RAM.
I will upgrade my PC this year so maybe i can confirm this in a few months.
My theory is that, everytime you smash these objects, the game somehow thinks there isnt enough RAM and wants to get the sounds effects from said folders and just doesnt save them in RAM because of suposed lack of capacity.
I want to gather information about the systems on wich this issue exists, to narrow down the cause of it.
What is your RAM generation?
- DDR3
- DDR4
- DDR5
0
voters
What is your RAM Capacity
- 8GB
- 16GB
- 32GB
- 48GB
- 64GB
- More than 64GB
0
voters
What CPU are you running (please specify further in a comment)
- AMD
- Intel
0
voters
What GPU are you running
- AMD
- Nvidia
- Intel
- Integrated
0
voters
Drive, on wich the game is installed
- HDD
- SSD (M.2 or External/Sata)
0
voters
I have no idea. It definitely is very weird. Thatās also the case with the car taillights being too bright. Some people have it, some people donāt. Itās frustrating to say the least.
Could you (and ideally everyone who sees this) tell me the frequency of your ram?
Hi
I have started thinking that it is related to the RAM or the SSD, I tried everything and read a lot and did not find a solution except restarting the game which āsometimesā fixes the stuttering.
some topics mention that it needs a certain compatibility between the RAM sticks themselves, or that the SSD has bad sectors, so I might try getting a single 32GB RAM instead of 2x16GB, then I might try a faster SSD. Anyway, I attached a pic of the RAM and SSD specs on my device:
HP OMEN 15-dc1000ne i7-8750H , RTX 2070 Max-Q
I run the game on 2k - High settings and I get 50-60 FPS with VSync ON
Note: All other games run smoothly, only FH4 & FH5 have this annoying stuttering.
Edit: Stuttering in my case is random and is not related to smashing anything, I used to play FH4 before ~ 3 months without any issues, the problem appeared after either a Windows 11 Update or a GPU driver update, so it might be related to Windows/Driver updates if itās not related to HW.
Okay that is interesting, i think what you are experiencing is still a bit different. In FH4 i dont have this issue.
EDIT:
It seems like your RAM is only running at 2667MHz. Idk if its the max but maybe try enableing XMP in your BIOS.
I have exactly the same problemā¦
No matter what graphic setting, or the target frame rate. If I hit the specific objects, the stutter occur for a fracure of second. Iāve tested this with the lowest preset graphic setting.
- If I lock FPS to 60 ā smash something ā FPS drop to 58
- If I lock FPS to 83 ā smash something ā FPS drop to 79
- And so onā¦
i5-11400 / RTX 4070 / 16 GB DDR4 3200
Microsoft Sotre version, game installed on M.2 SSD
Thank you for your info on your specs too. I think that it has to do something with the RAM, as it seems we all have DDR4 RAM with no higher speeds than 3200MHz.
I hope soon i will be able to try out with new RAM and either confirm or deny.
EDIT:
I also asked ChatGPT about this (i know what your thinking) but its suggestions have brought me further than forza support so here is what it said:
FH5 relies heavily on CPU ā RAM ā GPU communication.
- When crashing into objects, the game dynamically loads physics assets and recalculates collisions.
- Lower RAM speeds = slower data fetching = stutters.
What You Can Try
- Overclock Your Current RAM to 3600MHz (if it supports it).
- Go to BIOS and set RAM to 3600MHz manually (try with 1.35Vā1.4V).
- Run a stress test (MemTest86) to check stability.
- If unstable, try tightening timings instead.
- Example: Instead of 3200MHz CL16, try 3200MHz CL14 (lower latency helps).
- If you upgrade, get 3600MHz CL16 or better.
If your try this PLEASE BE CAREFULL AS THIS CAN END BADLY first of all make sure you know how it works and make sure your RAM supports this.
I dont take responsibility in what youre doing.
I donāt know what stutter really means, but my problem is not just FPS drop, the game freezes randomly for ~ 0.5 - 1 second. like a total freeze that makes me lose track of the game, and it only happens in FH4 & FH5 ā¦ if not stutter, what is the name of my issue?
No you are right it is a stutter, but since your stutter occurs under different circumstances, its probably something else causing it.
I have a PC with DDR5 memory and the problem exists, but it is mitigated if the number of fps is not very high, for example with a 4070 Ti in Extreme (Textures in Ultra) with RT in Extreme, the fps go between 65 to 90 fps and there the stuttering is almost imperceptible, or in the frametime graph it is not noticeable.
But if I activate Frame Generator, the fps increase from between 90 to 130 fps with the same configuration, but there the stuttering when colliding with objects or passing certain areas in the Rally Adventure map, the stuttering and jumps in the frametime become noticeable.
So although DDR5 does mitigate the problem by having more bandwidth, it would not solve it, since the readings continue to occur and the higher the framerate, the more noticeable the stuttering.
Well that is quite demotivating, to say the least.
But still knowing that the issue will get better with better RAM, is somewhat good, since FH5 is in its last days for good now after 3 years.
I just hope this issue is eliminated in FH6.