Conflict checking cannot be used to prevent you from making multiple bindings to an Action. You are confusing the Action system with Controller Elements. ![]() Conflict checking rules are all based on the map categories of the maps in question. You set up your categories first and the checking rules in a data-driven way, not when you make the function call. It returns a large struct which contains the entire description of the mapping including partial axis mappings.īecause I designed my system to work that way. Rules are all set up beforehand in the Rewired Input Manager: You do not set up rules about what to conflict check against in the ElementAssignmentConflictCheck. Even I do not use this low-level API since Input Mapper was created to wrap it and simplify it. It is taking a great deal of your time and mine because you're not using the provided system for handling input mapping and are trying to use the low-level system without thoroughly understanding it by using the source code example provided for it as a guide. The intended and supported way to remap controls in Rewired is through Input Mapper.not the API you're using. I have also provided you a complete, easy to use wrapper - Input Mapper - which is a replacement of this undocumented low-level API. This is and always has been the documentation for this topic. ![]() I have provided you with a complete example on using the system - the Control Mapper source code. This Conflict Checking and low-level mapping API has always been considered an advanced topic and is unsupported. The Action Element Map is a complete description of the binding that conflicted. It returns a large struct which contains the entire description of the mapping including partial axis mappings.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |