Tried to analyze crashdump, that's what it is pointing out to me - 0xc0000005 error in bfv.exe!fb::Twinkle::getShaderHandler. Crash dumps show a consistent null pointer dereference at the same address (r15 = 0x0).
This occurs on a clean Windows 11 install with all drivers, DirectX, and game files verified. I've ruled out overlays, anticheat, config corruption, and user profile issues. It appears to be an engine-side issue possibly related to shader or scripting initialization purely.
Meaning that based on the crash dump and stack trace, the issue is an access violation caused by a null pointer inside the game’s own engine code (fb::Twinkle::getShaderHandler), not overlays or drivers.
Tried to analyze crashdump, that's what it is pointing out to me - 0xc0000005 error in bfv.exe!fb::Twinkle::getShaderHandler. Crash dumps show a consistent null pointer dereference at the same address (r15 = 0x0).
This occurs on a clean Windows 11 install with all drivers, DirectX, and game files verified. I've ruled out overlays, anticheat, config corruption, and user profile issues. It appears to be an engine-side issue possibly related to shader or scripting initialization purely.Meaning that based on the crash dump and stack trace, the issue is an access violation caused by a null pointer inside the game’s own engine code (fb::Twinkle::getShaderHandler), not overlays or drivers.
Finally, someone with a knowledge and understanding unlike the majority of permanent resident here.
As I already posted and pointed out in first release of Javelin, there are many hook that seem absurd and doesn't work on older game circa pre BattlePOS 2042, but no they forced Javelin on everything that don't even need it in first place.
Someone here even suggested doing a clean install, very dumb suggestion that ignores core problem and and just entirely blame to the user.
