It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Community
ControlCTD in Anchor fight(104 posts)(104 posts)
(104 posts)
Pages:
1
2
3
4
5
6
7
This is my favourite topic
Posted April 29, 2021
Another user had the same problem a few months ago while I using the Epic version did not experienced the issue at all. We ended up mixing both versions and his GOG version stopped crashing so it is definitely a problem with the GOG version. I told 505 game multiple times in their discord but so far no definitive reply which is a pity for all who own the game on GOG.
Post edited April 29, 2021 by MarkoH01
Posted April 29, 2021
avatar
MarkoH01: Another user had the same problem a few months ago while I using the Epic version did not experienced the issue at all. We ended up mixing both versions and his GOG version stopped crashing so it is definitely a problem with the GOG version. I told 505 game multiple times in their discord but so far no definitive reply which is a pity for all who own the game on GOG.
Can you elaborate a bit more, what you mean with "mix". Just the game exe's or what?
Post edited April 29, 2021 by russellskanne
Posted April 29, 2021
avatar
MarkoH01: Another user had the same problem a few months ago while I using the Epic version did not experienced the issue at all. We ended up mixing both versions and his GOG version stopped crashing so it is definitely a problem with the GOG version. I told 505 game multiple times in their discord but so far no definitive reply which is a pity for all who own the game on GOG.
avatar
russellskanne: Can you elaborate a bit more, what you mean with "mix". Just the game exe's or what?
As far as I remember we had to take the complete main folder.
Posted April 29, 2021
Having the same issues and tried the suggested workarounds, still crashing as soon as the boss opens. GOG users really are cursed. Will send a ticket to the support, maybe they can arrange an answer from 505 or Remedy.
Posted April 30, 2021
avatar
argenisX: Give those all together a try, that's a bit insane, considering that the boss itself is also kinda hard to beat until way later on.
avatar
Manaflower: Those are all things I included in my attempts. But yeah, probably RTX specific issue and not just related to having raytracing enabled, just having the card seems enough.
Nope hqppen the same with a GTX 970
I still have the chance to see it's attack for three to five time
I have 16 Go of Ram so try this, teleport yourself to the anchor control point do a complete computer restart do nothing else than start the game and try the figth
Posted April 30, 2021
I have the problem that the boss does not appear at all

missing boss
Post edited April 30, 2021 by RMT1983
Posted May 04, 2021
high rated
So I tried again to get some attention form 505 on their official discord channel. Unfortunately all I was able to get is this reply:

"Unfortuantely, there isn't anything that we can do about this from our position in support. I understand that this has been reported, but it still helps for every person having this problem to submit their own seperate report so that the team can see how prevalent this issue is. If they think only one person is having the issue then they won't fix it (I hope that makes sense). Also, they don't look through unofficial forums so if they aren't posting their issues where the Control team is looking, then they might as well not have reported it at all.

So in summary, anyone that is having an issue with the GOG specific Anchor issue (or any issue for that matter) should report their instance of the issue to the bug form pinned at the top of this channel."

So I ask everybody who has the issue of the game crashing when fighing the anchor to post an official bugreport here:

https://fs30.formsite.com/505games/control/index.html

The more people will report the issue the higher the chance that this will ever be fixed and obviously it is not known to Remedy/505 that this issue is reported quite often and only in the GOG release. So PLEASE report.
Posted June 22, 2021
Same here, just got the game, only had 1 CTD in the game, before this 100% reproducible CTD on this boss.

Win 10 2004 + 3700X + 5700XT.
Given lots of different CPUs & GPUs are affected, I tend to think it's a purely software based issue.

I managed to fight the Anchor without a CTD by launching directly the Dx11 version of the game .exe, not through Galaxy (which by default runs Control.exe first, which then starts Control_DX11.exe) .
Post edited June 24, 2021 by elgoretto
Posted July 18, 2021
Just wanted to throw my 0.02 cents here. I'm running Win10 x64, Ryzen 5800X, 16gb RAM, RTX 3060. The only way I was able to get through this fight was to run the game at 720p low preset windowed. I ran it at 768p medium preset and it would run ok until about half the fight when he spawns more enemies. Everything else crashed almost right away. I tried a bunch of the suggestions here but none worked. I issued a report in the linked page...
Posted July 20, 2021
What worked for me was setting to the process affintiy in taskmanger for game to the first 4 cores.

