Phoenix 2.5 Update - News

[SadSack]

Luckily there always someone willing to pre-release anything
Anyhow getting a private beta is great..see nearly all new features. Most of the time beta testing is a final product but people are odd and do something different and say its a pile of poo update when perhaps they don't really understand what the hell there doing IE Thick

BTW this is aimed at non-beta testers in general

[Mart61]

Wonder how long it'll take to be released. Anyone have experience of how long the last major release took from announcement to available?

[GravityKills]

...Seems like a very harsh post to me.

Of course, you may disagree with me. All I want to do is fly.What annoys me is when the beta turns into the de-facto product. You're effectively forced to use it, since nobody in multiplayer uses the old version. I did not like it very much how it was handled in 2.00. And, a lot of multiplayer bugs got never fixed. I wasn't serious about paying me for beta testing. Instead, the point was this: When they release a beta, it should be *reasonably* tested and useable before it's released to the public. I don't know how much sense it makes to quote Microsoft for comparison in software quality. But what I do know is that 99 % of all "segfault"-like errors on my PC come from Phoenix. No, what I'm asking for is that the developer does his homework, runs a proper test cycle and testing tools before a release (I'm a UNIX guy, not Windows, but for example Linux "valgrind" comes as close to a magic bullet as you can get for free). Then, as beta tester, I'll get the occasional "assertion failed at line 12345 in physics.h". That's OK - I can tell them what led to the error and they have a good chance at fixing it. But the current situation (example from the production version) is more like "there's a 30 % chance that it segfaults when it has to change scenery on entering a multiplayer session". And, harsh post or not, here I feel that my time gets wasted.

[GravityKills]

PS sorry for the formatting mess in the post above. The more I edit, the worse it gets.Oh well must be a windows bug... I'll go flying :-)

[dogg5306]

Don't you think that new models are needed?

I know that it won't change the sim high level of quality... but it would be nice to have some Hirobos (after all they were on the podium of the last 3D masters editions)...

[Boggy]

Don't you think that new models are needed?

.

there are some in the update.


Align T-Rex 250
__ • Rave 450
__ • Outrage G5
__ • Outrage G550
__ • Protos 500
__ • Huey UH-1H "Iroquois"

[Holst]

there are some in the update.


Align T-Rex 250
__ • Rave 450
__ • Outrage G5
__ • Outrage G550
__ • Protos 500
__ • Huey UH-1H "Iroquois"

Thats quite a good start.

I like the look of the protos so it will be interesting to try it in phoenix

[dogg5306]

None of my helis are considered as Phoenix models
There's no chance in this world to convert me to the Align religion... not a chance!!!

[andylinney]

None of my helis are considered as Phoenix models
There's no chance in this world to convert me to the Align religion... not a chance!!!

well, follow the instructions on the site and submit the pictures so we can all see how well the new Hirobo flies...

[dogg5306]

Well, it is more complex that it looks...

[andylinney]

Well, it is more complex that it looks...

Have a nose here, they need about 15 photos...


I guess if you want your models to appear then it's the most direct route to getting it done.

[Flying Elvis]

Phoenix Rc 2.5 beta You tube video!!!

Hi all,
I've just seen this on You Tube. It's some video of Phoenix Rc 2.5 (Beta). The blades of the Trex 450 really do look different. Anyway check it out for yourself.

[ame=http://www.youtube.com/watch?v=xtmOM2XmIY4]YouTube - Phoenix RC - Trex 450 - Like This LIke That[/ame]

[trvo]

Just a quick note to add... whilst there may be bugs in Phoenix, the testers do not have access to every single OS, software configuration, hardware configuration etc that exists so it is impossible to catch every single bug no matter how large your beta test team is.

Trev

[TheLawyer]

Just a quick note to add... whilst there may be bugs in Phoenix, the testers do not have access to every single OS, software configuration, hardware configuration etc that exists so it is impossible to catch every single bug no matter how large your beta test team is.

Trev

I want to add something to that, if someone notices an bug or error of some kind, try to mail it to the developers at phoenix, maybe you're even contributing to the game this way

[GravityKills]

Just a quick note to add... whilst there may be bugs in Phoenix, the testers do not have access to every single OS, software configuration, hardware configuration etc that exists so it is impossible to catch every single bug no matter how large your beta test team is.

Trev

erm it seems to be possible, as an example take just about any other PC game with multiplayer.
of course, if I insist on using for example home-grown GUI code instead of standard components...