Incorrect Stealth - maybe just GUI
Moderator: Oberlus
Forum rules
Always mention the exact version of FreeOrion you are testing.
When reporting an issue regarding the AI, if possible provide the relevant AI log file and a save game file that demonstrates the issue.
Always mention the exact version of FreeOrion you are testing.
When reporting an issue regarding the AI, if possible provide the relevant AI log file and a save game file that demonstrates the issue.
Incorrect Stealth - maybe just GUI
as per heading
b
b
Re: Incorrect Stealth - maybe just GUI
Welcome to the most annoying and confusing part of flux stealth (and stealth in general). So meter growth (e.g. PP change, troop growth, stealth changes etc.) happens towards the end of turn processing. It happens after movement and combat. Currently that ship is 0 stealth and if it hits an enemy it will be 0 stealth, as the combat occurs before its stealth meter updates to 5.
This makes the timing of movement, stopping and combat fairly important. For instance mine are 35 at max. stealth and a dyson is 30 detection. I can move into a dyson as my stealth will be 35 on arrival. The dyson will still blockade and stopping drops the stealth to 5, so it'll become visible and I can not remain stationary on the dyson. Likewise when my flux ships attacked you at Na Atibu they arrived with 35 stealth and you were unable to see them in the 1st round of combat. This occurred even though they were set to initiate combat, as the stealth meter had not yet updated.
This makes the timing of movement, stopping and combat fairly important. For instance mine are 35 at max. stealth and a dyson is 30 detection. I can move into a dyson as my stealth will be 35 on arrival. The dyson will still blockade and stopping drops the stealth to 5, so it'll become visible and I can not remain stationary on the dyson. Likewise when my flux ships attacked you at Na Atibu they arrived with 35 stealth and you were unable to see them in the 1st round of combat. This occurred even though they were set to initiate combat, as the stealth meter had not yet updated.
Re: Incorrect Stealth - maybe just GUI
30 is their detection range. What is their detection strength? You say 30, but how do you know that?
viewtopic.php?f=6&t=12598&p=114369&sid= ... c0#p114369
I saw that
1) If you arrived with initiate combat, then I should be able to detect you first round.
2) if you were stting there already and then initiated combat, then I feel its fair enough that I dont detect you first round.
Re: Incorrect Stealth - maybe just GUI
I meant that for monsters range and strength are the same value. Range is 30? Strength is 30.
And that's why it makes no sense to put a second icon in monsters: both will show the same number.
Re: Incorrect Stealth - maybe just GUI
I don't necessarily agree (or disagree) but I'll bring up the larger issue which has been around for ever. When an attack ship moves into an ion storm and hits you it is not stealthed. When an attack ship jumps you by moving from an ion storm to outside the ion storm it is stealthed.
Re: Incorrect Stealth - maybe just GUI
regarding the OP, there are multiple issues.
0)
flux stealth is complicated, brittle and needs a while to master. i like it
1)
the way that stealth is subject to the +1 turn delay as all meter effects are as wobbly commented - which is often so surprising that it is "broken" in a way (e.g. the ion storm effect). to fix this we would need some kind of pre-movement effect application.
2)
what is the UI showing? the fleet UI sais it has 0 stealth, but the mouse over sais it is 5. (i think the mouse over gives the projected stealth value?)
daybreak, is that a newly build ship or an existing one?
3)
we have multiple visibility updates during turn processing, so stealth, detection, and turn processing interact (e.g. sitrep from a ship arrival in a system, which gets invisible "at the same moment" because the system provides some stealth to it)
0)
flux stealth is complicated, brittle and needs a while to master. i like it
1)
the way that stealth is subject to the +1 turn delay as all meter effects are as wobbly commented - which is often so surprising that it is "broken" in a way (e.g. the ion storm effect). to fix this we would need some kind of pre-movement effect application.
2)
what is the UI showing? the fleet UI sais it has 0 stealth, but the mouse over sais it is 5. (i think the mouse over gives the projected stealth value?)
daybreak, is that a newly build ship or an existing one?
3)
we have multiple visibility updates during turn processing, so stealth, detection, and turn processing interact (e.g. sitrep from a ship arrival in a system, which gets invisible "at the same moment" because the system provides some stealth to it)
Any code or patches in anything posted here is released under the CC and GPL licences in use for the FO project.
Look, ma... four combat bouts!
Look, ma... four combat bouts!
Re: Incorrect Stealth - maybe just GUI
True - but it creates confusion.
If we have a second icon, then -
1. No confusion for ships, monsters or planets.
2. At some stage if it is decided that range does not equal strength for monsters, then simple to change.
3. Would also allow us to have variety for Detection strength for ships and planets, instead of one Empire detection strength.
Anyway - not going to pursue this.
However Pedia should be updated for Monsters. The pedia on a Dyson forest has nothing about Detection strength.
Existing ship for a number of turns.
image above was when I arrived athe system
This image is becuase I am sitting there, so flux interference comes into play.
b
Re: Incorrect Stealth - maybe just GUI
+1, should be shown in pedia for each monster, or at least mentioned. Preferrably done in generic monster text template. Could you pleas open an UI issue for that?
so the image is correct after a turn sitting? The original UI is still weird - that is not like it supposed to be in my opinion.
The flux interference malus was already there when you arrived, so it should have been in effects accounting, which is used for generating those info lines about effects. (More precisely, the flux interference effect happened after your movement and the effects accounting should have shown that).
I was weary that it could be wrong because it shows the next-turn prediction, but that should also have included flux interference.
Any code or patches in anything posted here is released under the CC and GPL licences in use for the FO project.
Look, ma... four combat bouts!
Look, ma... four combat bouts!
Re: Incorrect Stealth - maybe just GUI
Unfortunately I don't know how to do that.
so the image is correct after a turn sitting? The original UI is still weird - that is not like it supposed to be in my opinion.
The flux interference malus was already there when you arrived, so it should have been in effects accounting, which is used for generating those info lines about effects. (More precisely, the flux interference effect happened after your movement and the effects accounting should have shown that).
I was wary that it could be wrong because it shows the next-turn prediction, but that should also have included flux interference.
[/quote]
Yes, so in laymen terms, the original image showing zero stealth is correct and just the hover does not show the flux interference malus of 30.
Re: Incorrect Stealth - maybe just GUI
Had not thought of that
Original Image
Just switched from non - agression to agression before landing. That image was taken that turn after landing
Second image
Been sitting there for awhile in Agression mode.
Edit - your post disappeared Wobbly
Original Image
Just switched from non - agression to agression before landing. That image was taken that turn after landing
Second image
Been sitting there for awhile in Agression mode.
Edit - your post disappeared Wobbly
Re: Incorrect Stealth - maybe just GUI
Yeah I deleted. Didn't realize you'd already read it. Pretty sure my post was wrong anyway, as it'd show more then +15 for the hull.