Emperor L
[ Posts : 1237 ]
 | [Post Date: 22-Jan-2007 20:13]
In pleiads I got the report:
'Our NODE is trying to generate a BLACK HOLE [503:201]' the galaxy time was 12:5:20
But it did not create a BH, and even more strange is that there is no star in that location...the star I was trying to colapse was 502,199
My U4 dissapeared, just as they should when a star is colapsed, except it did not crush a star...
I am sure I sent it to the correct location, and even if I didn't, usualy you get an error message if the star does not exist...
There is another BH near it, so maybe there was a star at 503:201, but it was destroyed a while ago, not sure. Maybe the game still thinks it exists, but I would expect the U4 to get sucked in by the BH if this was the case...
|
Emperor L
[ Posts : 1237 ]
| [Post Date: 22-Jan-2007 21:21]
Ok, I think the reason this happened was because I sent the u4 to 502:200 (next to the star so I could accelerate it). But this quadrant was near enough to the other BH to be effected by it, so the U4 was pulled towards the BH, but it still tryed to crush the star, even though it got pulled away from it, and so it was not in the correct place.
I have tested it with Y-units and they do get pulled towards the BH
I guess the same would happen if a WH was created on top of a U4 as it was about to jump into a star to colapse...
|
Green
[ Posts : 1005 ]
 | [Post Date: 23-Jan-2007 11:01]
Also note, that BHs are joined into one, if they are near each other, and resulted BH can be placed far far away from initial position. When tested BHs algorithm, we faced with one BH, which moved around all galaxy
|
Emperor L
[ Posts : 1237 ]
| [Post Date: 24-Jan-2007 00:23]
Quote
Also note, that BHs are joined into one, if they are near each other, and resulted BH can be placed far far away from initial position. When tested BHs algorithm, we faced with one BH, which moved around all galaxy
|
|
Yeah, I had a few big chain reactions this round But this was just because the U4 got pulled away from its location, I guess that once an order is accepted and RTTA is calculated, nothing else checks for changes caused by BH, so RTTA should have been 1, but BH pulled node and changed its location, but the game still thinks its time to fire the U4, so it did it in the wrong place where no star existed causing it to fail...
|
|
