Torque 3D Status - 6/30/2010

#81 We need a Torque version of this:
developer.valvesoftware.com/wiki/Valve_Time

#82

Quote:We need a Torque version of this:
developer.valvesoftware.com/wiki/Valve_Time

That also happens to be the time zone I use for my game project ;)

#83 Glad to see this thread.

I know there was a previous thread containing updates that the community thought needed addressed the most. Can't find it, and I've a meeting in 3

I chimed in on the camera. Can we get a sneek peek at some of the camera changes/fixes being addressed? Maybe some of the other smaller changes?

Thnks
J

#84 "J", are you talking about http://www.torquepowered.com/community/forums/viewthread/115787 ?

If so, nothing official ever came from that, nothing official that was reflected back to the community that is. I think it was more smoke a mirrors to get complainers to stop complaining, and look like busy work was being accomplished. Notice the date that was posted? That was started right after much forum discussion about being jerked around and lied to about T3D... And look where we are today? Much sunnier and nice isn't it?

Im glade to see TorquePowered is constantly proving the complainers wrong!
(Of course as soon as i post this we will be receiving the T3D update we all have been waiting for...)

Disclaimer: Perceived tone may seem more negative then intended

#85 I believe the purpose of that thread was to produce an easy to access index of issues for the newly-formed (at the time) QA team to sort through. Many of the posts linked by users in that thread were subsequently officially "tagged" by the QA team, which, while not an especially transparent process, at least suggests that someone has marked them for some level of internal assessment. Previously, bug reporting was a sort of hit-and-miss matter of getting the attention of the dev team and hoping they were logging the issues, so I feel like there has actually been improvement here (assuming these QA-tagged issues actually result in solutions).

If you have specific bug reports that haven't been tagged by either a dev or QA team member, I'd suggest bumping them or posting a new thread, as the QA team seems to still be doing forum sweeps for issues.

I've vented my own frustrations with the 1.1 cycle just like many others, but I'm also aware that moving to working with a full internal QA team can really change things up for a dev team. I expect that we would have seen B2 long ago had the official QA system not been thrown into the mix, but I also believe we'll be seeing a far cleaner release this time than we would have. It shouldn't really ever have been the job of the core dev team to scan the forums and index every bug report, as they have more critical matters to focus on.

Now, whether the middle of a beta cycle was the appropriate time to introduce significant changes to the dev process or not is another debate that might be worth having, but at this point it seems it would be in our best interest to focus on making sure the existing engine bugs have all been tagged.

#86 Please do not start bumping bug threads just for the sake of bumping them. That will only guarantee they get overlooked while bugs are being logged.

#87 I have to agree with Henry, both iTGB and TX went through the QA cycle, while it did slow things down, especially it seemed with iTGB they both really came out better than an other previous release of the respective products.

Believe me I feel the pain, I use 3 Torque products all going through updates. It has been really frustrating as I have clients I am using these for. While it has been frustrating it has also been worth it.

#88 Yes, it is just very hard to exercise patients with my free time trickling down to a mere 2 weeks left, and T3D is continually delayed. I expected to be spending my time plugging the components of my project together. Not harping about such stupid crap.


@Scott: What is the best way to bring attention to old overlooked bug postings? Not that i have any, but just for information sake.

#89 I think the best way to do that would be to use the Submit Bugs form on the site which is under Support. That will ensure myself and others see it. That way bugs won't be changing position while the interns are logging them.

#90 Sounds good Scott, thanks.

#91 Sorry, I have to admit I wasn't even aware that there was a Submit Bugs form. I'll keep that in mind in the future. I just came up with the bumping theory because I wasn't aware there was any other way to bring 6-month-old untagged issues to the surface without starting a redundant thread, which seems like an even worse strategy.

Might want to note the existence of that form in the official "how to submit torque 3D bugs" thread... it's over a year old and only refers to forum postings.

#92 If everyone used the Submit Bugs form, and did not make a post of some type in the forums, many redundant bug reports would flood the system, not to mention the missing support on bugs fellow community members may be able to help alleviate.

#93 Hrm...Im assuming it would be a fairly easy, for a short term fix, for us to catch the submission, send it to a table, and then provide a simple look-up. I hate to brainstorm in the forums, but I'll look into this.

#94 I was working more to the assumption that using the Submit Bugs form option is primarily a means to catch all the older overlooked bugs. Once the next T3D is out, all old bugs that (may) persisted would become NEW bugs, and the system that have been in place for years now would still be efficient and refreshed upto date with the new QA process.

#95 I want an associates t-shirt that only says "Forum #45". :)

#96

#97 Torque 3D 1.1 Beta 3 is Released!