In adding our own shaker machining token, prompts and Global Variables ... noted that the Applied FE Finished Panels in MV are producing (2) LEFTS - Not a RH and LH as it should be doing. You get (2) of the same ...
Note: the COMPOSITE - both are facing the same direction. It should be (1) LH and (1) RH or mirrors of each other. If this was made from (1) sided material face DOWN - This would result in making junk because you get (2) of the same handing, not a LH and RH.
Now I have NOT modified the subassemblies to correct this yet. Checking into it this is what I have noted. This is the same within as subs in a Base Cabinet OR as a single Left or Right Finished Panel products.
FE Left - Z Rotation: -90 in parent
- Base Point: 3
- Machine Point: 1
- Rotation: X0, Y-90, Z90 in sub
FE Right - Z Rotation: 90 in parent
- Base Point: 2
- Machine Point: 2M
- Rotation: X0, Y-90, Z90 in sub
This results in (2) FEs facing the SAME direction and NOT mirrors of itself. This becomes apparent with you extend the FE to the floor and notch for toe kicks. While the Carcass Base (Or Tall or Upper) the Left and Right Sides are mirrors of each other with:
Left Side: Base Point: 4, Machine Point: 1 - (Open Int would be 7M)
Right Side: Base Point: 3, Machine Point: 2M - (Open Int would be 8)
I believe the FEs need to be corrected with the same Z rotation in the parent level. The Base Point need to be right though to insert with correctly within Carcass Cabinet
- LH FE to have Base Point: 3 and Machine Point: 8
- RH FE to have Base Point: 4 and Machine Point: 7M
(I might have the Machine Points "flip flopped" ... just with wanting to machine the FE face 6 UP for machine point for our shaker machining modification translated to face 5 tokens)
I have not checked for Upper and Tall FE ... but I assume are the same issue / appears to be incorrect as well.
Can anyone explain why I shouldn't correct this? Is there a reason why the FE are produced in the same direction? It's obviously a mistake in my eyes ...
Component Library 50.5 - Build 23.1.808.641 (This was an issue in previous builds as well)
Thoughts???