@ Yates: Yes, that was an accident in the release process and not intended. Will be changed back to the known default (with that filter being enabled).

are you sure its not by default? from what I see it is.

I just installed a fresh version and the filter option "Yes & has same version" was not enabled. I saw bars of red flashing in front of my eyes. It was terrible, horrific, I have never witnessed such madness..

I'm sure.

Alright, it might have been some failure when building final release then.

Something weird just happened on my radar

@ Masea: Do you use launcher or bat files when running cs2d? I think it's causing it. You should use only exe

@ SQ: Yeah I use that but why is it standing there if I shouldn't use it? :S Or does it no longer exist in new versions?

What SQ is actually trying to say: He moved all the options from the command line args to the in game graphics menu so you can conveniently switch the settings there.

This is the new and recommended way of choosing the resolution / window mode.

The command line args - and the launcher which is just using them - still exist (and I want to keep them) but as you see there seem to be bugs with them in some cases.

@ Masea: Anyway, I would like to know what were options you were using for the bat file so I could fix it.

@ SQ: 1366x768 and fullscreen which makes me say why the fuck is it causing a bug like that.

@ Hajt: It's already fixed for dedicated. You need to download it. Will be fixed for next client as well. (I don't see point to update clients just for this command)

@ Masea: It is quite complicated to explain as there is few systems that are interfering. For example if graphics is initialized more than 2 times (having two graphical contexts at the same time), this happens. And batch sometimes forces to initialize graphics twice.

I can't reproduce it. You are able to reproduce it all the time? OpenGL or DirectX? Also there might be additional steps involved, like opening menu and pressing ok (applying graphics settings again)

@ SQ: Happens on both, OpenGL and DirectX. Nothing happens by opening the menu and pressing OK afterward.

By the way, the bug is about the file .bat as you said. No matter what settings you set up.

Seems like you must see the minimap/radar code yet again and work on it.

Ok, nice to know. Are you also going to add a new command setassist or sth like that?

@ Masea: It's a code related to FBO (Fast Buffer Objects) that I'm using for those fancy lighting/radar features. Well I just don't prefer using bats, but yes I'll try to find the problem when I'll manage to reproduce it.

Oh also you info is misleading. Minimap has a cache, so once it's loaded, even though corrupted, it will always show that map until you delete cache. This thing is also reproducible only on DX or OpenGL, not on both (since I know the issue, but forgot which graphics driver causes it). Check your stuff multiple times before reporting.

@ Hajt: There are setassists <id> <ass> and setmvp <id> <mvps> commands already I think.

Did anybody report this bug?

I found a bug with laser mines: they stand in an unusual direction, but the real lines go through the original ones.
Screens related:

Looks weird, doesn't it?

I've Expirienced the same bug here also.

Regarding the laser mines: SQ did some "optimizations" in the network code and broke it but I think he already fixed it for the next version. Thanks for reporting!

@ Gaios: What exactly are you referring to? 3D/shadow order stuff or something else?