New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Star Wars: The Old Republic black screen on start #81
Comments
Try to apitrace the game, that could be really helpful. |
I can't. The game is run through launcher which runs the actual game exe. What this .dll is supposed to do? |
You don't have to start through apitrace.exe. put the d3d9.dll in the wrapper folder next to the .exe and set d3d9 to native,builtin |
I didn't know that output files will appear on my desktop. I expected it appear in the game folder. Sorry. |
That file is way too small. You still did something wrong. |
I have black screen and d9vk just stuck on the CreatePixelShader call. |
Are you trying to apitrace it with d9vk? Because that is really not preferred and could cause issues. Use wined3d or better, native D3D on Windows instead. |
Yes.
Okay, I run it with wined3d. Here's .trace file. |
I have the same issue with latest master & release, here's my trace: https://drive.google.com/file/d/1jT3oTXEyG1Z07JjoPKK0pZGYSJXWq_aF/view |
Because the trace was done under wined3d it doesn't have the issue, however they can still look at the api calls to figure out why d9vk wouldn't work. ps your trace works as well in the same manner: |
Why are you posting logs if the issue is fixed? |
It's not fixed here, splash screen starts but crashes thereafter. |
Then post an apitrace so we can actually debug this |
Here's an apitrace, as you see it just hangs at the splash screen. I also used native d3d_compiler & d3dx9 as suggested in the release notes. https://drive.google.com/file/d/1uDsT16FPVBVPCfUhC9rf24RWKbi_QSKI/view |
Software information
The game works fine under wine and normal wine's d3d9.
System information
Apitrace file(s)
Log files
swtor_d3d9.log
swtor_dxgi.log
The text was updated successfully, but these errors were encountered: