Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
To help us most effectively identify the issue we'd greatly appreicate if you could provide more specifics and answer some questions:
1. What was the exact loadout used when this occurred?
2. Have you had it occur on different loadouts?
3. Has it always been the exact same Ghast III or has it occurred in other Layers/Phases?
4. When executing the Ghast III - are any other inputs being pressed/held?
5. Have you got a video/recording of the issue occurring?
6. Are there any other details that you think could be relevant to the issue occurring?
1. Slow-fire/spin pistols / 3-hit spin sword / sniper rifle / build wrath on health armor / unpredictable (can't remember wording) wrath gem
2. I've had it occur with only the above loadout so far
3. It's exactly the same one and only the one prior to the transition from the 2 to 4 part laser cage section
4. Nothing is being pressed or held--shoot heavy weapon once (sniper rifle) to stun, get close, press Y, go into execute animation, corpse stays
5. I do not have recording but will try to capture some today if I can recreate
6. It could be with how soon after stun I am killing the enemy, but I can't imagine that is the case because if it were a frame window there's no way I would have hit it three times without trying to do so. If anything it seems like it is something unique with that enemy specific to the execution action. In other play on the same difficulty I was able to execute the same enemy without issue.
It is also perhaps worth noting that this soft-lock can be circumvented by NOT executing the Ghast III (as it's apparently called)--if you take it down purely with heavy weapons fire or normal attacks its corpse dissipates properly.
Sorry I wasn't able to provide better information as the bug was one I encountered last night and just reaching it on the highest difficulty is something I could not do consistently. I will set aside some time tonight to attempt to recreate the bug.
If you are keen to keep helping the team, they have kindly requested if you could please send us through your game logs.
To do this:
1. Navigate to this folder on your PC: C:\Users\{username}\AppData\LocalLow\Playside Studios\KILL KNIGHT
2. Please copy the Player.log and Player-prev.log file to a seperate folder
3. Zip the folder
4. Upload to our Zendesk - https://playside.zendesk.com/hc/en-us/requests/new?ticket_form_id=10810187909263
Also absolutely no need to apologise, we greatly appreciate all the time and effort you've been putting in to help us resolve this.
I wrath bursted so he was purple. The ♥♥♥♥♥♥ part is I think I somehow managed to execute this enemy AS he was disappearing, like he started to go under,ground and he popped back out of the ground when I stabbed him. I immediately knew something slightly unusual had happened. (maybe he had inflictum still when this happened too?)
I had many attempts before this happened where he died just fine. Now, he will never disappear when I kill him on any subsequent attempt. The game then will not progress past the laser-box section (after killing the 2 pursuers). Verifying game files doesn't work. However, reinstalling the game cleared the bug it seems.
Another bug on Switch version: After clearing the final level for the first time, the window that pops up showing the Sufferance difficulty is unlocked is frozen with no way so close it. Was playing it docked. After closing the game from Switch menu and restarting everything was fine. Screenshots below.
Screenshots of the above issues[imgur.com]