That is NOT the way I work, my friend. YOU have improved the add-on, therefore YOU deserve some credit.ElChristou wrote:Bob, it's before all Cap-team' ssc, so no need to credit me.
Hi Cham, I think the orientation of the solar panels is probably correct for Dawn's "typical" orientation during cruise. The most efficient way of boosting an orbit is to thrust along the velocity vector, so the engine(whichever is in use at the time - assume it's the centre one) will be pointing in that direction most of the time. Axis of rotation of solar panels will be perpendicular to the spacecraft-sun line to maximise power output. High Gain Antenna I think faces the Sun (to keep the science payload in shadow?) But if you still want a model with rotated solar panels, it's no problem - just let me know.Cham wrote:I think the model is wrongly oriented, relative to its trajectory, and the solar panels should be 90° rotated.
Your English is very good my friend. The "cockpits" in Orbiter are really only for visual amusement (although some have functional switches, etc.) - all commands to the vessel can be entered via the keyboard. It's a shame that Orbiter is not available for Mac - it's the only reason I still use Windows.ElChristou wrote:LOL! (Sometime the English and I...)
But still curious, from what I now, in general Orbiter allow the user to enter the craft's cockpit to use the commands; in the case of Dawn, how do you do? (ok, perhaps my question can be silly but as I'm on Mac could never use this soft...)
BrianJ wrote:Did you mean "manned spacecraft flight simulator"?ElChristou wrote:BTW Brian, how do you use such model in Orbiter? Orbiter is a manned spacecraft fight simulator, right?(although I think some people would like to use it as a fight simulator!) Orbiter is just a "spaceflight simulator" - manned or unmanned. Most folks use it for Shuttle missions but my personal interest is trying to figure out interplanetary trajectories and simulating current real-life missions.
Bob - thanks for the info, methinks the file paths for the textures needs to be relative, yes? Like ..\textures\medres (that's what I've set it to now)
See if the .3ds model in this .zip behaves better....
http://myweb.tiscali.co.uk/briansutilitysite/dawn.zip
EDIT: OH! I see you've got it fixed anyway! Well done!!
I hope the scale and axis orientation are OK.
Regards,
Brian
Just tried it again, and it works just FINE for me.danielj wrote:The link seems broken.I can?t download it...
Code: Select all
"Dawn" "Sol"
{
Class "spacecraft"
Mesh "dawn.3ds"
Radius 0.012
Orientation [ 90 0 0 1 ]
Beginning "2007 09 27 12:41:00"
Ending "2015 02 01 00:00:00"
SampledOrbit "dawn.xyz"
Albedo 0.05
UniformRotation
{
Period 50000
}
BodyFrame
{
TwoVector
{
Center "Sol/Dawn"
Primary
{
Axis "-z"
RelativePosition
{
Observer "Sol/Dawn"
Target "Sol"
}
}
Secondary
{
Axis "x"
RelativeVelocity
{
Observer "Sol/Dawn"
Target "Sol"
}
}
}
}
}
...Adirondack wrote:Christophe?
Why did you (or CAP-Team) use the 'modify' command for "Dawn" "Sol"?
If I'm not completely wrong, this would also work:
EDIT:
Well, this does not work (no encounters)!
Can somebody explain why?
Yes, the add-on DOES modify the trajectories of Vesta and Ceres. It DOES follow the encounters exactly as described on the Dawn Mission website, but these are not very close encounters.chris wrote:There are two possibilities:
1. Does the add-on modify the trajectories of Ceres and Vesta? The default EllipticalOrbits in Celestia aren't accurate enough.
2. I recall that the Dawn trajectory on HORIZONS doesn't actually include the orbits around Ceres and Vesta yet; this part of the mission may not be planned out in detail yet.
--Chris
Thanks, Chris, for this clarification. I knew there was something.chris wrote:That works, but only in 1.6.0.
As Chris stated here, this is the problem with the not-so-close flybys as depicted with this add-on. It is still a rather interesting depiction of the approximate fly-bys though. Have a look at the ReadMe.txt file and see what it does do.chris wrote:I recall that the Dawn trajectory on HORIZONS doesn't actually include the orbits around Ceres and Vesta yet; this part of the mission may not be planned out in detail yet.
danielj wrote:Sorry.The second time,it worked.But in 2011,Dawn is still millions of km of Vesta...
Code: Select all
LEAPSECONDS_FILE = /nav/dawn/import/naif/leapseconds.tls
SPK_FILE = sb_vesta_071107.bsp
IAU Number: 4 <= vesta
Summary for: sb_vesta_071107.bsp
Bodies Start of Interval (ET) End of Interval (ET)
------- ----------------------------- -----------------------------
2000004 VESTA 2007 JUL 20 00:00:00.000 2018 JAN 23 00:00:00.000Code: Select all
"vesta" "Sol"
{
Radius 265
SpiceOrbit {
Kernel "sb_vesta_071107.bsp"
Target "4"
Origin "10"
BoundingRadius 1
}
SpiceRotation
{
Kernel "dawn_vesta_v01.tpc"
Frame "4"
BaseFrame "eclipj2000"
Period 5.342
}
}
Funnily enough, I was offered the part of Bill Wyman in one the Rolling Stones tribute bands a while back....but that was just too confusingAdirondack wrote:@ BrianJ: You aren't a reincarnation of a Rolling Stone? Sorry, I couldn't resist.
You're very welcome to the "Dawn" model - nice to see it up on the Motherlode Thanks to you, Brian, for the add-on. Don't mind all of the griping here. Some people ain't NEVER happy...BrianJ wrote:Hats off to the folks who did the major part of the work with the trajectory, add-on format, etc.
I just know that I'm going to be sorry I asked this, but the add-on does not work on my system (see specs below) and I just thought I'd ask what we need in order to use spice kernels.CAP-Team wrote:(if this does not work on your system, it might be handy to know that I use spice kernels for all solar system bodies).
Yeah, I ended up downloading a toolkit for my PC, and a ReadMe to see what all the fuss is about. Got Various components for the C language HERE.ElChristou wrote:Bob, you need a special version of Celestia to use those files. For your question, try the search engine, you will find easily.