Games that launch on consoles first often reach PC weeks or months later, and the delay is rarely a marketing choice. It comes from what the PC is as a hardware target.
A console is a single known machine
A console has one specification. The studio knows the graphics chip, the processor, the amount of memory and the speed of the storage, and every unit in the world matches.
That certainty makes optimisation exact. Engineers can measure how long a frame takes on the only hardware that will ever run the build, then cut work until the frame fits.
The job is finite. Once the game runs well on that machine, it runs well everywhere the game will be sold.
The PC is a range rather than a target
On PC the same code has to run on graphics cards separated by several generations, processors with wildly different core counts, and memory configurations the developer has never seen.
Each combination moves the bottleneck. A build limited by the graphics card on one machine is limited by the processor on another, and the fix for one is not the fix for the other.
Testing therefore multiplies rather than adds. Every setting that can be changed independently widens the number of paths a tester has to walk through before launch.
Drivers sit between the game and the hardware
PC graphics run through drivers written by the card vendors, and those drivers carry their own optimisations, their own defects and their own release schedule.
A game frequently needs vendor attention before it ships, which means sending builds to hardware companies and waiting for driver updates timed to the release date.
That coordination is slow and cannot begin until the game is close to final, so it naturally lands after the console version has been locked down.
PC features are built, not switched on
A settings menu is a feature set. Every option, from resolution scaling to shadow distance to field of view, is a code path someone wrote and someone else has to verify.
Ultrawide displays, variable refresh rates, mouse handling and rebindable keys carry the same cost. Skipping them is what produces the ports players complain about for years afterwards.
Doing them properly takes engineering months the console build never needed, so the PC version is genuinely further from finished at the same point in the schedule.
Staggering the launch spreads the risk
Publishers also separate the dates deliberately. A simultaneous release means every platform's problems arrive on one day, and support teams are swamped by all of them at once.
Launching on fixed hardware first produces a stable build and real player data before the open platform receives it, and many PC-side issues are understood by then.
The cost is a visible gap that reads as neglect. The alternative is a PC version that ships on time and runs badly, which damages the game for far longer.