Arx Libertatis Bug Tracker ~ [CLOSED] #1293 - Player loses control of view on level 5 (caves)

Arx Libertatis Bug Tracker

CLOSED Bug report #1293 - Player loses control of view on level 5 (caves)

Posted Nov 25, 2018 - updated Jul 11, 2021 Shortlink: http://arx.vg/1293

Votes

This issue has been closed with status "Fixed" and resolution "RESOLVED".

Issue details

Type of issue

Bug report Unknown issue type
Status

Fixed

Status not determined
Assigned to

Not assigned to anyone
Progress
Type of bug

Not triaged
Likelihood

Not triaged
Effect

Not triaged
Posted by

nemyax

nemyax
Offline

This user was last seen online at Nov 25, 2018 - 17:27

Show user details

Close this menu
Owned by

Not owned by anyone
Estimated time

No time Not estimated
Time spent

No time No time spent
Category

Not determined
Resolution

RESOLVED Not determined
Priority

Not determined
Reproducability

Always Not determined
Severity

Not determined
Targetted for

Not determined
OS

Not determined
Architecture

Not determined
Fixed in

Arx Libertatis 1.2Not determined

Issue description

If you use the attached save, then on level 5 the camera gets stuck overlooking some goblins in their camp. You can still control the player character marker in the minimap (and apparently the player character proper), but that doesn't affect the view. If you use "cameraactivate none" in the command console, the problem goes away permanently.

Steps to reproduce this issue

Load the save and warp to level 5

Show system-generated comments

Comment posted by

nemyax

Nov 25, 17:26

A file was uploaded. save0011.zip

Comment posted by

Guest user

Apr 05, 02:40, in reply to comment #1

I have this same bug! Was any fix ever found?

nemyax wrote:

A file was uploaded. save0011.zip

Comment posted by

Guest user

Apr 05, 02:41, in reply to comment #3

Whoops, had to read more. Thanks.

Guest user wrote:

I have this same bug! Was any fix ever found?

nemyax wrote:
A file was uploaded. save0011.zip

Comment posted on behalf of

Daniel Scharrer

Apr 12, 00:12

This issue has been updated with the latest changes from the code repository.

Fix wrong path waypoint event
 
When a frame hit the target time of a path waypoint exactly we
incorrectly reported the next waypoint index as reached.
 
Additonally, when loading old saves this could mean that we
send the &#039;on pathend&#039; script event again for paths that were already
completed: Even though the path time was past the end before saving,
the millisecond resolution in the save file could result in it
being rounded down to match the end exactly after loading.
 
Fixes: bug #1293

Comment posted by

Daniel Scharrer

Jun 14, 15:46

This is fixed in 1.2-dev-2020-06-14.

The issue was updated with the following change(s):

This issue has been closed
The status has been updated, from New to Fixed.
The resolution has been updated, from Not determined to RESOLVED.
This issue's progression has been updated to 100 percent completed.

Comment posted on behalf of

Daniel Scharrer

Jun 25, 20:44

This issue has been updated with the latest changes from the code repository.

Fix wrong path waypoint event
 
When a frame hit the target time of a path waypoint exactly we
incorrectly reported the next waypoint index as reached.
 
Additonally, when loading old saves this could mean that we
send the &#039;on pathend&#039; script event again for paths that were already
completed: Even though the path time was past the end before saving,
the millisecond resolution in the save file could result in it
being rounded down to match the end exactly after loading.
 
Fixes: bug #1293

#10

Comment posted on behalf of

Daniel Scharrer

Jul 11, 14:48

The issue was updated with the following change(s):

The custom field Fixed in has been updated, from Unknown to Arx Libertatis 1.2.

fb564d6

master Revision fb564d612bcdc916ef758967f025797d33c63560 by

Daniel Scharrer

Apr 10, 21:17 - Preceeded by 9e46a684563277d9950b49c1e9d845809a35737f

Show more details

Log entry

Fix wrong path waypoint event

When a frame hit the target time of a path waypoint exactly we
incorrectly reported the next waypoint index as reached.

Additonally, when loading old saves this could mean that we
send the 'on pathend' script event again for paths that were already
completed: Even though the path time was past the end before saving,
the millisecond resolution in the save file could result in it
being rounded down to match the end exactly after loading.

Fixes: bug #1293

fb564d6

travis Revision fb564d612bcdc916ef758967f025797d33c63560 by

Daniel Scharrer

Apr 10, 21:17 - Preceeded by 9e46a684563277d9950b49c1e9d845809a35737f

Show more details

Log entry

Fix wrong path waypoint event

When a frame hit the target time of a path waypoint exactly we
incorrectly reported the next waypoint index as reached.

Additonally, when loading old saves this could mean that we
send the 'on pathend' script event again for paths that were already
completed: Even though the path time was past the end before saving,
the millisecond resolution in the save file could result in it
being rounded down to match the end exactly after loading.

Fixes: bug #1293

* Username
* Display name
The "display name" is the name shown to others
Real name
* E-mail address
* Confirm e-mail

Welcome to The Bug Genie

Really delete this comment?

Really delete this comment?

Really delete this comment?

Really delete this comment?

Really delete this comment?

Really delete this comment?

Really delete this comment?

Really delete this comment?

Really delete this comment?

Really delete this comment?

Username
Password