Astrolog: The Next Version
Astrolog 6.40 was released at this site on July 22, 2018. The next version
is under development. :-)
- Yearly transit to natal graph bug: The -Vy and -VY command switches
to do a transit to natal graph for a year or five year period don't work fully,
and instead just do a graph for a single month. This bug only affects the
command line, and not when selecting a year or years in the Windows version
interface. There is a workaround: Append "=By _B" to the end of the
command line involving -Vy, and that will turn on the "do a whole
year" setting. (The trick is to use the -B transit to transit graph to
turn on the "do a whole year" setting, and then turn the -B chart
back off, which leaves the "year" setting on.)
- Sidereal fixed stars bug: Astrolog's fixed star objects aren't
positioned correctly when the sidereal zodiac setting is on, because they apply
the tropical to sidereal offset twice. Workaround options: (1) Ensure the
tropical zodiac setting is on. (2) Use the "show all stars" feature (Ctrl+s
hotkey in Windows version) with charts that support it which does still place
stars correctly regardless of zodiac. (3) Use version 6.30 or before in which
this worked. (4) Wait for the next version in which this is fixed.
- What it is: You display a chart for "now", either by
looking at the default chart that comes up in the Windows version, or by using
the -n command switch, and the result is that the "now" chart is
always off by a few hours. (And it's still off even when you've made sure
Astrolog's default time zone setting is correct and have double checked your
- The correction (short version): Open your "astrolog.as"
default settings file (in your Astrolog install directory) in a text editor. Go
to line 7, and change the line "-Yz 0" by replacing the "0"
with the number of minutes the "now" chart is off by. For example, if
the "now" chart always seems to be two hours ahead, change it to
"-Yz -120" (minus the quotes of course).
- The correction (long version): The problem is simply due to Astrolog
thinking the current time on your machine is different from what you think it
is. The problem isn't a bug or inaccuracy on Astrolog's part, as once it gets a
time, it casts the chart for that time perfectly. It's just a matter of getting
the right time in the first place. The way Astrolog gets its "now"
time, is that first it queries your system for its local time. Then it
translates that local time to GMT, by querying your system for what time zone
your system time is in. Once the GMT time is obtained, and the chart is cast,
the GMT time is translated back into your local time using Astrolog's default
time zone, and that time is displayed as the time for the chart. The system
time zone and Astrolog's default time zone are two different things, so if
they're different, then the result of the "now" time and your system
time differing happens. Note that Astrolog's default time zone only affects how
"now" times are displayed in the program; changing it won't affect
the absolute "now" time or cause planets to move. The case for most
people is they don't have any system time zone variable set, so Astrolog always
thinks their local time is in GMT or Pacific time. The most correct fix is to
set your TZ environment variable, so your machine has a correct system time
zone setting. See the documentation for the -n command switch for how to do
this. The alternative way is to just give Astrolog a correction factor of some
amount of time to add to all its "now" charts, using the -Yz switch
described above. See the documentation for the -Yz switch for more details.
- Note: This shouldn't ever be a problem on modern Windows systems.
Windows Astrolog gets the current time (and whether Daylight Time is in effect)
from Windows, and will accurately reflect that time. However this issue may
occasionally appear on non-Windows versions of Astrolog that are compiled
Have you found a bug in Astrolog? Tell me!
This site produced by Walter D. Pullen
(see my homepage), hosted on Magitech and astrolog.org, created using Microsoft FrontPage, page last updated
April 19, 2019.