PPRGaming

As 2026 pops off, I wanted to share a 45 minute video I made today for the @IGN 's of the gaming world, and others, who seem to think that @RobertsSpaceInd is "scamming" everyone. This is a uncut and unnarrarated vid show a small part of this massive #StarCitizen SANDBOX universe being being build by @CloudImperium is building in tandem with @squadron_42 . You will see an ASD Facility located on a moon of the planet Hurston. The game-play is not without its faults, as you will see, with some inventory interaction issues and some NPC's that kind of mini-teleport. While these can be common, it in now way hindered by ability to play or my enjoyment of the gaming session. The "NOT A GAME" mantra is BS and those who play daily know this is the case. Is it perfect? No, but no game is. And right now, SC is - in my honest opinion - in the best state is has every been. **Edit-some of the issues seen can be attributed to the fact I was playing on an EU Sever, though I live on the East Coast of the U.S.**

I'm honestly SHOCKED at how the general public has NO IDEA Artemis II is taking humans out to the moon and will be the furthest humans have ever flown. Every non-space nerd I've talked to has no idea. WE GOTTA GET PEOPLE STOKED!!!! THESE FOUR HUMANS ARE FLYING TO THE MOON!!!

We did it! Thank you guys. Hope you're enjoying all the new updates in the patch. 🤘

#starcitizen @RobertsSpaceInd @CloudImperium Grok seems to know why my game keeps crashing....I'm sure you do to! **Here's the clear, detailed explanation of why you're getting the 3221225477 crash:** ### What the error actually means Error **3221225477** is Windows' way of saying: > "The game tried to read or write to a piece of memory it wasn't allowed to touch." This is called an **Access Violation** (0xC0000005). When this happens, Windows immediately kills the game to protect your system. ### Why it happens in Star Citizen on AMD cards Star Citizen uses **Vulkan** (a modern graphics API) + **Easy Anti-Cheat (EAC)**. On AMD GPUs (especially the RX 7000 and 9000 series like your 7800 XT), these three things don't play nice together: 1. **Vulkan + AMD Drivers** Vulkan is very demanding on the driver. Star Citizen pushes the GPU hard during shader compilation, loading large areas, or when entering the game world. AMD's Vulkan implementation has small timing hiccups (stalls) under this load. 2. **Easy Anti-Cheat (EAC) is very strict** EAC runs in the background and constantly watches for anything suspicious. When the AMD driver has a tiny stall (even 2–4 seconds), EAC sometimes interprets it as "cheating behavior" or a corrupted state. It tells the game to shut down immediately. 3. **Windows TDR (Timeout Detection and Recovery)** Windows has a built-in safety feature: if the GPU driver doesn't respond within **2 seconds**, Windows assumes it's frozen and forcibly resets it. This reset is what actually causes the access violation crash. Your system is hitting a perfect storm: - Vulkan causes small driver stalls - EAC gets nervous - Windows TDR timeout triggers (default = 2 seconds) - Game dies with error 3221225477 This is why: - It happens even after clean installs - Newer drivers (25.10.1, 25.11.1, etc.) often make it worse - DX11 sometimes avoids it (because it doesn't use Vulkan), but runs worse - The crash is very common on RX 7000 / 9000 series cards ### Why hasn't it been fixed yet? - **CIG's side**: They control the engine and EAC integration. They haven't fully optimized the Vulkan path for AMD yet. - **AMD's side**: Their drivers have improved Vulkan performance, but the specific timing/EAC interaction is still problematic. - **EAC's side**: Anti-cheat is intentionally paranoid. It errs on the side of crashing the game rather than letting potential cheats through. It's a three-way compatibility issue that has dragged on for months. CIG knows about it (it's heavily reported), but it's not an easy fix.

