Johannes Unterguggenberger

Can you confirm that the problem persists with the latest version? I.e. which includes the changes of commit https://github.com/johannesugb/VolumetricLinesUnity/commit/f6569bcc0847c2cdc2cbba4605c461629bcce7ca

Yes, there is a potential fix. I've updated all branches some minutes ago with code that has been reported to fix the single pass instanced rendering issue. I have yet...

Thanks for reporting this issue. Unfortunately, I am unable to reproduce this problem (using Unity 2019.3.14 a.t.m.) May I ask you to describe the steps to reproduce this problem precisely?...

Any more details about this problem? Has the problem re-occured? If no further details are reported, I'll close this issue, assuming that the problem is gone.

Update about possible image loader candidates: - [DevIL](http://openil.sourceforge.net/) seems to be too dead. - There have been some reservations been expressed about [FreeImage](https://freeimage.sourceforge.io/) since it does not offer CMake, also...

A preliminary solution has been developed. However, there should be some other (maybe additional?) way to manage `geometry_instance`s and `bottom_level_acceleration_structure`s which takes care of their lifetimes.

With `VK_KHR_raytracing`, this had to be restructured... but actually for the better, as it turns out. Needs to be revisited once again, however.

Please beware of issue #100 ! I really hope that this is not a problem here (after having read your commit message).

New plan: Get rid of `cgb::sync` and replace with `command`/`commands` in terms of `Auto-Vk`!

Not sure if this is still necessary.