List: All the things which can fail to spawn

[Drake Ravenwolf]

Lets compile a list of all the items which can fail to spawn (or I suspect may actually spawn just fine but then immediately falls through the world thus making you think they didn't spawn)

I'd find such a list helpful for myself so I imagine it'd help others as well.
I'll start with what I've seen in posts on this forum.

Chapter 1:
Key item: Stasis Module - FIXED in 1.04?
Quest items: Data Board, Marker Fragment #1

Chapter 2:
Audiologs: Secret Room behind bookshelf, Scientific Methods - FIXED in 1.04?
Battery: Details (more than one) - conflicting reports but still NOT fixed for at least some
Quest item: Hydrazine Tank
NPC: Captain's Corpse Transformation

Chapter 3:
Battery: Engine Ignition
Key Item: Fuel Station Keycard - FIXED in 1.04?
Weapon: The Ripper - FIXED in 1.04
Flamethrower Upgrade
NPC: Enemies for the "Manual Engine Start" sequence

Chapter 4:
Quest Item: Marker Fragment #4 - FIXED in 1.04

Chapter 5:
Weapon: Line Gun
NPC: Hunter/Mercer (NOT fixed)
(apparently there is also a door that can get stuck on "Stand By" infinitely too)

Chapter 6:
Battery: Details - conflicting reports but still NOT fixed for at least some
Audiolog: Premeditated Malpractice
Key Item: Prototype Stasis Module

Chapter 7:
Audiolog: Kyne's Hideout - FIXED in 1.04
Battery: Details - FIXED in 1.04
Security Clearance Rigs: Level 3 - FIXED in 1.04?
Admin - FIXED in 1.04

Chapter 9:
Audiolog: Alien Boarders - FIXED in 1.04?
Battery: Details

Chapter 10:
Battery: Details
Key Item: Crew Deck Keycard (NOT fixed)
Security Clearance Rig: Team Supervisor Benson's (NOT fixed)
Weapon: Gravitic Amplifier for Force Gun
NPCs: Mercer/Temple (NOT fixed)
Kyne (NOT fixed)

Chapter 11:
NPC: Kyne (NOT fixed)

Chapter 12:
Battery: Details - FIXED in 1.04

Help me flesh out this list if you know of something not on it which should be

[Drake Ravenwolf]

Originally posted by MusicTyp66:

help me the battery doesn't spawn in the emergency room if i turn off the backup it should appear next to it it doesn't actually appear it doesn't have restarted the game several times other memory status checked user files it doesn't help without the battery don't get any further in the story to the capitan NPC

oof, ya, each time you load a glitchy area for the first time you are rolling the dice to see if the bug will happen or not... I did hear a rumor that capping your framerate to 30 *might* help the area not glitch... but I literally have nothing else to offer I'm afraid - I'm just waiting to play till they patch this, the only other option is to go back to saves where the bugged area has not been loaded yet and roll those dice over and over :S

Just keep in mind that you do need a save far enough back, cause if the bug happens and then you save - the bug is stored in the save and probably even a patch wouldn't fix that :S

[Deathwing Zero]

I'm still curious on whether giving your save to someone that's unaffected by this would do anything. I'd be willing to test but someone then has to be willing to trust me with their save data for likely no benefit to them. If Drake's theory is correct, there's nothing I could do to fix it. However, if it's some other kind of issue and it does spawn for me I could progress past the progress block and send an updated save in return. The problem with this is there's no guarantee it won't happen in future.

[Drake Ravenwolf]

Originally posted by Deathwing Zero:

I'm still curious on whether giving your save to someone that's unaffected by this would do anything. I'd be willing to test but someone then has to be willing to trust me with their save data for likely no benefit to them. If Drake's theory is correct, there's nothing I could do to fix it. However, if it's some other kind of issue and it does spawn for me I could progress past the progress block and send an updated save in return. The problem with this is there's no guarantee it won't happen in future.

You'd need a case 1 situation save, a case 2 save wouldn't tell us anything

Originally posted by Drake Ravenwolf:

Originally posted by Deathwing Zero:

I wonder if loading a save from someone affected by objects not spawning would make them not spawn for someone that isn't having that issue? I'm sorry if that's worded strangely.

I imagine it would depend.

Case 1) The save is already storing the location information of the object and that location information is wrong eg under the floor - then you loading that save would see the bug, because the bug is now stored in the save

Case 2) The save is from BEFORE loading the glitchy area - in this case the area would load for the first time when you loaded it up and any bug would have to occur while your machine is running because no location data has been stored in that save for the glitchy item

[JackieTheDemon]

Originally posted by Deathwing Zero:

I'm still curious on whether giving your save to someone that's unaffected by this would do anything. I'd be willing to test but someone then has to be willing to trust me with their save data for likely no benefit to them. If Drake's theory is correct, there's nothing I could do to fix it. However, if it's some other kind of issue and it does spawn for me I could progress past the progress block and send an updated save in return. The problem with this is there's no guarantee it won't happen in future.

I could get you a save file.

[Drake Ravenwolf]

Get a save from someone not in impossible mode imo; one who saw the bug but then went elsewhere thinking that'd "fix" it but actually just locked them into a set of autosaves where every single one now has the bug... I'll post a link to such a thread I saw... somewhere...

Oh the one I was remembering isn't quite a spawn bug but here it is:
https://steamcommunity.com/app/1693980/discussions/0/3762229949244708927/