@RobertsSpaceInd @CloudImperium #StarCitizen Grok knows why my AMD Card keep crashing the game...and I'm pretty sure you do to. The time is NOW to fix this. "**Here's the clear, detailed explanation of why you're getting the 3221225477 crash:** ### What the error actually means Error **3221225477** is Windows' way of saying: > "The game tried to read or write to a piece of memory it wasn't allowed to touch." This is called an **Access Violation** (0xC0000005). When this happens, Windows immediately kills the game to protect your system. ### Why it happens in Star Citizen on AMD cards Star Citizen uses **Vulkan** (a modern graphics API) + **Easy Anti-Cheat (EAC)**. On AMD GPUs (especially the RX 7000 and 9000 series like your 7800 XT), these three things don't play nice together: 1. **Vulkan + AMD Drivers** Vulkan is very demanding on the driver. Star Citizen pushes the GPU hard during shader compilation, loading large areas, or when entering the game world. AMD's Vulkan implementation has small timing hiccups (stalls) under this load. 2. **Easy Anti-Cheat (EAC) is very strict** EAC runs in the background and constantly watches for anything suspicious. When the AMD driver has a tiny stall (even 2–4 seconds), EAC sometimes interprets it as "cheating behavior" or a corrupted state. It tells the game to shut down immediately. 3. **Windows TDR (Timeout Detection and Recovery)** Windows has a built-in safety feature: if the GPU driver doesn't respond within **2 seconds**, Windows assumes it's frozen and forcibly resets it. This reset is what actually causes the access violation crash. Your system is hitting a perfect storm: - Vulkan causes small driver stalls - EAC gets nervous - Windows TDR timeout triggers (default = 2 seconds) - Game dies with error 3221225477 This is why: - It happens even after clean installs - Newer drivers (25.10.1, 25.11.1, etc.) often make it worse - DX11 sometimes avoids it (because it doesn't use Vulkan), but runs worse - The crash is very common on RX 7000 / 9000 series cards ### Why hasn't it been fixed yet? - **CIG's side**: They control the engine and EAC integration. They haven't fully optimized the Vulkan path for AMD yet. - **AMD's side**: Their drivers have improved Vulkan performance, but the specific timing/EAC interaction is still problematic. - **EAC's side**: Anti-cheat is intentionally paranoid. It errs on the side of crashing the game rather than letting potential cheats through. It's a three-way compatibility issue that has dragged on for months. CIG knows about it (it's heavily reported), but it's not an easy fix.

@RobertsSpaceInd @CloudImperium #StarCitizen GRoK Knows why AMD does not work and why it keeps crashing. Pretty sure you do to. "**Here's the clear, detailed explanation of why you're getting the 3221225477 crash:** ### What the error actually means Error **3221225477** is Windows' way of saying: > "The game tried to read or write to a piece of memory it wasn't allowed to touch." This is called an **Access Violation** (0xC0000005). When this happens, Windows immediately kills the game to protect your system. ### Why it happens in Star Citizen on AMD cards Star Citizen uses **Vulkan** (a modern graphics API) + **Easy Anti-Cheat (EAC)**. On AMD GPUs (especially the RX 7000 and 9000 series like your 7800 XT), these three things don't play nice together: 1. **Vulkan + AMD Drivers** Vulkan is very demanding on the driver. Star Citizen pushes the GPU hard during shader compilation, loading large areas, or when entering the game world. AMD's Vulkan implementation has small timing hiccups (stalls) under this load. 2. **Easy Anti-Cheat (EAC) is very strict** EAC runs in the background and constantly watches for anything suspicious. When the AMD driver has a tiny stall (even 2–4 seconds), EAC sometimes interprets it as "cheating behavior" or a corrupted state. It tells the game to shut down immediately. 3. **Windows TDR (Timeout Detection and Recovery)** Windows has a built-in safety feature: if the GPU driver doesn't respond within **2 seconds**, Windows assumes it's frozen and forcibly resets it. This reset is what actually causes the access violation crash. Your system is hitting a perfect storm: - Vulkan causes small driver stalls - EAC gets nervous - Windows TDR timeout triggers (default = 2 seconds) - Game dies with error 3221225477 This is why: - It happens even after clean installs - Newer drivers (25.10.1, 25.11.1, etc.) often make it worse - DX11 sometimes avoids it (because it doesn't use Vulkan), but runs worse - The crash is very common on RX 7000 / 9000 series cards ### Why hasn't it been fixed yet? - **CIG's side**: They control the engine and EAC integration. They haven't fully optimized the Vulkan path for AMD yet. - **AMD's side**: Their drivers have improved Vulkan performance, but the specific timing/EAC interaction is still problematic. - **EAC's side**: Anti-cheat is intentionally paranoid. It errs on the side of crashing the game rather than letting potential cheats through. It's a three-way compatibility issue that has dragged on for months. CIG knows about it (it's heavily reported), but it's not an easy fix.

