[Responded]Mac client not fully loading

1. Reproduction Rate: 100%
   
2. Blocker? yes
3. Details: I get to roughly 90% loaded and the screen shows Equipping Avatars then the text on the screen starts flashing. It just sits there in an endless loop.
4. Steps to Reproduce:Just log in with a Mac client
   
5. User Specs: Macbook Pro OS X El Capitan nvidia geforce GT 750m 2048 MB

 

I have something you can try to see if it helps. When you run the launcher, click on the gear icon in the top right to open the options, then in the "Launch Arguments" box, put in the following: -force-glcore

Let me know if that helps!

 

Launching from Steam so the launcher does not have any options.

 

Update: I can load to the novia map. Shortly after entering map the graphics colors all go strange. I get stuck in the loop if I try an enter a zone.

 

Ah, sorry. You can do something similar through Steam. Right click on the game in your library and go to Properties, then click the Set Launch Options.... button and paste in: -force-glcore

 

That got me back in!! Thanks!!

 

@BurningToad Loading OK for me on build 731 without additional launcher argument:

User Specs:
OS: Mac OS X 10.12.6
CPU: Intel(R) Core(TM) i5-5675R CPU @ 3.10GHz (4) System RAM: 16384
GPU: Intel(R) Iris(TM) Pro Graphics 6200 GPU RAM: 1536
SotA.EarlyAccess.LIVE.OSX.64.731.Date.02.21.18
Area: POT_island_metropolis_01_template/Rift's End
Area Display Name: Rift's End
Loc: (45.3, 89.2, 4.3)

Haven't tried starting up outside the POT as yet.

 

I am having the exact same issue. I tried the -force-glcore argument and it worked. Is this a temporary workaround or will this need to be a permanent thing that all mac users do from now on?

User Specs:
OS: Mac OS X 10.11.6
CPU: Intel(R) Core(TM) i7-4850HQ CPU @ 2.30GHz (8) System RAM: 16384
GPU: NVIDIA GeForce GT 750M OpenGL Engine GPU RAM: 2048
SotA.EarlyAccess.LIVE.OSX.64.731.Date.02.21.18
Area: POT_forest_metropolis_01b_template/Verat Chaos
Area Display Name: Verat Chaos
Loc: (18.2, 36.0, 429.5)
Debug: UE9UX2ZvcmVzdF9tZXRyb3BvbGlzXzAxYl90ZW1wbGF0ZXxWZXJhdCBDaGFvc3woMTguMjE4LCAzNi4wMDEsIDQyOS40NzQpfCgwLCAwLjc4OSwgMCwgMC42MTUpfDEwNC4xMjk1fDEwfDcuNTYyNTgx

 

I also found I needed the -force-glcore (by the way what does that do)


User Specs:
OS: Mac OS X 10.11.6
CPU: Intel(R) Core(TM) i7-4771 CPU @ 3.50GHz (8) System RAM: 32768
GPU: NVIDIA GeForce GTX 780M OpenGL Engine GPU RAM: 4096
SotA.EarlyAccess.LIVE.OSX.64.731.Date.02.21.18
Area: Novia_R8_City_PointWest
Area Display Name: Point West
Loc: (-159.8, 38.0, -414.8)
Debug: Tm92aWFfUjhfQ2l0eV9Qb2ludFdlc3R8fCgtMTU5Ljc5OSwgMzcuOTk3LCAtNDE0Ljc1KXwoMCwgLTAuODYyLCAwLCAwLjUwNyl8NTk1LjM4NDN8OS4zMzEzMzl8MS43ODI4NjM=

 

Unity for OSX supports two different graphics APIs, OpenGL and Metal (https://en.wikipedia.org/wiki/Metal_(API)). Metal should provide performance improvements for most machines. SotA supports both methods, but last release OpenGL was set to the first priority to use if supported, and this release we changed it to use Metal if supported. However, it appears that even though Metal is supported on yall's machines, it doesn't work very well for some reason. You could try checking if your graphics drivers, etc are up to date and see if you see any improvement. If this is a very widespread thing, we can change it back to prefer OpenGL.

 

@Undone @BurningToad FWIW, I notice that the two recent posters who are having trouble are on OS X 10.11, while I am on 10.12 and it's working OK in current default. I'm also current on all of Apple's patches for the level of OS X.

(This feels odd. I'm usually the one crashing and complaining while others are working...)

 

I tried again. This time it loaded into the world map (last time i tried to enter a POT). But as soon as it loaded, the screen went a neon orange/green, and then flickered to black/white and stobed back and forth between the two until i about had a seizure and had to force close.

I wish i could update, but this is a development machine and our toolchain is tailored specifically for 10.11. Upgrading isn't in the picture (at least for a while).

For the time being i guess i'll stick with the workaround.

 

OK at the following I still need -force-glcore but I am one release back on the OS, Comcast is not being very fast at the moment and I need to fix that first but I will try and update OS over the weekend


User Specs:
OS: Mac OS X 10.11.6
CPU: Intel(R) Core(TM) i7-4771 CPU @ 3.50GHz (8) System RAM: 32768
GPU: NVIDIA GeForce GTX 780M OpenGL Engine GPU RAM: 4096
SotA.EarlyAccess.LIVE.OSX.64.735.Date.02.23.18
Area: Novia_R8_City_PointWest
Area Display Name: Point West
Loc: (-168.0, 38.4, -431.2)
Debug: Tm92aWFfUjhfQ2l0eV9Qb2ludFdlc3R8fCgtMTY3Ljk1OCwgMzguMzY4LCAtNDMxLjIzMil8KDAsIDAuOTg0LCAwLCAtMC4xOCl8MjAwLjczMjd8MTB8MTIuMjExNQ==

 

OK Comcast just fixed my internet so it is back up to speed and I updated to 10.13 and no longer need -force-glcore (I guess I am now running on Metal) new specs


OS: Mac OS X 10.13.3
CPU: Intel(R) Core(TM) i7-4771 CPU @ 3.50GHz (8) System RAM: 32768
GPU: NVIDIA GeForce GTX 780M GPU RAM: 4096
SotA.EarlyAccess.LIVE.OSX.64.735.Date.02.23.18
Area: Novia_R8_City_PointWest
Area Display Name: Point West
Loc: (-168.8, 38.4, -432.7)
Debug: Tm92aWFfUjhfQ2l0eV9Qb2ludFdlc3R8fCgtMTY4LjgyOCwgMzguMzcsIC00MzIuNzQxKXwoMCwgMC45OTgsIDAsIDAuMDY5KXwtMTg1LjM0MzN8MjcuNDcxMTF8MTIuMjExNQ==

Might what to add to the instructions that old version of OS-X might need the -force-glcore

 

I was able to upgrade to 10.13, and using the default Metal worked. However, since doing that, i was having a terrible time double-clicking things. When i went back to thoe old way (with the -force-glcore flag), double clicking was no longer an issue. I guess for now i'll stick with glcore.