Advertisement
[4.2] Bugs Squashed
#31
Posted 04 October 2012 - 05:00 AM
6:00 am .. still awake .. gave it a try .. got stable 125 fps .. wasn't playing on a 32slot server but nevertheless it seems i might not even have to beg for an optimized build anymore ..
if it stays that way with higher server loads i will be happy to stick with 4.2 ..
thanks for working on those improvements...
as far as i can tell .. good job fs
if it stays that way with higher server loads i will be happy to stick with 4.2 ..
thanks for working on those improvements...
as far as i can tell .. good job fs
if you don't like uptown, you are basically hating urban terror.
#32
Posted 04 October 2012 - 06:00 AM
4.2.002 improved hits
ahah what is going on here?
ahah what is going on here?
This post has been edited by Pez: 04 October 2012 - 06:02 AM
#33
Posted 04 October 2012 - 10:22 AM
Steady... please.
I realise it took longer than antisipated for 002 (but thats only while we worked out some workflow stuff out amongst our team now we are bigger). The UrTUpdater exists so that we can have short release cycles if we need too.
So rather than bitch and say "back to 4.1" and make the dev team all feel utterly miserable, how about report the bugs like you are and let us fix them.
That crouch bug is really annoying, and it looks like a back of the knee malformed. Thats a good set of proof in the video, but a demo also would have been great as we can debug with the gamedata demos :)
Note: remember my warning to everyone about "if you can't be nice, or its not in the dev teams interest to have you around you will be gone / banned or muted" ? That applies here, so watch yourself s please.
I realise it took longer than antisipated for 002 (but thats only while we worked out some workflow stuff out amongst our team now we are bigger). The UrTUpdater exists so that we can have short release cycles if we need too.
So rather than bitch and say "back to 4.1" and make the dev team all feel utterly miserable, how about report the bugs like you are and let us fix them.
That crouch bug is really annoying, and it looks like a back of the knee malformed. Thats a good set of proof in the video, but a demo also would have been great as we can debug with the gamedata demos :)
Note: remember my warning to everyone about "if you can't be nice, or its not in the dev teams interest to have you around you will be gone / banned or muted" ? That applies here, so watch yourself s please.
#34
Posted 04 October 2012 - 12:59 PM
+1
aka Dead f.S. - aka |CoN|-=V0l3ur=-, Playing UrT from 2001 - RedCap bot Developer
[img]http://www.dead.it/UrT/logop.png[/img]
[img]http://www.dead.it/UrT/logop.png[/img]
Advertisement
#36
Posted 04 October 2012 - 03:47 PM
X3igh7, on 04 October 2012 - 02:07 AM, said:
What's with the hits?
You should recruit this guy to your QA team cause it took him a couple hours to find some pretty obvious flaws.
Thanks for the update though. Keep up the work.
You should recruit this guy to your QA team cause it took him a couple hours to find some pretty obvious flaws.
Thanks for the update though. Keep up the work.
The only way we were able to duplicate this bug was by running an out of date player model package on a server. What may be occurring is the server operator installed 4.2 over top of a 4.1 build putting the clients out of sync with the server.
As far as a test go it's incomplete as the process only points out the fact that a no-hit can be created based on an unknown variable assuming what someone sees is the root problem. Our testing process is based on the idea that what you see is what the server has decided what has actually occurred to identify the true nature of the bug.
So far this is the only video we have seen that collision detection is not occurring in the crouch position that has not been validated or properly tested to confirm that it's not a improperly configured server where the server is running an older animation.cfg file that does not match the same cfg as the client.
Here is how it works.
When the game loads it loads first to last based on the naming of the cfg file in alphabetical order. If an older pk3 file is loaded last it could overwrite the proper animation control file putting the hitmesh out of sync on the server as compared to what looks right on the client. The hit mesh is there it's just being indexed to the older control file.
This is where the second half of the testing needs to be done by assuming that the way the server see things, and you don't, is always right compared to what one sees as being the truth. To see if it's a cfg mismatch one has to test to see if they can find where the HM is located in relationship to the clients rendered player model by firing around the player model instead of into it. In this case, based on what I know to be true, is if one is getting hits behind and above the player then it's a server side cfg problem that can be easily corrected by the server operator by preforming a clean install of 4.2.
doing "stuff" with dead things.
#37
Posted 04 October 2012 - 08:10 PM
RaideR, on 04 October 2012 - 10:22 AM, said:
Steady... please.
I realise it took longer than antisipated for 002 (but thats only while we worked out some workflow stuff out amongst our team now we are bigger). The UrTUpdater exists so that we can have short release cycles if we need too.
So rather than bitch and say "back to 4.1" and make the dev team all feel utterly miserable, how about report the bugs like you are and let us fix them.
That crouch bug is really annoying, and it looks like a back of the knee malformed. Thats a good set of proof in the video, but a demo also would have been great as we can debug with the gamedata demos :)
Note: remember my warning to everyone about "if you can't be nice, or its not in the dev teams interest to have you around you will be gone / banned or muted" ? That applies here, so watch yourself s please.
I realise it took longer than antisipated for 002 (but thats only while we worked out some workflow stuff out amongst our team now we are bigger). The UrTUpdater exists so that we can have short release cycles if we need too.
So rather than bitch and say "back to 4.1" and make the dev team all feel utterly miserable, how about report the bugs like you are and let us fix them.
That crouch bug is really annoying, and it looks like a back of the knee malformed. Thats a good set of proof in the video, but a demo also would have been great as we can debug with the gamedata demos :)
Note: remember my warning to everyone about "if you can't be nice, or its not in the dev teams interest to have you around you will be gone / banned or muted" ? That applies here, so watch yourself s please.
Hey
We played last night and found everything great! The server ran very smooth and this seemed to improve the hits. Gameplay was awesome. We only had about 8 people in there at the time though so we'll see how it works out on a full server.
We saw a lot of people trying to get in but didn't make it, probably hadn't updated yet. If the client checked for new updates automatically upon starting then the community would be less hard pressed to figure out that there was an update and the servers would start filling up much faster.
There is still a slight med bug as stated earlier when too close. Try to med and nothing happens until you move out a little.
We did have one member who couldn't see anything in the server list, and another that got the same missing dll file error as in the prior release. Once she went to the link supplied in the How To doc you supplied, and installed the Microsoft C++ update, she was okay.
Thanks, gang. Great job! Looking forward to continued updates. Hope there are no problems with the Auth system. We will eventually run with it activated, but will wait to see how it works out first.
|30+|LtStriker
#38
Posted 04 October 2012 - 08:45 PM
Thanks for the upgrade.
I applied it on my client (Win7) and everything went well, could connect to other servers. But then I upgraded my server on Linux 32bit, and can't connect to it.
What is wrong?
I can get in, but then server kicks me with something notoriety message and then get this window.
Any idea? Thanks
I applied it on my client (Win7) and everything went well, could connect to other servers. But then I upgraded my server on Linux 32bit, and can't connect to it.
What is wrong?
I can get in, but then server kicks me with something notoriety message and then get this window.
Any idea? Thanks
1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users
Advertisement