SE 3.9.4: Problems setting a poly

[Anonymous]

Hello,

I was on my way writing a scenario under 3.9.4.

Wanted to add an "add station" VC to one side. This failed, I wasn´t able to set the poly. It always disappeared.

I remember that bug from an older ANW version. I thought this bug was eliminated.

Setting a poly worked when I created an "protect station" VC for the other side - here the poly was created properly.

But even here there was an inconveniance: In 3.6.2, on the moment of opening the VC dialogue, you see the poly you have set.

Not so in ANW 3.9.4.

It all worked perfectly in scen edit 3.6.X. I just have restarted writing the same scenario - in 3.6.2.

Any clue regarding the ANW 3.9.4 SE ?

[FreekS]

I've not seen this problem. But then I made all my scens in 3.6.3 SE version and then converted at the end to 3.9.4.

Freek

[Anonymous]

ORIGINAL: FreekS

I've not seen this problem. But then I made all my scens in 3.6.3 SE version and then converted at the end to 3.9.4.

Freek

Yes, works perfectly well in 3.6.X. This is an ANW SE bug which I thought had been resolved.

So nobody uses the ANW SE and obviously for good reasons. I see.

thx, Freek.

[rsharp@advancedgamin]

I've confirmed some odd behavior here. You can create a poly for the station or protection station VC fine. However, when modifying an existing victory condition of this type you first have to press Set Poly to view the existing poly.

Both victory conditions worked the same for me.

Thanks,

[Anonymous]

Hi Russell,

ORIGINAL: rsharp@advancedgamin

I've confirmed some odd behavior here. You can create a poly for the station or protection station VC fine. However, when modifying an existing victory condition of this type you first have to press Set Poly to view the existing poly.

Both victory conditions worked the same for me.

Thanks,

It is a brandnew scen. I created a new poly and it never appeared when I opened the VC menue. The workaround works, yes: First clicking on "Set poly" displays the polys already set. Weird.

This is annoying. I simply cannot understand why bugs like this typical one ever could find their way in the code.

Will you repair that one for 3.10 release?

thx,
Ralf

[rsharp@advancedgamin]

Yes, though I probably shouldn't at this stage of development (waiting on packaging). Though annoying this is a cosmetic glitch.

Still, you've been even tempered and patient Ralf and so your request deserves time and respect.

Thanks,

[hermanhum]

I guess four years (or is it 16?) is just too short a waiting time for some bugs to be fixed.

AGSI's List of * Known Harpoon [ANW] Issues

[Anonymous]

Hi Russell,

ORIGINAL: rsharp@advancedgamin

Yes, though I probably shouldn't at this stage of development (waiting on packaging). Though annoying this is a cosmetic glitch.

I see. Yes, it is not game-stopping and not worth stopping the delivery process. Please note it for the next bug-fix.

ORIGINAL: rsharp@advancedgamin

Still, you've been even tempered and patient Ralf and so your request deserves time and respect.

Thanks,

Curious that one gets a compliment for simple correct behaviour No problem, you´re welcome.

Ralf