One cannot select any different setting in a dropdown-box which is used on the 3rd or 4th option-position of a module!
Interface-size set to small: 3rd module option slot
Interface-size set to normal: 4th module option slot
One cannot select any different setting in a dropdown-box which is used on the 3rd or 4th option-position of a module!
Interface-size set to small: 3rd module option slot
Interface-size set to normal: 4th module option slot
Behaviour: No dropdown opens, and you cannot select any different setting than the default one
Expected behaviour: Setting of that dropdown can be selected and changed
Issue still present in current perf binaries! But I found that the above specifically happens with interface-size set to "small"! With interface-size "normal" it breaks on the 4th option slot.....
Can confirm. It seems like there's an invisible control blocking input in that specific region of the screen.
Hi, @highhead
We know about this mess in Editor. It´s under investigation now. You can switch Interface Size to Very Small, Large or Very Large, for now. Drop down will be functional to all Game modules and Triggers.
I´ll close this ticket now.
Thank you for your report.
@Alwin the issue is still present in the dev build(s). It don't think this should've been marked as "resolved" to be honest.
This is a very annoying UI issue and constantly causes me to misclick settings on modules. This issue is not resolved in 1.68.
This issue is not resolved. For example, using the ALiVE mod in 1.68, 64-bit, the Military Commander Military Objective module dropdowns for Objective Size Filter don't appear, and it's forever stuck on "Ignore Small Objectives." The other options, of which there are several, do not show up because the dropdown list can't open.
As expected we now have support calls incoming because of this issue! Please be aware, this also affects ZEUS: https://forums.bistudio.com/forums/topic/202806-eden-editor-64bit-update-bug/
Lovely! Sorry for being sarcastic! It's really a pity that this made it to LIVE even after it has been detected, reported and acknowledged in A3 DEV branch 3 months ago (!) already...