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

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.

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

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

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

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.

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

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, reloading the game exposes the "unexplored" space each and every time for me also.

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?  

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.

This problem is still appearing on Crusades.

Yes, I've noticed this as well.