As I mentioned in my last post, you need to pay attention to whether you are using brackets or parentheses (or a mix). It will make or break the double lookup. You also need to understand what the range values on the double lookup are actually doing. You also need to understand what the different visibility states represent.
Going back to this thread: https://forums.autodesk.com/t5/dynamic-blocks/dynamic-block-visibility-state-combining-with-a-array-...
In that thread I showed how to have the main linear parameter and small parameters work together with the double lookup to determine the visibility state. In that block, when the main linear parameter was at its maximum size (2205), and the small adjustment linear parameter was at 160, there was a partial window beam on the little base and then a FULL window beam. Since that version of the block, you have moved the entire window down 160 units so now when the window is at 2205 and the fine adjustment parameter is at 160 there is just the base and a single partial window beam that is truncated at the bottom. Which should it be? If the new version is correct with it moved down 160 units, then you will need to add another 12 visibility states. Previously the states that were required were as follows: one state for when the top window beam is full size (this state showed the arrayed beam), a state for all partial beam sizes over 2205 (this state showed the arrayed beam and the partial beam on top), and a third state for partial beam sizes with the main linear parameter at 2205 (this showed the partial beam and did not show the arrayed beam because at 2205 there were no full beams). If the window moved down 160 units is correct, then you will need to accommodate the visibility states of the main linear parameter at 2205 and fine adjust at 160 (showing no full or partial beam over the base and bottom truncated beam and showing the bottom truncated beam with a full profile on the top) and also add the states for the main linear parameter at 2205 and the fine adjust at all values other than 160 (only the bottom truncated beam shows and it is flat on the top).
As far as your problems, Problem 1 is caused by a combination of your misuse of the brackets/parentheses and your incorrect visible objects. Again, a bracket next to the value includes the value in the range. A parenthesis next to a value does not include the value in the range. The arbitrary use of brackets/parentheses will result in either duplicate row values on the table or having possible parameter values that are not on the table at all. For the states of 0-P through 5-P, the arrayed beam AND the partial beam need to be visible. For the states of 0-160 through 5-160, the arrayed beam needs to be visible and the partial beam needs to be invisible. The states of 0-2p through 6-2p will need to be adjusted after you answer the above question of whether or not the new window position of 160 units lower is correct or if the previous position was correct.
Problem 2, yes that is easily done. After you answer the prior question about window position I will show how to make that change.
Problem 3, yes that is possible and now that you have been shown these techniques you should be able to accomplish that on your own.
Problem 4, again, the techniques have been shown. You need to include the direction of rotation lines in the appropriate stretch actions so that when the frame size is changed, the lines are stretched/scaled accordingly. What part of that is of particular difficulty?
You must bear in mind that I am not paid anything to help you. I am just another forum user. I have donated a very large amount of my time to assist you with your block issues, but that assistance is in order to help you understand how the block can work and to make it yourself. That assistance is not so that I can continuously provide step-by-step information on techniques that have already been demonstrated in your own threads. If you have specific issues that you still do not understand how the techniques work then feel free to ask, but creating screencasts for new applications for the techniques I have already shown is not a valuable use of my time.
