Unknown renderer error

[Andy90]

Hello

As already mentioned in Discor, here is the bug report of the renderer error. It occurs spontaneously when switching from one map to another. So far it has only happened when I switch back from Map B to Map A. From Map A to Map B I haven't received this error yet.

You can reproduce the error if you use the teleporter to change the map several times in a row. You can use the teleporter by letting the character walk on it and pressing enter. Alternatively, you can of course also change the teleport components. This is located in Source/Components/Custom. 

Files:
https://1drv.ms/u/s!Aum5gwXzTrOyv3hfHkhC8P002lYC?e=XnFOSZ

Screenshots:




 

 

[Josh]

Which map should I be starting in? There are several, but none are called Map A or Map B. I just ran with the default map, and switched back and forth a few times, with no errors.

Is this happening in debug mode or release mode, or both?

Memory usage looks good:

[Josh]

Do you have the Vulkan SDK installed?:
https://vulkan.lunarg.com/

[Andy90]

yes. It happens the most time when you go from the desert map to the other. 

[Josh]

2 minutes ago, Andy90 said:

yes. It happens the most time when you go from the desert map to the other. 

Do you have the Vulkan SDK installed?

Are you using the beta branch or default branch?

[Dreikblack]

You can reproduce it like SpiderPig suggested:

It's very inconsistent tho. Sometimes few times in row and in another test attempts only 1 out of 10.

[Andy90]

10 hours ago, Josh said:

Do you have the Vulkan SDK installed?

Are you using the beta branch or default branch?

I think i have not the vulkan sdk installed if its not get installed with the engine. Im on the beta branch. 

[Josh]

I highly recommend installing the Vulkan SDK, This will enable validation layers so if there is a Vulkan error it gets caught immediately:
https://vulkan.lunarg.com/

[Josh]

It looks like @Dreikblack has managed to isolate this issue. I am working on the solution now:

 

[Josh]

I believe this issues is solved. Please let me know if that is not the case.