Still skipping explored spaces as it travels.

yep it increases production by 20% instead of Manufacturing by 25%

Confirm I have seen skips in the FOW reveal in latest patch.

Just checked my homeworld and the Txlrp is giving +25% manufacturing according to the Planet tooltips. Ejecting the Txlrp changed the Manufacturing numbers but not the Production numbers.  Didn't run the numbers because I'm lazy like that, but they looked right.

As for 25% or not, it is possible to lose track that the +25% applies to only the base manufacturing and not to the current total.  If there are other bonuses present, that makes a difference.  I can't tell from your post if that is a factor in your calculations.  You probably already know that and I am needlessly reminding you.  

Okay so this post doesn't come up again. I don't speak greek. Where, and how do I come up with these numbers if I don't count manufacturing points. Ok it shows it untill I count points lost. How do I calculate how much manufacturing should be added.

Quoting erischild, reply 2

Just checked my homeworld and the Txlrp is giving +25% manufacturing according to the Planet tooltips. Ejecting the Txlrp changed the Manufacturing numbers but not the Production numbers.  Didn't run the numbers because I'm lazy like that, but they looked right. 

your right its the "Pollen" who states to give +25% Manufacturing but gives +20% Production

there is a tooltip for Manufacturing,

just take the Base Manufacturing and multiply it with the Bonus so in this case: BaseManufacturing * 0.25

Ahhh.  I have learned something.  I don't think I have used that particular Merc, and certainly not double checked it.  Good catch.

I've seen the 'stuttering' of should-be-explored space so far back I wonder if I saw it in GC2.

Recently, I noticed an interesting related effect. If you bring an active sensor zone in close proximity (I forget it if needs to be just at the edge) of one of these annoying blank spots, the map data is revealed.

I either did or meant to send in a proper bug report with screen caps many moons ago, so I'm glad to see the topic raised again.

It's still skipping even after the most recent patch.

It seems to be either too complicated to fix or to be too low on the priority list (or both ;)) although it should be easy enough to recreate the problem since a lot of people report it (I have it also, on both my machines) so it can't be a problem with hardware configuration.

I had it too now for the 1st time, happened with a vanilla Krynn freighter, pls. see pic.

But after reload those black parts that the ship had already passed became uncovered as it should be, so it was ok again.

http://imgur.com/a/7TYLZ

If it's on my machine there is no way it's a hardware problem. 6700 SSD 16 gigs of ram 960.

I know it has been a while since this was brought up, but the last status I know of is that the problem is too intermittent to replicate reliably.

I have managed to do that with a minimum of steps from a game save file.  It works every time, or rather, fails every time.  I wrote it up and submitted it as ticket JJX-839-58167.  Hopefully it will give Stardock some clues as to what is going on.

I was kinda proud of actually catching the bug in action.  A seriously geek reaction. 

Sorry about the colors.  I seem to have lost an argument with the editor.

Yes, I've been seeing this quite consistently since 2.0 came out. Was bummed to see that it had come back as it appeared "fixed" for me with 1.9. With 2.0 I just have to have ships exploring without being in view for it to occur.

That's how it's "working" for me also.

For me all I have to do is move some, not always ship through unexplored space it doesn't matter if the destination is in explored space or not. This is exceptionally annoying when you are moving one of your survey ships, and later when the space finally shows umteen turns later there is a anomaly there.

This, and when there are resources you are wanting hidden there.

I guess I'm not sure how this is hard to reproduce--I reproduce it nearly every game. I think it occurs more on larger maps--but that may simply be because larger maps have more opportunities via more space to explore...

