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
BTW. there's no major advantage for D3D11 vs D3D9 for this game. D3D11 tends to be faster (even up to 40% better framerate in our tests with Undead Horde and DYSMANTLE), but Crimsonland doesn't require that much horse power to begin with.
Meanwhile, could you download the file https://www.10tons.com/files/developer.xml and place it in the same directory where the Crimsonland*.exe is? When you now run the game, it should generate log files to game app data roaming folder such as C:\Users\<username>\AppData\Roaming\10tons\Crimsonland\logs. Please send the contents of that folder to contact (at) 10tons.com for further investigation?
I find that if I run Crimsonland-D3D11.exe by double-clicking on the exe directly from the game's install folder I get a error window that says "The program can't start because XINPUT_1_4.dll is missing from your computer. Try reinstalling the program to fix this problem." This error window doesn't appear when launching through Steam. When launching the non DX11 version from the install directly it doesn't produce that error, and of course it launches from Steam without issue as well. I tested that because I thought perhaps it simply didn't like being launched directly as opposed to Steam. So this must be the explanation as to the error though I'm not sure what I can do to resolve it.
Edit to add: I now see that launching directly from the folder caused a log to be generated so I'll send that to you.
Additional note: I suppose it's possible the log was generated by successfully launching the DX9 version but I assume you can tell what generated the log somehow.
Anyway, we just updated a new build to update_beta branch of Crimsonland. Can you please test if it works now?
One odd thing about the DX11 version is lots of screen tearing. Is there a way to activate vsync in the game engine or should I just try to force it from the nVidia control panel?
VSYNC is disabled by default as it seemed to add some latency (not all noticed it though). You need to remove the text token DISABLE_VSYNC from prog.xml file to disable it. We should really put this into the graphics option screen (in our future games at least).