JT9D-59A cowl discrepancy
I noticed that on the JT9D variant, one of the “rings” around the engine’s bump map appears to be placed too far forward for the cowling, highlighted in red. On the bump map it appears to be aligned with the front of where the pylon attaches on the engine, where from images I could find it was further back aligned with a specific panel on the pylon behind the forward section, highlighted in green, making the strip in the middle visibly more narrow. Was hoping this could be rectified before release, I can’t imagine it would take very long, just shifting the ring back on the engine a bit. Real life example included for reference.
So, I've done some research and noticed some other issues with the engine. The biggest one is that the right engine has been mirrored from the left, and I presume possibly the pylon as well. This might also be an issue with the CF6 and should be reviewed, as the engines should be translated over. All the additional inlets and accessory ports are always on the same side of the engine, regardless of the side they are on. This includes the bottom vent which is placed improperly, being on the opposite side as a result of being mirrored, instead of the same side respective to the engine.
Additionally, it can be seen in various images that there appears to be no case of an A300 that has the extended bit of the exhaust nacelle on the rear, which was present on the DC-10 and 747 with identical engines. I am not sure why that is the case, it's just what every image I can find shows, so if that bit could be tweaked in the model and lopped off, it would look much better. In addition to that, the upper and lower vents in the middle of the nacelle seem abnormally wide, and would likely be 2/3-1/2 that width.
Finally, the bump map certainly needs updating, and G-MKGA at EGBP is present with JT9D-70A engines(visually identical in nacelle) and is being broken up soon and would be an excellent reference for rivet patterns for -70A and -59A JT9Ds.
I mean no undue criticism with this, I merely am a fairly pedantic person when it comes to this and am happy to provide references to otherwise unknown information that may have been missed by the dev team. And if any of these issues have already been fixed behind the scenes, then pay this no mind.