I find this bug occurs with some regularity when I select a ship and move it without it being on screen (e.g., when I'm zoomed in on an unexplored area)--or when I am not focused on a ship that moves through FOW when I press "Turn."

Yes, I have seen this bug for quite a while now, perhaps even in the EA. To provide some help to the devs I am offering this observation:

I have only seen it with ships on autopilot.

The amount of space not uncovered appears to be a function of the ship's speed (moves per turn), thus giving the patchy look observed. It is almost as if the space being exposed is only the space at the end of a ship's turn.

I vaguely remember the unexposed space being exposed after a save and reload. I am not sure, but this may have been in a prior level, or even in EA.

Yes, reloading the game exposes the "unexplored" space each and every time for me also.

Just reloaded so cannot confirm my guess: can it be that ships off-screen just jump to the next position in their predefined path by their movement rate and then apply their sensors only from this spot, so that this problem only occurs if the movement rate is bigger than the sensor range?

To describe my observations and conclusions, since I have paid some deliberate attention, enough to catch the bug in the wild, so to speak.

It happens most with high speed ships, and it happens when those ships are on a manually set autopath of multiple turns.  I have not seen it for ships on auto explore or auto survey.  If the ship is on a multi turn auto path and if it is off screen for an entire turn of that auto path, there is a chance that it will not display the fog-revealed tiles when you do get around to looking at that region of the map.  Generally, it happens when the ship is sent off into an area of solid fog. It is a display glitch.  Saving and reloading refreshes the display, which means the tiles were properly marked as "revealed" in the appropriate dataset  Often, sending a subsequent explorer nearby will start filling in the display when the second explorer comes close.  It looks like the second explorer has this sudden invisible magic sensor range that comes into effect.  It would be a clever trick if it were done on purpose.

To my knowledge, no one has successfully duplicated the behavior from a save game because, although it may be all too frequent, it is actually quite erratic.  Stardock has said they cannot produce the bug on their systems.  My conclusion is they need to play more and work less.    With some luck and some practice from a career of being an escalated trouble shooting resource, I managed to actually repeat it quite reliably.  The real trick was catching it on the first turn of the auto path.  I even took the save file to a second machine with a separate Steam account and a second copy of GalCiv, and it did the same thing.  In my career of being everybody's resource when they couldn't solve their tricky problems, intermittent issues were the worst.  Many a time I would have done many an evil thing to get my hands on a repeatable symptom.  I only hope this is that kind of clue, and that Stardock can make use of it.  Stomp those bugs!

If you are really curious, or bored waiting for Crusades, here is the dropbox of the files I sent to Stardock.  It seems that everyone has seen the problem first hand, but if you want, why not?  

Agree, this is what I have noticed also, with my less than attentive attention.

Yes, this has always been the case with me.

Yes, I've noticed this as well.

 It would be a clever trick if it were done on purpose.

My conclusion is they need to play more and work less.  

LOL I don't think too many of them would complain about doing that... except maybe Brad and Paul...

Good work, erischild,   just wanted to add my insignificant validation of what you've reported based on my own informal observations of this lovely issue.

Quoting erischild, reply 19

To describe my observations and conclusions, since I have paid some deliberate attention, enough to catch the bug in the wild, so to speak.

 

It happens most with high speed ships, and it happens when those ships are on a manually set autopath of multiple turns.  I have not seen it for ships on auto explore or auto survey.  If the ship is on a multi turn auto path and if it is off screen for an entire turn of that auto path, there is a chance that it will not display the fog-revealed tiles when you do get around to looking at that region of the map.  Generally, it happens when the ship is sent off into an area of solid fog. It is a display glitch.  Saving and reloading refreshes the display, which means the tiles were properly marked as "revealed" in the appropriate dataset  Often, sending a subsequent explorer nearby will start filling in the display when the second explorer comes close.  It looks like the second explorer has this sudden invisible magic sensor range that comes into effect.  It would be a clever trick if it were done on purpose.

To my knowledge, no one has successfully duplicated the behavior from a save game because, although it may be all too frequent, it is actually quite erratic.  Stardock has said they cannot produce the bug on their systems.  My conclusion is they need to play more and work less.    With some luck and some practice from a career of being an escalated trouble shooting resource, I managed to actually repeat it quite reliably.  The real trick was catching it on the first turn of the auto path.  I even took the save file to a second machine with a separate Steam account and a second copy of GalCiv, and it did the same thing.  In my career of being everybody's resource when they couldn't solve their tricky problems, intermittent issues were the worst.  Many a time I would have done many an evil thing to get my hands on a repeatable symptom.  I only hope this is that kind of clue, and that Stardock can make use of it.  Stomp those bugs!

If you are really curious, or bored waiting for Crusades, here is the dropbox of the files I sent to Stardock.  It seems that everyone has seen the problem first hand, but if you want, why not?  

Well put. This is all true to my experience of this bug as well.

My observations with regard to skipping explored space are it seems to only happen on big maps when the computer is being heavily stressed. I will have explorer ships with high speed and they will go from point A to point C, and not explore point B inbetween.

This problem is still appearing on Crusades.

This problem still has not been fixed. It is showing up on 2.5.

Yes, I've noticed this as well.