Stellarium Updates

[stephenb (Stephen)]

Thanks Barry. I've loaded it onto my new PC build and it runs beautifully.

[Visionoz (Bill)]

Barry

I did enquire of you in the past about not getting Stellarium to work with my SiTech controlled G11 mount - it's working seamlessly now with Stellarium

Not sure if this is the right place to post this - but since it's related to Stellarium I'd thought it best to post here anyway - hope you don't mind - delete this post if it's inappropriate here

For those interested I've used Stellarium with my now working SiTech Servo controller with my Losmandy G11 mount and the it's the current latest version with Stellarium Scope as well in order to connect to the ASCOM 6 SiTech driver - all running on i7 chipped Win7 64bit 16GB RAM, SSD HD AstroPC and Nvidia hi-end video card

The usual Ctrl-1, Ctrl-3 & Ctrl-5 works as advertised

It's singing along!!

HTH
Cheers
Bill

[Barrykgerdes]

Version 0.11.1 was released last week. It has many bug fixes and some new features

0.11.1 [2011-11-04]
Bug fix release.
Added:
- new skyculture: Arabic
- new moons and rings (LP: #815484, #834336)
- new translations for landscapes and sky cultures (LP: #849292)
- possibility to observate geo-orbiting satellites (LP: #837274)
- new cities (LP: #856343, #860206)
Fixed:
- misspelling on a star name (LP: #884795)
- location window: map pointer position is updated on longitude/latitude change.
- location window: fixed checking "Use as default" changing the name of the selected location to "New Location" (LP: #881613)
- Solar System Editor plug-in: a bug in the parsing of MPC lists: the epoch's Julian Day value was wrong by 0.5 JD (LP: #836839)
- Solar System Editor plug-in: crash while trying to browse for a local file (LP: #837396)
- Historical Supernovae plug-in: a bug in plug-in name (LP: #803157)
- Historical Supernovae plug-in: a bug in selected instead of nearby stars (LP: #835815)
- doesn't load localised description of skyculture/landscape if applanguage=system_default (LP: #845924)
- add/remove landscapes dialog bug in OSX 10.6.8 (LP: #812008)
- horizon line setting not saved (LP: #811945)
- orbital period totally wrong for Himalia (LP: #806174)
- flag_show_fps = false & flag_show_fov = flase (LP: #728294)
- 0.11.0 will crash if a landscape is selected with misspelled planet name (LP: #835422)
- crash on selecting off-Earth location in the Location window (LP: #834886)
- 0.11.0 crashes when switching language while location window is open (LP: #824936)
- 0.11.0 crashes when trying using custom distortion file (LP: #871313)

Barry

[ballaratdragons (Ken)]

I downloaded the new 0.11.1 last night (in the hope that it is better) and I still don't like it.
I have uninstalled it already.

The Southern sky is still really badly represented.

For example (and to be fair I'll use a common large DSO's), Tarantula Nebula.

Can you see it in Stellarium? No.
Is it shown on the map? No.
Does it appear even if I zoom waayyy into it? No.
It has a star marking its location when you bring up NGC2070.

Let's try another even more Massive common DSO, Carina Nebula.

Can you see it in Stellarium? No.
Is it shown on the map? No.
Does it appear even if I zoom waayyy into it? No.
It doesn't show much of anything when you go to NGC3372.

Try a few more popular southern objects. Same results.

I'll stick with Cartes du Ciel.

[Barrykgerdes]

The nebulae shown in Stellarium are anly superimposed textures. If there are no textures of the object there will not be a display. The particular nebulae you mention are not seen from the northern sky so they are not in the default package.

If you wish to see those two particular nebulae in stellarium down load the auxiliary textures package. Try this and follow the instructions. This package contains textures from some of our IIS members adapted to Stellarium, NGC3372, LMC, SMC, NGC2070, IC2944, IC4628, NGC104, NGC5128, NGC5139, rho ophiuchus, NGC6744 and many others

http://barry.sarcasmogerdes.com/stel...mnebulae-1.ZIP


In the future there will be textures of the whole sky from the digital sky survey

If you would like to see what this will be like You can download this patch to version 0.10 and follow the instructions


http://barry.sarcasmogerdes.com/stel...oast-patch.zip


Barry

[multiweb (Marc)]

Barry, how do you connect the G11 to stellarium?

[Barrykgerdes]

Originally Posted by multiweb

Barry, how do you connect the G11 to stellarium?

With a cable

Barry

PS do you have Gemini?

[Barrykgerdes]

Originally Posted by multiweb

Barry, how do you connect the G11 to stellarium?

Seriously

Stellarium uses the same protocol to drive the Gemini as an LX200. However there is a specific Losmandy G11 driver listed in Stellarium.

It connects to the telescope via a com port (or USB/RS232) and can use any Com port number.

The cable is a 4pin (RJ22)
Pin 1 N/C
Pin 2 Gnd
Pin 3 RxD
Pin 4 TxD

A LX200 cable is not suitable you will need to make your own

Trevor uses GCC but I have tested it with Stellarium. No bother! I also wrote a program in Qbasic to drive it with a different set of catalogues.

Barry

[multiweb (Marc)]

Originally Posted by Barrykgerdes

Seriously

Stellarium uses the same protocol to drive the Gemini as an LX200. However there is a specific Losmandy G11 driver listed in Stellarium.

It connects to the telescope via a com port (or USB/RS232) and can use any Com port number.

The cable is a 4pin (RJ22)
Pin 1 N/C
Pin 2 Gnd
Pin 3 RxD
Pin 4 TxD

A LX200 cable is not suitable you will need to make your own

Trevor uses GCC but I have tested it with Stellarium. No bother! I also wrote a program in Qbasic to drive it with a different set of catalogues.

Barry

Cool - I already have a USB to serial plugged into the RS-232 port. That's the way I connect the GCC and the Gemini.net ascom driver on COM4. So setting COM4 in stellarium will work. That simple?

[Barrykgerdes]

Originally Posted by multiweb

Cool - I already have a USB to serial plugged into the RS-232 port. That's the way I connect the GCC and the Gemini.net ascom driver on COM4. So setting COM4 in stellarium will work. That simple?

Hi Marc

If you already have ASCOM you can also use Stellarium scope (Not part of Stellarium). But ASCOM is not necessary for a direct connection Stellarium.

You can use any port up to at least COM16 but depending on the version of stellarium the window may not scroll past COM 4. Just type the number in the window.

Some programs can only use COM 1 or COM 2 so you may need to re-configure the Port to COM 1 or 2

However it looks like you already have the cable connected for GCC using COM 4, so Just run Stellarium and nominate COM 4. Oh! I forgot, Make sure that the Telescope drive module is configured from the plug in window to run at start up.

Barry

[multiweb (Marc)]

Originally Posted by Barrykgerdes

Make sure that the Telescope drive module is configured from the plug in window to run at start up.

Barry

No worries - thanks. Will try next time out.