Posted June 03, 2024
...by the same sort of crash(es) purchasers of Cyberpunk have reported for almost one-half a decade.
For instance:
....The thread attempted to read inaccessible data at <some address>...<=====over and over and over
or:
Expression: !( alignedOffset & 0xFFFFFFFF00000000 )
Message: Detected integer overflow for offset: 52850943600 aligned: 52850943600 capacity: 3303183975 elementSize: 16
File: E:\R6.Release\dev\src\common\redContainers\src\dynamicBuffer.cpp(96) <===over and over and over
I could list somewhere on the order of...it must be the better part of one hundred at this point.
Could the bug be fixed? Of course.[1]
CD Projekt Red knows this bug; and the project managers know its nature....and at this point, they ignore it. And why not? Cyberpunk is well past (from their perspective) its sell-by date.
Moving forward, I'll be very cautious about purchasing anything made by CD Projekt Red. Meaning it's very unlikely I will. Why subject myself to disappointment?
AFAICT, this is the (or possibly a, given the years of bugs in this game) hint: learn about de-referencing a pointer. That way, the software that is the game will not attempt to access something that is not in memory.
But then, I'm sure CD Projekt Red has in their pipeline some neat new game so they won't be able to fix this one. But they can definitely, to be sure, get some star power for it by selling a bill of goods with a bunch of really cool cultural references oh boy! can't wait!
[1] And before anyone tries to tell me about all the "fixes" or "solutions" or whatever seems to have worked: Just No.
It's not the GPU drivers nor any particular version of drivers; nor is it some DEP tweak; nor is it some other random thing like FPS set to a low value; nor over-clocking; or whatever superstitious thing that seems to have worked.
It Is The Game. The fault is solely in the game....particularly, in the programming which flows from the skill (and possibly care, or lack of care) of the people responsible for typing out the text compiled into the software that is the game.
For instance:
....The thread attempted to read inaccessible data at <some address>...<=====over and over and over
or:
Expression: !( alignedOffset & 0xFFFFFFFF00000000 )
Message: Detected integer overflow for offset: 52850943600 aligned: 52850943600 capacity: 3303183975 elementSize: 16
File: E:\R6.Release\dev\src\common\redContainers\src\dynamicBuffer.cpp(96) <===over and over and over
I could list somewhere on the order of...it must be the better part of one hundred at this point.
Could the bug be fixed? Of course.[1]
CD Projekt Red knows this bug; and the project managers know its nature....and at this point, they ignore it. And why not? Cyberpunk is well past (from their perspective) its sell-by date.
Moving forward, I'll be very cautious about purchasing anything made by CD Projekt Red. Meaning it's very unlikely I will. Why subject myself to disappointment?
AFAICT, this is the (or possibly a, given the years of bugs in this game) hint: learn about de-referencing a pointer. That way, the software that is the game will not attempt to access something that is not in memory.
But then, I'm sure CD Projekt Red has in their pipeline some neat new game so they won't be able to fix this one. But they can definitely, to be sure, get some star power for it by selling a bill of goods with a bunch of really cool cultural references oh boy! can't wait!
[1] And before anyone tries to tell me about all the "fixes" or "solutions" or whatever seems to have worked: Just No.
It's not the GPU drivers nor any particular version of drivers; nor is it some DEP tweak; nor is it some other random thing like FPS set to a low value; nor over-clocking; or whatever superstitious thing that seems to have worked.
It Is The Game. The fault is solely in the game....particularly, in the programming which flows from the skill (and possibly care, or lack of care) of the people responsible for typing out the text compiled into the software that is the game.