Arx Libertatis Bug Tracker
Please log in to bookmark issues
CLOSED  Bug report #1315  -  Overzealous sprite culling with very large resolutions
Posted Jan 20, 2019 - updated Jan 25, 2019   Shortlink:
icon_info.png This issue has been closed with status "Fixed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Bug report
  • Status
  • Assigned to
    Not assigned to anyone
  • Progress
  • 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
    Not determined
  • Reproducability
  • 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
as seen in the screenshot, the torch on the right is on, but its flame is not rendered. screenshot turn the camera slightly towards it then it is rendered. this only happens when the game window is wider than the normal 16:9. torches on the left side of the screen are not affected. it looks like the game culls torches with a fixed camera frustum without considering actual camera aspect ratio.
Steps to reproduce this issue
run the game on a 21:9 monitor or run the game in windowed mode and make the window wider than 16:9 find a burning torch, then turn the camera until the torch is on the right side of the screen, at this time it will go off. turn the camera slightly back it will start to burn again.

Comment posted by
 Guest user
Jan 20, 02:31
Actually, the description was wrong. I thought it was the aspect ratio, but turns out it's just the window size. If I just reduce the window size, then the problem is gone.
Comment posted by
 Guest user
Jan 20, 02:33
My screen resolution is 3440x1440
Comment posted by
 Guest user
Jan 20, 02:53
This happens in master. 1.1.2 doesn't show this issue
Comment posted by
 Guest user
Jan 20, 10:04
I'm the reporter, I can confirm the bug is now fixed in master. Thank you so much!