I have silently followed this thread and not put in my two cents so as not to confuse Doc's issue. He is not the only one utilizing the UCAC-3 catalog, I have it installed on three computers along with Guide8. To date I have only applied the July 2010 update to one computer, waiting for things to settle down, but I do not have the same issue as Doc......mine does display the star names. I do know from first hand experience that Doc had his Guide8 configured a little differently than I do, like screen color.....night mode I think, but we both have Guide8 operating at lower levels, mine is typically at 10.

I would be happy to attempt to replicate some things on the one machine mentioned as it is only a back up to the other two and they are all running WinXP SP3.

Dave

--- In guide-user@yahoogroups.com, Bill J Gray <pluto@...> wrote:
>
> Hello all,
>
> My thanks to all for pitching in on trying to puzzle this out.
> The error was subtle (obviously, or we'd have figured it out
> long ago), and it's due to something I did, not anything Microsoft
> (or Clay or anyone else) did.
>
> I was going to send Clay a "test" version with lots of debugging
> code to track down exactly where things went astray. In the process
> of adding that code, I spotted what I'd done wrong.
>
> The issue is this. A while back, I added to Guide the ability
> to display UCAC-3 files from the "raw" eight-GByte dataset distributed
> by USNO on two DVDs:
>
> http://www.projectpluto.com/update8e.htm#ucac3_hd_dvd
>
> I don't think many people are making use of this capability. There
> aren't a lot of UCAC-3 disks out there, and the benefit of using the
> raw data appears to be marginal in most cases. (Note that this is
> a controversial viewpoint, but there are definitely some weird things
> going on in UCAC-3 that we all wish weren't there.)
>
> Anyway. Clay _is_ one of those people. Maybe the only one. And
> it turns out that I added code to Guide that basically says, "If you've
> drawn UCAC-3 stars, you've drawn _all_ stars; don't bother looking
> at GSC or Tycho-2 or other datasets." The idea was to avoid having
> stars drawn twice, as false doubles. The problem is that if those
> other datasets don't get drawn, the labels associated with them don't
> get drawn either.
>
> Once I noticed this, I was able to replicate the bug. _All_ star
> labels, including common names, vanished if I was zoomed in to the
> point where UCAC-3 was being used. (At higher levels, the star labels
> came back on.)
>
> Fortunately, there is a way around this. The UCAC-3 stars are
> flagged as to whether they exist in Tycho-2. I will revise Guide to
> display "UCAC-3 not in Tycho-2", and then Tycho-2. I ought to be
> able to post this fix later today (it's about two lines of code, but
> I need to make sure that fixing one bug doesn't breed three more).
>
> Thanks! -- Bill
>