FAZ Beta R5 Known Issues

Dorjan · Post by **Dorjan** » Sun Nov 30, 2008 7:11 pm

R5 issue. With alliance on you cannot lock onto enemies with missiles.

Post by **FreeBeer** » Sun Nov 30, 2008 9:52 pm

Myotis wrote:QUOTE (Myotis @ Nov 30 2008, 03:06 PM) Ok.. installed the Artwork files, and running normal resolutions 800x600 @60hz AtiRadeon600 XPsp2

I can make a game, I can even start up the game.. but after I launch, at the point it should change from the launch animation to the cockpit view it crashes. Allegiance exited with code: x5c9b035fed62d487

Had that problem, too. I resolved it by adding the additional artwork files (I, too, thought I had them, but obviously I was wrong.) file: R5beta_artworkdevfolder.zip

Dogbones · Post by **Dogbones** » Mon Dec 01, 2008 12:19 am

Dorjan wrote:QUOTE (Dorjan @ Nov 30 2008, 02:11 PM) R5 issue. With alliance on you cannot lock onto enemies with missiles.

Logic error found and fixed (pending testing). Thanks for finding this. Just shows people really have not been playing the beta much at all. KGJV and I have launched small 3 player games on our local servers and tested weapons fire and such but I guess we either never launched missiles or noticed the lock problem.

I will update the beta, hopefully this evening.

Dog

finnbryant · Post by **finnbryant** » Mon Dec 01, 2008 1:03 am

you're right about people not playing the beta

at the moment I can't play on windows and ive been logging onto the beta servers in ubuntu every few days hoping someone might be there, i've yet to find another player.

Dorjan · Post by **Dorjan** » Mon Dec 01, 2008 11:03 am

I'm arranging events to try to get the alliance code tested. It's going to be a big thing for events and so I think it's my duty to get it done!

Finn, i'll add you to the mail list for people to come to the events on beta

Andon · Post by **Andon** » Mon Dec 01, 2008 11:37 pm

My controller doesn't register with the beta.

It is an X-box controller connected to a USB hub (That has an X-box controller port) connected to the computer, and I am using xbcd (I can't find a version number for it).

The game pad works fine with R4, but it does not work with R5

Dogbones · Post by **Dogbones** » Tue Dec 02, 2008 4:01 am

That is very odd Andon because as far as I know only the graphics DirectX calls were modified, the other DirectX interfaces were not touched. I'll ask about this in the dev forum.

Andon · Post by **Andon** » Tue Dec 02, 2008 5:18 am

at first I thought that something had come loose (not entirely uncommon), so I didn't worry about it.

Today, though, right before I posted, I started a regular game, tried it and it worked, then went to a beta game and it didn't work. After that I went to a regular game again and it still worked there

finnbryant · Post by **finnbryant** » Tue Dec 02, 2008 2:16 pm

Thanks dorjan, i didn't even know such a list existed!

I'll look forward to the next one.

TurkeyXIII · Post by **TurkeyXIII** » Mon Jan 05, 2009 4:29 am

parcival wrote:QUOTE (parcival @ Oct 12 2008, 08:12 AM) It still crushes (new R5) after some flying time with "Allegiance exited with code: x5c9b035fed62d487".

This with 08.11.22

NVIDIA GeForce 7600 GS
Various display settings and cores. I can't tie it to a specific event or anything either.