Delores: A Thimbleweed Park Mini-Adventure

Delores: A Thimbleweed Park Mini-Adventure

ZLDX12Renderer: Failed to present a frame
Summary:

  • Game crashes on start with error ZLDX12Renderer: Failed to present a frame.
  • Issue is not related to 4k.
  • Issue is not related to fullscreen (and thus, probably not related to my screen resolution at all, unless something terribly wrong is happening)

I've tried to rearrange the quotes to show the entire discussion below.

Escrito originalmente por Kat:
Escrito originalmente por Efreak Ƹ̵̡Ӝ̵̨̄Ʒ:

As soon as the game starts, I get:
ZLDX12Renderer: Failed to present a frame.[files.catbox.moe]

I'm on Windows 10 with igpu only (no graphics card right now :crykit: but according to another post, some issue with intel hd graphics was in a recent bugfix.

Hello,

we've had another person report the same error recently. Is your card powering a 4K display, by any chance? This issue might be caused by the card not being able to do 3D rendering at such a high resolution.

We're currently looking into it - it'd probably be quicker to get in contact with us at support+delores@thimbleweedpark.com (we have some potential solution for you to try).

Escrito originalmente por Kat:
Escrito originalmente por Efreak Ƹ̵̡Ӝ̵̨̄Ʒ:
I'm on intel graphics only. Dual monitor setup with two 16:10 monitors (1920x1200 and 1680x1050). 16:10 causes issues with some games, because apparently 16:9 is the only valid aspect ratio in existence. The main issues this causes for me is that I can't run some games full-screen (16:10), and unity games run at low FPS (igpu). I've never tried running anything very demanding on it since my gpu died. GPU is i5 4690k's Intel® HD Graphics 4600[ark.intel.com], which can handle 4k despite my not using it.

Thanks for the info. We think that launching the game in windowed mode could potentially resolve this issue. Can you try the following?

1) Navigate to C:\Users\(your username)\AppData\Roaming\Terrible Toybox\Delores .
Hopefully, the Terrible Toybox and Delores folders got created.
2) You should see a Prefs file inside the Delores folder.
3) Open this file and you should see a parameter named windowFullscreen: 1. Just change the value to windowFullscreen: 0.
4) Save the file and exit it.
5) Try running the game again.

This should force the game to run in windowed mode. It might solve the problem, but it also might not. If not, we'll continue looking into it.

Escrito originalmente por Kat:
Escrito originalmente por Efreak Ƹ̵̡Ӝ̵̨̄Ʒ:
I'm on intel graphics only. Dual monitor setup with two 16:10 monitors (1920x1200 and 1680x1050). 16:10 causes issues with some games, because apparently 16:9 is the only valid aspect ratio in existence. The main issues this causes for me is that I can't run some games full-screen (16:10), and unity games run at low FPS (igpu). I've never tried running anything very demanding on it since my gpu died. GPU is i5 4690k's Intel® HD Graphics 4600[ark.intel.com], which can handle 4k despite my not using it.

Thanks for the info. We think that launching the game in windowed mode could potentially resolve this issue. Can you try the following?

1) Navigate to C:\Users\(your username)\AppData\Roaming\Terrible Toybox\Delores .
Hopefully, the Terrible Toybox and Delores folders got created.
2) You should see a Prefs file inside the Delores folder.
3) Open this file and you should see a parameter named windowFullscreen: 1. Just change the value to windowFullscreen: 0.
4) Save the file and exit it.
5) Try running the game again.

This should force the game to run in windowed mode. It might solve the problem, but it also might not. If not, we'll continue looking into it.

Escrito originalmente por Kat:
Escrito originalmente por Efreak Ƹ̵̡Ӝ̵̨̄Ʒ:
Same error. If you want me to, I'll start a separate thread. I'm planning to get rid of my dual-monitor setup anyways soon (imagine going from dual to single monitor. but I need the desk space, and someone else needs a monitor). If the issue is caused by having two DPIs or something like that, I'll know soon.

That would be great if you could start a separate thread for the "ZLDX12Renderer: Failed to present a frame" error. We've had several people report the same problem since your original post and we think we might now know what's causing it. We're currently waiting to hear some confirmations from them.


