FatsharkLev

Queue fixed once again

The Access Violation crashes all seem to differ. I’ve added them to our database. Apologies for the inconvenience.

I’ve added this crash to our database - thank you for the report!

I’ve notified a backend developer - this should hopefully be resolved shortly.

Just to update - we’ve made progress on a permanent fix which should be coming real soon. I can appreciate how frustrating this issue is - apologies again to anyone affected.

I’ve notified a backend developer - this should hopefully be resolved shortly.

Just to update - we’ve made progress on a permanent fix which should be coming real soon. I can appreciate how frustrating this issue is - apologies again to anyone affected.

@orvis25

Please do let us know how it goes with the texture setting after the update

In answer to your questions -

1. 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.

2. We have for a duration had additional debugging enabled in builds to find stability issues. This has meant a slight reduct...

Hi @nudsu1,

For performance, I recommend to try disabling the Steam Overlay (if enabled) as this has been known to cause noteable performance issues, and other potential solutions here:

@t3blake, The original crash reported here is still under investigation. It would be great to check if you’re running into the exact same crash, or a different one.

Could you please provide a crash report or your console log so we can take a look?

@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 implem...

Hi @Tingles,

As for the first issue, this will be due to bad luck. May the Emperor bless your coming missions!

As for contract progression, there is a known issue we are aware of and investigating. I’ll merge this with the pinned topic.

Apologies for the inconvenience whilst we iron this out!

Hi @winzer102h,

We’ve made some tweaks to try to fix this - could you please check again and see if you are now able to purchase sale items?

Thank you!

@orvis25, a developer has suggested the following tests to see if there’s any improvements -

• Try running without FSR enabled
• Alternative test, to try FSR 1 instead of FSR 2

We’re aware of this issue and plan to have a fix out soon.

Apologies for the inconvenience in the mean time!

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.

I’ve added this crash to our database for investigation. Thanks!

It’s a good question, and something we did discuss. Though, it isn’t something we can safely automate without days of testing first. We decided we’d use those days to work on a permanent fix and eliminate the issue instead.

Positive news - progress has been made, and we’re testing a fix internally.

Hopefully we’ll be rid of this once and for all soon!

It’s a good question, and something we did discuss. Though, it isn’t something we can safely automate without days of testing first. We decided we’d use those days to work on a permanent fix and eliminate the issue instead.

Positive news - progress has been made, and we’re testing a fix internally.

Hopefully we’ll be rid of this once and for all soon!

Update! This issue has been investigated and now has an internal fix.

It may not quite make it into our very next update now, but if not, it should come in the one to follow.

Thanks for confirming. We’ve received other similar reports from players based in Korea. We’re looking into it!

Apologies for the inconvenience in the mean time.

Hi @winzer102h,

Which region are you playing from?