Is the next TGB patch coming anytime soon ?

#21 It has been for almost 4 versions of TGB 1.5 (including betas) that the very same grave issues are persisting for me (camera jittery mounting...).
I would retain my congratulation until I see this fixed for good.

#22 @Benjamin: Maybe that would be a good second question for Ask GarageGames?

--clint

#23 QA is taking a lot of time it seems. I dearly hope they didn't added any new features other than bugfixes to this version.

#24 Nope, actually the delay is due to the fact we're working on a potential camera jitter fix that we really want to get into the release. So once we get a possible fix we need to personally test it, then push it to QA to test it with the rest of the build. Would rather spend more time on QA than less :)

#25 Thank you for the update Matthew. Can you comment on possible fixes for the particle system (problems with the system destroying the files, particle collision does not work in 1.5.1). Thank you!!

#26 Unfortunately nothing good to say about the particle destroying the files, we've had a hard time tracking that down. I'll bring it up though, while we are waiting to get another fix in there, no promises though. As far as particle collisions, I didn't know there was an issue currently with that, I wrote it down and will confirm it and ensure it's filed if it isn't already. Thanks for the feedback.

#27 Hm, I posted it here: http://www.garagegames.com/mg/forums/result.thread.php?qt=65685 - not in an own thread though. Does it make sense to do that now?

#28 @Christian
The temporary solution is to backup your .eff files between each particle saving.

#29 Thank you Benjamin. For me the bug in the particle collisions is more severe since I cannot find a workaround to get it working at all.

#30

Quote:Right now there's not much information on Torque 2. But the keynotes and Q/A session reiterated that if you are working on a project in the next 6-9 months, use existing tech. Torque 2 is for your next project, not the one you are working on now.

Lol, I'm still using TGB 1.1.3 for my current project! :P

To Garage Games:

Glad to hear you guys are still working on TGB! I don't care when it comes out! (As long as it does . . .)

[edit]

I guess GG doesn't do the whole [quote=Person X] thing!
The quote is from David Blake, near the top.

#31 Regarding the Particle bugs. We did find a problem where in certain situations the particle emitters were trying to divide by zero which has the potential to corrupt memory. This issue has been fixed.

I cannot say whether this will fix the particle file corruption problems some people have reported. We were never able to reproduce that bug.

One thing to note about this fix is that the divide by zero is actually a user error. This fix will catch the error, but it will prevent particles from appearing. So in the new version, if your particles are not displaying at all you need to edit the graph fields for particle life time base and variation.

In particular, you should be very careful that a particles lifetime can never be zero. The easy fix for this is to make sure the BASE minimum value for particle lifetime doesn't read 0 in the graph editor.

#32 I'm quite certain the lifetime thing isn't what I was seeing with the corrupted particle files, but there's of course the potential it might have been...
I'll test out the new version when it's released/when I get a chance.

#33 What about the particle collision bug? Have you been able to solve it? In my opinion particles collisions do not work at all in 1.5.1 :-(

#34 I posted another potential problem here with sample effect here:

www.garagegames.com/mg/forums/result.thread.php?qt=69459

This happens a lot to me too. What I usually do is to create the effect again and normally it works.

#35 Posted: Nov 03, 2007 05:43
The next version (fixing some issues) of TGB is currently being processed through QA.

It's Dec 06, and is it still hold by QA? The efficiency is really low as I saw, maybe a hotfix first?

Sorry to mention this again, but what happened actually?

#36 It's actually been pushed out of QA and then we've pushed a couple additional builds into QA with further fixes and additions. We are trying to create a process in which we don't want to push to QA at the last moment, rather they get ahold of it sooner and find issues sooner and while we change things. The last big pass on it has finished and we have only a minor pass to ensure nothing blows up based on a minor installer configuration change :) We had mentioned we wanted more transparency so hopefully this will give you a bit of insight into the development process we are trying to create.

#37 Cool! Thanks for the update Matthew!

#38 Yes, transparency is good. I hereby award you the Alpha Channel Award. Looking forward to the update.

#39 Any ideas of when its gona be released then?... cuz, sorry if i sound rude, but all that sounds cool and all, but we need dates!... there are certain bugs that are killin me, and since probably most of them are gonna be fixed on the next release, im SO waiting for it...

#40 So... it is a smarter choice to wait for the next release instead of trying to fix several bugs?