Problem:
The user would like to filter views by a custom field created by ACF. An address field as an example.
Solution:
If the field is simple it will work. If the field is complex and needs some logic by another plugin (e.g. a checkboxes field of ACF) it will likely not work as each plugin will have a particular logic/syntax and Toolset Views can't guess it. It can only guess Toolset Types complex fields.
The address field, provided by Toolset Maps, is an advanced field, and all I could imagine it to work with Views is a simple text input search or so, like for a single line field, but nothing else.
Note, managing with Types won't solve a thing in those cases, because you will simply lose the "other" plugins syntax and apply Types syntax on the field, that's all, so it is not really that you can "solve" this limitation with controlling the field by types, you can merely workaround it.
Finally, Toolset Views offers a way to hook into its query, you can always extend the query of a view with custom code. Check all views hooks.
Relevant Documentation:
https://toolset.com/documentation/programmer-reference/views-filters/
