- Status Closed
- Percent Complete
- Task Type Bug Report
- Category 3D Art → Models and Maps
- Assigned To No-one
- Operating System
- Severity Medium
- Priority
- Reported Version
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
Opened by Kadu Kov - 11.08.2009
Last edited by Steven Schwartfeger - 12.08.2009
FS#3091 - Map Leak
There's a map leak in the entrance to Hydla, coming from Ojaveda. I didn't find it in this link, so I decided to create a new report.
To explain where it is and what happens, let me describe the whole situation. Going from Oja to Hydla, you exit the Oja gates and go through a pass (pass 1) to a field with a river (field 1), and then there's a green-stoned pass (pass 2) with figures drown on the walls that leads to a second field (field 2). Between this field and the Hydla gates, there is a third pass (pass 3), in which the map leak is located (I have a snapshot, but nowhere to upload it. If really necessary, I can ask some favours).
Most times, when I try the way between Hydla and Oja (back or forth), I fall through the floor at pass 3 and respawn near pass 2. That's really troublesome because i have low stamina, and it takes me 15-30 minutes (I am new to the game, so maybe I don't know the shortest way yet) and 4 or 5 sittings to arrive there, and 3 out of 4 tries result in me being "teleported" to pass 2 (sometimes, i'm lucky enough to spawn on the hydla side)
For the record, I tried climbing the cliff that can be seen on the right side of the pass and jumping inside. Didn't help. Also, I don't know wether or not it makes a difference, but I'm a Mac user. I remember being told map leaks are more frequent between Mac users.
(keywords: map, floor, road, leak, hole, bug, teleported, teleport, respawn, out of bounds positional data, reset, resetting your position )
| ID | Project | Summary | Priority | Severity | Assigned To | Progress | |
|---|---|---|---|---|---|---|---|
| 1796 | PlaneShift | Critical | Mike Gist |
12.08.2009 01:03
Reason for closing:
Additional comments about closing:
Duplicate of PS#1796. Thanks for your
report; the reason it's not listed in
the report you linked is this is not
actually a map bug, it's a graphics
engine bug; fixed in the development
version.