[лапата смерти]

In 10 chapter Hunter didn't spawn after cutscene with Mercer and Temple, but in the next room he was spawned by the script

[Fated Retribution]

Bump for Chapter 11.

[waltonwing]

Chapter 10 Gravitic Amplifier for Froce Gun is not spawning for me.
My game is on an SSD and I have no problem for anything else on the list.

[Drake Ravenwolf]

Originally posted by waltonwing:

Chapter 10 Gravitic Amplifier for Froce Gun is not spawning for me.
My game is on an SSD and I have no problem for anything else on the list.

:(
thanks for the report at least :S

[Herobrine]

I really find it odd that so many people have this issue and I'm three playthroughs in and have yet to see it myself. I wonder what's going on under the hood that causes this to happen, and if it's related to something specific. Then again, I don't think Frostbite has ever been the most stable engine.

[Drake Ravenwolf]

Originally posted by Noodleman:

I really find it odd that so many people have this issue and I'm three playthroughs in and have yet to see it myself. I wonder what's going on under the hood that causes this to happen, and if it's related to something specific.

I've seen reports from ppl solely running HDDs say they've had no issues at all and ppl with the game entirely on SSDs report the same issue.

Originally posted by Drake Ravenwolf:

All we know is that ppl report the bugs both with HDDs and SSDs so the fault in the game applies to both. If eg 90% of gamers still use HDDs then you'd expect 90% of the reported bugs to be from ppl with HDDs if the issue wasn't affected by the drive at all

I think this part here is the part people don't understand, I think there is some commonality, but I don't think we can find that commonality like a dev could with access under the hood of the game engine. But what ever it is, it's a fairly serious issue; one which the average player writes off as something happening to other ppl but not themselves... until it happens to them as well

[Herobrine]

Originally posted by Drake Ravenwolf:

Originally posted by Noodleman:

I really find it odd that so many people have this issue and I'm three playthroughs in and have yet to see it myself. I wonder what's going on under the hood that causes this to happen, and if it's related to something specific.

I've seen reports from ppl solely running HDDs say they've had no issues at all and ppl with the game entirely on SSDs report the same issue.

Originally posted by Drake Ravenwolf:

All we know is that ppl report the bugs both with HDDs and SSDs so the fault in the game applies to both. If eg 90% of gamers still use HDDs then you'd expect 90% of the reported bugs to be from ppl with HDDs if the issue wasn't affected by the drive at all

I think this part here is the part people don't understand, I think there is some commonality, but I don't think we can find that commonality like a dev could with access under the hood of the game engine. But what ever it is, it's a fairly serious issue; one which the average player writes off as something happening to other ppl but not themselves... until it happens to them as well

Yeah, I know it's weird. This shouldn't be happening at all. And like I said before, it could be an engine fault from Frostbite itself, you may have missed that because I did edit. I just hope that they fix it up because as a veteran I do feel this is the superior game (minus Kyne, I don't like his new voice.) Have there been any reports about this happening on consoles btw? I haven't seen any personally.

[Drake Ravenwolf]

Originally posted by Noodleman:

Originally posted by Drake Ravenwolf:

I've seen reports from ppl solely running HDDs say they've had no issues at all and ppl with the game entirely on SSDs report the same issue.


I think this part here is the part people don't understand, I think there is some commonality, but I don't think we can find that commonality like a dev could with access under the hood of the game engine. But what ever it is, it's a fairly serious issue; one which the average player writes off as something happening to other ppl but not themselves... until it happens to them as well

Yeah, I know it's weird. This shouldn't be happening at all. And like I said before, it could be an engine fault from Frostbite itself, you may have missed that because I did edit. I just hope that they fix it up because as a veteran I do feel this is the superior game (minus Kyne, I don't like his new voice.)

Do you know if it was Frostbite engine for DS1 or did they migrate to a new engine for DSR?
If it was changed that would explain a lot

[Herobrine]

Originally posted by Drake Ravenwolf:

Originally posted by Noodleman:

Yeah, I know it's weird. This shouldn't be happening at all. And like I said before, it could be an engine fault from Frostbite itself, you may have missed that because I did edit. I just hope that they fix it up because as a veteran I do feel this is the superior game (minus Kyne, I don't like his new voice.)

Do you know if it was Frostbite engine for DS1 or did they migrate to a new engine for DSR?
If it was changed that would explain a lot

Dead Space (08) used a very heavily modified build of the engine used for the old EA TigerWoods golf games (I know it sounds weird.) Dead Space 2 also used this engine. I believe Dead Space 3 used a different engine but I'm unsure what exactly. Dead Space Remake redid everything from scratch, so completely new code and assets.

[Drake Ravenwolf]

Originally posted by Noodleman:

Originally posted by Drake Ravenwolf:

Do you know if it was Frostbite engine for DS1 or did they migrate to a new engine for DSR?
If it was changed that would explain a lot

Dead Space (08) used a very heavily modified build of the engine used for the old EA TigerWoods golf games (I know it sounds weird.) Dead Space 2 also used this engine. I believe Dead Space 3 used a different engine but I'm unsure what exactly. Dead Space Remake redid everything from scratch, so completely new code and assets.

Hmmm if it was built from the ground up - all new stuff - then that wouldn't explain it... but there is a saying in Computer Science - "A lazy coder is a good coder" I bet someone did some copy/pasting they shouldn't have from the old code and maybe that is where some of the issues come from...