These limits are very likely to be exceeded in an external application, and linking specific object facets to specific parts of the flight model calculation would be an importer nightmare. When the bodies are modeled in Planemaker, in other words, they are known quantities with absolute limits. You can't link the polygon parameters to the flight model if you import geometry from outside Planemaker. The main reason you can't import 3D bodies is that the geometry modeler in Planemaker is directly tied to the flight model calculations. Then there's importing objects for the purposes of presenting a high quality rendering model that is not low poly. One is the dream of importing bodies like the low poly fuselage, nacelles and the like, along with the wings as special calculation objects.
There are two different importing discussions here. I haven't tried doing the same thing in AC3D, but it should be possible, using surfaces and subdivision and what not to generate a surface that has a vertex right where you need it. When I model things in Rhino, I create specific objects that I know have one vertex at each end of the rotation axis I want to establish in AC3D. Sometimes you can model a helper object that puts a vertex right where you need it, and then you can individually move the end of the rotation to the correct vertex of the helper object. Generally you use the same technique above, but with vertices, not objects. You can then fine tune the location, if you need to, using the + and - Move buttons with the increments set in the three Move windows. Then select the rotation axis, and press the Move To button underneath the coordinates.
ROTATE X PLANE AC3D WINDOWS
In object mode, you can select the object, and then use the > button to inject it's center coordinates into the position windows on the left (the topmost set of x, y & z coordinates).
0 kommentar(er)
