YeahOkayFineWhatever
YeahOkayFineWhatever
About
- Username
- YeahOkayFineWhatever
- Joined
- Visits
- 24
- Last Active
Comments
-
Okay, so i checked up on all of my settings and turns out I have legacy instead of UEFI. Am i just doomed?
-
@redglyph said:
I don't know the technical reason, but I have a friend who got it back to normal by reinstalling the steam client.
It may have something to do with the boot options mentioned above.
How do you do that?
-
Has anyone found a solution other than changing the launch setting?
-
@Emeal said:
So I tried to check out what @brizzyne was talking about, like seriously you say you fixed it but don't post your findings? smh
Anyway, I believe it was this thread.https://steamcommunity.com/app/381210/discussions/0/4360123339072186980/
They suggest to add "-dx11" to the Steam Launch settings. like this: Right Click game in menu list/ properties / General:
https://us.v-cdn.net/6030815/uploads/K6R4WGHSB0IZ/image.png
I already tested it, it fixed the issue for me and allowed me to go from the Loading Screen into the Main Menu without getting stuck on "Initializing Shaders". I encourage everyone here who has this problem to try it and tell us all if it works for you.
This could be a clue to what is wrong. Good luck.
I tried this and it gets past the initializing renders, and the cut scene, to only crash mere seconds later. I did eventually get past the crashing and into the game, but the minute i clicked on tomes it crashed again…
-
Yeah, it stays stuck on "Initializing Shaders." and when i close it, it says security error found or something like that.
-
Yeah it sucks…I really do grind in this game..
-
I have the same problem, except mine doesn't crash. It stays stuck on, "Initializing Shaders". I have never had this problem before…