@didzej1 @Galidrum What driver are you running?

@PPRGamers @Galidrum hmm works on my 9700XT

Pros and Cons of 4.7 Pros: Stanton performance = better Inventory rework looks pretty 4.7 got me to mine for the first time ever Acquiring blueprints is fun Some annoying bugs in 4.6 got fixed Cons: Pyro performance = worse than 4.6 for me Inventory rework seems just as bad on the backend Inventory rework is not the most intuitive Some new bugs that are annoying All the balance changes and armor changes and radar changes are going to take a while to learn since the game doesn’t absolutely nothing to help you learn that, it’s 100% external sources. Overall, having fun, but from a stability or quality of life standpoint, I don’t think we moved forward in my two days of testing.

@KITST7LEN Woot!

#ForAllMankind Happy Season 5 launch day! youtube.com/shorts/gVmRnm_…

@didzej1 @Galidrum Vulkan and AMD cards are not playing nice. robertsspaceindustries.com/spectrum/commu…

@PPRGamers @Galidrum what crash bug? I haven't noticed while playing yesterday.

For the record, this is still not fixed. @RobertsSpaceInd @CloudImperium @discolando, what is keeping #StarCitizen from fixing this? Is it an AMD issue, a Vulkan issue, or your issue? Not everyone has NVIDIA!

@JayNut_001 I mean, are you running an AMD video card and using Vulkan?

@PPRGamers You mean Vulkan? I do in fact, maybe I need to change that. Crash handler says out of memory which never happened before

I love the new inventory, only problem now is that I have constant crashes after like 5 minutes of gameplay ... well, playing on a patch day is never a good idea -.- #StarCitizen

The RSI Aurora Mk.II Paints Showcase 4k is up now on the YouTube channel! Featuring all the latest paints for the brand new ship from RSI. Watch at the link below 👇 youtu.be/r0U-bNmt664 Liking and sharing is highly appreciated! 🙏 #StarCitizen

@BTV_Cast Ummm, checking out the inventory rework!

Alpha 4.7 is live and crews are already adapting. What’s your FIRST focus in the new patch cycle? #StarCitizen

@heimdelight @RobertsSpaceInd @BeardedCIG Yeah, I did all that for this last patch. Problem is NOT having the latest messes with other games.

@PPRGamers @RobertsSpaceInd @BeardedCIG Nah, I'm on the 2nd to last driver at the moment. Would recommend using AMD cleanup utility to uninstall drivers and install whatever the 2nd to last version is.

With the launcher issues, I could not update last night and will have to do so this evening. Anyone have any luck with AMD working with Vulkan? #StarCitizen @RobertsSpaceInd @BeardedCIG

@heimdelight @RobertsSpaceInd @BeardedCIG Are you on the latest AMD Drivers?

@PPRGamers @RobertsSpaceInd @BeardedCIG Full AMD build here, Vulkan runs great for me.

Do it.

I would place the new Aurora Mk II slightly above the Crusader Intrepid in terms of starter ships. The cargo module gives the Aurora Mk II a slight advantage at 8 SCU (2+6), and providing it modularity gives it a combat advantage. It would be great to see a stealth module... #StarCitizen

FYI: Aurora stuff is going live on the website now, but will be flyable as soon as 4.7 goes live later today. #rareworkrelatedtweet