I retested using an external FullHD display (while also keeping my laptop display on for other stuff) and everything works quite nice at max settings. I manage around 60fps (the maximum). Warping to jita station still crashes the client if settings are maxed out. Unfortunately I cannot test for more than 10 minutes at max settings as in my room there are 35°C at the moment, so the computer struggles a lot (as do I).
Generally if I want to upload a video for the devs - I load it to a shared Google drive then put the shared link in the bug report - then post the bug report number here with an “@“ at the dev.
Could you please try this a bit further? For me those shortcuts are working fine on the M1 (both MacMini and MBP). Are other shortcuts working correctly or are all broken? I know currently of one known issue with shortcuts, that with some language settings it is possible to break some shortcuts temporarily by pressing the key below the ESC key (as it triggers some kind of composition mode).
It would be great, if you could write bug reports about those issues, optimally from the client (F12 (or Help menu from Neocom) - Report Bug) - please include screenshots for the graphical glitches.
Hello, I was not able to join the mass test (AUTZ, it was like midnight on my time). But I just logged in and test things out.
My in:
MacBook Pro (13-inch, Mid 2012)
2.5 GHz Intel Core i5
6 GB 1600 MHz DDR3
Intel HD Graphics 4000 1536 MB
While the client is a bit slower on the open (kinda normal even with wine on my mbp). First impression on start is its more lightweight than wine client.
The only issue I’ve ran to so far is when like dragging to rotate (spin) ship view in station or in space, the cursor kinds of jumps around. Few minutes after I undocked, the client froze and crashed.
I will continue to play around with it, general experience is great. Thank you for making a native mac client.
Have only managed to log into Sisi onceso far. When I did finally manage to get in the hangar view was completely messed up (Blue screen ray trace style) and the n it crashed my Mac Pro into a reboot. I’ve tried logging bak into to Siri again and now only have a black screen. So far the new client is unplayable for me on both a 2019 MacBook Pro and a 2013 Mac Pro.
First quick remark: you have changed some of the essential shortcuts for the Mac version (ones like ‘stop ship’ etc) – this is completely unnecessary and annoying. We have been playing with these known and good shortcuts for years. There is no excuse to mess with them or change them for the Mac client. Just leave them what they’ve always been. No need to start relearning these things.
Runs like a dream, graphical improvements are stunning, general play through for about an hour last night and had no issues. Certainly a lot less drain on my MB - wine usually has my battery drained in about two hours!
Looking forward to this going live once the issues are resolved.
It has been impossible to get the Wine client to run on this machine but the new native launcher works like a dream. Graphics are beautiful, frame rates good and smooth play comparable to Windows. I wasn’t able to make the test (NZ early morning on a work day) but this evening a couple of hours basic travelling and ratting went very smoothly.
No obvious glitches so far (other than no character portraits). I’ll see if I can try out FW pressures tomorrow.
I am very grateful for the work you devs have put into making a native Mac client and so far, magnificent job. Well done!
My system: Macbook Pro 2017, 2.8GHz Quad Core Intel i7. 16GB RAM. Dual graphics: Radeon Pro 555, Intel HD Graphics 630.
I agree that the graphics look stunning and are a huge improvement over the Windows client. Some of the ship SKINs look like completely new versions, they are that good.
Haven’t experienced any problems running it yet, but I plan to spend a lot more time on Singularity still.
One other issue I noticed last night – there seems to be a dimming of certain ship hulls when docked in a station (Amarr). The station environment looks okay, but the ship is obviously dimmer than looks normal. I noticed this dimming with the Raven hull, for example. But some other hulls looked completely fine (Brutix Navy Issue didn’t appear to have this problem). I will have to check this again, to see if this is a consistent problem.
I have just noticed a weird thing: It does not appear that the native client forces the switch to the discrete GPU. I’ll try to explain better.
Even though when pressing ctrl+f it shows “metal \ AMD Radeon Pro 5300M”, when checking from the apple menu>about this mac which GPU is in use, it says that it’s using the Intel UHD Graphics.
I also checked the historical use using iStat Menus and the Activity monitor, and for the native client it does not switch to the discrete one.
I did the same thing using the wine client and it instantly switches.
I do not know if it manages to use the AMD GPU only for the game, but as far as I know, this system cannot use them both at the same time. I might also be missing something, but still, this had never happened.
I’ll do some testing by forcing the AMD GPU on from the system preferences, but it would be nice to have a feedback.
EDIT: I did some brief testing and disabling the “automatic graphics switching” from the battery menu, thus forcing the use of the AMD GPU, I get better FPS doing the same thing (engaging some rats in an asteroid belt with all settings to max and a resolution of 3072x1920 goes from around 20FPS to around 35FPS)
Seems like Eve nuked my profiles on its own without backing them up… ouch!
Profiles are gone from the TQ folders too though (EDIT: They actually still work on TQ, but copying to SISI doesn’t work), so I’m not sure what the deal is. Perhaps a coincidence? No other known issues with the computer though. (New intel MBP).
We have just deployed a new build to Sisi. The main changes are:
Crashing should be vastly reduced. Any crashes from this point are probably not known to us. If you get a crash, please file a bug report, and let us know what you were doing.
@Aleksandre_Makan , @Meridan_Night - Could you open the FPS windows (Control + F) and see what GPU it reports there?
Would you kindly bug report this (F12) so we can get more system details. This is a very weird bug that we’ve not seen before. It may explain why some users are seeing suboptimal performance
