Jump to content
  • Sign Up

PiXY.6841

Members
  • Posts

    11
  • Joined

  • Last visited

PiXY.6841's Achievements

  1. I just bought an 800€ eGPU just to play Guild Wars 2. this is not happening. WTF. I honestly feel cheated. I put so much trust into your Mac support and defended the poor client quality in the beginning and now this.
  2. As Feedback to the Devs: I can't remember the last time I saw texture flickering ?
  3. I got a warning as well but it didn't mention 32-bit. It just said that it won't work in future versions. I thought it was due to OpenGL being deprecated in Mojave. #Metal
  4. Since the last update I occasionally have green people running around. You can see it in the attached screenshot. It also includes the flickering problem that was reported before. The leaves lose their texture for a split second and then they reappear causing the flickering.https://imgur.com/a/NZBsZx9 EDIT: When I started the game today, it told me that it found corrupted files the last time and asked to repair the data file, that fixed the green people.
  5. The F11 Key is broken in the latest build. It just doesn't get recognised when pressing. All other F-keys work like a charm I'm on MacBook Pro 2016 13" with Touch Bar (the F-keys are on the Touch Bar)
  6. I updated to High Sierra, but I have an SSD anyways so the high I/O Problem wasn't that much of a deal for me anyways. However, I just checked and after 10 Minutes of playing I had around 130MB of Read and Write. So seems like that problem's solved?!
  7. I came to tell how well the client works for me by now. I had to play on all low settings when the client was released and have a frame limiter set to 30 FPS. It rarely hit that limit when the client came out but I noticed yesterday that it was basically stuck to 31 FPS no matter what I did so I started bumping up the settings a bit. I now play with all high textures and high shaders on. The only thing I did was lower the resolution to 1650x1050 (which still is close to 1080p) and disabled DPI scaling. This is amazing and I love how you are constantly improving the client bit by bit with small steps! :) It does lag the first few Minutes when I start the game but gets smoother and smoother the longer I play. I assume that it takes a while until the engine loaded everything into memory and renders stuff? I can only speculate though. I also still have flickering leaves on trees and bushes. I'm happy to provide additional debugging help if necessary. My setup is a standard MacBook Pro 13" from last year: Model Name: MacBook ProModel Identifier: MacBookPro13,2Processor Name: Intel Core i7Processor Speed: 3,3 GHzNumber of Processors: 1Total Number of Cores: 2L2 Cache (per Core): 256 KBL3 Cache: 4 MBMemory: 16 GB
  8. An idea is to definitely check the hard drive I/O and see how much that is slowing down the game.
  9. The client works great for a Beta :) I turned down the resolution a bit to get constant 30 FPS but I have the feeling that it gets better with every update with a few FPS more each time! Thanks guys, keep up the good work!
  10. Thanks, I turned them off as you said, problem solved. Still there must be some way to override them, since there was no such problem in the 32-bit client. There is a difference in the implementation, since the new client supports native fullscreen it automatically brings along all the other benefits of a native fullscreen application. In your case it's unfortunate that it disturbs your game but I'm glad for my part that I can have different workspaces and can easily switch between Wiki and game and won't want them to get rid of it (disclaimer: I'm not using the arrow keys for movement but WASD and I have 'show all useable object names' turned on).
×
×
  • Create New...