Arx Libertatis Bug Tracker
Please log in to bookmark issues
CLOSED  Bug report #594  -  Missing cursor and glitchy main menu
Posted Dec 03, 2013 - updated Jun 24, 2018   Shortlink:
icon_info.png This issue is a duplicate of issue #593 - "[META] Rendering issues with AL 1.1+"
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
  • Priority
  • 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 regular game works but when the patch is loaded the mouse does not show up and the main menu screen is very glitchy/ patchy. I am wondering if I did anything wrong while installing.
Steps to reproduce this issue
Nothing entered.

Comment posted by
Dec 03, 01:17
Hello Guest user, thanks for reporting this bug.

We're aware of the issue (see related Bug report 593 - [META] Rendering issues with AL 1.1+) but unfortunately none of the developers can reproduce it.

Can you please provide more information about your system ? Posting your arx.log file would also be useful (under Windows this file is located here: C:\Users\USERNAME\Saved Games\Arx Libertatis)

If you could join #arxfatalis on, we could have a chat and probably try to provide you a tentative patch for you to test once we can better understand the issue.

Comment posted by
 Daniel Scharrer
Jun 15, 21:22
Hi, in case you see this, could you please check the latest development snapshot to see if this is still and issue?
Comment posted by
 Daniel Scharrer
Jun 24, 22:44
Closing this issue as there is no useful information beyond what is already in the meta bug.

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.