former FS member
As already mentioned in other topics, you can't watch a 4.2.011 demo (or previous) with a 4.2.012 client. That's why you are experiencing all this mess
Advertisement
[4.2] Update 4.2.012
Rate Topic:
#121
Fenix 
Posted 02 May 2013 - 01:22 PM
Follow me: https://github.com/danielepantaleone
MultiQuote
#122
LtStriker
Posted 03 May 2013 - 10:05 PM
Hey
We are still seeing problems with Pague V2 not playing right. The jitters are back, for lack of a better term. Ramelle also has the jitters, just like way back when we went to 4.2. Some players actually have trouble moving or are moved around a little by the map. That's what they have reported, anyway.
Also believe the bandaging has been messed up. Players bleed out because bandage just keeps going and does not stop bleeding soon enough.
We sometimes have to restart the server to improve the hitability factor. When the hits are on, they're on.
Please restore support for mouse4.
Really wish that once you have fixed something you would not keep going back to earlier versions of the game to find fixes for other problems that inevitably break things that had already been fixed. I suggest that older versions should be not be reintroduced as they will bring back old bugs. Maybe I'm not understanding what takes place during the development of the game, but it seems that we are always seeing old bugs reappearing when what we should be seeing is the state of the game improving, growing, moving forward.
I'm not taking away from the improvements we have seen. If there was no improvement we would have stopped playing 4.2 by now. We do appreciate the advancements made. However, we want to feel like, you, FS, are winning this battle. Once you have fixed something we should not see the problem come back again. Just seems to make sense.
Thanks for your efforts,
|30+|LtStriker
We are still seeing problems with Pague V2 not playing right. The jitters are back, for lack of a better term. Ramelle also has the jitters, just like way back when we went to 4.2. Some players actually have trouble moving or are moved around a little by the map. That's what they have reported, anyway.
Also believe the bandaging has been messed up. Players bleed out because bandage just keeps going and does not stop bleeding soon enough.
We sometimes have to restart the server to improve the hitability factor. When the hits are on, they're on.
Please restore support for mouse4.
Really wish that once you have fixed something you would not keep going back to earlier versions of the game to find fixes for other problems that inevitably break things that had already been fixed. I suggest that older versions should be not be reintroduced as they will bring back old bugs. Maybe I'm not understanding what takes place during the development of the game, but it seems that we are always seeing old bugs reappearing when what we should be seeing is the state of the game improving, growing, moving forward.
I'm not taking away from the improvements we have seen. If there was no improvement we would have stopped playing 4.2 by now. We do appreciate the advancements made. However, we want to feel like, you, FS, are winning this battle. Once you have fixed something we should not see the problem come back again. Just seems to make sense.
Thanks for your efforts,
|30+|LtStriker
#123
FS BladeKiller
FS chief admin
Posted 04 May 2013 - 04:48 AM
Old bugs reappear for a variety of reasons and sometimes are hard to anticipate when you are working on a different area of the code. Q3 mod code is not nice to work with. This is very old code also that a lot of coders have worked on so things are not always clear as to what they do. It isn't like we put the old bugs in again or go back to older versions. That isn't how that happens. The bug may act the same but the cause can be from something completely different.
Lag causes that feeling of being pulled around the map.
I do not expect you to have good performance with prague v2 and say so in it's readme. It was made for a different engine. To get it to compile I had to remove a lot of the details in it as it is. I just wanted to get it play tested a bit so I released it. I don't expect it to replace the old version which is why I gave it a different name.
Ramelle has always had performance issues over the years due to its layout and impossibility to vis block it. This stutter seems to be unrelated to the map though from what I am seeing written by the people who have it. I and one of the coders managed to get our systems to stutter but that was by setting rate at a maximum and setting it back to a lower setting got rid of the stutter. I don't know if these are related. They probably aren't. No one in FS or QA has had the stutter yet so it's hard to debug. We shall keep gathering information on it.
Lag causes that feeling of being pulled around the map.
I do not expect you to have good performance with prague v2 and say so in it's readme. It was made for a different engine. To get it to compile I had to remove a lot of the details in it as it is. I just wanted to get it play tested a bit so I released it. I don't expect it to replace the old version which is why I gave it a different name.
Ramelle has always had performance issues over the years due to its layout and impossibility to vis block it. This stutter seems to be unrelated to the map though from what I am seeing written by the people who have it. I and one of the coders managed to get our systems to stutter but that was by setting rate at a maximum and setting it back to a lower setting got rid of the stutter. I don't know if these are related. They probably aren't. No one in FS or QA has had the stutter yet so it's hard to debug. We shall keep gathering information on it.
#124
[SEG]garcassgrinder
Posted 05 May 2013 - 03:38 PM
BladeKiller, on 04 May 2013 - 04:48 AM, said:
Old bugs reappear for a variety of reasons and sometimes are hard to anticipate when you are working on a different area of the code. Q3 mod code is not nice to work with. This is very old code also that a lot of coders have worked on so things are not always clear as to what they do. It isn't like we put the old bugs in again or go back to older versions. That isn't how that happens. The bug may act the same but the cause can be from something completely different.
Lag causes that feeling of being pulled around the map.
I do not expect you to have good performance with prague v2 and say so in it's readme. It was made for a different engine. To get it to compile I had to remove a lot of the details in it as it is. I just wanted to get it play tested a bit so I released it. I don't expect it to replace the old version which is why I gave it a different name.
Ramelle has always had performance issues over the years due to its layout and impossibility to vis block it. This stutter seems to be unrelated to the map though from what I am seeing written by the people who have it. I and one of the coders managed to get our systems to stutter but that was by setting rate at a maximum and setting it back to a lower setting got rid of the stutter. I don't know if these are related. They probably aren't. No one in FS or QA has had the stutter yet so it's hard to debug. We shall keep gathering information on it.
Lag causes that feeling of being pulled around the map.
I do not expect you to have good performance with prague v2 and say so in it's readme. It was made for a different engine. To get it to compile I had to remove a lot of the details in it as it is. I just wanted to get it play tested a bit so I released it. I don't expect it to replace the old version which is why I gave it a different name.
Ramelle has always had performance issues over the years due to its layout and impossibility to vis block it. This stutter seems to be unrelated to the map though from what I am seeing written by the people who have it. I and one of the coders managed to get our systems to stutter but that was by setting rate at a maximum and setting it back to a lower setting got rid of the stutter. I don't know if these are related. They probably aren't. No one in FS or QA has had the stutter yet so it's hard to debug. We shall keep gathering information on it.
Stutter seams to be a IP issue. Is there any possibility or procedure we can supply you with the needed information to catch the bug?
Advertisement
#126
[Sk&Bh]Txc
Posted 05 May 2013 - 07:37 PM
garcassgrinder, on 05 May 2013 - 03:38 PM, said:
Stutter seams to be a IP issue. Is there any possibility or procedure we can supply you with the needed information to catch the bug?
3 different providers -static IP - 4 years , since 10-11 months neighbour's wifi (btw it can be stable sometimes & I can get sometimes reasonable ping (50-60) ) - same ...
#127
diRf!Nikki
Posted 05 May 2013 - 09:50 PM
Txc, on 05 May 2013 - 07:37 PM, said:
3 different providers -static IP - 4 years , since 10-11 months neighbour's wifi (btw it can be stable sometimes & I can get sometimes reasonable ping (50-60) ) - same ...
I still don't understand what either of you are saying. The stutter most everyone is talking about has nothing to do with our ISPs... We're not talking about a crappy leech off of our neighbors wifi.
#128
[Sk&Bh]Txc
Posted 05 May 2013 - 10:09 PM
Nikki, on 05 May 2013 - 09:50 PM, said:
I still don't understand what either of you are saying. The stutter most everyone is talking about has nothing to do with our ISPs... We're not talking about a crappy leech off of our neighbors wifi.
I am giving an example why I doubt to be IP issue .
#129
[SEG]garcassgrinder
Posted 05 May 2013 - 11:25 PM
Txc, on 05 May 2013 - 10:09 PM, said:
I am giving an example why I doubt to be IP issue .
To me it seams that the issue happens at peak times. So could that not be an indicator for an IP issue? IPv4 works nice but is not perfect.
Want only to catch up the stutter for investigation to find a solution. Like to run a wireshark trace while gaming till it happens. If that could deliver helpful infos... but want to get an opinion from FS if that makes sense.
@nikki:
With IP I do not mean Internet Service Provider (ISP). IP = Internet Protocol
This post has been edited by garcassgrinder: 05 May 2013 - 11:56 PM
#130
thelionroars
QA member
Posted 06 May 2013 - 05:14 AM
garcassgrinder, on 05 May 2013 - 11:25 PM, said:
To me it seams that the issue happens at peak times. So could that not be an indicator for an IP issue? IPv4 works nice but is not perfect.
Turn the netgraph on, it should be a fairly reliable indicator of any problems with networking. Networking problems either tend to be upstream (the server or your ISP is overloaded), or caused by UDP packets being given the shaft by your home router in favour of one or several TCP streams underway (eg. torrents, youtube). Or a wireless connection.
A wireshark capture isn't going to show you anything, you will just load your cpu more. Traffic capture is fairly cpu intensive.
[img]http://i.imgur.com/OQ7HC64.gif[/img]
1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users
Advertisement