Complete computer crash while demolishing pipe leading to Liquid Dump

Consistently reproducible but usually only results in a crash of the game, but most recently resulted in the entire computer crashing.

To reproduce, use this save and try to demolish the entire old pipe out to the liquid pump.

Just for reference and curiosity, i tried and could not reproduce here. I erased from both directions and did not encounter a crash either time.

Is there perhaps some other action you did other than erase from "entire old pipe out to the liquid pump"??

Do you have Intel 14h or 15th gen processor by any chance? This reminds me this issue: https://steamcommunity.com/app/1594320/discussions/0/4362376451753243478/

Device name RyzenGeforceH
Processor AMD Ryzen 7 4800H with Radeon Graphics 2.90 GHz
Installed RAM 16.0 GB (15.4 GB usable)
Device ID 3D1B5DD2-B6C9-49C7-B554-BAB9A8BB3303
Product ID 00342-20788-20205-AAOEM
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display

DeletedAccount20950 wrote:

Just for reference and curiosity, i tried and could not reproduce here. I erased from both directions and did not encounter a crash either time.

Not this liquid pump - the one near the settlements that has a new blueprinted liquid dump (don't resume the game from paused mode).

Start demolish-selecting the pipe leading to the old liquid pump at the settlements from the start of the branch, and pull it towards the liquid pump.

Once you get to the lower part of the bend leading to the liquid dump, the game would consistently crash for me.

the_meanie [discord] wrote:

To reproduce, use this save and try to demolish the entire old pipe out to the liquid pump.

This location, not near the oil pumps. The save named Windows crash reproduction.save has the blueprint already set up

ok sorry! its late now but ill try to reproduce for you tommorw, thanks

No rush, I just wanted to contribute as much as I could. :>

It's not a consistent issue for me, I just demolished it differently, but I thought it was a serious bug that I should let people know about.