new face cam in AW 3.4 (Community)

new face cam in AW 3.4 // Community

1  2  3  |  

anarkissed

Nov 18, 2002, 4:43pm
Why do people keep whining about this? We just got all these nifty new
features last spring with the multi-axis rotations, terrain (WOW) and so
forth. Lots of new fun things we're still playing with. Coronas are a
blast!
Most people really don't seem to know anything about a beta and don't give a
flying watoosi either. They're happily building away, often with those same
tired old 2.2 objects, chatting, sharing and having a fine time. Those who
didn't want to pay more went away to sister universes where they don't have
to, we who chose to stick around for whatever reason (why am I still here?
LOL) are enjoying the benefits of 3.3. I for one, prefer if they get that
beta snap-snip ship-shape perfect. I don't need to be crashing constantly
and downloading updates and patches just because some spoiled modern people
have to have every new thing yesterday.
If you think it's so easy, go build your own 3d universe!


[View Quote]

coryashire

Nov 18, 2002, 7:32pm
to technozues,

if you read lower into my post i state lagitamate reason why they should
release it including halt the additioon of more features and do a final comb
through for bugs then release, the point is that if they want to keep people
interested in there product they need to be giving us new material to work
with, it easy for you to take there side because your on beta and you get to
experince what was promised to us, but we are still waiting and we hear
nothing as to why we dont have 3.4.1 or 3.4.2 as was promised to the
community by the development team.

as for anarkissed, you need to remeber that most of the new features in
3.3 required a world to use, while they added to the overall effect of
creating virtual world, if you dont have a world you cant use them, i hope
eventually they through out registrys and make it automatic based on the
objects details then we could all have rotate and move commands then those
commands would be more useable by the average person. as for me being
spoiled, i think you need to think outside of your little box to see that
the most important factor in running a successfull biz is to give your users
what they want, sure we want new features, and new worlds, and new building
objects, but when we are told that we would be receving these ina certain
timeframe to see that thrown aout with out any response from awcom to the
non beta community on the new plan then they are doing something bad, they
are ignoring there user base.

thats why i say stop the addidtion of enw features and comb through the
program and search and destory bugs and bgive it to us, the paying
coustomers. take all those new features that you didnt add in and make say
3.4.2 like promised or make it in 3.5, we are paying alot more for this
program with the promise of a speedyer development, and while its nice that
we now get 2-3 new version a year as opossed to 0-1 a year, dont forget us
and how we matter in the success of your program and compony.

coryashire



[View Quote]

technozeus

Nov 19, 2002, 1:49am
Actually, I did read your entire post, and I know you do have a point, but you are missing something. Weather I was on the beta or not I wold feel the same way about it. I know this because I have been on the beta team and off the beta team many times over the years and my position on this has always been that the beta testers are not "getting" something extra but rather "giving" something extra. We all get something better because the beta testers were willing to work hard to help the developers do a better job in a shorter time. Sure they could go with short development cycles, and the two main advantages would be ease in locating the cause of most bugs and having something to show for it more frequently. There are also advantages to a longer development cycle. For example, elaborate additions simply can't be added quickly, so a short cycle would mean almost nothing really "great" could ever be added. Also, a longer development cycle generally means more multitasking so more can get done in the same period of time. Instead of one small new feature every month, you end up with a whole lot of small new features and a few big new features after several months. Believe me, I do understand your feelings about wanting to see something new. Even being on the beta team, I pretty much feel like begging for the alpha version to get pushed into beta... but more so that we can begin helping to get it ready for release than just to see it. Also, although I have expressed my opinion on the matter, I do feel that "pushing it ahead" too early would be a bad decision... so I'm trying to do my best to test the current beta version as thoroughly as I can in the hopes that my efforts will help pave the way for the next beta build, and I'm sure most of the other beta testers are doing the same thing. No one person can try everything possible with a piece of software this complex... it just can't be done... so the more testing we do, the less chance there is of bugs slipping through that only show themselves when someone tries something unusual.

Anyway, as I said... they were "very" close to release. It was not the developers who decided that certain features just couldn't wait. It was a few people complaining loudly and trying to make AW look bad, and the fact that so many people chose to stand behind them and and help turn the complaints of a few into an all out riot. A few people played terrorist and tried to start a public relations nightmare, and misinformed crowds gathered to back them up and help make them do their dammage. Now we live with the results, and those who were working hard to help get the beta finished up and released get to start over with a new beta and work even harder.

TechnoZeus

[View Quote]

e n z o

Nov 19, 2002, 12:06pm
Releasing a version means to do a research version then alpha then closed
beta then beta then release, following the release there are almost
certainly patches.

If we only add a few features to a version we end up repeating the entire
cycle many times over to get the same end result. In other words 3.4 done
the way it has been will take probably > 60% less time to final release than
doing 3.4 in bits and pieces. To add 1 feature into a beta version might
take 2 weeks, to add it after 3.4 is released would take a minimum of 5
weeks. It is frustrating, but since everyone insists on using different
hardware/software configurations that's the way it is. ;)

Sorry


E


[View Quote]

technozeus

Nov 19, 2002, 2:39pm
You worded that so much better than I did. Thanks E N Z O. :)
[View Quote]

1  2  3  |  
Awportals.com is a privately held community resource website dedicated to Active Worlds.
Copyright (c) Mark Randall 2006 - 2024. All Rights Reserved.
Awportals.com   ·   ProLibraries Live   ·   Twitter   ·   LinkedIn