Forum

> > CS2D > General > CS2D Bug Reports
Forums overviewCS2D overviewGeneral overviewLog in to reply

English CS2D Bug Reports

2,057 replies
Page
To the start Previous 1 2101 102 103 Next To the start

old Re: CS2D Bug Reports

mrc
User Off Offline

Quote
Has anyone ever reported that the decals don't appear in 3D mode?

old Re: CS2D Bug Reports

forfunlol420
User Off Offline

Quote
@user mrc:
Idk but maybe Env_Decal is 2D so it broken at 3D mode
Maybe not, I'm a dumbass
I use OpenGL and got this problem too but when I use DirectX it normal
And maybe because the bug only show up if the drivers suck(can't use "Lighting")I think

old Re: CS2D Bug Reports

Mora
User Off Offline

Quote
Idk this might be reported already but when I use custom bulletshells so shotgun's 1 (single) fire is dropping 5 shells, shouldn't be like that:
IMG:https://i.imgur.com/uOCLHce.png

old Re: CS2D Bug Reports

mrc
User Off Offline

Quote
@user DC: I think I found something that could help to fix the 'ghost grenade' bug.

Now that I know how to replicate this bug, I will find out in which version exactly this bug occurs, then it will be easier to find out what was changed in the version's changelog.

Alright, based on my tests, it started happening in version 1.0.0.4. After checking the changelog, I found this: FPS influenced Animations, projectiles, particles and effects speed. Maybe this can help you find the solution?
edited 12×, last 06.02.24 07:26:24 pm

old Re: CS2D Bug Reports

DC
Admin Off Offline

Quote
What is the ghost grenade bug? Grenades flying differently than they should exploding in weird, unexpected positions? If so: Yes, that the FPS influence change broke it would make perfect sense.

old Re: CS2D Bug Reports

mrc
User Off Offline

Quote
Sarcasm?

So, in previous versions, they also exploded in different places when players had low FPS, but the grenades didn't bounce off the walls incorrectly. With the 60 FPS, now they explode where they should, but bounce off the edges of the walls. A curious fact, if I replicate this bug without changing mouse position, sometimes it ricochets and sometimes it doesn't, randomly.

Also this is a different one, and exists since 0.0.3.1: https://prnt.sc/qmRlYMKLFw0i

If a player stands where the bullet mark is on the Host's image, they will take damage even if you are shooting at the wall as the Client's image.
edited 3×, last 06.02.24 08:51:09 pm

old Re: CS2D Bug Reports

Ranu
User Off Offline

Quote
@user mrc: That's due to the fact CS2D bullet tracers are being created and rendered locally (from the client), and there would be no better way unless DC decides to spend hours on creating a whole new system for that, that would work with the server by using seeds for Spray Patterns or the recoil pattern.

old Re: CS2D Bug Reports

SQ
Moderator Off Offline

Quote
@user Ranu: Regarding grenades - the issue is use of delta time for the movement.
The game doesn't have dedicated physics loop - leads to different results given different framerate.

The newer recoil system uses seed values, the default one does not.

old Re: CS2D Bug Reports

mrc
User Off Offline

Quote
@user SQ: Is it possible to fix this issue with grenades? By the way, the recoil mode is cool, but unfortunately, there are cases where other players keep shooting straight up. It's a bug, and I'll try to replicate it.

Alright, I was able to reproduce the recoil mode bug.

To replicate the recoil mode bug, follow these steps:
1. Open two clients, designate one as the Host and the other as the Client.
2. Set the Host as a Spectator and observe the actions of the Client.
3. With the Client, use any weapon (except pistols and shotguns) and shoot while moving.
4. You will notice that the Client shoots straight upwards in a straight line.

As you can see in the following image, it's not just visual; it actually deals damage:
https://prnt.sc/Hjob1RxycEyK

That also means that where the client is actually shooting, it doesn't cause damage (even though they see on their screen that their shot is heading in the direction of the crosshair).
edited 6×, last 07.02.24 03:39:28 pm

old Re: CS2D Bug Reports

Kolia_rus
Security Supporter Off Offline

Quote
Screenshots made via the F5 key while the game resolution is set to 800x600 are cropped incorrectly. With and without the checkbox "4:3 Ratio Gameplay" triggered.

old Re: CS2D Bug Reports

WatPz
User Off Offline

Quote
user mrc has written
@user DC: I think I found something that could help to fix the 'ghost grenade' bug.

Now that I know how to replicate this bug, I will find out in which version exactly this bug occurs, then it will be easier to find out what was changed in the version's changelog.

Alright, based on my tests, it started happening in version 1.0.0.4. After checking the changelog, I found this: FPS influenced Animations, projectiles, particles and effects speed. Maybe this can help you find the solution?


It also happened when you try shooting.
You may shoot on the walls, However, the enemy received damage.
( Like the de_cs2d upper road, CT can use AUG to kill anyone who wants to enter the A side. Sometimes you may shoot on the wall, but the damage occured)

I guessed that was because of the incorrect mouse pos & player pos, which was different from Clients and Sv

And, yeah, in early version, there wasn't this problem.

old Re: CS2D Bug Reports

DC
Admin Off Offline

Quote
@user WatPz: Hah. Interesting. If you observe this behavior with weapons which have no spread and after being idle on the same spot with the same rotation for a while (like a second or so)... well then this may be caused by an optimization by user SQ where the rotation angle which is sent from client to server was changed from float (4 bytes) to short (2 bytes). It probably works fine at most angles but since 2 bytes can "only" represent 65,535 values there might be a few inaccuracies at very specific angles.

This change was introduced with version 1.0.0.4

old Re: CS2D Bug Reports

Ranu
User Off Offline

Quote
user DC has written
@user WatPz: Hah. Interesting. If you observe this behavior with weapons which have no spread and after being idle on the same spot with the same rotation for a while (like a second or so)... well then this may be caused by an optimization by user SQ where the rotation angle which is sent from client to server was changed from float (4 bytes) to short (2 bytes). It probably works fine at most angles but since 2 bytes can "only" represent 65,535 values there might be a few inaccuracies at very specific angles.

This change was introduced with version 1.0.0.4
I debugged it exactly where that happens, this is the result of the Test 1:
In client 1: it shows client 1 rotation is -13.6020 but in client 2 it shows 346.99768 for client 1 rotation (when 360 - 13.6 = 346.4).
Test 2:
Client 1 Rotation shows 145.489
Client 2 shows Client 1 rotation as 144.99755

old Re: CS2D Bug Reports

DC
Admin Off Offline

Quote
That sounds very suspicious 360 / 65,535 is about 0.00549 - which is the precision I would expect. I think I already found the issue.

old Re: CS2D Bug Reports

Ranu
User Off Offline

Quote
It seems to be the issue, yeah. Also, the default recoil system doesn't use seed values for the recoil, so could have a similar outcome and cause the same issue. Would be happy to see seed values being used for the recoil in next update. (The tests above were without recoil)

EDIT: OpenGL in CS2D has an extra latency. With 60 FPS Lock, it is about 18 ms, however, with about 300 FPS, it is about 3 ms. In DirectX with 60 FPS or 300 FPS, in both cases its ~0 ms

EDIT 2: I found a couple new issues:
1. Mousex and Mousey through
player(id, 'mousex'), player(id, 'mousey')
don't get synchronized accurately, In other words the client doesn't give the server the actual mouse position, there is usually a difference by 1 to 3. I believe it's the same case for reqcld. This is also a part of causing the latest bug reported.
2. After a period of client inactivity, the mousex and mousey return -1, and this is stupid. The right way to do this is to after a period of inactivity use the cached latest client mouse position instead of returning -1. Once again, I believe its same for reqcld.

This could partake in fixing the nade issue and the shooting issues. To fix them, all of the following have to be done:
Quote
Summary:

1. Fix mousex, mousey synchronization (for reqcld aswell)
2. Fix the rotation synchronization
3. Use seed values for the default recoil
edited 3×, last 01.03.24 08:01:48 am

old Re: CS2D Bug Reports

Mora
User Off Offline

Quote
In addition :
Your may add an image
pointer = image("gfx/pointercustom.png", 0,0,1)
and update it
imagepos(pointer,player(1,"mousex"),player(1,"mousey"),0)
on always. Start a server with new game and join it. Even having 1-3ms would cause offset on mouse move and stop. The sync is visible.
To the start Previous 1 2101 102 103 Next To the start
Log in to replyGeneral overviewCS2D overviewForums overview