Just taking a leaf out of your book.
It appears you agree that your assertion "that's what a 3-4° turn looks like" is baseless, not to mention the fact that the radar based ground angle change is around 1.5 degrees, not "3 to 4".
I mentioned numerous of your values, all were shoddy, none have been rectified or even admitted to be shoddy. Pfft.
Scale models are already to scale
Totally dependant upon rendering environment.
I did apply the correct dihedral and flex of a wing in flight.
How, and what angle ?
That's obvious, as I said.
it took longer to calculate the positions
You've shown repeatedly that you are incapable of accurately performing even simple measurements. You should use the satellite imagery as a plane within your rendering environment. That allows you to provide visual confirmation of absolute object placement, orientation and relative placement.
and set up models than it did to make them
Make them ?

You have one stock aircraft model, and two "boxes", even though I've already provided you with these models...
You may think your efforts are far superior
I know they are
they're not far superior if they consistently show the wrong angle
I'm quite happy with the accuracy of my values.
Are you going to get even one measurement done accurately any time soon ?
If you wish to verify my angles all you have to do is create your own scale model. You have all the information you need to do so.
Grow up.
The satellite imagery is not a part of your scene.
There are only three to remember. With a tube passing through the length of the fuselage the model can be placed over a rod protruding from the scale building. That rod can be accurately positioned to achieve the specified pitch and yaw angles and the model can then be rotated on the rod to get the desired roll angle. Unlike your "superior model" mine is actually at 12° when I set it to 12°. If the plan views you provided are anything to go by your models are at least 2° over the specified values.
As I said, ... oh dear.
When you don't understand something, stop and ask.
You are clearly clueless about the difference between object and world coordinate systems.
My plan views were provided to you so you didn't make such stupid mistakes.
On a plan view the horizontal angle between aircraft and tower is ABSOLUTELY not the same as the horizontal angle applied to the aircraft model, as the aircraft model has modifiers applied to all thee axes.
Just STOP until you get that simplest of factoids into your head.
They're not renders, they're real world models
The ONLY way you can't be wrong is if you've made cardboard models, which would be hilarious...especially getting the camera the right distance away.
If you haven't "made my day" by getting sticky tape out, no, they are renders.
Please, please say the towers are cardboard boxes
Secondary buildings are only needed to accurately locate the camera position.
Incorrect. Secondary buildings are required to verify numerous factors which include lens FOV, camera elevation relative to tower and aircraft, ...
When you don't know what you are talking about, don't make it up.
Since we know that position it's not essential that they're there.
Incorrect. See above.
I haven't attempted rotoscoping yet. Figured I'd do a quick physical model to double check first.
Please, please say you've made that out of cardboard...
I have no reason to fabricate results
You've clearly had an open and blatant agenta of attempt (and fail) to "prove femr2 wrong version the umpteenth".
You've stumbled from one "gotcha", been proven wrong, stumbled to the next, been proved wrong, ... many times.
This is no different.
I'm merely checking the alternative values against reality. It's not my fault that your values don't match.
ROFL. You'll get there eventually, once you actually get to grips with what you are trying to do.
IF (and it's a big if in my book)... IF you're actually trying to do "this thing" properly and accurately...you'll end up clearly showing the NIST impact orientation is out of whack.
Nothing has been adjusted to make NIST correct and you wrong. Positions are worked out, the camera is set and the chips fall where they may. As I said, if you want to check you're more than welcome to do your own model to verify.
ROFL. Again, grow up. You've seen the results of me "doing my own model" many times.
Tada...
Actually you haven't explained it, merely asserted it.
Incorrect. Re-read our discussion. You bore me. When you deny such again, I'll spend the extra 30s it takes to refute you.
Seems fairly straightforward to me. Two images of the same aircraft in the same orientation, one with the camera at ground level, one with the camera at the same level as the aircraft. Building width is matched and the aircraft length matches. You can check this yourself by raising the camera and doing a render in your 3d environment if you want. Viewer elevation makes no difference, that's why the 2d check works.
It does not work. Deary me.
You cannot treat features on separate planes as if they are coincident.
Your method is fatally flawed, as I have previously explained to you.
To "others": Can you "imagine" the number of "laughing dogs" that would emerge if I started making such dumb-derrier assertions about basic three dimensional geometry ?
Please, please tell me you made your "physical models" out of cardboard.