I think there a deadlock condition occurring due to crappy multthreaded programming.
Posted September 13, 2021
Here's my experience with this problem, hopefully it will be of use to others. This post necessarily will contain spoilers about the boss fight and its attack pattern.

TLDR: Rush whatever platform the boss is currently preparing to unleash its attack on.

For me, this prevented the gun-toting hiss from spawning on said platform. THEY are the cause of the crash (for my system at least). The clock spewing attack that the anchor is unleashes is just correlation.. not causation. So long as you stand to the side of the platform, it's attacks will mostly miss you and you can dart ahead to its next attack location. It attacks in a clockwise pattern (appropriately) so get ahead of it. Once it opens up to attack use launch to chuck anything (mostly likely a clock) into the glowing orb in its maw. If you time it right, this will negate its attack, which while not the reason for the game crashing, will at least keep you safe. It will spawn in kamikaze hiss that fly towards you to blow up.. These are fine.. They didn't crash the game for me.. Only the gunner hiss do. If you are keeping just ahead of the anchor, being on the platform it's prepping to attack, these will not spawn.

I ran the game at the full nVidia optimized settings for my card and the clock attack goes off without a hitch if you can keep the gunner hiss from spawning in.

I tried all the recommended fixes on gog's/steam's forums and nothing worked. This includes: lowering all graphical settings to their lowest/disabled values with a resolution of 640x480 and turning in-game volume all the way down(?), turning off full screen optimization in the executable's compatibility settings, forcing physX to CPU mode only. There was one about swapping dll files around.. Nothing worked.

I have reported my experience to Remedy/505.

CPU: Intel i7-6700K @ 4.0 Ghz
RAM: 32GB DDR4 GSkill Ripjaw series
GPU: nVidia GTX 970 FTW2 (4GB video ram)
OS: Windows 10 Pro (up to date with as much telemetry disabled as possible ;)

Edited: fixed typo
Post edited September 15, 2021 by Phin77
Posted October 10, 2021
I tried disabling fullscreen optimization and forcing CPU PhysX, but neither of these helped me avoid the Anchor CTD. What worked was going into Nvidia Control Panel and locking the max frame rate to 60 fps. After making that change, I was able to take down the Anchor- with no need to dial down any settings or use the one-hit kill assist.

CPU: i9-10900KF
GPU: RTX 3080
RAM: 32 GB
Windows 10 Pro
Playing with max settings, 2560 x 1440, RTX, and DLSS.
Posted October 14, 2021
avatar
ProphetOfMetal: Same here with a 3600X, 2060 Super, and 16gb DDR4. Got through the fight using the following:

1. Windows - Run DX11 version
2. Windows - Windows 7 compatibility mode
3. Windows - Disable full screen enhancements
4. Game - Turn all graphics settings to lowest possible
5. Game - Turn off all graphical enhancements
6. Game - Lower the resolution to smallest possible (640x480)
7. Game - Turn sound all the way down

This seems like a memory allocation error with the vast number of objects the game creates, so shrinking the memory footprint using the lowest settings should work. Even with these settings I had to make sure I killed all of the enemies to prevent a crash. Thankfully there is a savepoint right next to it, but hopefully this gets corrected at some point.

Also, you don't need to use the Red Clocks to deal massive damage. Any clock will do.
This worked for me (except I used 720p resolution), thank you.

My specs:
3700X OC/UV, 3080FE UV, 32go DDR4, WIN10 PRO.
Post edited October 14, 2021 by Ulk007
Posted October 31, 2021
avatar
Phin77: Here's my experience with this problem, hopefully it will be of use to others. This post necessarily will contain spoilers about the boss fight and its attack pattern.

TLDR: Rush whatever platform the boss is currently preparing to unleash its attack on.