Some new information:

  1. My setup is currently single-monitor instead of dual, and still suffers the same issue.
  2. The issue (probably unrelated, an issue with windows/other software) that I thought was a dual-monitor issue turned out not to be (I'm now guessing that it's actually intel refusing to update their drivers[forums.intel.com]; having said that, I have no issues with games, only hardware-accelerated text rendering in windows proper, steam, and other electron/cef apps and such). Unfortunately there doesn't seem to be a fix for this one :sadkit:, however it shouldn't cause any issues with DirectX support.
  3. DirectX Version 12[files.catbox.moe]), Direct3d DDI 12 and Feature Levels 11_1, 11_0, ...[files.catbox.moe]. Full report is here[files.catbox.moe]
Última edição por Efreak Ƹ̵̡Ӝ̵̨̄Ʒ; 21/mai./2020 às 10:42
Escrito originalmente por Kat:
Hello,

thank you for starting a new thread for this issue!

We have found out that this problem is related to specific Intel graphics card driver version (20.19.15.5126). This particular driver version is being offered via Intel's site only.

This is what we'd suggest as a solution:
1) Go to Device Manager -> Display adaptors.
2) Under Display adaptors, right-click on your Intel card and select "Update driver" from the context menu.
3) Choose "Search automatically for updated driver software". This should download the driver version that's more compatible.

Of course, do this only if you want to change the driver you're currently using. It seems the driver version that you currently have may be causing some problems and crashing. So that's why the annoying ZLDX12 Renderer error keeps appearing. This bug has already been reported to Intel, since it's an issue on their end.
< >
Exibindo comentários 15 de 5
Um desenvolvedor deste aplicativo indicou esta mensagem como a resposta do tópico.
Kat  [desenvolvedor(a)] 21/mai./2020 às 10:49 
Hello,

thank you for starting a new thread for this issue!

We have found out that this problem is related to specific Intel graphics card driver version (20.19.15.5126). This particular driver version is being offered via Intel's site only.

This is what we'd suggest as a solution:
1) Go to Device Manager -> Display adaptors.
2) Under Display adaptors, right-click on your Intel card and select "Update driver" from the context menu.
3) Choose "Search automatically for updated driver software". This should download the driver version that's more compatible.

Of course, do this only if you want to change the driver you're currently using. It seems the driver version that you currently have may be causing some problems and crashing. So that's why the annoying ZLDX12 Renderer error keeps appearing. This bug has already been reported to Intel, since it's an issue on their end.
Última edição por Kat; 21/mai./2020 às 10:52
Escrito originalmente por Kat:
Hello,

thank you for starting a new thread for this issue!

We have found out that this problem is related to specific Intel graphics card driver version (20.19.15.5126). This particular driver version is being offered via Intel's site only.

This is what we'd suggest as a solution:
1) Go to Device Manager -> Display adaptors.
2) Under Display adaptors, right-click on your Intel card and select "Update driver" from the context menu.
3) Choose "Search automatically for updated driver software". This should download the driver version that's more compatible.

Of course, do this only if you want to change the driver you're currently using. It seems the driver version that you currently have may be causing some problems and crashing. So that's why the annoying ZLDX12 Renderer error keeps appearing. This bug has already been reported to Intel, since it's an issue on their end.
Unfortunately, intel has abandoned older "legacy" devices (see this link[forums.intel.com] I mentioned above), so there is no newer driver available for me. You might want to revise or add a note somewhere about a minimum driver version, so others don't encounter the same issue (and possibly a more useful error message)
Última edição por Efreak Ƹ̵̡Ӝ̵̨̄Ʒ; 21/mai./2020 às 11:12
Kat  [desenvolvedor(a)] 21/mai./2020 às 11:16 
Escrito originalmente por Efreak Ƹ̵̡Ӝ̵̨̄Ʒ:
Unfortunately, intel has abandoned older "legacy" devices (see this link[forums.intel.com] I mentioned above), so there is no newer driver available for me. You might want to revise or add a note somewhere about a minimum driver version, so others don't encounter the same issue (and possibly a more useful error message)

Yeah, there's not a newer driver available at the moment, but in this case, it might be a good idea to downgrade via the Device Manager, since this newest driver version that Intel's offering on their site seems to contain a bug.
Última edição por Kat; 21/mai./2020 às 12:03
spysiuk 24/mai./2020 às 2:50 
I've just tried downgrading the driver and for my i5-4200U (Hasswell 4th gen) working version is: win64_15407.4279 (from 2015).
WaltPilo 10/mai./2021 às 6:30 
I have the same problem. Fix this or stop wasting our time.
< >
Exibindo comentários 15 de 5
Por página: 1530 50