Game Development Community

Torque Constructor 1.03 is up

by Kenneth Holst · in Constructor · 08/02/2007 (3:19 pm) · 26 replies

Matt Fairfax will be along when he gets a chance to describe the changes/fixes, but I wanted to let you know it is up in your my account page now.
Page «Previous 1 2
#1
08/02/2007 (3:27 pm)
NICE, Thanks Ken
#2
08/02/2007 (4:08 pm)
Thank Ken, again... you rock! So does Matt!
#3
08/02/2007 (5:25 pm)
Thanks!
#4
08/02/2007 (7:29 pm)
Will it still say 1.0.2
#5
08/02/2007 (8:39 pm)
So 1.0.3 constructor is up officially?
#6
08/03/2007 (4:06 am)
Works great. Thanks.
#7
08/03/2007 (4:10 am)
Thanks for the update. If it still says 1.0.2 when you install it, you have to uninstall the previous version and then install 1.0.3. At least that what I had to do.
#8
08/03/2007 (4:27 am)
I cannot get 1.03 registered, it does not recognize my registration number.
Mac version, using the exact same number listed for Constructor in my account page.

Any clues?
#9
08/03/2007 (11:01 am)
Gustavo, does it give you any sort of error message, or just tell you that the number is invalid? I will check your account and see if perhaps it has been disabled for some reason.
#10
08/03/2007 (2:21 pm)
I'm having the same issue as Gustavo, it won't accept my ignition key from my account page.

Here's a partial dump of the console.log

Loading compiled script constructor/defaultExportCfg.cs.
- Loading default scene ...
!!! Not a light entity
!!! Set entity internal property 'direction' to 0 0 0.558505
!!! Performing a registration check

--------- Initializing: Torque Creator ---------
Loading compiled script creator/editor/editor.cs.
Loading compiled script creator/editor/particleEditor.cs.
Loading compiled script creator/scripts/scriptDoc.cs.
Loading compiled script creator/ui/creatorProfiles.cs.
Loading compiled script creator/ui/InspectDlg.gui.
Loading compiled script creator/ui/InspectAddFieldDlg.gui.
Loading compiled script creator/ui/GuiEditorGui.gui.
Engine initialized...
Basic mouse capture enabled.
!!! DRM::registerProduct()
!!! Initial status: InvalidKey
Exporting prefs
creating path constructor/prefs.cs
Exporting config
creating path constructor/client/config.cs
Exporting client prefs
creating path common/client/prefs.cs
Exporting server prefs
creating path common/server/banlist.cs
MR::RemoveFromQueue(): Queue does not exist: MRQueue_PreferenceChange
Shutting down the OpenGL display device...
Cleaning up the display device...
Killing the texture manager...
Making sure the rendering context is not current...
Deleting the rendering context...
Destroying the window...
#11
08/03/2007 (3:01 pm)
Can you guys install to a fresh directory and check this? I have not run into it here as of yet. Also, will be looking into resetting your ignition keys and trying that. Hope to have this resolved for you asap.
#12
08/03/2007 (3:21 pm)
Hey Kenneth
I deinstalled, redownloaded, and installed to a different directory and got the same result.

The message says: The registration number you entered is not valid. Please re-enter your number.







P.S. just to clarify - I'm also using the OS X version.
#13
08/03/2007 (3:28 pm)
Ok, thanks for checking that out. Gustavo, are you on OSX as well?
#14
08/04/2007 (12:02 am)
Yes, OsX too here, in an intel Imac. Same message than Corey.
#15
08/04/2007 (1:52 pm)
There doesn't seem to be any support TGEA with this latest Construtor v1.0.3..... I was able to export my DIFs properly.. without error or problems..

But now, I get an error in TGEA saying that the DIFs are the "wrong version" or something. >:(
#16
08/05/2007 (10:09 am)
Andy, that will require TGEA 1.02 which is not quite out yet, but is on top priority to get out to you all.
#17
08/05/2007 (9:11 pm)
I, too, am having problems getting 1.0.3 installed/registered on OS X.
#18
08/06/2007 (8:50 am)
@ Andy and Ken..

Same here. In fact I think 1.0.3 will be useless to me until 1.0.2 TGEA arrives... dunno.


Where is that list/info of whats changed in 1.0.3? It was never posted.
#19
08/06/2007 (10:42 am)
Registration problem here too on Os X. :p
#20
08/06/2007 (10:51 am)
We have found the issue and are working on a resolution. Will let you all know in this thread as soon as we have it.

Sorry guys, and thanks for your patience!
Page «Previous 1 2