Skip to content
This repository has been archived by the owner on Apr 17, 2022. It is now read-only.

Vertical Sync causes carashes in Ubuntu 16.10 #4540

Closed
wzdev-ci opened this issue Dec 11, 2016 · 7 comments
Closed

Vertical Sync causes carashes in Ubuntu 16.10 #4540

wzdev-ci opened this issue Dec 11, 2016 · 7 comments

Comments

@wzdev-ci
Copy link
Contributor

resolution_external type_bug | by OFelix


Hi,

I have been suffering from ccrashing whilst setting single player battle options or starting the battle.
This problem is constant not intermittent and the symptom is that the game interface freezes.

Testing has shown that in a clean copy of Ubuntu 16.10 and WZ2100 3.1.1 from Ubuntu repo the problem occurs, whereas in 16.04 with the same game version it does not. I have also tested 3.2.1 built from source which also crashes on 16.10.

The issue is fixed by switching 'Vertical Sync' off. Unfortunately VSync On is the default and other users may not discover this fix.

My system is 64bit i5-6600K Skylake with integrated HD530 graphics, 27" 2560x1440 screen on Display port.


Issue migrated from trac:4540 at 2022-04-16 12:39:19 -0700

@wzdev-ci
Copy link
Contributor Author

OFelix commented


Further testing shows that this problem only occurs on Ubuntu 16.10 with the following settings:

Active Sync is enabled (the default setting)
Resolution 2560x1440
Full screen

If I select 1920x1080, full screen, active sync On then it works okay.

@wzdev-ci
Copy link
Contributor Author

OFelix commented


Hi

FYI, I have tested this in 3.2.2 and the issue is not resolved.

But the scrolling on 3.2.2 feels realy nice :-)

@wzdev-ci
Copy link
Contributor Author

vexed changed status from new to closed

@wzdev-ci
Copy link
Contributor Author

vexed changed resolution from `` to external

@wzdev-ci
Copy link
Contributor Author

vexed changed blocking which not transferred by tractive

@wzdev-ci
Copy link
Contributor Author

vexed changed blockedby which not transferred by tractive

@wzdev-ci
Copy link
Contributor Author

vexed commented


Pretty sure this isn't our issue per se.

We use SDL 2, so, that issue you are having is actually either SDL 2, or video driver, or gdm issue.

Nothing we can do in our codebase to fix that, sorry.

Closing as external.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant