Skip to content
This repository has been archived by the owner on Nov 1, 2020. It is now read-only.

Switching framegraph crash (Fallback Layer) #376

Open
MeineZ opened this issue Jun 14, 2019 · 2 comments
Open

Switching framegraph crash (Fallback Layer) #376

MeineZ opened this issue Jun 14, 2019 · 2 comments
Labels
bug Something isn't working

Comments

@MeineZ
Copy link
Contributor

MeineZ commented Jun 14, 2019

Describe the bug
Wisp crashes when running Wisp on a machine that doesn't support DXR (so only supports the Fallback Layer) and switching framegraph to any framegraph that is using an Acceleration Structure.

To Reproduce
Steps to reproduce the behavior:

  1. Run Wisp
  2. Press F2 to switch framegraph
  3. Experience the crash

Expected behavior
Just switch framegraph. No crash should be involved.

Screenshots
image
Deepest error location

image
Deepest 'high level' error location

image
Callstack

System (please complete the following information):

  • OS: Windows 10
  • NVIDIA GeForce GTX 1050
  • RAM 16GB
@MeineZ MeineZ added the bug Something isn't working label Jun 14, 2019
@161563
Copy link
Contributor

161563 commented Jun 21, 2019

I think this is ray-tracing/fallback crashing, not the framegraph switching.

@161563
Copy link
Contributor

161563 commented Jun 21, 2019

just tested it, when using hybrid as the startup framegraph it crashes as well, so it's an issue in ray-tracing/fallback, not the framegraph.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants