Unplayable after update 2.0.2.26

Here is the save and now I got the same thing when trying to leave the load game selection while having the save activated.

Something brings the Memory Usage to go beyond my 27GB that I have to spare.

I had the exact same problem. Verifying the game files via Steam made it possible for me to load the save again

it was working fine before this latest patch, updated it and it's loading forever

creating a new game works, but my progression..

I have a save where when you go from the hydrogen ship camp to the ice cave the game "lags" and then starts eating more and more ram/memory at 100mb per few seconds rate and wont stop until i kill the game. If i instead just play around at the camp it will take ages until the game eats itself.

Edit: Steam game verification didnt help still lags out and starts eating memory at low settings.

Edit2: IF i wait long enough in the main menu it wont even load in to the game it will start eating ram in loading screen.

I am having similar symptoms. For me the game won't go past the loading screen when entering a save game and my ram just fills up all the way. Should you need the log, i will attach it here.

Yep same. I answered on another bug report. The patch seems to have broken something.

Same here. It worked the first time, but after a crash and restart I can't load any saves.

Same here. It worked the first time, but after a crash and restart I can't load any saves

In their Discord, they have already said they are aware of the issue and are looking into it already. Though, didn't say what that specific issue is, but it's leaning towards a huge memory leak issue.

My game ran well without any of the following issues yesterday, but with the new hotfix my experience now is:

- Constant freezes in simulation (see se grass swaying, clouds moving, but I am frozen)

- Endless loading times on saves

- Game crash on save

- High GPU memory usage (4070ti Super 16gb). My memory is completely used up on low or medium settings.

- High RAM memory usage, 22gb used (I have total of 32gb)

Update 1: I managed to actually load my savegame by using the "advanced options" to load a backup. To be precise: the backups listed the save from yesterday evening and one (the current revision) from today. Which is strange, because I never managed to load the game today. I rolled back, loaded and continued playing. But 10min later it started "soft"-freezing (audio on, visual effects moving, but no values, e.g. like target coordinates, changed; world/physics frozen, but visuals still running), going back and forth to "hard"-freezing (absolutely no reaction; windows asking whether one like to wait or terminate the game), and several minutes later simply crashed to desktop (without any error messages or anything).

I attached the logs of this session now, too.

Same issue. Unable to play any length of time without a CTD.

I'm getting the same, loading a existing save causes ram to run-away. Also starting new game as soon as it hits a auto-save point. Have tried dropping graphics presets to minimum - no difference. Running on AMD CPU and NVIDIA GPU

Same issue here...

Version VRAGE3 v2.0.2.26 Release Alpha.

I'm no longer able to load my last saved survival game saved yesterday evening with the previous version that should be the first VS2 released (22:00 PM CET 2025/12/03).

The issue seems to be only with the Continue option,

Just tried using the load option and seems to have loaded the game correctly

Same issue on my PC, hard freeze after minutes of playing. Once it froze so bad I couldnt open the task manager to close it and had to hard reboot.

I7 9700K and Radeon 9060XT 16GB.

