Matthew Argyros
Assigned
Reported
MC-138790
VBO's option missing from the settings menu and options file
Works As Intended
MC-133110
placing and simultaneously breaking a sign causes a crash
Incomplete
MC-133109
Tridents tend to stay in place even after the block they are thrown on has been broken
Cannot Reproduce
MC-115892
problem with the new snapshot 17w15a
Duplicate
MC-115599
in the newest snapshot "17w14a" if you update a world from previous versions your crafting recipes get deleted
Duplicate
Comments
I just tried doing that but it says that this is the "newest driver"... So basically, is this laptop doomed?
Here's my crash report from earlier... I can't do the F3+C thing because I won't be in game for 10 seconds... As soon as I join it crashes...
I went on and actually deleted all the resource packs I had in my system (didn't need them anyway) and still got a crash when I made an attempt to open a world in the newest snapshot... I couldn't find a GPU model with a number as described (4000-1000) Instead I've enclosed all the information I could find above, along side with yet again my latest log and a screenshot of my DirectX diagnosing tool... Hope you'll find this helpful
just uploaded a crash report, my latest log file (Which ended up in a game crash) and all the info I could find about my graphics card... I think I provided my OS version above in case that's what you're mentioning and I'm not missing anything. It's: Os: Windows 8.1 , 64 bit build 9600 (6.3.9600.17415). Additionaly I was unable to find my "driver version" but if it's still needed, I will do my best to provide the adequate information as this is a serious matter for me... However it's not the game crash which bothers me this much but the removal of the VBO's option... My computer couldn't handle VBO's being "on" since 1.10 and now that the option is forever activated and there's no option to change that I can no longer play the game... I think that many weeker systems like mine will probable face similar issues
The pictures I just uploaded are from the newest snapshot (19w42a) and I think I found the cause of the problem, it must be the hitbox positioning making it so the trident can get stuck mid air like that