[...] As a developer myself, I don't understand how something so important to a quest doesn't have a lock property to prevent something stopping quest progression. Delamain.theHeist.allowUpsideDown = false.
Same here: Jackie+, Delamain- before update; Jackie-, Delamain- after 1.05.I have the same problem and, despite it's listed as fixed, 1.05 didn't fix it, actually it made it worse. I installed the patch for PC this morning, but now not only the car is invisible, but also Jackie is gone.
I have had my game progress halted due to a bug pertaining the delamain, but noit the quest involving phones, which seens to be the most common.
My issue is trhat in this quest, after I left Dexter Deshawn office, while planning the aforementioned heist, I went on errants to level up, and returned several saves and levels later. Problem is, while Jackie is ready and willing waiting for me in the afterlife's parking lot, the delamain itself isn't, and Jackie seens to be leaning on thin air. Take a look in the attached file.
This bug is rarely mentioned in consersations, and the 1.04 patch notes are inconclusive as to wheter or not it was addressed (I've seen someone in the internet mentioning it was - in my case, it isn't fixed - but as I read the page created by CDPR, there is no specific mention of 'the heist" questline - though it might be possible it is amongst the "other quests" mentioned.
Can anyone confirm to me if this was already "fixed"? If it was, it probably just won't retroactively fix already broken savefiles, and I'd be better off restarting the game. Anyway, I'd love to be sure before I throw away almost 20 hours of game progress (I've been doing sidequests a lot waiting for a fix, and probably already are overleveled for this quest,,,)
Anyway, thanks in advance for confirmation of this.
I hope you are not serious.
In case you are: no offense but you don't seem to have any idea how a complex 3D game engine works. The car object's XYZ position and orientation (rotation) is most likely stored in the save file directly. It's surely more than a simple boolean flag.
Yours is upside down (wrong rotation). For many others, like me, the car most likely fell through the ground at some point in time as CapacAmaru illustrated above - permanently giving it wrong position coordinates when the game is saved and subsequently loaded.
To fix that for existing save games, the game would need to check any critical quest-related objects at load time and correct invalid positions of such objects automatically if applicable. And then it depends what they make the game detect as "invalid" - only position (too far away) or also rotation (upside down)?
However, that's just speculation on my part. They could also have gone an entirely different route - I don't know how their engine works and what possibilities they have. It's also possible they could fix the bug to prevent it from happening with 1.05 for new players but can't fix existing save games that already have a misplaced car (which I hope is not the case). But we don't know. When the patch lands in PC land and more affected people can test it, we'll know more.