The green dimensioned ‘Glue to’ landing components (here A=500 mm) preserve their given length(s). Spacing them B, C, D and E (red values) are resp. 300, 500, 800 and 900 mm
Say your real world overall length isn’t 5000 mm but 10,938 mm. Select only the face and scale it dragging the right green grip to some arbitrary length and then immediately type 10,938 mm [Enter]
The red lengths adjust accordingly, but relative to their anchored positions, the landings.
Vertical scaling the ramp to the correct overall rise can be done in the same way with the top mid green grid.
It all boils down to:
a rectangular face
‘Glued to’ components at length
first one anchored (local origin) on the corner down left
last one (if included in the overall length!) mirrored anchored on the top right corner
(if not included, then not mirrored but still anchored on the top right corner)
other landings spaced according to (say) BBB or BCB or BCDE or whatever you need
In short: use ‘Glue to’ components and pay attention where to they are anchored on the face!
I haven’t read everything yet, but one thought is that FlexTools has a ramp tool which is a dynamic component, but I confess I haven’t used it much. That said I don’t know if you would find it helpful or not. Here’s what the parameters look like:
Appears not, but as I said I haven’t really used the tool; just throwing out the fact that somebody did make a dynamic component for ramps. I have other thoughts about how I would approach it with native tools.
Here’s a quick look at the way I would approach it. Start with a seed component based on the “not to exceed standards” (for me that’s ANSI A177 and ADA). Make a unique component copy for this particular case. Move duplicate it with trial and error until there are enough repeats to fit, and then edit the component to less than the worst case version.
Without trial and error: try creating a ramp with four landings, fixed size (say all included in the overall length. The distances between them have to obey/maintain the ratio 5:7:6
(Taken that all will stay within an acceptable slope. That’s easy to check in advance)
So you are dealing with the case ABACADA
No extensions, no dynamic components, just native tools, accurate and no difficult math involved.
p.s. this is more along the line of OP’s question.