07.03.2011, 00:28
(
Последний раз редактировалось Diablosrouge; 07.03.2011 в 02:40.
)
During 0.3 period, more particularly on 0.3c, we've seen some changes, both to worse and better.
All of you know the sync problems 0.3a had and fortunately they were mostly fixed on 0.3b.
Now on 0.3c, we have the player sync a bit better than 0.3b but some problems came up, which are very toxic specially to the Death Match.
Let's speak about FPS drops. Since 0.3 version the FPS dropped considerably and players who would get constant 45 fps, now get FPS drops every 5 minutes or so. And those who have older computers (starting by intel core duo dual cores) and used to get 45 fps without a problem and even run another game behind SAMP, are now having trouble maintaining a constant 45 fps along their playing time.
This change has been noticed on the transition from 0.2X to 0.3(abc).
Problem #1:
The suspected main cause of this, is the chat GUI that was modified prior to 0.3. The letters have more Bold than the previous version 0.2X, which means more graphical performance is required to process the chat.
It has been noticed that if you click F7 once, your chat gets lighter and more transparent, and an average of 7-10 FPS increase, resulting on a better game stability. Even the high-end computers (i5, i7 and so on) do have this lag and get a better performance once the chat is lighter.
Solution:
My proposal to fix this FPS drop problem should be to get the old chat GUI from 0.2X, keeping the 0.3 features, so it wouldn't require as much CPU and Graphic usage, allowing players to have a quite bigger FPS average while playing.
Problem #2:
The weapon sync got worse from 0.3b to 0.3c in what touches to bullet count. SA-MP has difficulty in many cases to sync the players and their bullet ammount on a gun. For example, on Spas12 now players are seeing each other reload pretty often, when, in fact, they are shooting the player.
Basically Player1 shoots 6 bullets, switch to a weapon and then switch back to Spas, he will shoot another load of bullets and Player2 will see him reloading instead.
It is confirmed that this problem appeared on 0.3c and is a critical point to the Death Match community, which its fixability is a must.
Video:
[ame]http://www.youtube.com/watch?v=NcypBhbihlw[/ame]
Solution:
Review the 0.3c weapon sync code and comparing it with 0.3b, see what changed and perform tests to see if the bug was fixed.
Problem #3:
Sniper sync was also critically affected on 0.3c because this bug was inexistent on all the other SAMP versions.
The problem with sniper is that you have 25% of probability to see a sniper his own head. Another thing that is very critical specially on Attack and Defend matches in which Sniper is a vital weapon and if the sync is failing, then all the match will be affected, causing people to get mad, and closing doors to SAMP DM expansion.
Video:
(soon)
Solution:
Review the 0.3c weapon sync code and comparing it with 0.3b, see what changed and perform tests to see if the bug was fixed.
I really hope 0.3d or 0.4 or whatever version comes next really fixes these 3 problems for good, because they born on 0.3c and it's starting to piss off many people inside the Death Match community.
0.3c brought in many cool things indeed, but if bugs start arising from nothing, they should be killed as soon as possible. On the old code this didnt happen, so you got a start point
Also you may not see many people comment this, because a major part of the DM community barely puts their feet here or isn't informed where about the Bug Report is. We are getting through a new generation of players and the old ones are leaving, that's why I'm here, to elaborate a bug topic dedicated specially to the DM side of SAMP, along with other opinions from other players from other SAMP Communities.
But since Kye and their Dev team read these forums, here I am posting the bugs.
Kind Regards,
Diablosrouge
All of you know the sync problems 0.3a had and fortunately they were mostly fixed on 0.3b.
Now on 0.3c, we have the player sync a bit better than 0.3b but some problems came up, which are very toxic specially to the Death Match.
Let's speak about FPS drops. Since 0.3 version the FPS dropped considerably and players who would get constant 45 fps, now get FPS drops every 5 minutes or so. And those who have older computers (starting by intel core duo dual cores) and used to get 45 fps without a problem and even run another game behind SAMP, are now having trouble maintaining a constant 45 fps along their playing time.
This change has been noticed on the transition from 0.2X to 0.3(abc).
Problem #1:
The suspected main cause of this, is the chat GUI that was modified prior to 0.3. The letters have more Bold than the previous version 0.2X, which means more graphical performance is required to process the chat.
It has been noticed that if you click F7 once, your chat gets lighter and more transparent, and an average of 7-10 FPS increase, resulting on a better game stability. Even the high-end computers (i5, i7 and so on) do have this lag and get a better performance once the chat is lighter.
Solution:
My proposal to fix this FPS drop problem should be to get the old chat GUI from 0.2X, keeping the 0.3 features, so it wouldn't require as much CPU and Graphic usage, allowing players to have a quite bigger FPS average while playing.
Problem #2:
The weapon sync got worse from 0.3b to 0.3c in what touches to bullet count. SA-MP has difficulty in many cases to sync the players and their bullet ammount on a gun. For example, on Spas12 now players are seeing each other reload pretty often, when, in fact, they are shooting the player.
Basically Player1 shoots 6 bullets, switch to a weapon and then switch back to Spas, he will shoot another load of bullets and Player2 will see him reloading instead.
It is confirmed that this problem appeared on 0.3c and is a critical point to the Death Match community, which its fixability is a must.
Video:
[ame]http://www.youtube.com/watch?v=NcypBhbihlw[/ame]
Solution:
Review the 0.3c weapon sync code and comparing it with 0.3b, see what changed and perform tests to see if the bug was fixed.
Problem #3:
Sniper sync was also critically affected on 0.3c because this bug was inexistent on all the other SAMP versions.
The problem with sniper is that you have 25% of probability to see a sniper his own head. Another thing that is very critical specially on Attack and Defend matches in which Sniper is a vital weapon and if the sync is failing, then all the match will be affected, causing people to get mad, and closing doors to SAMP DM expansion.
Video:
(soon)
Solution:
Review the 0.3c weapon sync code and comparing it with 0.3b, see what changed and perform tests to see if the bug was fixed.
I really hope 0.3d or 0.4 or whatever version comes next really fixes these 3 problems for good, because they born on 0.3c and it's starting to piss off many people inside the Death Match community.
0.3c brought in many cool things indeed, but if bugs start arising from nothing, they should be killed as soon as possible. On the old code this didnt happen, so you got a start point
Also you may not see many people comment this, because a major part of the DM community barely puts their feet here or isn't informed where about the Bug Report is. We are getting through a new generation of players and the old ones are leaving, that's why I'm here, to elaborate a bug topic dedicated specially to the DM side of SAMP, along with other opinions from other players from other SAMP Communities.
But since Kye and their Dev team read these forums, here I am posting the bugs.
Kind Regards,
Diablosrouge
