FreeOrion

Playing last master version (compiled) as of this morning.

One of my scouts arrived to a previously unexplored (a "?" system). Combat issued with a gysache cruiser and the scout was destroyed. I know it is a gysache cruiser from the combat report (that only said it attaced the scout, 5 dmg, and the scout was destroyed), because the map does not show any ship or ghost sensor.

@devs: Should I expect a ghost sensor in that system after de combat?

In case this is relevant, I have just exited the game and can pack up auto-saves before and after the combat and all logs.

Oberlus wrote:@devs: Should I expect a ghost sensor in that system after de combat?

Yes you should. That's something I've started to look into before, but I'm not sure if I got around to opening an Issue on it. Please check if there is already an Issue open on github, and if not make one for it and include a savegame from the turn right before combat if that is available (since part of the fix may need to include some changes to during-combat visibility granting, not just display issues on the client UI).

I'll do as you say (autosaves must be there still, didn't start FO again), but next monday 'cause I'm out of home till then.

Can't start FO now to check things out. I think you just need to load turn 21 and press next turn, but I'm unsure if the scout that will be killed is already en route from turn 20 or the command must be issued there. To find out which scout will die and in which system you can load turn 22 and check the sitreps for the only combat that happened then.

This is still happening. In my new game with up to date FO (compiled), different settings, the same happened, a Frigate Ms (no stealth techs) has killed a scout of mine but there is no ghost sensor in the system where the combat ensued, to which my scout was arriving this turn.

reminder:

Dilvish wrote:Please check if there is already an Issue open on github, and if not make one for it and include a savegame from the turn right before combat if that is available (since part of the fix may need to include some changes to during-combat visibility granting, not just display issues on the client UI).

Oberlus wrote:I'll do as you say... but next monday 'cause I'm out of home till then.

Oberlus wrote:This is still happening.

Posting here to double check about whether something should be considered a problem or not is fine and good even, but once it's clear that there is a programming bug, the best way to help advance it towards resolution is to check if there is an existing github issue and either add to that or if there was not yet one then create one. Some of our posters here are not yet really ready to tackle an extra interface like github, but I think you are active enough to take that on.

Oh, sorry, I forgot about the github part and just posted the saves in here. Fixed.