posted 12-08- 11:04 PM               

Here is what I did:

1. smd the FokkerEIII.sm file
2. OL imported the FokkerEIII.ol file
3. Selected the object that needed to be positioned
4. Positioned the left wing object by draging it.
5. Saved the .ac file
6. Exported the .ol file as FokkerEIII2.ol
7. olc'd the FokkerEIII2 file into the FokkerEIII.sm file.
8. Opened the new SM file in OPS and saw that the wing was fixed!

Now I closed AC3D and re-opened the .ac file like you suggest. I then positioned the right wing object the same way and saved the .ac file. I then exported the .ol file and olc's it. But this time I got the positioning error you see in the screen shot. It looks perfect in AC3D, but is wrong when exported.

Any ideas? What do you think I should do? Maybe re-import the SM file instead of using the .ac file - and fix the right wing again?

Much thanks Hippie, this is going to be great! Wires will be MUCH easier to add with the entire aircraft in AC3D

------------------
-Sv =FC=

WWI in SDOE!

posted 12-09- 11:20 AM               

Always move all the LODs in a model part together

posted 12-09- 11:28 AM               

I select these three object, then move them all over to the right. When I export and look at the plane, the top and bottom triangle mesh is moved where I want it, but the center triangle mesh is left alone. The center triangle is a parent to the bottom triangle. The top triangle is its own object.

Any ideas on what I am doing wrong?

Thanks!

posted 12-09- 07:25 PM            

Is the structure of the left and right
wings the same? (Can't see all the Hierachy
in the screen shot)

In the screen shot it looks like you
are in vertex select mode, is this what you
intended? (It will only move the vertices
and not the position of the model part).

Those hidden lower detail LODs wont
be selected and moved, that could be a
problem if you want them all to line up.

What does the wonky .sm look like in AC3D if
you smd and ol import it again?

The "Models" take their position from
the position of the first LOD
in the model because in AC3D terms an object
with no vertices (The way I implement the
openplane model records) can't have a
"position". So you can move a child model
relative to it's parent by selecting the
first LOD of the model in object mode and moving it.

Busy again this weekend so I can't really
look into the code and remind myself how it is all supopsed to work

posted 12-09- 07:48 PM               

The left and right wings are indeed the same.

quote:

---

In the screen shot it looks like you
are in vertex select mode, is this what you
intended? (It will only move the vertices
and not the position of the model part).

---

No, that is object mode, the vertecies of selected objects highlight.

quote:

---

Those hidden lower detail LODs wont
be selected and moved, that could be a
problem if you want them all to line up.

---

Yes, I figured that, I am just making sure that I understand how OL positions things before I jump in full blast

quote:

---

es the wonky .sm look like in AC3D if
you smd and ol import it again?

---

It looks finein AC3D. So I move the objects and export - this sm file is bad. I smd this file and import it into ac3d again, and it is magicaly fixed again!

quote:

---

Busy again this weekend so I can't really
look into the code and remind myself how it is all supopsed to work

---

posted 12-10- 04:06 PM               

It works sweet, and the DOF tool is far beyond anything we have now. However, you can not use OPS with an aircraft that has been edited using the OL tools this way. The OL tools store the DOF data in its prop list form - OPS can only handle the DOFS in binary form.

You can still view the plane in OPS, just don't save it!

From what I see, the main thing we lose by using the OL tools this way is the editing of inertia boxes. Also viewing alpha textures while positioning parts... and setting gun convergance.