Your tinfoil hat may be on just right… it’s certainly an easy way to force players with older hardware to quit without having to refund them…
I’m still not seeing any performance improvements with “EVE Evolved” - anyone else?
Dude, it’s not about just people with old hardware.
While running top on the line spec 9950x3d + 4090 and I’m here in that topic, posting about performance issues 
4 Likes
The game runs better on my steam deck than my PC, and my PC has much newer and more powerful hardware.
Their “custom graphics pipeline” is, as my daughter would say; dog water.
edit: To address your question; No. Not seeing any improvements whatsoever.
2 Likes
I don’t know about ‘‘EVE Evolved’’ (was that a release patch from 2022?), but performance significantly improved on my Macbook Pro a couple of weeks ago. I had had major overheating and CPU overload problems for at least a year prior to 2 weeks ago. It was so bad that I could hardly play the game with graphics disabled, let alone in potato mode (I suspect the issue had something to do with volumetric effects, as discussed earlier in this thread). And some time in the second half of April it got resolved. I am able to play with medium graphics enabled again.
I don’t know what they did, but now my machine runs just warm as opposed to hot and CPU is under control. For the record, I still can’t enable Direct X11, and I can’t disable volumetric effects entirely (even in low-setting mode they are on).
I run the game on Macbook Pro, 2017.
OS X 13.7.5.
2.8 GHz Quad-Core i7.
Radeon Pro 555, 2 GB.
I run 1 client (always have).
2 Likes
-
Old problem which became even more visible during last couple of months- client may abort last command given, especially when not in focus.
-
Memory leak with T3 cruisers and, in some situations, T3 destroyers, causing highly annoying 5-15 seconds long freezes of the client during session change (dock-undock, gate jump etc) and accessing/manipulating fitting tool. Particularly in high load systems like Jita.
-
Obvious problems with switching of LODs while zooming in and out in undocked T3C, particularly Loki
Remarks:
-(2) and (3) could be the same problem, but there were recent undocumented changes to Loki 3D artwork
-(2) and (3) cannot be attributed to obsolescent or low performance hardware, or not up-to-date drivers.
AMD Ryzen R7-5800X, 64GB RAM, RTX3080 10GB is still a decent rig (and going to remain valid for a few years more).
How these things were not noticed by internal QA- very interesting question. Probably meeting a release deadline was more important, lol
I am also not running old hardware…but here I am 
I have never flow a T3. Highest tech thing I have ever flown is a Hulk. I am having this issue on every nullsec undock
2 Likes
To run on to these issues it is sufficient to have T3C on grid with you.
Since downtime yesterday (April 30th) the client on my PC is force-switched to DX12 despite launcher settings telling it to use DX11. It did not do that before, and no changes in drivers or similar occured to cause that.
As a result i now have minor, persistent, constant graphical bugs in all kinds of situations. The exact same ones that caused me to switch to DX12 four years ago. You know, the glitches CCP is supposed to fix instead of waiting it out.
On a side note my passively cooled GPU now reaches 75°C and 43% utilization on minimal graphics settings (… at 138 fps, which is 60% less than i used to get without vsync). If it dies i’m sending the bill to replace it to Reykjavik.
So performance hit and hotter GPU?
1 Like
Yet they were bigging it up as a success today at fanfest lol.
3 Likes
Looks like quite a few more graphical enhancements on the horizon: cube maps, ray-tracing, etc.
Fog, don’t forget the fog.
And more smoke. And fog.
Smoke and Fog? → as in Fog of War? → as in vastly reduced grid size?
Well then surely this might be able to address the lags and stutters introduced by the graphics “improvements”?
Maybe also limit the maximum number of pilots present in any 0.0 system to 30 in total. This should help the “graphics improvements” to realize their full potential.
In all seriousness…time is ticking now for CCP. Unrenderable T3C fleets causing GPU dropouts and crashes and their impact on others were fun to watch for a while. But now subscriptions have started to been cancelled. It is up to CCP to deliver a graphics fix or this will manifest in an income drop when the paid playtime runs out and is not renewed.
Sorry how is the use of cube maps compelling in any way?
oooh check out my 6 pngs they slay chat -_-
No idea. I’ll let you know when they crash my Mac…
More like GPU is constantly at a fairly substantial base load, which it shouldn’t be under performance-optimized graphics settings. In return my CPU cores are basically idle.
Also visual bugs aplenty due to the client being forced into DX12.
Examples:
- solar system map does not show dscan cone or planet orbits, probes on solar system map occasionally disappear depending on zoom level
- occasionally see “effects” on screen as a plane of stripes. Think it’s lighting or reflection effects being rendered incorrectly.
- some ships (only some!) have e.g. forward-facing lines stretching to infinity during warp.
- ship is fully invisible under gate cloak (though that occasionally happened under DX11 too)
- found at least one system where the skybox flashes during warp in one certain position in system (reproducable)
1 Like
Workaround: Disabling DXVK for Proton forces Eve to launch in DX11.
No one brought up T3C issues in any of the live Q&A that I saw. Hopefully someone brought it up in one of the smaller groips.