I'm getting crashes after the update. I just got the game last week played it a couple of hours and shut if off. I had to work for a week and couldn't play. I fire the game up tonight it updated the patch and low and behold it crashes to desktop about every 5 minutes with no crash report and game is still running I can hear the sound but there's no video. I have to restart my machine to get back to desktop it's quite annoying to tell the truth. AAA title that's broken imagine that, I hope there is a fix soon cause this is for the birds.
intel i7 4790k
gskill 16gb 2400 ddr4
evga 980ti sc sli
windows 10 64bit
everything is up to date. This and the division are the only games giving me a problem.
same here ...Since the 1.1.5 patch, cant play for more than 5 mintues. freezes or close to desktop.
amd fx6100 @ 4200
gtx 1060 6gb
12gb 1600 vengeance.
Currently, my game crashes after playing for a random amount of time. Sometimes, it's as low as 5 min and other times, it can be after 4-6 hours.
Every times since a couple of day, I took note of what was happening in-game when the game crashes and there's 1 single common action that is taken every times the crash occurs.
I'm pretty sure (for me at least) the issues comes with some kind of looping error within the UI management.
To be more precise, at random times, the creation of an UI element goes wrong and from it comes a kind of memory leak effect (the game keeps looking for an UI element in the scene while it doesn't exist) and some kind of security measure set in-game to avoid data corruption simply close the application on the spot which seems like a Crash-To-Desktop. This would explain why, at the closing of the game, there's no Crash Report to be send and why even Windows doesn't register any kind of errors in its Event Logs.
Up to now, the number of crashes occurred when the following kind of action took place :
Spotting:
Some crashes occurred when the orange circle appears above an enemy's head.
I see the big flashing white/orange spot around the enemy (which takes around 0.5-1 sec max when he's spotter) and then the game freeze (FPS drops like hell) and the game close in the following 1-1.5 sec. (It's takes around 2-3 secs to crash in total, but during it, you can shortly notice what's going on.) This seems to happens also in Coop/Online when another player spot an enemy and it appears on your screen. (This explains why Coop seems to crash more often as the amount of spotting increases.)
This is the most common thing happening when the game crashes and would also explain why it crashed mostly when you're on foot and (almost) never when you're solo in a vehicle.
This can also happens when the AI spot an enemy on a AO site.
Generating the Map or Target's Graphics:
It rarely happened (only twice) when I opened the map, but it did also happened when I zoom out of the map onto the Target Graphics. The crash seems to occurs when one of the many portrait comes in. (Usually, one of the lower/right ones as they are instantiated slightly later.)
When the UI updates the button display (Controller/Keyboard):
This is something I have noticed too. As you move the mouse or press a keyboard button by mistake as you're using a controller (or the opposite. You accidentally move/press a button or trigger on your controller), the UI update its visual controls schemes in real-time. That's cool, but some rare times, it crashes the game the same way as the 2 other previously mentioned way.
In all those instances of the crashing situation, the most common point is that something in the UI is being generated/instantiated.
I have tried :
• Turning down the graphics to medium or low.
Didn't change the occurrences of crashes nor the effect explained above.
• Turning off the Controller Support
It did help at avoiding updating the UI, but the crashes still occurred during both the map & spotting circle are being generated.
• Verify game's files
Didn't change anything.
• Reinstalling a previous version of the NVidia Drivers (in case).
Didn't change anything.
• Reinstalling the latest version of the Nvidia Drivers.
Didn't change anything.
All the other drivers are up-to-date including the BIOS.
Intel i7 2600 @ 3.4 GHz 3.4 GHz
12GB RAM
64-Bits Windows 7 Home Premium
NVidia GeForce GTX 1060 6GB DDR5 (Zotak compact edition)
I tried monitoring the PC's resources as I was playing the game and, during the crash, there's not much of a change in the amount of heat or amount of data being stored/managed when the crashes occurred, but there is a small spike in both the GPU and RAM. (This monitoring includes the HDD, GPU, Processor and RAM usages.)
Even so, the game never exceed the usage of approx. 50% at most of the available memory (both VRAM and RAM).
My PC fans rarely goes into cooling mode when playing the game. It does some times, but there's not signs of the temperature being really high.
I'm able to play with all the graphical option maxed (at around 28-30 constant FPS), but I'm not a big fan of any kind of blur so I usually turn off Motion Blur and the DOF. Call me an old-school gamer if you want, but I like to be able to focus on everything on screen... not just what's is focused on. Hahaha. Got a constant 59-60 FPS when turning off all the blur effects + Gods' Ray + Advanced Vegetation. (I know the drop in FPS is mostly due to my processor which is getting old, but I'm still "getting used" to better graphics since I updated my GPU only 1 month ago from a Zotak GT730 4GB DDR3 to the GTX 1060 6GB DDR5).
From my own experience as a developer, I wouldn't be surprised if the issues comes from one (or more) of the many part of the Anvil Engine when it comes to managing the Z-Buffering involved with the in-scene UI. Could easily be a common Z-Buffering Sink where one of the shaders used by the engine fails to render something on screen because the UI element is either missing or it fails to analyses the pixels' values. (For those who ignores it, Z-Buffering/Buffer is the part of the rendering process where visual things like transparency is being calculated so that the value of any materials rendered behind a partially transparent object (or UI which is actually like a flat face with a transparent texture) can be added to the pixels values of the transparent object in the right order.
(It's possible to render transparency without Z-Buffering, but doing so involve the usual problem of having wrong priorities on the rendered pixel. For instance, having the object rendered faster being the one being rendered later regardless of what's closer to the camera/rendering point.)
I still haven't tried to turn off all the in-scene UI element in the game because... well... I'm playing solo and highly make uses of the UI element for now (especially spotting)... But I will try it at some points to see if this helps or not.
Still there is not a single word from ubisoft on this issue? Idk you guys but im not buying anything more from ubisoft until 3 months have passed after the release, just to make sure i can actually play the game im buying.
And that is in the case i buy anything from them after this crash fest.
That's all I get Oh no , it crashed it looks like it stats but black screen then Oh no , it crashed! send error report to bla bla bla
GTX1080Ti
32 gigs of ram
1 terra byte SSD
Correction. Still the same issue can not play nor have a refound, ty ubisoft, never wasting my money again in your bugs.
Through testing multiple configurations of settings and boot options, the set up that works best...
1. All settings can be Ultra if you have an adequate PC, but TURF MODE SHOULD BE OFF.
2. No boot up options applied in steam.
3. Video settings should be set to WINDOWED IN GAME.
Aside: I chose the option to run Steam as an administrator, but am not sure if this has affects anything. Additionally, you will still have sound occasionally cut out for a second or two while in game, but it won't crash and return to desktop.
Happy Hunting.
Hi guys, I was having this issue loads, tried so many things, turned out was something as simple as my CPU or GPU overheating and auto crashing the game.