Hello,
I've been writing configuration files for the JNSQ planet pack to implement axial tilt to the planets and change the moons' orbits and axial tilts accordingly. The orbits and tilts obtained are correct ; however, i've just noticed that the rotation of moons tidally locked to their parents fall out of sync, despite the fact that tidal locking is set to True. They all have in common that their axial tilts were edited.
Here is part of the code for the orbit patches:
@Kopernicus:FOR[JNSQ]
{
@Body:HAS[#name[Mun]]
{
@Orbit
{
@longitudeOfAscendingNode = 89.12579
@inclination = 23.85602
@argumentOfPeriapsis = 120.80061
}
@Properties
{
%tidallyLocked:NEEDS[Principia] = True
}
}
@Body:HAS[#name[Minmus]]
{
@Orbit
{
@longitudeOfAscendingNode = 86.83435
@inclination = 29.33432
@argumentOfPeriapsis = 302.83890
}
@Properties
{
%tidallyLocked:NEEDS[Principia] = True
}
}
}
Here are the corresponding axial tilt patches:
principia_gravity_model:NEEDS[JNSQ] {
body {
name = Kerbin
reference_instant = JD2451545.000000000
axis_right_ascension = 0 deg
axis_declination = 66.5 deg
reference_angle = 0 deg
}
body {
name = Mun
reference_instant = JD2451545.000000000
axis_right_ascension = -0.87421 deg
axis_declination = 66.14398 deg
reference_angle = 0 deg
}
body {
name = Minmus
reference_instant = JD2451545.000000000
axis_right_ascension = -3.16565 deg
axis_declination = 66.66468 deg
reference_angle = 0 deg
}
}
Finally, the cfg files for bodies of the JNSQ pack are in the following format:
@Kopernicus:FOR[JNSQ]
{
Body
{
Orbit
{
...
someOrbitalParamter = xxx
...
}
Properties
{
...
parentBody = something
tidallyLocked:NEEDS[Principia] = True
...
}
...
}
So my question is : is the lack of tidal locking a result of my own misunderstanding of moduleManager, or is it a limitation of Principia itself ?