UCS Millennium Falcon (75192) part collision issues in Stud.Io

[AColtsFan]

Usually I'm pretty good at resolving these issues with experimentation, calculation, etc., but I'm running into one that's got me just completely stymied.

The issue comes at step 361, where the assembly that will eventually be the bottom of the main thrusters clips on to the chassis.  There are three parts to that assembly--a center section that clips via hinge onto the chassis, and two "wings" that are hinged to the center section, and are supported on either end by resting on a slope brick protruding from the chassis.  However, I cannot figure out an angle--either between the assembly and the chassis, or between the wing and the center section, or a combination thereof--that avoids collisions.  If I have the wing of

the assembly resting on the slope brick as intended, the wing section collides with the bar arm below; if I have it angled up enough that it doesn't collide with that, it collides with some of the chassis bricks above.  There is also a range of angles where it collides above and below.

Right now, in the screenshot, you'll notice that I don't have the wing resting on the slope brick as intended.  If I do change the hinge angle to where it does rest, that solves the intersection with the upper brick on the chassis, but you'll also notice that the dome on the underside of the wing is already intersecting with the arm bar below; that problem will still exist if I hinge it farther down.

I have a couple of questions:

1. The part I'm calling an "arm bar" that's below this assembly is this piece.  Stud.Io calls it #30359b,  "Bar 1x8 with Brick 1x2 Curved Top End (Axle Holder Inside Small End)", Brickset calls it #60572, "Brick W. Shaft 1X8X1".  I've never actually encountered one in real life--is it supposed to flex somewhat?  If so, that may be the issue.

2. If that's not the problem (or not the whole problem), is there a solution to this that I'm missing, or is it just one of those things where Stud.Io has unrealistic expectations?

Also, if needed (and permitted) I can link to a higher-resolution version of the screenshot, I had to scale it down to fit the file size limit and it may be difficult to make out the details (I'm hardly a good judge of that since I already know what I'm looking for and where).