GTX 800M or lower owners READ IT!!!

[Yoki]

Hello
I suppose that you have crashes with game like I have

I have bad news for you. This is official answer from technical support:
"Unless Nvidia releases a new driver, you'll have to play the game with the branch legacy3 (OpenGL 3.5). Unfortunately Chaos and future expansions won't work. I'm sorry for this."

At first I thought that I have to wait for a new driver, but after visiting nVidia website I was disappointed: from April 2019 nVidia stopped support GPUs GTX 880M or lower and the April driver was the last one, It will be available just Critical security updates through April 2020.
nVidia info https://nvidia.custhelp.com/app/answers/detail/a_id/4779
full list of GPUs: https://nvidia.custhelp.com/app/answers/detail/a_id/4780

It means that we can't play in ChaosSM DLC and all futures releases.

I think that if you are not going to change your laptop in nearest time, you should refund for ChaosSM DLC via STEAM support

[void]

Hello, the game should work on a 880M with Vulkan using those April drivers and we'll keep investigating the Vulkan issues some people are still having (new build will go to beta later today). However, I fully understand everyone who doesn't feel like waiting.

[Yoki]

Ursprünglich geschrieben von void:

Hello, the game should work on a 880M with Vulkan using those April drivers and we'll keep investigating the Vulkan issues some people are still having (new build will go to beta later today). However, I fully understand everyone who doesn't feel like waiting.

I have 765M and it doesn't work, maybe owners of 880M are lucky ones. I can wait for a long time, while you are fixing bugs. But technical support said that problem is old GPU driver and only way to solve this problem is waiting for nVidia update, but it will never happens - Reasons I've described.

Or do you think this problem can be solved in other way (e.g. on your side)?

[TOFFster]

Only the 830M and below of the 800M series doesn't support Vulkan as far as I am aware.

[Yoki]

Ursprünglich geschrieben von TOFFster:

Only the 830M and below of the 800M series doesn't support Vulkan as far as I am aware.

If we go here https://developer.nvidia.com/vulkan-driver
We can see that all 600M,700M,800M,900M series have to support Vulkan
But I can't check it and I've renamed the topic

[void]

I would be highly surprised if the problem can't be fixed on our end. While driver regressions are a possibility, I think NVIDIA would update the driver if it's really broken.

[TOFFster]

Ursprünglich geschrieben von Zepp_Ditrih:

Ursprünglich geschrieben von TOFFster:

Only the 830M and below of the 800M series doesn't support Vulkan as far as I am aware.

If we go here https://developer.nvidia.com/vulkan-driver
We can see that all 600M,700M,800M,900M series have to support Vulkan
But I can't check it and I've renamed the topic

There is also an 820M which does not support Vulkan, but you're right, the 830M does.

[Yoki]

Ursprünglich geschrieben von void:

I would be highly surprised if the problem can't be fixed on our end. While driver regressions are a possibility, I think NVIDIA would update the driver if it's really broken.

I hoped that beta v1.3.3 helps. But not - Vulkan crah
This is my log file https://drive.google.com/file/d/1mQAGTv1d7PPu0fn-DfIMZ9uE4r_-ilu-/view?usp=sharing

[Arkaeon the Chosen]

I had the same problem with my GTX 760M , Vulkan errors no matter the latest drivers installed.

Honestly i really don't understand how devs of an already niche genre as turn based games, can alienate furthermore their players base with such questionable choices like "forcing" users to Vulkan all of sudden.

As it stands i can play the latest Total Wars game on my notebook (reducing specs of course), BUT NOT a turn based game like Warhammer 40,000: Gladius - Relics of War, just because devs decided to switch to Vulkan.

Really disappointed by devs choices and lack of support for so many graphic cards.

[Yoki]

Ursprünglich geschrieben von Arkaeon the Chosen:

I had the same problem with my GTX 760M , Vulkan errors no matter the latest drivers installed.

Honestly i really don't understand how devs of an already niche genre as turn based games, can alienate furthermore their players base with such questionable choices like "forcing" users to Vulkan all of sudden.

As it stands i can play the latest Total Wars game on my notebook (reducing specs of course), BUT NOT a turn based game like Warhammer 40,000: Gladius - Relics of War, just because devs decided to switch to Vulkan.