For me, this prevented the gun-toting hiss from spawning on said platform. THEY are the cause of the crash (for my system at least). The clock spewing attack that the anchor is unleashes is just correlation.. not causation. So long as you stand to the side of the platform, it's attacks will mostly miss you and you can dart ahead to its next attack location. It attacks in a clockwise pattern (appropriately) so get ahead of it. Once it opens up to attack use launch to chuck anything (mostly likely a clock) into the glowing orb in its maw. If you time it right, this will negate its attack, which while not the reason for the game crashing, will at least keep you safe. It will spawn in kamikaze hiss that fly towards you to blow up.. These are fine.. They didn't crash the game for me.. Only the gunner hiss do. If you are keeping just ahead of the anchor, being on the platform it's prepping to attack, these will not spawn.

I ran the game at the full nVidia optimized settings for my card and the clock attack goes off without a hitch if you can keep the gunner hiss from spawning in.

I tried all the recommended fixes on gog's/steam's forums and nothing worked. This includes: lowering all graphical settings to their lowest/disabled values with a resolution of 640x480 and turning in-game volume all the way down(?), turning off full screen optimization in the executable's compatibility settings, forcing physX to CPU mode only. There was one about swapping dll files around.. Nothing worked.

I have reported my experience to Remedy/505.

CPU: Intel i7-6700K @ 4.0 Ghz
RAM: 32GB DDR4 GSkill Ripjaw series
GPU: nVidia GTX 970 FTW2 (4GB video ram)
OS: Windows 10 Pro (up to date with as much telemetry disabled as possible ;)

Edited: fixed typo
I have the same setup as you, except that I'm running a 2060 Super. I had to rush through the battle as quickly as possible, using explosives and dash-gliding.
Post edited October 31, 2021 by Crazy_McGee
Posted November 03, 2021
avatar
Phin77: Here's my experience with this problem, hopefully it will be of use to others. This post necessarily will contain spoilers about the boss fight and its attack pattern.

TLDR: Rush whatever platform the boss is currently preparing to unleash its attack on.

For me, this prevented the gun-toting hiss from spawning on said platform. THEY are the cause of the crash (for my system at least). The clock spewing attack that the anchor is unleashes is just correlation.. not causation. So long as you stand to the side of the platform, it's attacks will mostly miss you and you can dart ahead to its next attack location. It attacks in a clockwise pattern (appropriately) so get ahead of it. Once it opens up to attack use launch to chuck anything (mostly likely a clock) into the glowing orb in its maw. If you time it right, this will negate its attack, which while not the reason for the game crashing, will at least keep you safe. It will spawn in kamikaze hiss that fly towards you to blow up.. These are fine.. They didn't crash the game for me.. Only the gunner hiss do. If you are keeping just ahead of the anchor, being on the platform it's prepping to attack, these will not spawn.

I ran the game at the full nVidia optimized settings for my card and the clock attack goes off without a hitch if you can keep the gunner hiss from spawning in.

I tried all the recommended fixes on gog's/steam's forums and nothing worked. This includes: lowering all graphical settings to their lowest/disabled values with a resolution of 640x480 and turning in-game volume all the way down(?), turning off full screen optimization in the executable's compatibility settings, forcing physX to CPU mode only. There was one about swapping dll files around.. Nothing worked.

I have reported my experience to Remedy/505.

CPU: Intel i7-6700K @ 4.0 Ghz
RAM: 32GB DDR4 GSkill Ripjaw series
GPU: nVidia GTX 970 FTW2 (4GB video ram)
OS: Windows 10 Pro (up to date with as much telemetry disabled as possible ;)

Edited: fixed typo
Swapping .dlls worked for me at first but not for the repeat fight of the boss in the DLC. In that instance I had to do exactly as you OR if the hiss DO spawn you MUST kill them before he unleashes his attack. If they are despawned/killed before his vomit it won't crash.
Pages:
1
2
3
4
5
6
7
This is my favourite topic
Community
ControlCTD in Anchor fight(104 posts)(104 posts)
(104 posts)