Offline
Note that SDL support is still experimental. There might be crashes and other issues.
Forum
News CS2D v1.0.1.8
CS2D v1.0.1.8
8 replies
1 
Note that SDL support is still experimental. There might be crashes and other issues.
Game crashes with DirectX 9 when changing resolution Languages which require special fonts (like Chinese) are not displayed properly anymore in the main menuWill fix these ASAP
Thanks for adding my localization and for fixing the x64 tile selection in the editor.
1.Copy and cut doesn't work in editor, for example can't copy Trigger_Delay and paste in other place
2.Bots when trying enter teleport1, but enters teleport2, they still trying to enter teleport1, even when between them are walls
I tested and both OpenGL and SDL OpenGL make the game crash, whereas SDL Direct3D 11 and DirectX 9 work.
P.S.:
DC this is very minor but perhaps it's time to update the Readme.txt now with the launch options for the new graphics APIs? homeless: Yes, known issue. See my previous post. Working on it.@
Stelient: Huh.. that must be an old issue. Didn't touch it. I'll take a look. Thanks!I don't fully understand the teleport issue. Are you talking about teleport buildings or map teleports? Teleport buildings are not properly supported for bots.
@
medeiros: Interesting. This must be a driver issue. It works fine for me.Will add the new graphics mode start params to the readme, thanks for pointing that out.
DC has written@ medeiros: Interesting. This must be a driver issue. It works fine for me.
Will add the new graphics mode start params to the readme, thanks for pointing that out.
medeiros: Interesting. This must be a driver issue. It works fine for me.Will add the new graphics mode start params to the readme, thanks for pointing that out.
I have done some more testing and if "Run in window" is selected, then OpenGL doesn't crash the game.
But yeah, attempting to launch the game already in fullscreen with anything that's not DirectX crashes it and gives the EXCEPTION_ACCESS_VIOLATION error, which is odd as this had never happened to me; I am using the latest NVIDIA drivers (610.88).
1