-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Moving from 1.54.3 -> 1.56.1 only closest light is shown? #8296
Comments
Noted in #8289, that
This implies that this might be due to the descriptor set change. |
@tcadanklefsen, can you elaborate on which backend (gl or vulkan) and platform (linux e.g) you are running on? |
Thanks, this uses Vulkan backend. Right now this uses a dart+native code in a large open source project; so its not entirely a small repro ;/ https://github.com/toyota-connected/ivi-homescreen-plugins/tree/v2.0/plugins/filament_view This is tested on ubuntu 20 and fedora 41 (Fedora we've hit a couple other issues that we're looking into separately) - and setup is done through here: https://github.com/meta-flutter/workspace-automation/ (if you're wanting the large repro case). I'll work on putting together a smaller repro case. If there's anything you want me to try and edit in filament code base I can try over here and report back as well. |
Good news, I was able to get it to happen in the lightbulb sample without changing anything: Building:
Running:
20241203_152815.mp4 |
that's strange, I'm not seeing the problem on the mac + moltenvk. do you see the same issue with |
I'm assuming opengl + wayland isn't supported?
./lightbulb -d -p -a opengl -m assets/models/monkey/monkey.obj Output:
|
Discussed in #8289
Originally posted by tcadanklefsen December 2, 2024
Hello,
Moving from 1.54.3->1.56.1 seems to have changed drawing to only show the closest light. Here's where I was at previously:
20241120_092802.mp4
and here's where I'm at now:
20241202_140206.mp4
Any thoughts on what might have changed and where I could start investigating?
The text was updated successfully, but these errors were encountered: