Hey knights!
Just wanted to know if anybody has got info about a bugfix for KDC?
Known bug is: game crashes after loading…happens on AMD graphic adapters runnin´ with latest Crimson driver…
When will this be solved?
greetz
Yes, known issue, I have it using Crimson.
They said yesterday, I think, that it could be solved in two days.
I will ask about it tomorrow in the office. 
Okay, I have some news about it, but unfortunately they are not good ones.
There is no easy way to fix it, because it is a bug about the newest AMD Crimson driver. It do have some problem with the new SVOGI global illumination lighting technique and reflecting light. We would have to rebuild the Alpha around this bug and shut down the new lighting system.
AMD already knows about this as Crytek is in contact with them and also we told AMD about the problem but didn´t get an answer about it yet. We will find a solution for it in the Beta, nevertheless if AMD will fix its driver or not, but it will be to much work to make a new alpha build about it.
2 Likes
That’s too bad. Because then 50 € expensive Alpha Access is worthless to me. As I said: It’s a pity I would have liked to take part in the development of the game.
1 Like
Yes, that is understandable, and we also are not happy about it.
The good thing is, some of the testers told me, we already have a fix for the beta, so it is confirmed that the Crimson driver will be no problem with the beta, but right now with 0.5 Alpha we can not make a fast fix about it.
There is a way you can start the game. You can put into the system.cfg or the autoexec.cfg in kingdom come the term “e_svoTI_Active=-1” or "e_svoTI_GsmShiftBack=0"
But the game will crash in some place anyway. Especially if you can see water. And that is the problem.
I’m not mad, but only a little disappointed. I will practice my patience and look forward to the launch of the beta.
Thank you for the fast reaction.
3 Likes
Same here, sad news, but we have to assume them.
Found this while ago, here a link
CRYENGINE 3.8.6 Hotfix
Our first update of 2016 is a nice hotfix for 3.8.6 that addresses some really important issues that kept our users up at night. The main reason for the hotfix is actually an incompatibility of our WAF build system with the latest Visual Studio 2015 Update 1. So guess what? We fixed it!
Here’s the full list of changes that went in:
• Fixed compile problems with VS2015 Update1.
• Fixed AMD new Crimson driver crash.
• Fixed a bug where an area proxy was not properly updated if a shape was modified.
• WAF: Handle new Windows SDK versions more gracefully by 1) trying to pick a Windows SDK version that roughly matches the preferred versions by the active compiler, or 2) as a fall back picking the highest installed Windows SDK version.
• Fixed parent particles never de-allocated - which exhausted the particle pool.
• Character Tool: Fixed where an empty AnimEventPlayer class returned true in its Play method even though it didn’t play anything. This caused the CharacterTool to stop playing audio events.
• Character Tool: Fixed where audio triggers did not follow the bone that they were assigned to.
• Workaround for vegetation “blend with terrain color” flickering.
• Fix for flickering GI on glass shade.
2 Likes
Oh so there is hope… and I just recently redownloaded the alpha >.<
im downloading lates cry engine sdk maybe i can get those new dll’s and simply overwritte the ones that are in game folder … will see
So this is something we have to do or that developers have to do?
Thanks for this info.
no unfortunately swapping just sdk files doesnt work
it has to be kingdomcome compiled
so i guess we need to wait for a small game patch just with updated cry engine
1 Like
There is another slightly older thread discussing this here Game crashing at startup
Also using “e_svoTI_Active=-1” in my config works so far. The game starts to main menu and I can change settings and even load in. It crashed when I looked around but that could have been due to me overdoing it with the graphic settings.
If this Alpha gets running to game graphic engine u should indeed play a bit with framerate targets and other graphic settings via crimson and ingame especially.
VRAM overflow happens many times. Even with an 4GB graphics adapter…
Hope i could help a bit…
Greetz Hardy