Really disappointed by devs choices and lack of support for so many graphic cards.

Absolutly agree with you.
What about lagacy 4 (OpenGL4.0) is it work for you?

[Der_Ferb]

Is it possible that some older AMD GPU's have the same problem?
I have still an AMD Radeon R9 270X and even after the last updates, my Game crashes when i click on play in the launcher.
Before the DLC i havn't almost no problems with playing except with low framerate in late game what was expected with my weak hardware.

Maybe I'm just stupid but it seems that the last driver update for my GPU was in summer 2017.
I couldn't find a newer one.

Sorry for my bad english i hope its understandable

[TOFFster]

Ursprünglich geschrieben von Der_Ferb:

Is it possible that some older AMD GPU's have the same problem?
I have still an AMD Radeon R9 270X and even after the last updates, my Game crashes when i click on play in the launcher.
Before the DLC i havn't almost no problems with playing except with low framerate in late game what was expected with my weak hardware.

Maybe I'm just stupid but it seems that the last driver update for my GPU was in summer 2017.
I couldn't find a newer one.

Sorry for my bad english i hope its understandable

Every card on this list supports Vulkan:

AMD Radeon™ R9 Series graphics
AMD Radeon™ R7 Series graphics
AMD Radeon™ R5 240 graphics
AMD Radeon™ HD 8000 Series graphics for OEM systems (HD 8570 and up)
AMD Radeon™ HD 8000M Series graphics for notebooks
AMD Radeon™ HD 7000 Series graphics (HD 7730 and up
AMD Radeon™ HD 7000M Series graphics for notebooks (HD 7730M and up)
AMD A4/A6/A8/A10-7000 Series APUs
AMD A6/A8/A10 PRO-7000 Series APUs
AMD A6/A8/A10/FX™ 8000 Series APUs
AMD E1/A4/A10 Micro-6000 Series APUs
AMD E1/E2/A4/A6/A8-6000 Series APUs
AMD A4-1200, A4-1300 and A6-1400 Series APUs
AMD E1-2000, E2-3000, A4-5000, A6-5000, and A4 Pro-3000 Series APUs


I recommend double checking for GPU driver updates on AMD's official driver page. If you need support don't hesitate to make a new thread or contact [e-mail].

If the error you are receiving is related to a queue error, that is currently known and is being worked on by the developers.

[Arkaeon the Chosen]

And yet again, with next update the already small community of this games suffer from the Vulkan error.. over and over again.

Definitely disappointed by devs choices and lack of support for so many graphic cards.

[void]

Hello, we didn't even change any rendering code with the last two updates after so many people reported 1.3.7 was working so well for them. Believe me when I say this is bugging us just as much as you guys. Even the latest Vulkan validation layers don't report any API misuse for this crash and we just can't reproduce it on the half-dozen older NVIDIA cards we have tested it on.

However, we have contacted NVIDIA about the problem, and the DevTech for our region will be back in office next week. Also, I'll get my hands on another laptop with NVIDIA card later today, hoping the crash occurs there.

Anyone who experiences the issue and has the time and will to install the Vulkan SDK to try the debug beta branch, please send your Gladius.error.log and a DxDiag report to [e-mail].

Big sorry for the troubles, we'll keep at it.

[Arkaeon the Chosen]

The patch fixes up to 1.03.7 made most of us able to enjoy playing the game once again, even the older cards, and for that we are grateful indeed.

But with this 1.04 we are back to ground zero again, at least for me, cannot even play a single turn without having a Vulkan return to queue error of some kind

Update: Actually the errors appears when trying to play a new game created with 1.04 version, older saved games i tried to load seems to remain stable.

[I>U]

Guys, it's not just unsupported adapters. Vulkan is generally unstable (in this game). I have been having crashes\display errors since it was introduced on 3 different v/cards.

Just like that, 2 builds prior the current one, everything worked perfectly fine. For me, but not my playbuds, lol. And on the past build I've got display error (so-called "disco effect", as they've named it in discord) in less than 10 minutes in-game. Apparently, there should be something else but the rendering code to it.

