This is not just the case with jump cloak. Happens when ship is using a cloaking device too. This a new bug, I’ve had it happen a week at the most.
1 Like
Several times now my laptop just switched itself off due to overheating since the patch. Highest temperature values I get before it all goes black is when logging in a character, or undocking from a station, or jumping a stargate.
I expereince that too with my mining ships
There is no need to disable proton. You just need to pass it an option and you are up and running again in DX12 on wine. Check the linux section in the forums. I have written it down many times.
DX12 is not what i want though. See my post above for why.
Going by loglite the client now apparently attempts to start the DX redist exe to discern supported DirectX version, which apparently fails on DXVK (but works with WINED3D11). On a fail the client defaults to DX12 on launch.
I had that before this new patch. Paradoxically, for me all overheating issues were resolved with the new patch or whatever CCP did around 2 weeks ago.
before the patch I had no problems at all. I could even run 10 clients on my laptop. now if I start the second one before the first one is completely loaded the system overheats
Did the patch today fix the issue?
It is better indeed. I didnt read about any changes but temp dropped by around 10°C
lol, 3 min after I wrote this computer switched itself off again
how is there still no fix lol?
1 Like
Fix please, im tired of my pc crashing cause of hic bubble graphics.
I crashed my client twice today just by clicking on the F9 system map after a gate jump with a T3C. This is absolutely lovely when you are being hunted by hostiles and the game attempts to hand them your ship on the silver platter.
still no fix then?
idk which patch was that, but today and yesterday I am still having high RAM after taking gates and crashing, or EVE just gets broken without fully crashing which is even worse
Common denominator is we all live in null, dock and undock from citadels out there,
Your post has its own answer. If we collectively haven’t found a workaround yet… it must not be US, huh? I mean, since it happened after they made a big update to the core of the game and all? Dumbass.
Sorry, didn’t mean to be so harsh, but this is ridiculous. WHO lets their software stay like this so long?
1 Like
If this was affecting every player in nullsec, they would have fixed it the very next day. That’s literally thousands of players. The one thing CCP does is cater to nullsec. If multiple thousands of players in null were having this issue daily, the outcry on Reddit would have been so great they would have fixed it long before now.
So, again, it’s some sort of common denominator among your system specs, GPU, drivers, something…
It’s not rocket science. I don’t have any problems whatsoever getting around null, docking or undocking in citadels, or with T3C’s. So, what could the issue be? Hmm, let’s see. We are both playing the same game with the same update. What’s the only difference? Our systems…
docking undocking citadels bad
same as jita 4 4 also bad
still bad, sometimes randomly one client will spike from 2% cpu usage to +70% and freeze and never ever again go down until the client freezes and then crashes
1 Like
I tend to think it’s the system issue as well, with the reports on T3Cs. I’m having no issues. Sure, something that CCP has implemented in their updates is causing this problem on some player rigs, but the fact that other people are having 0 issues when trying to recreate problematic game situations, would let one to believe the real fault is one kind of system setup thingie/file/extension/whatever on players’ computers not being able to handle some kind of game configuration.