Arx Libertatis Bug Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report #1424  -  Extreme mouse lag/frame skipping
Posted Feb 28, 2020 - updated Apr 02, 2022   Shortlink: http://arx.vg/1424
action_vote_minus_faded.png
0
Votes
 action_vote_plus_faded.png
icon_info.png This issue is a duplicate of issue #1605 - "Arx Libertatis 1.2 Hard Freeze at start"
icon_info.png This issue has been closed with status "Not a bug" and resolution "DUPLICATE".
Issue details
  • Type of issue
    Bug report
  • Status
     
    		 Not a bug
  • Assigned to
    Not assigned to anyone
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
    Guest user
  • Owned by
    Not owned by anyone
  • Estimated time
    Not estimated
  • Category
    Not determined
  • Resolution
    DUPLICATE
  • Priority
    Not determined
  • Reproducability
    Not determined
  • Severity
    Not determined
  • Targetted for
    icon_milestones.png Not determined
  • OS
    icon_customdatatype.png Not determined
  • Architecture
    icon_customdatatype.png Not determined
  • Fixed in
    icon_customdatatype.png Not determined
Issue description
The mouse appears to be skipping heavily, to unplayable levels. I've uninstalled Arx Fatalis and Arx Libertatis and reinstalled. Curiously, Arx Fatalis itself isn't having the problem. There's no skipping at all in the original version, but any version of Libertatis has this problem for me. It was quite literally working fine one day, and having this problem the next
Steps to reproduce this issue
I'm not really sure how you'd reproduce this.

#1
icon_reply.pngReply
Comment posted by
Guest user
Feb 28, 22:57
Also forgot to mention that this is on windows 10. This is also running through a vm, but since it was working fine, and nothing else is affected, I don't think it's the vm.
#2
icon_reply.pngReply
Comment posted by
Guest user
icon_reply.pngFeb 29, 04:39, in reply to comment #1


Guest user wrote:
Also forgot to mention that this is on windows 10. This is also running
through a vm, but since it was working fine, and nothing else is affected,
I don't think it's the vm.


I decided to see what reinstalling the vm and windows would do, and now it runs fine again. It's the exact same setup, so I'm still not really sure what caused it.
#3
icon_reply.pngReply
Comment posted by
Guest user
Mar 28, 18:59
I experience the issue on Ubuntu Linux 21.10 with the following setup: CPU: Intel i7-3632QM VGA: AMD Radeon HD7730M (mobile) with switchable graphics

I'm launching the game as follows: 
  1. DRI_PRIME=1 ./arx-portable  # make sure to use discrete video card

Arx Libertatis reports at startup: 
  1. [I] OpenGLRenderer:110   Using OpenGL 4.5 (Compatibility Profile) Mesa 21.2.6
 
  1. [I] OpenGLRenderer:113    ├─ Vendor: AMD
 
  1. [I] OpenGLRenderer:116    ├─ Device: AMD VERDE (DRM 2.50.0, 5.13.0-38-generic, LLVM 12.0.1)
 
  1. [I] OpenGLRenderer:130    ├─ Context type: no error
 
  1. [I] OpenGLRenderer:183    └─ VRAM: 2048 MiB, 2048 MiB free

The game intro runs at 60 FPS normally, but the menu is unusable in fullscreen whenever the mouse is moved. Switching to windowed mode (with Alt+Enter) fixes the mouse movement in the menu. It doesn't do anything in-game, though.

Builtin FPS meter shows that while moving mouse, it takes up to a 100 ms to draw a frame and the game becomes unplayable, whether in freelook or cursor mode.

I tried both USB and Bluetooth connected mouse to no avail.
#4
icon_reply.pngReply
Comment posted by
Daniel Scharrer
Apr 02, 15:11
There was Bug report 1595 - fps issue and stuttering with 1.2 that will be fixed in the next version but that would not have affected the main menu and only applies to certain parts in the game.

Possibly related to Bug report 1605 - Arx Libertatis 1.2 Hard Freeze at start.
#5
icon_reply.pngReply
Comment posted by
Daniel Scharrer
Apr 02, 15:22
Marking this as a duplicate for now as the symptoms are similar enough.

The issue was updated with the following change(s):
  • The status has been updated, from New to Not a bug.
  • This issue has been closed
  • The resolution has been updated, from Not determined to DUPLICATE.