Beta 4B - Praise and a few problems

1. Beta 4B is the most stable of the betas so far. I haven't had a single crash to the desktop.

2. I like the new UP issues, especially the "war tax" issue.

3. I'm playing a gigantic galaxy and performance is pretty darn snappy on my 833 MHz Pentium 3.

There are some things amiss though...

1. There are still some timing issues that unless you know about them can lead to what appears to be a lockup.

Please see my post entitled "4A - More timing wierdness with dialogue boxes". The same issue is still happening from multiple entry points. Most commonly from the UP results screen, a GNN report, or an espionage result screen.

2. I consistently have constructors dropping out of autopilot about half a sector away from their destination, which is invariably a starbase that they are supposed to be upgrading. This happens about two-thirds of the time. It has never happened when they are headed for a bare resource.

3. when one of my starbases is destroyed and I send another constructor to the same spot on autopilot, usually a resource, to rebuild the starbase the constructor stops dead on the correct endpoint but doesn't come up with the "would you like to harvest this resource?" box. Nor will it permit me to build a starbase on that spot.

If I move the constructor off the resource and use the arrow keys to manually move the constructor back onto the resource all performs as expected and the starbase is built.
108 views 3 replies
Reply #1 Top
Magus,

On your bug #2, it may help the Stardock people to know whether or not this always happens when the status of the target tile changes. Cari fixed a similar problem not too many builds ago where a ship would drop out of autopilot when the status if the ship's target tile changed. This was particularly true of contructors when more than one had a destination to a tile and one oif them reached it and was used to build a star base. There are other possible causes, of course, but it would be nice to eliminate the possibility that an old fixed bug has somehow crept back into the code.
Reply #2 Top
Jack,

I'm not quite sure how to answer your question...

The destination point is invariably an already constructed starbase. The only thing that _may_ be changing is that between the time the constuctor was dispatched and the dropout from autopilot is that another constructor may have upgraded the same destination starbase.

I'll have to keep an eye on it but I don't _think_ that is the case in 100% of the cases.
Reply #3 Top
On closer examination it seems that the behavior I reported in bug #2 only occurs if the subsequent constructors are "offscreen" or outside the current visible area on the main map when another constructor upgrades the starbase.

My guess is that it's an inadvertant side effect of the changes to the pathfinding code Brad mentioned. The one where "offscreen" ships "jump" from place to place rather than _really_ going from point to point.