posted 01-02- 02:20 PM               

---

Hehe.
I'm not sure that it's the y2k bug, but something is preventing Ops to save my Dofs as I've aligned them and defined them. I have Futilously tried to set up the landing gear of the p39 (it worked fine before). The prob is that the Dofs are all unaligned and out of whack. When I rotate them and save them in that position and reselect a Dof, the changes dont stick. Right now the Airacobra rolls like the Keystone Kop Kar.
I've deleted the landing gear dofs and redefined them, but no luck. They all are out of whack even though the axis numbers in the dof window are nice integers. They just dont stick. Any ideas are appreciated. All the Lods have been reworked but are oriented in the same way as I've exported them from Ac3d, then lined up in OPS.

IP: Logged

posted 01-03- 01:41 AM               

---

I just went through this with Bryan about a week ago. Here's the work around he showed me (for now) that seemed to work. Highlight the part with the dof you are working with (be in dof mode). Then select another part, and again go back and select the one you are working on. In the dof properties window set your axis' like this

x=0.0
y=1.0
z=0.0

You should now be able to rotate your dof to the right position and then save it. This time it should stick. If I'm off a little on this hopefully Bryan will correct me, but if my memory serves me right, this should work.

IP: Logged

posted 01-03- 01:41 AM               

---

Double post, oops.

[This message has been edited by Pete Hawk (edited 01-03-2000).]

IP: Logged

posted 01-03- 01:59 PM               

---

There's definately somthing weird in Ops as changing the integers in the DOF window does nothing to alter the appearance of the Dof onscreen, even after changing to camera mode and back. Bryan, please help!

IP: Logged

posted 01-03- 06:09 PM               

---

The problem with the DOF's in OPS is mainly a display problem rather than anything else and has to do with a D3D function I am using to orientate the widget, misbehaving when the parent (and grandparent) models are rotated too far from their origin. It seems to handle it OK when you use axis that are fully X,Y or Z orientated.

The workaround is to:

1. Setup the Axis manually so that either X, Y or Z is 1.0 (the rest should be zero). Use the one that is closes to your desired orientation.

2. Click on another model, and then back onto the target model to re-align the DOF Widget,

3. Move the widget where you want it

4. Save

Another workaround may be to re make the parent so it doesn't have to be rotated so much. I know that when I made some wheel struts and rotated them quite a lot into position I couldn't get the wheels to spin right, and had to "make" the structs in the right position to get the wheels to work OK.

On thing to remember in OPS with all the property windows is that they currently don't communicate very well with the other windows, which means there is not allot of dynamic updating happening in either way. To update most things you will need to click on another model and then back to get it to update.

IP: Logged

posted 01-04- 12:22 PM               

---

Thanks Bryan.
Unfortunately I did remake the parents for the wheels. In this case, the strut. No cigar. Could it mean that the ultimate parent (fuse) is out of whack? I have tried the manual entry after rotating the widget, and new numbers pop into the property window. Even tho the two gear widgets are parallel to each other, the decimal numbers dont't reflect parallellity. Weird. I've tried all the OPS versions from 6-17 to 1-03 and its all the same. All the other planes are fine, but the P-39 isnt. Any DOF gurus wanna look into it?

IP: Logged

posted 01-04- 10:48 PM               

---

I'm not sure, but I think the D3D bug (or maybe just the way I'm using it ) has a problem calulating relative orientation, so yes, it would probably have something to do with a part in the chain that is rotated too much. Maybe your strut is still rotated, but it just doesn;t look like it is, if that makes sense. For the next version of OPS I have added a XForm (matrix) reset, that will reset all of the rotations (+ matrix translations) for a model, and buttons to align a DOF with the owning models X, Y or Z axis. These last buttons don't quite work right, which is probably related to the main problem.

IP: Logged