You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Made multiple strong references to loaded texture handle
Stored a reference as a resource + inserted materials with said references to dozen of entities
Did not create camera OR hid all the entities (ie removed the Visible component)
Enabled camera OR made one entity with texture handle visible again
What you expected to happen
To not panic and for the texture to be drawn on my screen
What actually happened
Game panics and crashes upon enabling the camera or making an entity visible after it had been disabled/made invisible.
Additional information
I thought this #693 from a year ago was meant to fix this issue but it seems to have not. Textures still keep sort of "unloading" themselves from the GPU and panics whenever it gets asked to be rendered again by the same texture handle
The text was updated successfully, but these errors were encountered:
Actually, after playing around with my code a bit, turns out the reason for the problem wasn't what I initially thought it was.
Basically, I had this system that would run for every new texture and change some filter settings (that funnily enough doesn't even work), and that would in turn recreate the so called texture sampler, and the sampler that is used for every other entity would suddenly become invalid, even though the handle to the texture wouldn't change. But what still bugs me is that it WOULD only happen when there's no camera, and for some other reason whenever all the entities using that texture would lose its visibility (if they're out of range for example) and then I'd come in range again, the event listener to AssetEvent would, if I'm not mistaken, spit out another AssetEvent::Created event and the filter settings would be reset again, therefore reinitialising the texture sampler, before crashing the program because the old sampler lost its validity or something or another. Needless to say, after I disabled that system, everything went on as normal.
Summary:
New renderer works fine + what I said wasn't entirely factual. Apologies for your time!
Bevy version
0.5.0
Operating system & version
Manjaro LTS
What you did
What you expected to happen
To not panic and for the texture to be drawn on my screen
What actually happened
Game panics and crashes upon enabling the camera or making an entity visible after it had been disabled/made invisible.
Additional information
I thought this #693 from a year ago was meant to fix this issue but it seems to have not. Textures still keep sort of "unloading" themselves from the GPU and panics whenever it gets asked to be rendered again by the same texture handle
The text was updated successfully, but these errors were encountered: