> For the complete documentation index, see [llms.txt](https://docs.enercalc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enercalc.com/efr-user-manual/calculation-types/working-with-beam-calculations/beam-supports13/resolving-ambiguous-support-co.md). # Resolving Ambiguous Support Conditions How ENERCALC for Revit resolves ambiguous beam support conditions using precedence rules and manual conflict resolution during calculation launch. In some framing conditions, ENERCALC for Revit’s detection process may identify multiple possible support elements very close to each other. A number of these ambiguities are resolved on the fly without user input by the following precedence rules: 1. When two possible supports coincide at the same location, priority is given to the element whose solid centroid is lower in 3D space. According to this logic, framing conditions with stacked columns will not result in ambiguity warnings because the lower of the two columns is suggested by default. ![](https://4249100372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgHVzpA9PT0VcuNGp6j39%2Fuploads%2Fgit-blob-7973e0f9a99c4a0719ae621fbab0a3e0fd749e26%2Fclip0098.png?alt=media) ![](https://4249100372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgHVzpA9PT0VcuNGp6j39%2Fuploads%2Fgit-blob-58b14020b16cd46d91fadac7fedc43506b3ddedd%2Fclip0099.png?alt=media) Similarly, a wall below with column above condition will not result in an ambiguity warning because the lower of the two (the wall) is suggested by default. ![](https://4249100372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgHVzpA9PT0VcuNGp6j39%2Fuploads%2Fgit-blob-f5f7e456d04eddacb2f015ec09dab60cdfffe40e%2Fclip0100.png?alt=media) 1. If the coincident supports have closely matched physical locations in space such that the “lowest support” test is inconclusive, then the following priority is applied: 2. Columns have priority over walls and beams 3. Walls have priority over beams ![](https://4249100372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgHVzpA9PT0VcuNGp6j39%2Fuploads%2Fgit-blob-84121cc4906a51c18961c000132861ffdbe1efb5%2Fclip0101.png?alt=media) ![](https://4249100372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgHVzpA9PT0VcuNGp6j39%2Fuploads%2Fgit-blob-3a5d03186b004a0192b63ab9d08ae89bf952a94a%2Fclip0102.png?alt=media) For any framing condition where the user’s design intent does not align with the logic used to automatically limit ambiguous conditions, the load path may always be corrected by choosing the “Select Supports Manually” button. As discussed in “[Manually Selecting Support Conditions](/efr-user-manual/calculation-types/working-with-beam-calculations/beam-supports13/manually-selecting-support-con.md)”, the user may manually choose from ***ANY*** beam, column, or wall element that is found in physical proximity to the beam to be designed. The proximity and geometry of the possible supports may not allow for a clear recommendation for one element or the other in all cases. If this occurs, the user will be notified in the approval form that a potentially conflicting support condition is found. For example, if two columns with nearly identical geometry are found very close to each other, the user will be presented with the option to “Confirm Selected”, “Select Supports Manually”, or “Resolve Conflicts”. ![](https://4249100372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgHVzpA9PT0VcuNGp6j39%2Fuploads%2Fgit-blob-a262e19697be953c9920a7c5ef510c2e2aa0f60d%2Fclip0103.png?alt=media) Users should be aware that proceeding via “Confirm Selected” or “Select Manually” may result in a downstream warning if the chosen supports are placed too close together. The minimum span length permitted is 0.25 ft. If any two support centers are more closely spaced, the calculation launch will be terminated with a warning, and the problematic supports will be indicated in the Revit view. ![](https://4249100372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgHVzpA9PT0VcuNGp6j39%2Fuploads%2Fgit-blob-e1139a3a204a811b3297ec89db27ef6dfdc144fd%2Fclip0104.png?alt=media) If the user opts to “Resolve…”, then the program will lead the user through a series of verifications for each location along the beam where conflicting supports are found. Clicking this button will take the user to the first location where supports conflict. ![](https://4249100372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgHVzpA9PT0VcuNGp6j39%2Fuploads%2Fgit-blob-254f9cf2048b34425dc45c0a4fd5eea8615a6013%2Fclip0105.png?alt=media) At each location, the conflicting supports will be automatically selected in the Revit view and a Revit multi-select process will begin. The Revit status bar (lower left corner of the main Revit window) indicates the number of conflicts found and gives instructions about how to proceed. ![](https://4249100372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgHVzpA9PT0VcuNGp6j39%2Fuploads%2Fgit-blob-85708e543030f0dd44f25867d931284237040b5b%2Fclip0106.png?alt=media) Moving the cursor over an element that is already selected will indicate the “-“ option to remove it from the selection. ![](https://4249100372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgHVzpA9PT0VcuNGp6j39%2Fuploads%2Fgit-blob-e42b2ed6a7def308e82d8f360c95253535097742%2Fclip0107.png?alt=media) Moving the cursor over an element that is not selected will indicate the “+” option to add it to the selection. ![](https://4249100372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgHVzpA9PT0VcuNGp6j39%2Fuploads%2Fgit-blob-02fde52edcf1941b8d444022a0642074af1c5f39%2Fclip0108.png?alt=media) After manual selections have clarified the desired condition at the current conflict, clicking ”Finish” will cause the program to proceed directly to the next conflict. When all conflicts are resolved, the program will proceed to the next step of the calculation launch process. During the process of resolving conflicting supports, clicking “Cancel” on the Revit ribbon at any time to end a multi-select will terminate the calculation launch with a notification. ![](https://4249100372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgHVzpA9PT0VcuNGp6j39%2Fuploads%2Fgit-blob-d3c2e4f7ba460435c7e530b74e92ee4b946a8bd1%2Fclip0109.png?alt=media) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.enercalc.com/efr-user-manual/calculation-types/working-with-beam-calculations/beam-supports13/resolving-ambiguous-support-co.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.