GPU Driven Pipeline/Carbon Update - Known Issues

Following the 2025-03-18.1 release with the GPU Driven Pipeline update a known issues thread has been set up for issues specifically relating to engine/graphics for this update.

Game launching and crashing issues on certain Intel Graphics Cards
We have seen an increase in clients having issues with onboard Intel Graphics Cards, which are typically found on laptops and some desktop PCs without a separate dedicated graphics card.
All reports so far have shown old GPU drivers that are many years old. While we continue to investigate this problem, please update your GPU drivers from Intel here, which may resolve the issue for you: https://www.intel.com/content/www/us/en/support/detect.html

Selecting DirectX 11 in the launcher may also resolve this issue, however, you should still update your GPU drivers first.

4 Likes

MacOS performance on the M4 chip has been halved (I’ve detailed this in a separate thread). CPU load and temperature is up, disabling hardware acceleration sees no degradation in performance and the Upscaling options don’t save or aren’t implemented.

I don’t even think the GPUs are being utilized (which would explain the CPU and temperature spike).

System is a MacMini M4 purchased new <2 days ago and completely up-to-date. Was running flawlessly up until the new patch was rolled out.

You should seriously consider rolling back this update.

9 Likes

Waiting for the Next eve is dying thread :frowning:

1 Like

it’s not possible to select DirectX 11 on macOS launcher

3 Likes

I can only imagine the scenes of utter carnage when I try this on my steam deck later.

I just know it’s going to be a bloodbath.

Stats

I play in DirectX 11 in potato mode with the iGPU (HD530) of an i5 6600 Skylake. I experience at least two massive FPS drops during session changes; dock/undocks or jumping through any type of gate. Then the FPS stabilizes at 60 and I can move around the solar system without problems. In DirectX 12 I only see black screens and the game mouse pointer.

Drivers are up to date.

MacOS MacBook M3 Pro
Map looks like:


Performance is significantly worse than before the update.

6 Likes

I’m on an M1 Max and I’m seeing similar “stripes” in green/pink/blue near stations and gates (less extreme than Rievolilen Kalkoken, above, but feels meth’d-out nonetheless).

1 Like

GPU 3070 ti / 3080 , switched from dx11 to 12 for the update
Hard crashed all clients at the same time, and triggered a blue screen.
updated the drivers and still had the same issue

Turning Volumetric effects to low Fixed the issues, now running 5 clients no issues

2 Likes

Forced to lower multiple game graphics settings to maintain ~60 FPS while docked. i5-9600KF 16GB GT 1030. Game now looks like PS2 graphics with lower FPS than PS2.

1 Like

Do you experience huge memory spike and drop? Especially during the fps drops?

I usually play from an old tater laptop and clients now run for ~10-30 seconds after loading in then crash (sometimes taking the OS with it, W10).

Probably unreasonable of me to expect continued support for such old hardware.

/e: the drivers on this thing were already up to date, btw. I guess I finally get myself a contemporary 'puter!

It looks like the M3 chipset may be affected as well. The ‘green map’ is absolutely horrible!

Docked in station (v-sync on)
• Main client (3200x1800): 30-32fps
• Alt clients (2@ 1440x810): 55-60fps

Docked in station (v-sync off)
• Main client (3200x1800): 38-40fps
• Alt clients (2@ 1440x810): 38-40fps

Still scratching my head at this one. De-sync’ing the game results in a fps increase of 20% on my main client window and a decrease of -20% on the two alt client windows.

Client crashes for me today always coincided with a failure of multithreading, i.e. one CPU core suddenly spiked to 100% and stayed there while the rest idled. Client terminally freezes during this until force-quit. Happened within 30 seconds after loading in.

Also this happened regardless of computer btw, occured on three different ones with different CPU, GPU and OS setups.

GPU goes 100% after docking into player owned station.
Intel(R) Core™ i7-7700K CPU @ 4.20GHz
NVIDIA GeForce GTX 1060 3GB

I am using 2 accounts at the same time. Issue is following a character that undocked second and will follow it until session ends.
Session start order is irrelevant. Docking order is irrelevant. Usage goes back to normal after affected character undocks.

EDIT: should mention: dx11, settings set to performance

EDIT2: Updated drivers (released new 2 weeks ago) and changed fps cap in nvidia control panel to 30 allowed me to fix the issue and play rather smoothly (so far) on ‘optimized for memory’. It is still major downgrade in graphics from before the patch.

1 Like

got 30% FPS drop after today’s update…previosly 450-550, now 300-350 :frowning:
7800x3d, 7900xtx, win11 24h2, latest drivers…SADNESS

2 Likes

Update: It seems I can load & use characters indefinitely if they’re out in space.

But if they’re in a structure, viewing outside, a crash seems inevitable.

/edit: actually, it seems to be rendering several ships that causes my crashes.

Out in space at a safe w/just one ship: fine indefinitely.

In station or in a structure using View Inside: fine indefinitely.

On a busy grid (Jita/MJ-5F9) out in space, or in structure using View Outside: crashes.

1 Like

@CCP_Zelus Are you looking into the MacOS-related issues that a lot of us are reporting?

5 Likes

They appear to have pulled the update, it’s not downloading for me.

2 Likes