Bug-Fix-Only-Version of T3D Pro - RESOLVED

#1 for steve: Abracadabraalakazam

@Thomas i'm pretty sure somebody posted it would be completed about a month after 1.2.

#2 We are almost finished with it.

#3 Bloodknight's correct, we stated it would be 30 days after the release of 1.2, and as Mich said it's almost finished.

#4 The 1.2 Bugfix Patch for 1.1 is now available for download from your products page.

#5 Scott, it's not showing in my products, nor on the studio page.

#6 We hooked it up to the 1.1 Individual and Studio products only, so if you have 1.2 then you won't see it.

#7 So does this mean I am not able to get the 1.1 bugfix patch because I upgraded to 1.2?

#8 There are people who have upgraded to 1.2 that are still working on 1.1 projects, adding the patch to the 'previous versions' section seems a reasonable thing to do.

I'm glad i didnt upgrade all my licenses :)

Which makes me wonder, do people who just bought 1.2 actually get previous versions?

#9 Hey Bloodknight, We do get previous versions, but i was very surprised to see that it was not availible there. Dosnt really matter to me im using 1.2 but its the fact that I may need 1.1 at some point and would perfer the bug fixed version.

#10 When we pushed it yesterday it didn't really make sense to attach to 1.2 since, in theory, those users would already have it from upgrading. I received enough requests for it from people still finishing off 1.1 based projects so I'll have Matt add it to 1.2 Previous Versions.

#11 Matt has gone ahead and made the patch file available under the previous version section for Torque 1.2 owners. Thanks for the feedback!

#12 Thanks a lot guys!

#13

Quote:The 1.2 Bugfix Patch for 1.1 is now available for download from your products page.

I love you.

#14 I'm still not seeing this on my Products page. Am I missing something?

#15 @Kevin
It's not a separate product, just another download in the downloads for Torque 3D Professional which you can access from your product page.

#16 Ok, found it. (Duh!)

Thanks, Scott.

#17 No worries, looking back at my post I can see how one could end up looking in the wrong place for it as I was a little vague. A side effect of a hectic end of the year week and being in "kick this mother out the door mode" at the time. :)