Hmmm. System specific bug? For your info I'm running Orbiter 2006P1 on a six year old computer with an Intel Pentium4 chip,Windows XP Home SP3, nVidia G-Force FX5600 XT graphics card.Brian: I ran tests on a different machine using your config file and an initial angular velocity vector of {2,0,20} deg/s. I observed the expected symmetric top type precession in both 2006 P1 and Beta 091124 (as best as I can tell. Cool idea for a module: add an angular velocity vector and angular momentum vector to the visual representation of the vehicle). If I can get fraps working here I will provide a video. I can confirm that I was definitely not getting this behaviour on my other machine last night. Weird...
I'm using the default settings on the Orbiter Launchpad/Extras/"Angular Velocity Propagation" tab.
Doesn't look like what I get using rotation {2,0,20} and .cfg inertia parameter of "Inertia = 1 1 2"EDIT: Have a look at this video and see if it looks anything like what you are getting and/or are expecting: http://orbiter-forum.com/images/orbiter_sym_top_precession.wmv (my apologies for the terrible frame rate, I am not having much luck with fraps atm, it used to be much better than this...)
I get the same old 180deg aperture cone.
Your video does look more like what I would expect to see - but...as far as I understand it, for an Oblate body (where Iz > Ix) the precession rotation should be in the opposite sense to spin rotation.
In your video it looks like the precession rotation is in the same sense as the spin rotation.
So I would say that your video still shows incorrect precession behaviour.
Thanks for taking the time to look at this, anyway
Cheers,
Brian


