FAZ Beta Wednesday - January 18th

ThePhantom032 · Post by **ThePhantom032** » Tue Jan 17, 2012 5:47 pm

more tests.

he3 vision seemed to work without failure. I am very pleased. Not explaining the detailed tests cause for some reason I'm writing this part last and still put it on top.

test about rock vision

1) both teams scout the rock
2) blue loses eye on it
3) yellow build base with uneyed con. blue sees particles while the con enters the rock (if you zoom in on it enough, which you wont if you dont see the con), but no buildsphere. The rock does NOT disappear. YEEHAW.
4) blue eyes the rock again (the rock, not the base): the rock disappears. Clever people will see this and guess there might be a base there now.
5) blue eyes the base, the base is visible.

All is good (for the normal testcase).

Things that need to be tested:
a) what happens if base destroyed between 3 and 4. what between 4 and 5.
b) what happens if base captured by a third party between 3 and 4 (4 and 5).
c) what happens if 5 happens before 4 (high sig base on low sig rock (IIRc dreg he3 mines are an example))
d) what do you see if 1 never happens but you see the con planting (he3 mine again)
e) what do you see if in 3 you see the con without seeing the rock (he3 mine again)
f) what do you see if you see the rock (2 never happens), but you do not see the con.

tell me if you can think of more.

general allied vision tests (noone plays allied games anyway so I would test these last unless someone wants to hold an allied zonegame on beta):

Do allies share vision on rocks (pretty much all the rock vision tests just let allies scout it)
What about allied-shared he3 vision?
What about allied shared minimap vision? (there used to be problems with that and I do not remember them being fixed)

Help with testing all of these would be appreciated, as it takes quite a while to set a single test up.
And my computer can only run like 8 copies of alleg at a time without getting noticeably slow, even if i could manage to keep track of which Alleg is doing what (which I dont once its more than 4).

TheDevil · Post by **TheDevil** » Wed Jan 18, 2012 5:34 pm

Makida · Post by **Makida** » Wed Jan 18, 2012 6:45 pm

Two potential problems I saw today in testing R6 -- I'm not sure if these were brought up before to be honest.

1) While an asteroid that the enemy team has built a base on won't disappear on your command map until you have something in that sector, an asteroid that the enemy team kills (e.g. with seismic missiles) *will* disappear, even if you have nothing in the sector to eye it. The explosion and the asteroid's disappearance will be visible on F3 from base. Not sure if this is a problem, really, considering how rarely asteroid-killing is actually done, but still.

2) The "dock" option on F6 does not work properly if you are not viewing the sector the drone is in through F3. Tried this with a carrier and a miner, and another player tried it with a con. While docked in base, I viewed a sector different from the one my drone was in in F3. I brought up F6, right clicked the drone, and gave the dock (or "dock/flee" for the carrier) order. Then I switched to looking at the sector the drone was in. Basically, it looks like all this did is cancel whatever the drone was currently doing. When I did this to the carrier, it just sat in place motionless, without trying to flee to a base or dock or anything. When I gave this order to a miner, it started to mine instead (previously I had ordered it to go to some random waypoint in the sector; it seems to have "forgotten" this order as soon as I gave it the dock command through F6, and just started doing whatever it would normally do at that point without any orders at all). I tried doing this again when the miner was mining at a rock, and it seems it stopped mining for a moment, then started again. So it looks like if you aren't actually looking at the drone in F3, the new "dock" command merely makes the drone stop whatever it's doing, and "resets" its orders.

I haven't tried this when out of base, though, although I think someone on the other team did, and I *think* the same thing happened -- the drone doing nothing at all -- when they gave the order while OOB in another sector.

Post by **pkk** » Wed Jan 18, 2012 6:53 pm

girlyboy wrote:QUOTE (girlyboy @ Jan 18 2012, 07:45 PM) 1) While an asteroid that the enemy team has built a base on won't disappear on your command map until you have something in that sector, an asteroid that the enemy team kills (e.g. with seismic missiles) *will* disappear, even if you have nothing in the sector to eye it. The explosion and the asteroid's disappearance will be visible on F3 from base. Not sure if this is a problem, really, considering how rarely asteroid-killing is actually done, but still.

http://trac.alleg.net/ticket/254

girlyboy wrote:QUOTE (girlyboy @ Jan 18 2012, 07:45 PM) 2) The "dock" option on F6 does not work properly if you are not viewing the sector the drone is in through F3.

http://trac.alleg.net/ticket/253

Makida · Post by **Makida** » Wed Jan 18, 2012 7:07 pm

pkk wrote:QUOTE (pkk @ Jan 18 2012, 01:53 PM) http://trac.alleg.net/ticket/254

http://trac.alleg.net/ticket/253

Thank you.

Spunkmeyer · Post by **Spunkmeyer** » Thu Jan 19, 2012 12:55 am

Phantom032 wrote:QUOTE (Phantom032 @ Jan 17 2012, 11:47 AM) d) what do you see if 1 never happens but you see the con planting (he3 mine again)

We just tested this and it works fine. Con disappears when building (becomes part of the rock I guess) which makes sense in that context.

By extension, I believe e) is the same scenario.

We also tested c) I think - the rock is never shown.

Stone · Post by **Stone** » Thu Jan 19, 2012 1:09 am

I'm striking out on the beta mode. I've installed the 2 other items, switched to BETA mode and updated the files. However, it keeps saying that the allegiance.exe is invalid and asks if I want to re-downloaded/fix it.

I have even re-installed several times, just in case. Clearly, I've done something wrong in the process, but I can't pinpoint it. (It's likley Win 7 x64 related, isn't it?)

Is there app/debug logs that I can look into?

Post by **FreeBeer** » Thu Jan 19, 2012 1:37 am

Have you used the "fix/update" option found in the ASGS menu?

Stone · Post by **Stone** » Thu Jan 19, 2012 1:40 am

FreeBeer wrote:QUOTE (FreeBeer @ Jan 18 2012, 09:37 PM) Have you used the "fix/update" option found in the ASGS menu?

Yea.. Tried after switching to beta, like the instructions said. Also reinstalled and tried fix/updating, then switching to beta mode, then fix/updating again.

Post by **FreeBeer** » Thu Jan 19, 2012 1:42 am

Try running the installer with Admin privileges. I have Win 7 64-bit and had no issues, myself, but sometimes permissions can be a little funky and tricky to diagnose.