The TBC client fails to start its graphics. In particular, I managed to trace the error message in gx.log:
Error CreateGraphicsPipelineState failed: The parameter is incorrect. (0x80070057)
Here is the entire log.
Game worked pretty much OK before today’s pre-patch upgrade.
A full Windows10 reinstall, including driver upgrades, did not solve the issue.
I further installed Windows Graphic Tools, and attempted to run TBC classic with the debug layer forced on, but nothing changed.
The output of dxdiag.exe can be found here.
How do I proceed with solving the issue plz?
i have the same issue i think here’s my post from “general discussion” :
Hi there,
I have an “noscreen” type of issue when i start the game… let me explain:
So basicly when i first start it i had an “invisible” full screen game (i could see the wow cursor and hear the music) and by that i mean i could see my desktop while i was clearly on the game window (like i could see trough it if that make sense).
My first plan was to run it in windowed mode: same thing is happening exept the window is now white (still hear music and see wow cursor but i cannot “see trough” like before)
Then i tried updating all my plugings, windows, directx, … -->Still no changes
Then i try to force it to run on directx 11 with the little command in the options → still nothing
i also have deleted all wow games/folders and reinstall it from scratch → nothing
So i would like to know this: why on earth i can run Classic AND a lich king 3.3.5a client (yes i have one of those, don’t ask) BUT NOT the game that came inbetween…
Did they change anything graphicly speaking ? is it just a “Sry bro, u now have to have a fkin warmachine to play a 10+y old game” kind of thing ? cuz i really don’t get why my lich king client runs so smooth on this old pc but BC Classic can’t.
Yes, your description is the same issue as mine.
A white game window, with sound playing, and a cursor visible.
Fullscreen was transparent.
You can check your gx.log file, in the Logs folder, to see if you are getting the same error code.
Edit: Adding the -d3d11legacy command-line option seems to have fixed the issue.
My GPU fully supports DX11, but provides only limited DirectX 12 support, so I believe the issue is caused by the client attempting to create a graphics device context that requires features from Shader Model 5.1 (full DX12 support). The legacy option would revert to the previous shader model. Indeed, I remember some options in the ‘Graphics’ settings that were indicated as unavailable due to graphics limitations, which might be just that.
I finaly fixed it too ! glad to hear yours work as well !
Has the command line fixed it for you, or have you come up with another solution? I have the same issue, but sadly adding the command line as people recommend did not help.
1 Like