Hi @orvis25,
Your default GPU is currently set to AMD Radeon™ Graphics. Which is likely resulting in your crashes as it cannot handle the demand. Do you have another GPU that isn’t being detected?
Please check out this article:
Hi @orvis25,
Your default GPU is currently set to AMD Radeon™ Graphics. Which is likely resulting in your crashes as it cannot handle the demand. Do you have another GPU that isn’t being detected?
Please check out this article:
Hi @orvis25,
Each log shows that you’re running into a Deadlock
type crash - which are difficult to troubleshoot.
Your GPU being below minimum requirements shouldn’t outright prevent you from playing, but it will very likely result in more instability than usual.
Firstly, I recommend ensuring you have the latest Windows updates, BIOS update and GPU drivers installed.
We’re working on many crash fixes and overall stability improvements. In the mean time, I suggest running through our general crash solutions, and checking after our next hotfix whether you still run into similar crashes.
@orvis25, apologies for the delayed reply! This slipped through the net.
I’ve just messaged a couple of our developers to see if they have any input or advice here. Due to the late time of day now, it’ll likely be tomorrow that I get any response.
I’ll update you when I hear back from them.
Hi @orvis25,
I’m still waiting to hear back from developers. I’ve pinged them an additional time and will keep chasing.
Apologies for the delay on this, and thank you for your continued patience.
@orvis25, a developer has suggested the following tests to see if there’s any improvements -
@orvis25 A few developers have discussed this. Feedback has been that you’re running below minimum specs, and although you played before, this was essentially quite lucky.
Minimum specs require a dedicated GPU with at least 4GB of GPU memory, and 8GB RAM. As you’re using an integrated GPU this means you’re sharing GPU memory with RAM, so you would need to have at least 12GB of RAM, but with memory left over for your OS and other things. So, 16GB+ RAM is likely needed to run the game with an integrated GPU. If you have below this, it could explain the ‘out of memory’ crashes.
As for a command/code to force textures - there isn’t anything we can use to do this right now. However, the setting for Texture Resolution should be returning in our next update. So, when this is implemented this is something you can use to hopefully improve things.
Please do let us know how it goes with the texture setting after the update
In answer to your questions -
The only reason would be a bug in the upscaling implementation, as FSR2 hasn’t been in our code base for as long as the native rendering. Though, the main reason to try it, is because it’s one of the changes we have made since the betas (to default to FSR upscaling, and updates to our FSR implementation) and we wanted to make sure it was not the culprit.
We have for a duration had additional debugging enabled in builds to find stability issues. This has meant a slight reduction in performance. With the last patch, some of that debugging information was disabled and we solved some issues with the default settings for some players with hardware that does not support raytracing that may have been affecting you. For those changes to take effect you must allow the launcher to reset your user settings and avoid manually modifying your user_settings.config file. Some community guides at current unfortunately provide faulty information on how to manually edit user settings to gain performance.
We are focusing on solving the performance issues that we know of. We’re also continually optimizing our systems for each patch - but this is likely in smaller increments and may not be noticeable.
It is however hard to know exactly why you are seeing performance degradation, and we can’t guarantee if our fixes/improvements in our upcoming update will have solved your issues specifically.
@orvis25
Thank you for detailing your findings with FSR. I’ve passed this on to the development team, and we’ll be investigating as it definitely sounds off that we see higher memory usage with FSR 2 on than off.
Regarding 2.2, at this time I can’t speak to any future plans. I’ve mentioned this internally though, and it’s a discussion point for sure.
After the new patch, the Texture Resolution setting may allow you to run the game better. Though, you are still treading a very thin line memory-wise. Unfortunately, as we are not actively supporting your setup with an integrated GPU and 8GB RAM you will likely continue to experience issues with running out of memory every now and then, for example during some levels that might be more memory heavy.
That’s strange - do you not have the ‘Texture Quality’ setting under ‘Advanced Graphics’?
image3440×1440 239 KBI’ll speak with the developers again and see what they say. I’ll update you when I hear back from them.
I’ve checked and the setting should absolutely be present - though the setting is only available in-game, and not from the launcher settings. Could this be why?
The developers have also said that setting the graphics quality will also affect texture quality so if you have graphics preset to low the texture quality will also be set to low when the game starts.
Thank you for the feedback - I’ve passed this on to the developers once again. We’ll need to investigate the possibility of memory consumption increasing.
As you are running below minimum specs memory-wise, and there isn’t an immediate solution or fix we can provide, I’m happy to request a refund for you.
I appreciate that this isn’t ideal, but please let me know if this is something you’d like to do.
Thanks @tamalero. The data from these crashes show that you’re running into a GPU Hang, and not specifically an issue with your GPU being Out of Memory. We’re working to resolve generic GPU crashes as a top priority still and continuous improvements should be seen with each update!
Your crash error -
HRESULT: 2289696773 = DXGI_ERROR_DEVICE_REMOVED: GetDeviceRemovedReason() = DXGI_ERROR_DEVICE_HUNG
orvis25’s error -
HRESULT: 2147942414 = E_OUTOFMEMORY