- Screenshot_20241112_182001.png (59.74 KiB) Viewed 690 times
[Klonan] Inserter blacklist quality filter renders twice
-
- Long Handed Inserter
- Posts: 61
- Joined: Tue Mar 22, 2016 6:35 pm
- Contact:
[Klonan] Inserter blacklist quality filter renders twice
The ">." is rendered both large and small, seems like it's rendering as it would for whitelist and then again for blacklist.
Re: Inserter blacklist quality filter renders twice
Thanks for the report. Are you using any mods?
If you want to get ahold of me I'm almost always on Discord.
-
- Long Handed Inserter
- Posts: 61
- Joined: Tue Mar 22, 2016 6:35 pm
- Contact:
Re: Inserter blacklist quality filter renders twice
Just default space age mods, base, elevated-rails, quality, space-age, all on 2.0.15.
Re: Inserter blacklist quality filter renders twice
Can you post a save file with this issue? When I test, it seems to be normal. Maybe also a screenshot of your graphics settings?
If you want to get ahold of me I'm almost always on Discord.
-
- Long Handed Inserter
- Posts: 61
- Joined: Tue Mar 22, 2016 6:35 pm
- Contact:
Re: Inserter blacklist quality filter renders twice
Interesting, I wouldn't have thought it'd be a difficult one to reproduce. I'm on Linux, but I didn't think that'd be the difference that would cause it.
- Attachments
-
- 638457-reproducer.zip
- (2.76 MiB) Downloaded 16 times
Re: Inserter blacklist quality filter renders twice
I'm running on Windows and it does that too:AndrolGenhald wrote: Wed Nov 13, 2024 4:26 am Interesting, I wouldn't have thought it'd be a difficult one to reproduce. I'm on Linux, but I didn't think that'd be the difference that would cause it.
2.0.17 with space-age, elevated-rails & quality.
Re: Inserter blacklist quality filter renders twice
Ah that's what I was missing. With any actual item in the filter it always renders correctly. It's also not centered correctly when drawn with just quality.
If you want to get ahold of me I'm almost always on Discord.
Re: [Klonan] Inserter blacklist quality filter renders twice
Thank you for the report
This was fixed a few versions ago internally
This was fixed a few versions ago internally