Disable multi-processing and Anti-aliasing in options if you have one - that should gradually increase stability. If it's possible with your adapter (for quite a few of mobile ones), overrriding AA via Nvidia inspector will help as well, so you can download Nvidia Inspector and Profiles and try this

<?xml version="1.0" encoding="utf-16"?>
<ArrayOfProfile>
<Profile>
<ProfileName>blablableh</ProfileName>
<Executeables>
<string>Gladius.exe</string>
</Executeables>
<Settings>
<ProfileSetting>
<SettingNameInfo>Maximum pre-rendered frames</SettingNameInfo>
<SettingID>8102046</SettingID>
<SettingValue>1</SettingValue>
</ProfileSetting>
<ProfileSetting>
<SettingNameInfo>Texture filtering - Quality</SettingNameInfo>
<SettingID>13510289</SettingID>
<SettingValue>4294967286</SettingValue>
</ProfileSetting>
<ProfileSetting>
<SettingNameInfo />
<SettingID>13983613</SettingID>
<SettingValue>4194497</SettingValue>
</ProfileSetting>
<ProfileSetting>
<SettingNameInfo />
<SettingID>14888842</SettingID>
<SettingValue>4194497</SettingValue>
</ProfileSetting>
<ProfileSetting>
<SettingNameInfo />
<SettingID>269192926</SettingID>
<SettingValue>0</SettingValue>
</ProfileSetting>
<ProfileSetting>
<SettingNameInfo>Anisotropic filtering setting</SettingNameInfo>
<SettingID>270426537</SettingID>
<SettingValue>16</SettingValue>
</ProfileSetting>
<ProfileSetting>
<SettingNameInfo>Power management mode</SettingNameInfo>
<SettingID>274197361</SettingID>
<SettingValue>1</SettingValue>
</ProfileSetting>
<ProfileSetting>
<SettingNameInfo>Enable FXAA Indicator</SettingNameInfo>
<SettingID>275315612</SettingID>
<SettingValue>0</SettingValue>
</ProfileSetting>
<ProfileSetting>
<SettingNameInfo>Enable FXAA</SettingNameInfo>
<SettingID>276089202</SettingID>
<SettingValue>0</SettingValue>
</ProfileSetting>
<ProfileSetting>
<SettingNameInfo>Antialiasing - Mode</SettingNameInfo>
<SettingID>276757595</SettingID>
<SettingValue>1</SettingValue>
</ProfileSetting>
<ProfileSetting>
<SettingNameInfo>Anisotropic filtering mode</SettingNameInfo>
<SettingID>282245910</SettingID>
<SettingValue>1</SettingValue>
</ProfileSetting>
<ProfileSetting>
<SettingNameInfo>Antialiasing - Transparency Supersampling</SettingNameInfo>
<SettingID>282364549</SettingID>
<SettingValue>56</SettingValue>
</ProfileSetting>
<ProfileSetting>
<SettingNameInfo>Antialiasing - Setting</SettingNameInfo>
<SettingID>282555346</SettingID>
<SettingValue>38</SettingValue>
</ProfileSetting>
<ProfileSetting>
<SettingNameInfo />
<SettingID>284639831</SettingID>
<SettingValue>268435472</SettingValue>
</ProfileSetting>
<ProfileSetting>
<SettingNameInfo>Antialiasing - Transparency Multisampling</SettingNameInfo>
<SettingID>284962204</SettingID>
<SettingValue>4</SettingValue>
</ProfileSetting>
<ProfileSetting>
<SettingNameInfo>Multi-display/mixed-GPU acceleration</SettingNameInfo>
<SettingID>537586684</SettingID>
<SettingValue>3</SettingValue>
</ProfileSetting>
</Settings>
</Profile>
</ArrayOfProfile>

Save this text into "blablableh.nip" and then import it. Oh, and if your computer bursted, that's not my fault.

There would be some errors with autorun, just push Ok untill it settles. Also units may move in a bit of a lope, because it's just a general solution for games with display errors popping up - you can google it yourself, but it did help me on certain builds (when patching's patching up patchjob instead )

At any rate, a crash\display error occuring in ~100 turns is a harsh reality. People playing in singlepalyer just ignore it. but it really ruins multiplayer sessions.