The game consumes all system memory and then crashes. I did get it to run once by copying my save (from before today's hotfix) and loading the copy. However, once I saved that it will no longer load.

Same as Kerbo for me, since 2.0.2.26 today. 100%, not 75%.

Same issue here after Hotfix 2.0.2.26.

- Game loads to title screen

- I select my save game

- Game updates to a loading screen background with loading graphic spinning in the bottom right of the screen.

- I waited for 20 minutes before I had to force quite it. I noticed the ram usage according to task manger was at 26 GB (I have 32 GB total).

Attempted reloading the game again and repeated the steps above and same result, endless loading.

Attempted verifying the files in steam incase it was a file corruption issue, but that also made no difference.

Specs: AMD 5700X3D, 32GB DDR 4 Ram, GTX 3080 10GB VRam

I've attached the Logs file from AppData\Roaming\SpaceEngineers2\Temp\Logs

The game freezes when I try to enter the planet's atmosphere (or approach the planet). The only thing that helps is to kill the process in the task manager and restart the game. And it freezes again in the same place.

The game doesn't crash, it just freezes and does't respond to controls (passive movement in the game continues, such as the movement of clouds).

Win11, Core i9 13th, RTX5080, 32Gb

Attached Log Files for last game run instance.

Release notes say this, below. I found on the Steam Beta tab "se2version1_5". Anyone have luck with finding 2.0.2.21 or 2.0.2 as a steam beta?

• Starting with this release, we will always keep previous versions of the game available after major updates. This means you can return to an earlier version at any time and, for example, save your blueprints or creations. You will find these builds in the Steam Beta tab.
  

the game finally started after the update, so that's one issue done

now it's freezing within a minute of continuing my survival game

Something is wrong with the last update. When loading a saved game, the loading screen appears but it doesn't load. It uses a lot of memory, 22-23 GB, while the CPU is at 20-30%.

Same happened to me. By the time I checked task manager it was up to over 43GB of memory usage. I force closed through task manager and reloaded the game. It worked normally the second time around.

Same issue. Randomly locks up and memory just fills up with garbage.

Just got the same issue...

What is strange is that the games seems to work as clouds are moving, but cannot take control of the ship, nothing else is moving and cannot get to the menu.

Only solution was to kill the process.

After today's update, every time I try to enter the planet it freezes, and after starting the game, it freezes again after 3 minutes. I've tried several times, but the game doesn't work.

I have the same bug. Pioneer Edition.

Ryzen 9 7950X, RTX 3080 OC, 32GB. It climbed to 95% Memory usage out of nowhere and freeze me. The game doesn't actually freeze my computer since I can easily alt tab and do other things and even the clouds are animated with no lag at all when I am frozen. It seems to happen the most when traveling in and out of atmosphere (more in than out) and traversing through the planet.

Drivers are updated, and on the latest patch.

I can't load a Survival save game, both the one I've been playing since VS2, but also new ones I have created since today's update.

I can load old Creative saves no problem though.

14.88km froze again. I have restarted pc made sure everything was updated to the fullest. Clouds still move ship says 300m/s but isnt moving any closer at all.

I find the lack of regression testing disturbing.

Im having freezing issues after 2.0.2.26. Game freezes within a min or so of loading saved game. Clouds still move while im flying into the atmosphere of the plane, ship speed shows 300m/s but the ship is frozen from moving at all just stays at 14.88km away from destination.

Had same issue, no crash log generated and session not saved.

I can create a new game, but load a savegame from previous hotfix fail in infine loop. No matter from where is loaded: Continue, Load or Backups.

As it loads save file or continue I notice memory usage also climbs until I run out and then game lock or crash/ 32g mem locks up around 25-27 gig usage

It seems random whether your save will reload or not after.. If you have Task Manager open and see the RAM usage go up, it won't.. When it doesn't, it will!

Same on the lastest version.

Day 1 I could play 3h no problems (except 2-3 random crashes)

Intel i7 12700

32 gig DDR4

RTX 4070

I have a similar problem. While loading my save it seems to load for like, 15-25 minutes than freezes up on the loading screen.

It was working fine on hotfix 2.0.2.21 then on the latest hotfix it seems to have like corrupted my save.

I got the same bug, and my task manager says the same thing, it starts at 11000 mB and just continues going up all the way till 26000

Same problem here. Game kept loading and loading. Eventually after 5 minutes or so my whole computer was having issues, Turns out my 32GB of RAM was maxed out. Can't continue my game. Game is currently broken and unplayable due to the memory leak.

Same problem here. Game kept loading and loading. Eventually after 5 minutes or so my whole computer was having issues, Turns out my 32GB of RAM was maxed out. Can't continue my game. Game is currently broken and unplayable due to the memory leak.

Here is the log from the latest attempt.

Also tried to load a backup. Does not help.

UPD: Successfully loaded backup where i am still near verdure. Kemik backups do not work.

Same issue here, game kind of freezes. I can see thruster and cloud animations still moving, but no response to input, physics seems to stop working (my ship is reported going max speed but is not moving), can't escape to main menu (have to kill the game and restart).

it's literally unplayable since the hotfix.

I can start the game and watch the memory filling up with trash while doing nothing.

If i fly a ship up in space it fills up even faster and at a certain point the game freezes.

Actually, the game doesn't freeze when I try to enter a planet; it freezes after 4 or 5 minutes of gameplay. When it freezes, I have to press Ctrl+Alt+Del and close everything.

Yeah, the 2.0.2.26 hotfix makes the game freeze instantly now in Bazzite running ProtonGE-Latest instantly now, had nearly 4 hours stable before that with no crashes.

Yup, broken here too. I can manage to get about 30 seconds in game before it freezes and the memory leak begins. It seems to begin quicker the older the save is e.g. if I start a new save it'll give me maybe 5 minutes, but for an existing save, less and less.

Today is the 3rd of December...

game plays fine for till I try to finish a contract on planet game freeze's but a can hit window button and then click on the game icon and then click X close it started back fine for about 45 minutes after the after tried again same thing

Same here as well, used up a bunch of memory and also spiked the CPU just before freezing.

CPU: AMD Ryzen 7 7700X

GPU: RX 7600 XT

Pretty disappointing that they release a "fix" without testing it, and it is clearly breaking everyone's game, can we at least get a rollback?

Game softlocks on loading a saved game. Could play by starting a new creative play, then loading a save. But that now softlocks the game. Animations still play, and voice overs. but unable to move or interact with environment.

In your "Welcome to Verdue" folder, you should have backups. Copy the contents of an earlier backup that you think works to the main folder (overwrite the files), and try to load again. That's what i'm having to do right now.

"Hey AMD GPU users, we know you are having issues with the opening cinematic, and even though we had a functional work around, we have instead decided to level the playing field, and now nothing works for anyone! Oh and we don't have game versions available in steam. Sucks to suck! Byyyeeeeeee"

I am also having the same issue. Happens much faster when I fly the grasshopper over 200m/s but happens regardless if I do nothing or not. I've done pretty much all the same troubleshooting that everyone else has done. If I had to warrant a guess the issue is connected to AMD Processors in some way. Specs below

AMD Ryzen 9 5950X

32 GB DDR4 RAM (2133 MT/s)

Nvidia RTX 5070

Samsung 970 Evo Plus 2TB NVMe SSD

Windows 11 Pro 25H2 Build 26200.7171

My backup loaded fine. I flew for less than a minute and crashed again. Likely bad/corrupted chunks trying to load but can't.

Loaded a backup prior to the corruption and crashed again after 1 minute of flying back to the station. Here are my logs:

Loads in but locks up after 1 or 2 frames, im in a ship at full speed on the planet, Also it refuses to load straight from continue, i have use load save.

I can't even enter the world

Exactly the same thing happening to me. (old saves wont even load) but when trying to load them the Ram keeps going up and up till it breaks and crashes. (new game will work for 4-5 Minutes) then randomly freeze and i watch the ram build and build until it uses all 32gig's and crashes. PLEASE FIX! also P.S. I am loving this game! great job and i know glitches will happen!

had to start up new world due to loads not working at all. Then when i finally did get into the new world. The game freezes up after trying to move from the cave to the next area. So it is very broken for the moment. and unplayable in survival mode for the most part. Since todays update was working fine yesterday. However today the game also uses up silly amounts of ram during the process. So memory leak is my main big problem since update. Game uses more then 23gb of ram while trying to run it.

I also have 3 other friends with me experiencing the same issues

and im running a RTX 3050

intel 11th Gen i5-11400h

with 32GB of ram,

i've loaded a different save, and while in game i load the save i actually want, seems to be working some of the time to get around the forever loading thing

Same problem here. Can't leave the cave for the weather station as of today. Game locks up.

The issue seems to occur on both Intel and AMD CPUs, as it's happening to me as well on a Core i7 9700K, RTX 2070, 48GB of RAM.

me too, i9-9900k, 2080ti, 32gb ram, nvme drive

Same Issue. Don't know why .dmp can't be uploaded so changed extension to txt.

my ship use to demande 8GB ram now its 15GB and i cant place the newest version of it because my 32GB isnt enough when it use to demande 14GB before the survival update

I can only play for about 10 minutes before the game locks up & I have to alt-F4.

Win11, i9 11900KF, 64GB RAM, ASUS 3090 Ti

Yeah exact same thing with the save not loading here (although not the menu loading issue). And attempting to load any backup just infinite loads or say something like "World could not be loaded. See log for details."

I think their newest hotfix may have broken something? Unless it has to do with something after reaching Kemik. I had just recently completed one of the two initial contracts there.

i get about 30 mins of gameplay before i have to reload with 32GB of RAM also cant progress the story / tutorial as aproaching the ice cave causes the game to freeze

Hi, the same thing happened to me. Right after the hotfix was released.

Hi, the same thing happened to me. Right after the hotfix was released.

Hi, ever since the latest fixes, Space Engineers 2 keeps freezing in flight mode — whether I’m going from a planet into space or back down again. The sound continues, the clouds keep moving, but the mouse, keyboard, and the ship no longer respond at all.

The game seems to keep running in the background: the CPU stays around 35% usage, and you can literally watch the RAM filling up more and more. My system: Windows 11, i7 13th Gen, 32 GB RAM, RTX 4080. Restarting the game doesn’t help at all.

At the moment the game is basically unplayable, because you need to save every few minutes just to avoid constantly starting over.

Yep, same here. about 30 seconds into flying the grasshopper game locks up and then crashes... weirdly the clouds start moving rapidly...

Same here...

14th gen I7

64GB DDR5

RTX 5070

Steam:

I was tripping but I'm pretty sure the clouds were moving and everything else locked up

Happens to me on kemik at a higher atmosphere in survival and happens on all planets spawned using debug tools in creative mode unless approached using jetpack boost.

Same to me. Looks like it happened after last hotfix 2.0.2.26. In space - works, on Earth or nearby - stop. No any input. Only cloud animation and sound work. Graphics quality doesnt influence on it.

Same to me. Go to planet and image stop. Only cloud and sound work. If i reload the game - memory leak. If happened after last hotfix.

Had a very long load attempt and terminated SE2 after about 15 mins. Tried again a few minutes later and the game loaded fine with no crashes.

after doing some research, it sounds like I'm having a memory leak issue. doesn't matter what the graphic settings are it still crashes. while monitoring PC performance my RAM keeps climbing. while changing the graphic settings low i am also having more difficulty even loading the game

I have the same issue. From one moment to another (one day to antoher acutally) I can't load my last save. It is unmodded vanilla. While loading my PC is filling up the whole 32GB of memory and the circles keep circling forever. Unless I klick. The SE2 becomes unresponsive and I can choose to wait or close. I am waiting for about 3 minutes and my PC starts "working". So it gets loaded. And the game itself is stuck in the loading screen. I didn't play that much so far. Maybe some hours. But still sad. Do you need any save game sent in or so? I double checked and loading doesn't work at all. Restarting works. ANy ideas?

Got an update now. I created a fresh Survival Game. Saved after skipping the intro and tried to load. The same issue. I can't load at all. So this bacame unplayable,...unless,...I keep SE2 open forever :-)

Going to thumbs up this, as I think it's the same issue I've been having. When I'm travelling to the weather station, which is high in altitude, the game freezes. I still hear sound, but the ship stops moving. This is observed since Hotfix 2.0.2.26

Same here, no menu issue. But no error messages. I cut the game after 20minutes of loading my 20hr save. It just pushed more and more data to RAM. I have only 16GB and once allocated ram got to 52GB (and still rising) i cut it. New game loads just fine. Will need to buy more RAM...

Edit: So, new save loads fine, ~28BG allocated, then i fly for like 5 seconds, game lags, sound cuts off, sound restores, game still lagged and i see allocated memory rise again.

For me it's if i try to leave the Atmosphere of Verdure, around the time when i receive the message that Atmo-Thrusters will stop working at specific altitudes.

Pour c'est la même chose lorsque je par en vole avec mon vaisseau le jeux ce fige et plante Windows me dit que le jeux ne répond pas

pour moi c'est la même chose

Hello Engineers,

We are aware of the issue and we are currently working on a solution. We will provide an update as soon as the matter is resolved.

Thank you for your patience and understanding.

Kind Regards,

Bartosz

Keen Software House

Game freezes up at random times.

Here my logs, same scenario as everyone else, was just flying around looking for gold. Game froze, clouds moving but no interactions available. Had to ALT+F4 to close the game.

I have the exakt same problem, but at planet. It seems like the problem only appears while flying, independent wether I use a spacecraft or not. If I start with running and then fly later, the problem apperas not while running phase, it only appears a while after I start flying.

I have made some videos of the behaviour too, but they are to big to attach. If you tell me, I can share them using Google Drive.

I found this error message in my logs!

2025-12-04 13:13:33.678 - Main Thread -> [DefinitionManagerDefinitionSerializationContext] Could not find 2609394a-6cf3-4798-ae05-10a33c0aa4fc

2025-12-04 13:13:33.678 - Main Thread -> [DefinitionManagerDefinitionSerializationContext] Could not find 2d912bf6-ac2a-474e-ae0a-257f97d7ecd6

2025-12-04 13:13:33.678 - Main Thread -> [DefinitionManagerDefinitionSerializationContext] Could not find 3b5b63f4-c71f-45d1-8399-ceb360104ba1

2025-12-04 13:13:33.678 - Main Thread -> [DefinitionManagerDefinitionSerializationContext] Could not find d06e0a51-ec7b-40d1-a1a1-a730b115cbfe

2025-12-04 13:13:33.678 - Main Thread -> [DefinitionManagerDefinitionSerializationContext] Could not find 2d912bf6-ac2a-474e-ae0a-257f97d7ecd6

2025-12-04 13:13:33.678 - Main Thread -> [DefinitionManagerDefinitionSerializationContext] Could not find 3b5b63f4-c71f-45d1-8399-ceb360104ba1

2025-12-04 13:13:33.678 - Main Thread -> [DefinitionManagerDefinitionSerializationContext] Could not find d06e0a51-ec7b-40d1-a1a1-a730b115cbfe

2025-12-04 13:13:33.678 - Main Thread -> [DefinitionManagerDefinitionSerializationContext] Could not find 2d912bf6-ac2a-474e-ae0a-257f97d7ecd6

2025-12-04 13:13:33.678 - Main Thread -> [DefinitionManagerDefinitionSerializationContext] Could not find 3b5b63f4-c71f-45d1-8399-ceb360104ba1

2025-12-04 13:13:33.694 - Main Thread -> Info: Error handled by Keen.VRage.Library.Serialization.Validation.OnDataLossSimplyClearAttribute. Original message: Failed to locate definition with Id 2609394a-6cf3-4798-ae05-10a33c0aa4fc.

2025-12-04 13:13:41.361 - Main Thread -> [DefinitionManagerDefinitionSerializationContext] Could not find 2609394a-6cf3-4798-ae05-10a33c0aa4fc

2025-12-04 13:13:41.361 - Main Thread -> [DefinitionManagerDefinitionSerializationContext] Could not find 2d912bf6-ac2a-474e-ae0a-257f97d7ecd6

2025-12-04 13:13:41.361 - Main Thread -> [DefinitionManagerDefinitionSerializationContext] Could not find 3b5b63f4-c71f-45d1-8399-ceb360104ba1

2025-12-04 13:13:41.361 - Main Thread -> [DefinitionManagerDefinitionSerializationContext] Could not find d06e0a51-ec7b-40d1-a1a1-a730b115cbfe

2025-12-04 13:13:41.361 - Main Thread -> [DefinitionManagerDefinitionSerializationContext] Could not find 2d912bf6-ac2a-474e-ae0a-257f97d7ecd6

2025-12-04 13:13:41.361 - Main Thread -> [DefinitionManagerDefinitionSerializationContext] Could not find 3b5b63f4-c71f-45d1-8399-ceb360104ba1

2025-12-04 13:13:41.361 - Main Thread -> [DefinitionManagerDefinitionSerializationContext] Could not find d06e0a51-ec7b-40d1-a1a1-a730b115cbfe

2025-12-04 13:13:41.361 - Main Thread -> [DefinitionManagerDefinitionSerializationContext] Could not find 2d912bf6-ac2a-474e-ae0a-257f97d7ecd6

2025-12-04 13:13:41.361 - Main Thread -> [DefinitionManagerDefinitionSerializationContext] Could not find 3b5b63f4-c71f-45d1-8399-ceb360104ba1

2025-12-04 13:13:41.371 - Main Thread -> Info: Error handled by Keen.VRage.Library.Serialization.Validation.OnDataLossSimplyClearAttribute. Original message: Failed to locate definition with Id 2609394a-6cf3-4798-ae05-10a33c0aa4fc.

2025-12-04 13:14:00.568 - VRAGE Watchdog Worker -> [Watchdog]: The application froze with freeze type MainThreadFreeze. Capturing dump.

Have the Same Problem. The Update installed yesterday. I loaded my Survival World and after a few Moments the game froze only sound was playing. Cannot load my World now. Only starting a new save works

2025-12-04 15:41:42.987 - Render thread -> VRAM report about missing bytes is changed from 303808512 Bytes to 313790464 Bytes

2025-12-04 15:41:42.987 - Render thread -> Frame [2468] Parallel Render Command Batch RCB-114 created with rcb: 40123141

2025-12-04 15:41:42.987 - Render thread -> Frame [2468] Parallel Render Command Batch RCB-115 created with rcb: 23694839

2025-12-04 15:41:42.987 - Render thread -> Frame [2468] Parallel Render Command Batch RCB-116 created with rcb: 23104223

2025-12-04 15:41:42.987 - Render thread -> Frame [2468] Parallel Render Command Batch RCB-117 created with rcb: 24222635

2025-12-04 15:41:43.002 - Render thread -> Frame [2468] Parallel Render Command Batch RCB-114 processed in 1 frames.

2025-12-04 15:41:43.015 - Render thread -> Frame [2468] Parallel Render Command Batch RCB-115 processed in 1 frames.

2025-12-04 15:41:43.024 - Render thread -> Frame [2468] Parallel Render Command Batch RCB-116 processed in 1 frames.

2025-12-04 15:41:43.048 - Render thread -> Frame [2468] Parallel Render Command Batch RCB-117 processed in 1 frames.

2025-12-04 15:41:43.080 - Render thread -> VRAM report about missing bytes is changed from 313790464 Bytes to 313565184 Bytes

2025-12-04 15:41:43.088 - Render thread -> VRAM report about missing bytes is changed from 313565184 Bytes to 313749504 Bytes

2025-12-04 15:41:43.097 - Render thread -> VRAM report about missing bytes is changed from 313749504 Bytes to 313921536 Bytes

2025-12-04 15:41:43.486 - Render thread -> VRAM report about missing bytes is changed from 313921536 Bytes to 314052608 Bytes

2025-12-04 15:41:43.498 - Render thread -> Frame [2491] Parallel Render Command Batch RCB-118 created with rcb: 46669916

2025-12-04 15:41:43.564 - Render thread -> Error: Model TrussFrame_Wide_Fractured_LOD0.mwm part BrushedMetal does not have material assigned.

2025-12-04 15:41:43.590 - Render thread -> VRAM report about missing bytes is changed from 314052608 Bytes to 313896960 Bytes

2025-12-04 15:41:43.620 - Render thread -> Frame [2492] Parallel Render Command Batch RCB-118 processed in 2 frames.

2025-12-04 15:41:43.669 - Render thread -> VRAM report about missing bytes is changed from 313896960 Bytes to 313843712 Bytes

2025-12-04 15:41:43.685 - Render thread -> VRAM report about missing bytes is changed from 313843712 Bytes to 314011648 Bytes

2025-12-04 15:41:43.697 - Render thread -> VRAM report about missing bytes is changed from 314011648 Bytes to 314167296 Bytes

2025-12-04 15:41:43.720 - Render thread -> VRAM report about missing bytes is changed from 314167296 Bytes to 314134528 Bytes

2025-12-04 15:41:43.721 - Render thread -> Error: Model TrussFrame_Long_Fractured_LOD0.mwm part BrushedMetal does not have material assigned.

2025-12-04 15:41:43.741 - Render thread -> VRAM report about missing bytes is changed from 314134528 Bytes to 314183680 Bytes

2025-12-04 15:41:43.833 - Render thread -> VRAM report about missing bytes is changed from 314183680 Bytes to 315494400 Bytes

2025-12-04 15:41:43.865 - Render thread -> VRAM report about missing bytes is changed from 315494400 Bytes to 316051456 Bytes

2025-12-04 15:41:44.000 - Render thread -> VRAM report about missing bytes is changed from 316051456 Bytes to 316084224 Bytes

2025-12-04 15:41:44.233 - Render thread -> VRAM report about missing bytes is changed from 316084224 Bytes to 316071936 Bytes

2025-12-04 15:41:44.300 - Render thread -> VRAM report about missing bytes is changed from 316071936 Bytes to 316108800 Bytes

2025-12-04 15:41:44.372 - Render thread -> VRAM report about missing bytes is changed from 316108800 Bytes to 316370944 Bytes

2025-12-04 15:41:44.398 - Render thread -> VRAM report about missing bytes is changed from 316370944 Bytes to 316309504 Bytes

2025-12-04 15:41:44.432 - Render thread -> VRAM report about missing bytes is changed from 316309504 Bytes to 317898752 Bytes

2025-12-04 15:41:44.465 - Render thread -> VRAM report about missing bytes is changed from 317898752 Bytes to 317927424 Bytes

2025-12-04 15:41:46.250 - Render thread -> VRAM report about missing bytes is changed from 317927424 Bytes to 317906944 Bytes

2025-12-04 15:41:46.287 - Render thread -> VRAM report about missing bytes is changed from 317906944 Bytes to 318246912 Bytes

2025-12-04 15:41:46.402 - Render thread -> Error: Model Shower250_Deformed_LOD0.mwm part BrushedMetal does not have material assigned.

2025-12-04 15:41:46.798 - Render thread -> VRAM report about missing bytes is changed from 318246912 Bytes to 318541824 Bytes

2025-12-04 15:41:46.849 - Render thread -> VRAM report about missing bytes is changed from 318541824 Bytes to 318603264 Bytes

2025-12-04 15:41:46.914 - Render thread -> VRAM report about missing bytes is changed from 318603264 Bytes to 318996480 Bytes

2025-12-04 15:41:47.964 - Render thread -> VRAM report about missing bytes is changed from 318996480 Bytes to 320241664 Bytes

2025-12-04 15:41:51.682 - Render thread -> VRAM report about missing bytes is changed from 320241664 Bytes to 320200704 Bytes

2025-12-04 15:41:51.738 - Render thread -> VRAM report about missing bytes is changed from 320200704 Bytes to 320253952 Bytes

2025-12-04 15:41:51.981 - Render thread -> VRAM report about missing bytes is changed from 320253952 Bytes to 320237568 Bytes

2025-12-04 15:41:52.015 - Render thread -> VRAM report about missing bytes is changed from 320237568 Bytes to 320278528 Bytes

2025-12-04 15:41:52.935 - Render thread -> VRAM report about missing bytes is changed from 320278528 Bytes to 320225280 Bytes

2025-12-04 15:41:52.970 - Render thread -> VRAM report about missing bytes is changed from 320225280 Bytes to 320282624 Bytes

2025-12-04 15:41:53.076 - Render thread -> VRAM report about missing bytes is changed from 320282624 Bytes to 320229376 Bytes

2025-12-04 15:41:53.148 - Render thread -> VRAM report about missing bytes is changed from 320229376 Bytes to 320241664 Bytes

2025-12-04 15:41:53.168 - Render thread -> VRAM report about missing bytes is changed from 320241664 Bytes to 320294912 Bytes

2025-12-04 15:41:53.398 - Render thread -> VRAM report about missing bytes is changed from 320294912 Bytes to 320266240 Bytes

2025-12-04 15:41:53.451 - Render thread -> Info: [FlaresContext] FlaresContext draw buffers were not big enough for 4 needed elements, resizing from 1 to 4.

2025-12-04 15:41:53.451 - Render thread -> Info: [FlaresContext] FlaresContext occlusion buffers were not big enough for 4 needed elements, resizing from 1 to 4.

2025-12-04 15:41:53.459 - Render thread -> VRAM report about missing bytes is changed from 320266240 Bytes to 320004096 Bytes

2025-12-04 15:41:53.482 - Render thread -> VRAM report about missing bytes is changed from 320004096 Bytes to 320311296 Bytes

2025-12-04 15:41:59.107 - Render thread -> Error: Model Gyroscope250_Deformed_LOD3.mwm part Fracture05-WindowGlass does not have material assigned.

2025-12-04 15:41:59.185 - Render thread -> VRAM report about missing bytes is changed from 320311296 Bytes to 320770048 Bytes

2025-12-04 15:41:59.331 - Render thread -> VRAM report about missing bytes is changed from 320770048 Bytes to 321228800 Bytes

2025-12-04 15:42:00.454 - Render thread -> Info: [FlaresContext] FlaresContext draw buffers were not big enough for 64 needed elements, resizing from 4 to 64.

2025-12-04 15:42:00.454 - Render thread -> Info: [FlaresContext] FlaresContext occlusion buffers were not big enough for 64 needed elements, resizing from 4 to 64.

2025-12-04 15:42:00.477 - Render thread -> VRAM report about missing bytes is changed from 321228800 Bytes to 320860160 Bytes

2025-12-04 15:42:00.697 - Render thread -> VRAM report about missing bytes is changed from 320860160 Bytes to 321384448 Bytes

2025-12-04 15:42:00.719 - Render thread -> VRAM report about missing bytes is changed from 321384448 Bytes to 321867776 Bytes

2025-12-04 15:42:01.194 - Render thread -> VRAM report about missing bytes is changed from 321867776 Bytes to 323506176 Bytes

2025-12-04 15:42:01.831 - Render thread -> VRAM report about missing bytes is changed from 323506176 Bytes to 325799936 Bytes

2025-12-04 15:42:03.688 - Render thread -> VRAM report about missing bytes is changed from 325799936 Bytes to 325787648 Bytes

2025-12-04 15:42:03.775 - Render thread -> VRAM report about missing bytes is changed from 325787648 Bytes to 325804032 Bytes

2025-12-04 15:42:04.181 - Render thread -> VRAM report about missing bytes is changed from 325804032 Bytes to 327184384 Bytes

2025-12-04 15:42:04.211 - Render thread -> VRAM report about missing bytes is changed from 327184384 Bytes to 327245824 Bytes

2025-12-04 15:42:04.394 - Render thread -> VRAM report about missing bytes is changed from 327245824 Bytes to 327385088 Bytes

2025-12-04 15:42:04.411 - Render thread -> VRAM report about missing bytes is changed from 327385088 Bytes to 328040448 Bytes

2025-12-04 15:42:04.430 - Render thread -> VRAM report about missing bytes is changed from 328040448 Bytes to 328359936 Bytes

2025-12-04 15:42:04.459 - Render thread -> VRAM report about missing bytes is changed from 328359936 Bytes to 328302592 Bytes

2025-12-04 15:42:04.482 - Render thread -> VRAM report about missing bytes is changed from 328302592 Bytes to 328425472 Bytes

2025-12-04 15:42:04.511 - Render thread -> VRAM report about missing bytes is changed from 328425472 Bytes to 329146368 Bytes

2025-12-04 15:42:04.590 - Render thread -> VRAM report about missing bytes is changed from 329146368 Bytes to 329097216 Bytes

2025-12-04 15:42:04.645 - Render thread -> VRAM report about missing bytes is changed from 329097216 Bytes to 329154560 Bytes

2025-12-04 15:42:05.232 - Render thread -> VRAM report about missing bytes is changed from 329154560 Bytes to 414027776 Bytes

2025-12-04 15:42:05.258 - .NET TP Worker -> Screenshot root: AppData

2025-12-04 15:42:05.258 - .NET TP Worker -> Screenshot SaveGames\Welcome To Verdure 1\thumb.jpg saved!

2025-12-04 15:42:05.258 - .NET TP Worker -> Screenshot absolute path: C:\Users\Xavier\AppData\Roaming\SpaceEngineers2\AppData\SaveGames\Welcome To Verdure 1\thumb.jpg

2025-12-04 15:42:05.258 - .NET TP Worker -> Screenshot exists on target path.

2025-12-04 15:42:05.282 - Render thread -> VRAM report about missing bytes is changed from 414027776 Bytes to 413007872 Bytes

2025-12-04 15:42:05.756 - Render thread -> Info: Frame[3597] - Available VRAM budget has changed: 19024 MB

2025-12-04 15:42:05.790 - Render thread -> Info: Frame[3599] - Available VRAM budget has changed: 18360 MB

2025-12-04 15:42:06.257 - Render thread -> Info: Frame[3627] - Available VRAM budget has changed: 18487 MB

2025-12-04 15:42:06.380 - Render thread -> VRAM report about missing bytes is changed from 413007872 Bytes to 417988608 Bytes

2025-12-04 15:51:07.794 - .NET TP Worker -> Screenshot root: AppData

2025-12-04 15:51:07.794 - .NET TP Worker -> Screenshot SaveGames\Welcome To Verdure 1\thumb.jpg saved!

2025-12-04 15:51:07.794 - .NET TP Worker -> Screenshot absolute path: C:\Users\Xavier\AppData\Roaming\SpaceEngineers2\AppData\SaveGames\Welcome To Verdure 1\thumb.jpg

2025-12-04 15:51:07.794 - .NET TP Worker -> Screenshot exists on target path.

2025-12-04 15:52:20.389 - Render thread -> VRAM report about missing bytes is changed from 417988608 Bytes to 420020224 Bytes

2025-12-04 15:52:32.225 - Render thread -> VRAM report about missing bytes is changed from 420020224 Bytes to 420192256 Bytes

2025-12-04 15:52:32.292 - Render thread -> VRAM report about missing bytes is changed from 420192256 Bytes to 420364288 Bytes

2025-12-04 15:52:32.358 - Render thread -> VRAM report about missing bytes is changed from 420364288 Bytes to 420708352 Bytes

2025-12-04 15:52:32.424 - Render thread -> VRAM report about missing bytes is changed from 420708352 Bytes to 421052416 Bytes

2025-12-04 15:52:32.457 - Render thread -> VRAM report about missing bytes is changed from 421052416 Bytes to 421224448 Bytes

2025-12-04 15:52:32.476 - Render thread -> Info: Frame[41077] - Available VRAM budget has changed: 18365 MB

2025-12-04 15:52:32.492 - Render thread -> VRAM report about missing bytes is changed from 421224448 Bytes to 421396480 Bytes

2025-12-04 15:52:32.524 - Render thread -> VRAM report about missing bytes is changed from 421396480 Bytes to 421740544 Bytes

2025-12-04 15:52:32.591 - Render thread -> VRAM report about missing bytes is changed from 421740544 Bytes to 422084608 Bytes

2025-12-04 15:52:32.624 - Render thread -> VRAM report about missing bytes is changed from 422084608 Bytes to 422256640 Bytes

2025-12-04 15:52:32.658 - Render thread -> VRAM report about missing bytes is changed from 422256640 Bytes to 422690816 Bytes

2025-12-04 15:52:32.690 - Render thread -> VRAM report about missing bytes is changed from 422690816 Bytes to 422813696 Bytes

2025-12-04 15:52:32.724 - Render thread -> VRAM report about missing bytes is changed from 422813696 Bytes to 422985728 Bytes

2025-12-04 15:52:32.790 - Render thread -> VRAM report about missing bytes is changed from 422985728 Bytes to 423157760 Bytes

2025-12-04 15:52:32.858 - Render thread -> VRAM report about missing bytes is changed from 423157760 Bytes to 423034880 Bytes

2025-12-04 15:52:32.924 - Render thread -> VRAM report about missing bytes is changed from 423034880 Bytes to 423206912 Bytes

2025-12-04 15:52:32.957 - Render thread -> VRAM report about missing bytes is changed from 423206912 Bytes to 423256064 Bytes

2025-12-04 15:52:35.758 - Render thread -> VRAM report about missing bytes is changed from 423256064 Bytes to 422887424 Bytes

2025-12-04 15:52:35.976 - Render thread -> Info: Frame[41287] - Available VRAM budget has changed: 18475 MB

2025-12-04 15:52:36.158 - Render thread -> VRAM report about missing bytes is changed from 422887424 Bytes to 422969344 Bytes

2025-12-04 15:52:36.191 - Render thread -> VRAM report about missing bytes is changed from 422969344 Bytes to 423051264 Bytes

2025-12-04 15:52:36.225 - Render thread -> VRAM report about missing bytes is changed from 423051264 Bytes to 423313408 Bytes

2025-12-04 15:52:36.274 - Render thread -> VRAM report about missing bytes is changed from 423313408 Bytes to 423198720 Bytes

2025-12-04 15:52:36.334 - Render thread -> VRAM report about missing bytes is changed from 423198720 Bytes to 422682624 Bytes

2025-12-04 15:52:36.408 - .NET TP Worker -> Screenshot root: AppData

2025-12-04 15:52:36.408 - .NET TP Worker -> Screenshot SaveGames\Welcome To Verdure 1\thumb.jpg saved!

2025-12-04 15:52:36.408 - .NET TP Worker -> Screenshot absolute path: C:\Users\Xavier\AppData\Roaming\SpaceEngineers2\AppData\SaveGames\Welcome To Verdure 1\thumb.jpg

2025-12-04 15:52:36.408 - .NET TP Worker -> Screenshot exists on target path.

2025-12-04 15:52:36.676 - Render thread -> VRAM report about missing bytes is changed from 422682624 Bytes to 422637568 Bytes

2025-12-04 15:52:36.708 - Render thread -> VRAM report about missing bytes is changed from 422637568 Bytes to 422686720 Bytes

2025-12-04 15:52:36.957 - Render thread -> VRAM report about missing bytes is changed from 422686720 Bytes to 422858752 Bytes

2025-12-04 15:52:37.643 - Render thread -> Info: Frame[41379] - Available VRAM budget has changed: 18362 MB

2025-12-04 15:52:37.657 - Render thread -> VRAM report about missing bytes is changed from 422858752 Bytes to 423030784 Bytes

2025-12-04 15:52:37.791 - Render thread -> VRAM report about missing bytes is changed from 423030784 Bytes to 423071744 Bytes

2025-12-04 15:52:37.866 - Render thread -> VRAM report about missing bytes is changed from 423071744 Bytes to 422973440 Bytes

2025-12-04 15:52:38.291 - Render thread -> VRAM report about missing bytes is changed from 422973440 Bytes to 422928384 Bytes

2025-12-04 15:52:38.324 - Render thread -> VRAM report about missing bytes is changed from 422928384 Bytes to 422973440 Bytes

2025-12-04 15:52:38.357 - Render thread -> VRAM report about missing bytes is changed from 422973440 Bytes to 422891520 Bytes

2025-12-04 15:52:38.391 - Render thread -> VRAM report about missing bytes is changed from 422891520 Bytes to 423055360 Bytes

2025-12-04 15:52:38.458 - Render thread -> VRAM report about missing bytes is changed from 423055360 Bytes to 422678528 Bytes

2025-12-04 15:52:38.624 - Render thread -> VRAM report about missing bytes is changed from 422678528 Bytes to 422850560 Bytes

2025-12-04 15:52:38.891 - Render thread -> VRAM report about missing bytes is changed from 422850560 Bytes to 423022592 Bytes

2025-12-04 15:52:42.724 - Render thread -> VRAM report about missing bytes is changed from 423022592 Bytes to 423194624 Bytes

2025-12-04 15:52:42.792 - Render thread -> VRAM report about missing bytes is changed from 423194624 Bytes to 422948864 Bytes

2025-12-04 15:52:43.191 - Render thread -> VRAM report about missing bytes is changed from 422948864 Bytes to 423243776 Bytes

2025-12-04 15:52:43.224 - Render thread -> VRAM report about missing bytes is changed from 423243776 Bytes to 423587840 Bytes

2025-12-04 15:52:43.258 - Render thread -> VRAM report about missing bytes is changed from 423587840 Bytes to 423415808 Bytes

2025-12-04 15:52:43.324 - Render thread -> VRAM report about missing bytes is changed from 423415808 Bytes to 423587840 Bytes

2025-12-04 15:52:43.357 - Render thread -> VRAM report about missing bytes is changed from 423587840 Bytes to 423759872 Bytes

2025-12-04 15:52:43.424 - Render thread -> VRAM report about missing bytes is changed from 423759872 Bytes to 424103936 Bytes

2025-12-04 15:52:43.524 - Render thread -> VRAM report about missing bytes is changed from 424103936 Bytes to 424275968 Bytes

2025-12-04 15:52:43.624 - Render thread -> VRAM report about missing bytes is changed from 424275968 Bytes to 424620032 Bytes

2025-12-04 15:52:43.690 - Render thread -> VRAM report about missing bytes is changed from 424620032 Bytes to 424792064 Bytes

2025-12-04 15:52:43.857 - Render thread -> VRAM report about missing bytes is changed from 424792064 Bytes to 424964096 Bytes

2025-12-04 15:52:47.457 - Render thread -> VRAM report about missing bytes is changed from 424964096 Bytes to 425136128 Bytes

2025-12-04 15:52:50.657 - Render thread -> VRAM report about missing bytes is changed from 425136128 Bytes to 425095168 Bytes

2025-12-04 15:52:58.191 - Render thread -> VRAM report about missing bytes is changed from 425095168 Bytes to 425373696 Bytes

2025-12-04 15:52:58.210 - Render thread -> VRAM report about missing bytes is changed from 425373696 Bytes to 425332736 Bytes

2025-12-04 15:52:58.242 - Render thread -> VRAM report about missing bytes is changed from 425332736 Bytes to 425377792 Bytes

2025-12-04 15:52:58.258 - Render thread -> VRAM report about missing bytes is changed from 425377792 Bytes to 424902656 Bytes

2025-12-04 15:52:58.624 - Render thread -> VRAM report about missing bytes is changed from 424902656 Bytes to 425078784 Bytes

2025-12-04 15:52:58.691 - Render thread -> VRAM report about missing bytes is changed from 425078784 Bytes to 424755200 Bytes

2025-12-04 15:52:58.976 - Render thread -> Info: Frame[42659] - Available VRAM budget has changed: 18455 MB

2025-12-04 15:52:59.558 - Render thread -> VRAM report about missing bytes is changed from 424755200 Bytes to 424984576 Bytes

2025-12-04 15:52:59.625 - Render thread -> VRAM report about missing bytes is changed from 424984576 Bytes to 424706048 Bytes

2025-12-04 15:52:59.991 - Render thread -> VRAM report about missing bytes is changed from 424706048 Bytes to 424529920 Bytes

2025-12-04 15:53:00.058 - Render thread -> VRAM report about missing bytes is changed from 424529920 Bytes to 424407040 Bytes

2025-12-04 15:53:00.424 - Render thread -> VRAM report about missing bytes is changed from 424407040 Bytes to 424529920 Bytes

2025-12-04 15:53:00.492 - Render thread -> VRAM report about missing bytes is changed from 424529920 Bytes to 424300544 Bytes

2025-12-04 15:53:00.725 - Render thread -> VRAM report about missing bytes is changed from 424300544 Bytes to 424263680 Bytes

2025-12-04 15:53:00.758 - Render thread -> VRAM report about missing bytes is changed from 424263680 Bytes to 424304640 Bytes

2025-12-04 15:53:00.959 - Render thread -> VRAM report about missing bytes is changed from 424304640 Bytes to 424181760 Bytes

2025-12-04 15:53:01.458 - Render thread -> VRAM report about missing bytes is changed from 424181760 Bytes to 424148992 Bytes

2025-12-04 15:53:01.491 - Render thread -> VRAM report about missing bytes is changed from 424148992 Bytes to 424185856 Bytes

2025-12-04 15:53:13.524 - Render thread -> VRAM report about missing bytes is changed from 424185856 Bytes to 424062976 Bytes

2025-12-04 15:53:13.858 - Render thread -> VRAM report about missing bytes is changed from 424062976 Bytes to 423940096 Bytes

2025-12-04 15:53:14.157 - Render thread -> VRAM report about missing bytes is changed from 423940096 Bytes to 423911424 Bytes

2025-12-04 15:53:14.191 - Render thread -> VRAM report about missing bytes is changed from 423911424 Bytes to 423944192 Bytes

2025-12-04 15:54:20.224 - Render thread -> VRAM report about missing bytes is changed from 423944192 Bytes to 423890944 Bytes

2025-12-04 15:54:20.258 - Render thread -> VRAM report about missing bytes is changed from 423890944 Bytes to 423948288 Bytes

2025-12-04 15:54:32.992 - Render thread -> VRAM report about missing bytes is changed from 423948288 Bytes to 423923712 Bytes

2025-12-04 15:54:33.025 - Render thread -> VRAM report about missing bytes is changed from 423923712 Bytes to 423952384 Bytes

2025-12-04 15:54:35.262 - Render thread -> VRAM report about missing bytes is changed from 423952384 Bytes to 423931904 Bytes

2025-12-04 15:54:35.291 - Render thread -> VRAM report about missing bytes is changed from 423931904 Bytes to 423956480 Bytes

2025-12-04 15:54:35.841 - Render thread -> VRAM report about missing bytes is changed from 423956480 Bytes to 423936000 Bytes

2025-12-04 15:54:35.875 - Render thread -> VRAM report about missing bytes is changed from 423936000 Bytes to 423956480 Bytes

2025-12-04 15:54:37.591 - Render thread -> VRAM report about missing bytes is changed from 423956480 Bytes to 423936000 Bytes

2025-12-04 15:54:37.625 - Render thread -> VRAM report about missing bytes is changed from 423936000 Bytes to 423956480 Bytes

2025-12-04 15:54:38.541 - Render thread -> VRAM report about missing bytes is changed from 423956480 Bytes to 423940096 Bytes

2025-12-04 15:54:38.575 - Render thread -> VRAM report about missing bytes is changed from 423940096 Bytes to 423960576 Bytes

2025-12-04 15:54:40.158 - Render thread -> VRAM report about missing bytes is changed from 423960576 Bytes to 423944192 Bytes

2025-12-04 15:54:40.191 - Render thread -> VRAM report about missing bytes is changed from 423944192 Bytes to 423960576 Bytes

2025-12-04 15:54:49.176 - Render thread -> Info: Frame[49271] - Available VRAM budget has changed: 18358 MB

2025-12-04 15:54:49.425 - Render thread -> VRAM report about missing bytes is changed from 423960576 Bytes to 424046592 Bytes

2025-12-04 15:54:49.458 - Render thread -> VRAM report about missing bytes is changed from 424046592 Bytes to 424108032 Bytes

2025-12-04 15:54:49.507 - Render thread -> VRAM report about missing bytes is changed from 424108032 Bytes to 424255488 Bytes

2025-12-04 15:54:49.757 - Render thread -> VRAM report about missing bytes is changed from 424255488 Bytes to 424443904 Bytes

2025-12-04 15:54:49.826 - Render thread -> VRAM report about missing bytes is changed from 424443904 Bytes to 424271872 Bytes

2025-12-04 15:54:52.125 - Render thread -> VRAM report about missing bytes is changed from 424271872 Bytes to 424443904 Bytes

2025-12-04 15:54:52.191 - Render thread -> VRAM report about missing bytes is changed from 424443904 Bytes to 424431616 Bytes

2025-12-04 15:54:52.225 - Render thread -> VRAM report about missing bytes is changed from 424431616 Bytes to 424448000 Bytes

2025-12-04 15:54:56.343 - Render thread -> Info: Frame[49697] - Available VRAM budget has changed: 18929 MB

2025-12-04 15:54:56.343 - Render thread -> Info: Frame[49697] - Available VRAM budget has changed: 18248 MB

2025-12-04 15:54:59.808 - Render thread -> VRAM report about missing bytes is changed from 424448000 Bytes to 424620032 Bytes

2025-12-04 15:55:00.151 - Render thread -> VRAM report about missing bytes is changed from 424620032 Bytes to 424660992 Bytes

2025-12-04 15:55:00.208 - Render thread -> VRAM report about missing bytes is changed from 424660992 Bytes to 424701952 Bytes

2025-12-04 15:55:01.475 - Render thread -> VRAM report about missing bytes is changed from 424701952 Bytes to 424873984 Bytes

2025-12-04 15:55:01.491 - Render thread -> VRAM report about missing bytes is changed from 424873984 Bytes to 425988096 Bytes

2025-12-04 15:55:13.477 - Render thread -> Info: Frame[50713] - Available VRAM budget has changed: 18352 MB

2025-12-04 15:55:14.007 - Render thread -> VRAM report about missing bytes is changed from 425988096 Bytes to 425979904 Bytes

2025-12-04 15:55:14.041 - Render thread -> VRAM report about missing bytes is changed from 425979904 Bytes to 425992192 Bytes

2025-12-04 15:55:16.258 - Render thread -> VRAM report about missing bytes is changed from 425992192 Bytes to 426164224 Bytes

2025-12-04 15:55:18.358 - Render thread -> VRAM report about missing bytes is changed from 426164224 Bytes to 426328064 Bytes

2025-12-04 15:55:18.392 - Render thread -> VRAM report about missing bytes is changed from 426328064 Bytes to 426336256 Bytes

2025-12-04 15:55:21.291 - Render thread -> VRAM report about missing bytes is changed from 426336256 Bytes to 426377216 Bytes

2025-12-04 15:55:21.524 - Render thread -> VRAM report about missing bytes is changed from 426377216 Bytes to 426426368 Bytes

2025-12-04 15:55:25.091 - Render thread -> VRAM report about missing bytes is changed from 426426368 Bytes to 426598400 Bytes

2025-12-04 15:55:25.724 - Render thread -> VRAM report about missing bytes is changed from 426598400 Bytes to 426770432 Bytes

2025-12-04 15:55:25.841 - Render thread -> VRAM report about missing bytes is changed from 426770432 Bytes to 426762240 Bytes

2025-12-04 15:55:25.875 - Render thread -> VRAM report about missing bytes is changed from 426762240 Bytes to 426770432 Bytes

2025-12-04 15:55:28.597 - Render thread -> VRAM report about missing bytes is changed from 426770432 Bytes to 426766336 Bytes

2025-12-04 15:55:28.625 - Render thread -> VRAM report about missing bytes is changed from 426766336 Bytes to 426774528 Bytes

2025-12-04 15:55:29.908 - Render thread -> VRAM report about missing bytes is changed from 426774528 Bytes to 426946560 Bytes

2025-12-04 15:55:30.708 - Render thread -> VRAM report about missing bytes is changed from 426946560 Bytes to 426950656 Bytes

2025-12-04 15:55:56.500 - Render thread -> Info: Frame[53279] - Available VRAM budget has changed: 18246 MB

2025-12-04 15:55:56.525 - Render thread -> VRAM report about missing bytes is changed from 426950656 Bytes to 427278336 Bytes

2025-12-04 15:55:56.559 - Render thread -> VRAM report about missing bytes is changed from 427278336 Bytes to 426991616 Bytes

2025-12-04 15:55:56.765 - Render thread -> VRAM report about missing bytes is changed from 426991616 Bytes to 427040768 Bytes

2025-12-04 15:56:18.379 - Render thread -> VRAM report about missing bytes is changed from 427040768 Bytes to 427065344 Bytes

2025-12-04 15:56:19.308 - Render thread -> VRAM report about missing bytes is changed from 427065344 Bytes to 427089920 Bytes

2025-12-04 15:56:31.826 - Render thread -> Info: Frame[55389] - Available VRAM budget has changed: 18345 MB

2025-12-04 15:57:09.992 - Render thread -> VRAM report about missing bytes is changed from 427089920 Bytes to 427261952 Bytes

2025-12-04 15:57:11.328 - Render thread -> VRAM report about missing bytes is changed from 427261952 Bytes to 427200512 Bytes

2025-12-04 15:57:12.360 - Render thread -> VRAM report about missing bytes is changed from 427200512 Bytes to 427139072 Bytes

2025-12-04 15:57:12.392 - Render thread -> VRAM report about missing bytes is changed from 427139072 Bytes to 427200512 Bytes

2025-12-04 15:57:13.608 - Render thread -> VRAM report about missing bytes is changed from 427200512 Bytes to 427139072 Bytes

2025-12-04 15:57:13.642 - Render thread -> VRAM report about missing bytes is changed from 427139072 Bytes to 427200512 Bytes

2025-12-04 15:57:16.260 - Render thread -> VRAM report about missing bytes is changed from 427200512 Bytes to 427143168 Bytes

2025-12-04 15:57:16.292 - Render thread -> VRAM report about missing bytes is changed from 427143168 Bytes to 427204608 Bytes

2025-12-04 15:57:17.677 - Render thread -> Info: Frame[58131] - Available VRAM budget has changed: 18236 MB

2025-12-04 15:57:19.726 - Render thread -> VRAM report about missing bytes is changed from 427204608 Bytes to 427147264 Bytes

2025-12-04 15:57:19.758 - Render thread -> VRAM report about missing bytes is changed from 427147264 Bytes to 427204608 Bytes

2025-12-04 15:57:29.039 - Render thread -> Info: [FlaresContext] FlaresContext draw buffers were not big enough for 128 needed elements, resizing from 64 to 128.

2025-12-04 15:57:29.039 - Render thread -> Info: [FlaresContext] FlaresContext occlusion buffers were not big enough for 128 needed elements, resizing from 64 to 128.

2025-12-04 15:57:29.048 - Render thread -> VRAM report about missing bytes is changed from 427204608 Bytes to 426962944 Bytes

2025-12-04 15:57:29.081 - Render thread -> VRAM report about missing bytes is changed from 426962944 Bytes to 427331584 Bytes

2025-12-04 15:57:40.276 - Render thread -> VRAM report about missing bytes is changed from 427331584 Bytes to 427278336 Bytes

2025-12-04 15:57:40.308 - Render thread -> VRAM report about missing bytes is changed from 427278336 Bytes to 427335680 Bytes

2025-12-04 15:57:41.909 - Render thread -> VRAM report about missing bytes is changed from 427335680 Bytes to 427286528 Bytes

2025-12-04 15:57:41.943 - Render thread -> VRAM report about missing bytes is changed from 427286528 Bytes to 427339776 Bytes

2025-12-04 15:57:42.808 - Render thread -> VRAM report about missing bytes is changed from 427339776 Bytes to 427290624 Bytes

2025-12-04 15:57:42.842 - Render thread -> VRAM report about missing bytes is changed from 427290624 Bytes to 427339776 Bytes

2025-12-04 15:57:43.442 - Render thread -> VRAM report about missing bytes is changed from 427339776 Bytes to 427290624 Bytes

2025-12-04 15:57:43.475 - Render thread -> VRAM report about missing bytes is changed from 427290624 Bytes to 427339776 Bytes

2025-12-04 15:57:44.044 - Render thread -> Info: Frame[59713] - Available VRAM budget has changed: 18368 MB

2025-12-04 15:57:44.777 - Render thread -> Info: Frame[59757] - Available VRAM budget has changed: 18273 MB

2025-12-04 15:57:45.608 - Render thread -> VRAM report about missing bytes is changed from 427339776 Bytes to 427298816 Bytes

2025-12-04 15:57:45.676 - Render thread -> VRAM report about missing bytes is changed from 427298816 Bytes to 427347968 Bytes

2025-12-04 15:58:08.844 - Render thread -> Info: Frame[61189] - Available VRAM budget has changed: 18367 MB

2025-12-04 15:58:09.979 - Render thread -> VRAM report about missing bytes is changed from 427347968 Bytes to 427311104 Bytes

2025-12-04 15:58:10.009 - Render thread -> VRAM report about missing bytes is changed from 427311104 Bytes to 427352064 Bytes

2025-12-04 15:58:11.459 - Render thread -> VRAM report about missing bytes is changed from 427352064 Bytes to 427315200 Bytes

2025-12-04 15:58:11.492 - Render thread -> VRAM report about missing bytes is changed from 427315200 Bytes to 427352064 Bytes

2025-12-04 15:58:12.044 - Render thread -> Info: Frame[61381] - Available VRAM budget has changed: 18268 MB

2025-12-04 15:58:13.743 - Render thread -> VRAM report about missing bytes is changed from 427352064 Bytes to 427319296 Bytes

2025-12-04 15:58:13.776 - Render thread -> VRAM report about missing bytes is changed from 427319296 Bytes to 427356160 Bytes

2025-12-04 15:58:16.312 - Render thread -> VRAM report about missing bytes is changed from 427356160 Bytes to 427327488 Bytes

2025-12-04 15:58:16.342 - Render thread -> VRAM report about missing bytes is changed from 427327488 Bytes to 427360256 Bytes

2025-12-04 15:58:16.946 - Render thread -> Info: Frame[61675] - Available VRAM budget has changed: 18391 MB

2025-12-04 15:58:18.963 - Render thread -> VRAM report about missing bytes is changed from 427360256 Bytes to 427335680 Bytes

2025-12-04 15:58:18.992 - Render thread -> VRAM report about missing bytes is changed from 427335680 Bytes to 427364352 Bytes

2025-12-04 15:58:21.125 - Render thread -> VRAM report about missing bytes is changed from 427364352 Bytes to 427343872 Bytes

2025-12-04 15:58:21.158 - Render thread -> VRAM report about missing bytes is changed from 427343872 Bytes to 427368448 Bytes

2025-12-04 15:58:21.592 - Render thread -> VRAM report about missing bytes is changed from 427368448 Bytes to 427491328 Bytes

2025-12-04 15:58:21.660 - Render thread -> VRAM report about missing bytes is changed from 427491328 Bytes to 427261952 Bytes

2025-12-04 15:58:21.908 - Render thread -> VRAM report about missing bytes is changed from 427261952 Bytes to 427241472 Bytes

2025-12-04 15:58:21.942 - Render thread -> VRAM report about missing bytes is changed from 427241472 Bytes to 427261952 Bytes

2025-12-04 15:58:21.942 - Render thread -> Too many VRAM reports, stopping printing

2025-12-04 16:00:30.229 - Render thread -> Info: Frame[69653] - Available VRAM budget has changed: 18271 MB

2025-12-04 16:00:34.294 - Render thread -> Info: Frame[69893] - Available VRAM budget has changed: 18395 MB

Game freezes on startup. Getting a message apologising for the crash.

hi,

i have additional information that may help reproduce this issue reliably. i was able to reproduce this freeze 100% consistently in the starting survival campaign. during testing it initially looked like the freeze was related to high speed, but after further experiments it seems more likely that the trigger is the distance traveled from the starting area. this is only my observation, not a confirmed technical cause.

steps to reproduce:

1. start a new survival campaign
2. take the starting ship and fly in a straight line
3. flying at around 150 m/s works normally
4. after traveling a certain distance from the starting area, the simulation freezes completely
5. immediately after the freeze, ram usage begins increasing extremely fast (+200-300 mb/sec)
6. space engineers 2 consumes all available free memory (in my case ~22 gb out of 32 gb)
7. the game stays frozen indefinitely while the process remains active

distance-based behavior (observed):

after repeated controlled tests using gps markers and identical flight direction:

- 100 m/s -> freeze at ~6.96 km

- 200 m/s -> freeze at ~5.00 km

- 300 m/s -> freeze at ~5.67 km

the freeze happened after traveling roughly the same distance (around 5–7 km), even though the speeds were different. higher speeds only caused the freeze to happen sooner in real time. this suggests the issue might be related to some kind of world displacement or loading process, but this is only based on my observations.

what happens during the freeze:

- physics and simulation stop entirely

- menus do not open and input becomes unresponsive

- skybox, lighting and audio continue normally

- ram usage rapidly increases until all free memory is consumed

- windows does not terminate the process

additional notes:

- happens in a completely new world and on a clean save

- also happens in an older save

- reproduces with obs running and without obs

- reproduces even with all background applications closed (no discord, no cider, etc)

- i recorded the entire behavior with fps, frametime, ship speed, traveled distance and ram usage visible

- attached logs and a compressed version of the video; the full recording is too large to upload, but i can share it via google drive if needed

system specs:

– ryzen 7 7700

– rtx 5070

– 32 gb ddr5 ram

– windows 11

– graphics preset: extreme, upscaler: quality, 2560×1440

thanks

Here's a new one. Driver time out? What the Heckle Jeckle and Heide.

Not sure what's going on Keen, but this is a new one for me. Driver Time Out.

I'm having the same problem.

worked great after they did the first survival fix now if it runs it crashes inside 30 mins

Getting the same. Though I have no issue reloading the save, entering gravity freezes my game. Have managed to get as low as .44g but consistently freezes with some variability in height. Clouds scroll by and sound is still playing but the grid is stationary and the game will take no input and has to be force closed via task manager.

Same here. Seems to have popped up for a few people recently so hopefully a bugfix is in the works.

Hello Engineers,

I am happy to announce that this issue is now fixed with the newest Hotfix - 2.0.2.29! You can find the contents of the Hotfix on Steam: Space Engineers 2 - Space Engineers 2: Dev Diary, Hotfix 2.0.2.29 - Steam News

I will close this thread as such. If you still encounter crashes, please create a new thread.

Happy Engineering!

Kind Regards,

Bartosz

Keen Software House