They took off memory leak from known issues even though it is still clearly happening as well…
EDIT: As of today I can’t even launch game at all as well…
1 Like
A new mail has been sent.
It’s mainly selecting cars and waiting in a lobby when it happens.
I want to play this game dammit
1 Like
It won’t even let me send the email… Something about remote server not configured. I sent it to forzafb@microsoft.com
Game just crashed another two times. While testing the car and going back to the menu. Tested the new Silvia and the Aventador. CTD’d on both occasions.
This is ridiculous
1 Like
Guess we’re all gonna have to buy an XBOX ONE X to truly enjoy FM7 without any CTD’s!
Cause I really can’t imagine the “X” version having the same issue like we do now on XBone & PC.
Can’t wait for them YouTubers to start uploading their findings… good or bad.
Refunded because of these issues. Go for refund, only that way T10 will do anything. MS made no problems with getting money back so it’s all fine!
1 Like
I wish I could. I did get a refund once. Unfortunately, after the first patch, I couldn’t help to buy the UE again. I really had faith the game would’ve been fixed. Silly me…
Two most common areas of crashes for me are rewards (credits not XP) screen after a race. Car selection screen after loading up a track.
More common in career mode from observation but not backed by proper testing.
I’m thinking all these performance issues are caused by DRM and other anti-piracy methods. Assassin’s Creed Origin is a beautiful game, with surprisingly not so demanding requirements. Yet players describe very similar issues as in Forza. Some person that cannot be discussed here found that it was the double-layer DRM protection that pushed hardware to the maximum at all times. Look it up.
There is something fishy about how games on Windows 10 run. I’ve noticed it on Killer Instinct, Gears of War 4, Horizon 3 and Forza 7. It almost feels as the game and everything done in it is being heavily monitored. Almost as if our computers are granted the privilege to play it under some one else’s terms, while being under surveillance. There’s not even game files visible.
I accept if it sounds stupid, but it’s how it feels. It’s hard to explain as I am no computer expert. But I feel that instead of getting rid of those heavy anti-piracy systems that I’m sure they are aware that it hinders the performance, they rather just try to go around it, be okay with releasing half-working games, or just put a bandaid on it.
Yeah, i’ve been reading up on this as well. DRM’s encrypting and decrypting of files stressing the hardware while you’re playing the game. No wonder the system can crash at a certain point. And as T10 is doing nothing about the CTD’s at this time, cause it’s been over a month and still NO fix, … like they know it’s not their fault in the program… but the DRM protection itself! And this is something they can’t and won’t be admitting of course. Yep, it’s all very fishy indeed!
That’s kinda weird, because my hardware is hardly ever pushed to the max by Forza. I am however only running 1920 x 1080 on Ultra settings, so higher resolutions may well cause hardware to max out, but I don’t think my CPU has gotten over 70% and GPU about the same. I’m running an AMD FX8350, a Radeon RX570 4Gb and 32Gb RAM. The only time I’ve CTD was using the design editor due to the memory leak, but that’s been fixed now. I play for hours on end too. 14 hours straight on Sunday, 4 hours Monday, 3 hours last night, and no CTD at all.
I was reading about an anti cheat layer in Windows Store games … So it could be a combination of optimisation + DRM + anti cheat that causes the complexities that they are struggling to deal with.
I have the same problemen, sound cutting out etc but the worst one by far is the ctd…
Deleted the game, fresh install but still the same crashes.
But i saw a post about breakout hopper being the worst so after hours playing rise of the supercar lobby … Not 1 crash…
Is thats just Lucky to play a few hours with out crashing or do others ppl have the same
So today I tried to do some online races which I haven’t tried since the latest patch.
I couldn’t even start a single race cause the game keeps crashing.
The crashing is caused by the memory leak that is still persistent in both this and FH3. Nothing will improve until the devs actually deal with the problem.
1 Like
The crashing made the game unplayable. Won’t turn it on until the next patch. It used to crash once to twice a week, now it crashes almost every hour.
1 Like
Same here, just so frustrating and disappointing, wish I could just put it down and wait, but when it works it’s a great drive! Wonder if I’ll ever play it in a stable state…
1 Like
Single player is fairly stable for me. Performance in races is great on ultra settings. Only see a CTD in single player about every 24 hours of gameplay.
However, in multiplayer, I can seldom do more than 3 races without the game crashing. This game is “broken” with respect to multiplayer.
Fortunately, I’m satisfied with single player. But, if I had purchased this for multiplayer, I would have asked for a refund.
win10pro 64bit
i7-4930k @3.4ghz. no overlock
32GB DRAM
evga gtx1080 ftw (2560x1440 @144hz )
samsung ssd 840pro
g27 wheel
I’m seeing a few people with no crashes and they all seem to have something in common: ram. Lots of it.
I was thinking of upgrading to 32gb, since it’s obvious that 20 is not enough. But I’ll wait until I build my 2018 rig. I’ll put all the ram I can so I can play this thing.
My current rig has served me well over the past year, but it’s obvious that games are becoming a bit too much for it. It’s going to the parts bin.
I’ve got 16 GB and my overall specs are more than minimum but less than recommended. It’s been running CTD-free since the Nov 03 update.
Of course, loads of other people are still getting CTD so clearly there’s several root causes for it. However, at least in my case, 16 GB has been sufficient.
My tests since the Nov 3 patch seem to show it isn’t even about the ram anymore. I have 8gb of ram and prior to this patch it would completely overflow it and crash around 99% usage, however with the new patch it crashes around 80-85% usage, indicating the problem most likely isn’t still memory related …