Obsidian Conflict Bugtracker - Obsidian Conflict | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0000038 | Obsidian Conflict | [All Projects] Bug-Report | public | 04.09.2010 20:25 | 12.09.2011 13:41 |
Reporter | W0rf0x | ||||
Assigned To | TESLA-X4 | ||||
Priority | immediate | Severity | minor | Reproducibility | always |
Status | resolved | Resolution | fixed | ||
Projection | minor fix | ETA | none | ||
Platform | OS | OS Version | |||
Product Version | 0.1.3.5 | Product Build | |||
Target Version | 0.1.3.6 | Fixed in Version | 0.1.3.6 | ||
Summary | 0000038: Bugs related to player nocollide | ||||
Description | The nocollide code has a few flaws that can seriously interrupt gameplay; -If nocollided players are inside each other while standing on a moving platform (func_tracktrain, func_movelinear, func_door etc.), They block the platform from moving and/or take the blocking damage until everyone moved out of each other, usually resulting in everyone getting instagibbed. If the platform is moving down, those players will float in place until they go out of each other. -Player collision is still predicted on the client, so for a second it will look like you still collide with other players before you can go through them, and movement is overall very sluggish when going through other players. All of the above applies to both trigger_nocollide and mp_playercollide 0. -When 2 nocollided players walk out of the trigger_nocollide at the same time, they both will get stuck in each other, checking if the player is currently in another before making them solid again should prevent that. | ||||
Steps To Reproduce | See description | ||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files |
Notes | |||||
|
|||||
|
|