FAZ Beta R4 Known Issues

[aarmstrong]

QUOTE (apochboi @ Jul 12 2007, 04:27 AM) I use the beta pretty frequently for testing and such like, I've noticed one thing with the miners. If there is an enemy in one of my controlled sectors and my miner is in base, the miner will launch. *snip*

This is a major problem.

As Immort was referring to earlier, I was comming a game and one of our miners entered a conflict sector to dock at the OP (nothing wrong with that - same thing happens on R3). However, the miner continued to launch in said conflict sector even though no friendly ships were launching. I could understand this if our guys were launching, but they weren't. Not only that, but the miner went over to mine an HE rock and didn't start running even when it saw enemy ships / was under attack. He just planted his ass on an HE rock and continued to mine until he was dead. Now I didn't order it back to base, but I didn't tell it to mine either. So it should have at least started running when it was under attack.

This is a show-stopping AI bug that really makes it even more difficult to protect a miner in a conflict sector.

[lemon_pie]

I kinda need help with Gettign on R4 i use. i downloaded it and tried to run it, but said had a problem i shoudl re download it. i did it, but it still didnt work.

[apathos]

Just tonight, a player logged in with the name ":" (that's right, just a colon), and no one could type chat unless they prefaced it with a space and a :, or possibly just a :. Messed chat up for a minute or two till he was convinced to switch tags, then it worked just fine.

[terrenblade]

Turret fire in big ships appears to be offcenter by quite a bit, more noticable in cap ships then others. I'm using a NVIDIA card in hardware mode with 800*600*32 and I have a few highres textures if it matters. not just me, other people on my team noticed it as well.

[Grimmwolf_GB]

QUOTE (mcwarren4 @ Aug 2 2007, 01:02 AM) Edit - also, when I was boosting one time my ship kept boosting even through the reload. I liked the fuel perk but I'm guessing it was a bug =P

It happens in R3 already. I don't know the exact circumstances, but I had it happen to me as well.

[juckto]

I know the exact circumstances, and it's exploitable.

f7 minimap does not display during launch animation.
Ripcord countdown does not display when viewing f3.
Some panels on the f5 menu were see through. The GT Research station (or rather, since Noir changed all GT bases to be the same model, all of them). I dunno if this happens in R3 too, it may be a problem with the graphic used for that panel. piccie

Minor:
AllegianceTest always starts in full screen mode.
My graphics card is kinda crappy, and sometimes it cuts out blocks of graphics. This has been happening a long time, and I've gotten used to it. But in R4 it seems to happen more often, especially in f3, and to a far greater extent. It seems to only happen if I view f3 while flying though - from base it's fine.

Okay... this is $#@!ing odd. Did some more testing and it doesn't happen if I have a base, ship, nothing or an asteroid "targetted".
Pictures: With a waypoint selected. With nothing selected

[Dogbones]

QUOTE (juckto @ Aug 3 2007, 06:42 PM) AllegianceTest always starts in full screen mode.

ASGS launches allegiance.exe with the -windowed -nomovies command line options. If you want AllegianceTest.exe to start in a window make a shortcut to it, select properties for the shortcut, and add the -windowed command line option.

Not sure about the others, especially the graphics blocks one. You using any of the high res textures?

[juckto]

uhh, High res explosions. IIRC the other ones affected my framerate so I uninstalled them.

Turns out the f5 menu panels isn't R4 related.

[Ramaglor]

major crash....

1. Hit an allied ship right when going through an aleph.
2. Frame freezes immediately after the hit.
3. Check task manager...allegiance not responding and using 610 mbs of ram

4. Kill the process then try to rejoin..
5. 3 seconds in game, long enough to tell I'm 10,000 out of sector, and freezes again.
6. Task manager shows ~50% cpu usage and 280 mbs of ram (I do have dual core, but neither core was running at peak).

7. Repeat steps 4-6 (same task manager results)
8. check flying in R3.....just fine
9. Will try the test again.....
10. Same problem, but only 120 mbs of ram

I was able to fly this morning just fine.

Windows XP Pro
2.3Ghz X2
2 gbs Ram

[Kap]

Hmm Im constantly freezing for seconds while in the new beta, this didn't happened in previous versions and doesn't happen in normal alleg.