I’m encountering consistent crashes with Eve Online on macOS Sonoma when using a MacBook Pro M2 Max with 64GB RAM and a MacBook M1. The game crashes under default settings, especially during large fleet battles or simply by being in 1DQ. The only workaround is to optimize for memory, which severely degrades the graphics.
Can the dev team replicate this by joining any major fleet battle or spending time in 1DQ with default settings? Also, has any other Mac user pinpointed which specific settings might be causing these crashes?
same here. Happens mainly in systems where there is a lot going on. But I had it happen today in a relatively quiet system and lost a ship+pod because of it.
Going full potato-mode (optimized for either memory or performance) does seem to help.
I’m having the same problem with an M2 Mac Mini, 512GB SSD and 16GB RAM, running Sonoma. It’s got to the stage where the crashes are so frequent that the game is becoming unplayable. I regularly have crashes when simply warping between two gates. I’m based in MJ-5F9. As others have said, crashes seem more likely when a large number of players in a system.
I tried a complete reinstall of the game but it hasn’t improved matters.
Encountering this as well at a stable rate, several times per day if in large systems. The issue seems to appear
In large systems during jump activity, especially if ppl jump through caps on station, this is prevalent the most in large null stagings
If people in system are all docked, the issue doesn’t appear, this happens most when a lot of ships are chilling on undock
This seems to be more prevalent in fleets
This seems to happen less if you are off grid in the same system
Disabling inspace skinning seems to reduce the frequency of crashes the most
However, this issue does not appear altogether if graphics are turned off. Max low graphics with no effects on still lead to crash, but with graphics turned off there were no crashes even with 3k local
There is a CPU spike during the crash
Unfortunately, here is not a single log message that appears during the crash, and doesn’t appear during the normal gameplay, this issue is most probably not covered by current logging
If you don’t have better leads - based on reproduction condtions I would be looking at potential issues appearing when other player’s skins are getting loaded into the client during jumps, undocking, docking and fleet drops.
Tested all graphics settings more thoroughly and got consistent reproduction steps.
Steps to reproduce:
Select High shaders in settings
Get near 50+ large ships on a structure. This doesn’t require capitals, seems to work with 50+ battleships, but the model has to be large.
Warp away from them around 1000km, still on grid
Zoom in the camera on your ship, point the camera at the direction of the ships, and start moving the camera around. This lead to crashes in 5-40 seconds consistently on 32GB M2 Mini.
High shaders with all other settings at low or off has led to crashes as well.
However, lowering shaders seems to work the best I am yet to crash with Medium shaders and all other settings maxed out. High shaders with all other settings low, as mentioned, was crashing.
Resolution and any other graphics settings had little to no effect. Changing shaders to medium has stopped the issue entirely, tested on M2 Mini on 3 simultaneous clients with medium shaders, all other available max settings and 4K res.
What a constructive comment, I am on OSX and CCP markets its product for OSX knowing that I have a model powerful enough to run 4 sessions in full graphics. It’s a code update that has been causing the crash for several months now. I think our request is completely legitimate vov