-
Notifications
You must be signed in to change notification settings - Fork 772
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
GRID 2 is stuck on a black screen #972
Comments
This can be fixed with nodvd but steam show same error in my case |
As I mentioned on Discord: D3D11 has a max 2D texture width/height of 16384 and and 3D of 2048 w/h/d. Since then, I have verified the behavior of this in native d3d11: |
Probably won't fix the issue but would mimic native behaviour better maybe? 🤷♂️ Edit: I made this at 3AM and realised it probably won't help at all. Oops. |
I tried to run versions of this game from Steam (wine and proton) for a few hours, unfortunately without success. https://www.youtube.com/watch?v=WKbxXebVPjw |
It doesn't start on my end, not in Lutris, nor in Steam+proton. I get:
System information
Log files
EDIT: The game seems to be running in background, but no window is created. |
@Zeioth that message comes from Steam (specifically, CEF), not the game. |
If you want to run this game (stem ver.), read this: @doitsujin this is not a problem with dxvk |
I think Pierre-Loup has mentioned CEG being an issue before -- not sure what the status is on that though. |
Tested and it's a DRM issue: https://www.protondb.com/app/44350 Unfortunately, I'm stuck on the "check for DLC" screen, but it's not an issue with DXVK. Can be closed. |
When I launch GRID 2 from Steam (got it for free from Humble) using DXVK (tried Proton and Lutris' Windows Steam with latest DXVK), the game is stuck on a black screen. Doesn't launch with WineD3D either.
In a d3d11 log, an interesting error pops up:
System information
Apitrace file(s)
Note: this apitrace was recorded on computer with Windows 7 and a pretty old card with a very outdated driver (as newer ones result in BSODs). And while it loaded the main menu and prompted to start a new game just fine, it got stuck on a loading screen, so the actual gameplay wasn't traced.
https://yadi.sk/d/NjJOr6eCYUHCIQ
Log files
The text was updated successfully, but these errors were encountered: