I gave an Orbital fabber on Planet A a command to build a Teleporter on Planet B. I saw the teleporter outline and everything on Planet B. The Orbital Fabber build a teleporter on Planet A. But when I gave the Orbital Fabber a move command to the second planet, and then a build command once it got there, it built a teleporter on Planet B.
Note: this is not PTE-specific. PA#3784 - Orbital fabbers build on current planet instead of target planet.
And... now it does remember. Must have have gotten some bad data in the current window position somewhere.
So, we've confirmed there is an audio subsystem crash that appears to be happening - you're seeing it if you try and start Galactic War, and possibly elsewhere. This is one of those weird ones of "We see why it's crashing, just kind of confused why it's only crashing just now, instead of a long time ago".
The fabbers has still a assist issue in the new PTE. When the objective is to "far away" from his own position, it refuse the assist order. And the area patrol pathfinding of the air units works also not really good. They're patrolling like I have only set two patrol-points. Well when I think about it, with the radius of the circle I make with the mouse I set only two points. (The point where I set the radius will be reflected.)
pathfinding seams to be rather glitchy atm, especially with fabbers stopping and refusing to move for no apparent reason. naval pathfinding along coasts is also really finicky, often getting stuck.
+1, Also, line building still gives a lot of false positives. Sometimes when I attempt to build a line of factories, all the outlines are white, but any that have obstructions in the way fail to build as they should. But the outlines don't go red.
69025: - Nuke launcher must have missed the firing->fired memo - Time display in System Editor - presumably lets you see when your planets will collide - More system editor refactoring around simulate/pause, rounding slider values
Oh, I meant to say, THANK YOU for no longer slightly altering all the model files' metadata in every build
Galactic War can now start. Unfortunately, it loaded me into a 6 planet game. Well, one of those planets were maybe i can't even tell but seems to be inside another planet. Doesn't appear to be colliding, maybe surfaces aren't touching while one contains the other. However, I accidentally sent my commander there, and I can select him I think, but cannot move him or command him or anything. *shrug* probably has to do with new scaling, so not really a bug, just a report.
This build has some systems working better, but like the first PTE stream on Friday, Galactic War can still break pretty easily, because of how the systems are generated. We don't have the new GW specific planet generation in yet. Scathis is working on it.
I found this during the build when I loaded a planet in system view. Uber trolls..... I hate Uber Trolls. I'm not sure if this is new or not, but still. Its the Unit Canon wreckage, and even has an "Out of Order" sign on one of the corners.
Just wondering; is there a reason why several fields in the planet editor now round decimal values to integers? Water height especially can change pathable areas significantly between integer values. I sometimes used decimal values to have more control over how land bridges / naval choke points appear.
All sliders now round to the nearest integer. From the code comments: Code: // Round to the nearest integer. Slider values can come back as 0.99999.
Well yes, but why? I understand that seed value needs to be an integer, but why round water height, etc?
