Jump to content
  • Sign Up

Stormy Dragon.9210

Members
  • Posts

    12
  • Joined

  • Last visited

Posts posted by Stormy Dragon.9210

  1. Right now, one of the hardest things for new players is understanding which skills cause soft-CC and which cause hard-CC. Why not make that easier by having the shape of the skill button on taskbar tell you that?

     

    Instead of having all the numbered skills be squares, why not have normal skills be circles, soft-CC skills be square shaped, and hard-CC skills be eight pointed stars?

  2. > @"ArmoredVehicle.2849" said:

    > > @"Stormy Dragon.9210" said:

    > > > @"ArmoredVehicle.2849" said:

    > > > > @"Stormy Dragon.9210" said:

    > > > > WINE 3.12 had the same problem as with WINE 3.11, and reverting back to WINE 3.10 allows it to run, so it definitely seems to be a WINE thing, but it also seems to not be affecting everyone.

    > > > >

    > > > > Which distro are you using? Maybe it's an Ubuntu 17.10 problem?

    > > >

    > > > I test the game on 3 different PC's each without issues, running a different distro: Mint 18.1, Debian 9, Ubuntu 18.04. Have you tried to run the game in a clean prefix?

    > >

    > > It turns out this issue was due to a bug in WINE that only occurred for CPUs with more than 16 logical processors (the CPU mask format changes and some of the functions couldn't handle the new format):

    > >

    > > https://bugs.winehq.org/show_bug.cgi?id=45453

    > >

    > > The good news is that I was able to work with one of the WINE devs to fix the bug and it was included in the WINE 4.0-rc1 release

    >

    > I read that one in the changelog, is 16 Logical processors as in 8 Cores + 8 Threads or 16 Real Cores? On my 1700X it runs fine on all 16, however performance is better if I limit it to the first 8 threads (taskset -c 0-7).

    >

    > I'm planning to update the Wine version when 4.0 is released however there's 1 small problem, from what I read, the PBA patches are having issues as of 3.21.

     

    In Intel processors, logical cores is 2x physical cores because of hyper-threading.

     

    As I understand the bug, it only occurs on architectures that supports MORE than 16 logical CPUs, so it's only an issue for really new ones like Skylake-X or Threadripper

  3. > @"ArmoredVehicle.2849" said:

    > > @"Stormy Dragon.9210" said:

    > > WINE 3.12 had the same problem as with WINE 3.11, and reverting back to WINE 3.10 allows it to run, so it definitely seems to be a WINE thing, but it also seems to not be affecting everyone.

    > >

    > > Which distro are you using? Maybe it's an Ubuntu 17.10 problem?

    >

    > I test the game on 3 different PC's each without issues, running a different distro: Mint 18.1, Debian 9, Ubuntu 18.04. Have you tried to run the game in a clean prefix?

     

    It turns out this issue was due to a bug in WINE that only occurred for CPUs with more than 16 logical processors (the CPU mask format changes and some of the functions couldn't handle the new format):

     

    https://bugs.winehq.org/show_bug.cgi?id=45453

     

    The good news is that I was able to work with one of the WINE devs to fix the bug and it was included in the WINE 4.0-rc1 release

  4. @""ArmoredVehicle.2849" :

     

    If it helps, this is the error log I am getting:

    >*--> Crash <--*

    >Assertion: jobThreads && (jobThreads <= hardwareThreads)

    >File: ..\..\..\Services\JobManager\Windows\JobManager.cpp(521)

    >App: Gw2-64.exe

    >Pid: 47

    >Cmdline:

    >BaseAddr: 0000000140000000

    >ProgramId: 101

    >Build: 90455

    >When: 2018-07-13T17:19:09Z 2018-07-13T13:19:09-04:00

    >Uptime: 0 days 0:00:01

    >Flags: 0

     

    My first hypothesis is that it has something to do with the changes in 3.11 made to the way the number of cores are calculated?

  5. I have lately been having a bug where every so often, the game will completely stop responding to keyboard inputs for about 20 seconds. During this time it responds to the mouse normally (e.g. I can click a button on the commander bar to activate a skill, but pressing the corresponding number does nothing) and key combinations that the operating system responds to (e.g. alt-tab, ctrl-esc) work normally.

     

    Has anyone else had a similar issue? Does anyone know how I can stop this from happening?

×
×
  • Create New...