TGB 1.8 Bugs
by Orion the Hunter · in Torque Game Builder · 02/02/2013 (12:06 pm) · 49 replies
Hello,
I'm sure I'm not the first to see all the bugs that have been introduced in Torque Game Builder, 1.8. I think it would be great if the T2D legacy ended on a good note, but currently, I've seen a few problems with the engine recently. These may just be Mac specific, but here goes:
1. Annoying blue screen on startup. This isn't really a bug, but it sure "bugs" me. :P
2. Editor sometimes has button offset which causes problems. (For example, you might try to click on the "Y Coordinates" field and instead it will select the "X Coordinates" field.
3. GUI Editor and Level Editor save shortcuts no longer function.
4. F11 no longer closes the GUI Editor.
5. T2dScrollObject shows a weird white bar if it's moving and is about to repeat.
If anyone else finds more bugs, please list them here.
I'm sure I'm not the first to see all the bugs that have been introduced in Torque Game Builder, 1.8. I think it would be great if the T2D legacy ended on a good note, but currently, I've seen a few problems with the engine recently. These may just be Mac specific, but here goes:
1. Annoying blue screen on startup. This isn't really a bug, but it sure "bugs" me. :P
2. Editor sometimes has button offset which causes problems. (For example, you might try to click on the "Y Coordinates" field and instead it will select the "X Coordinates" field.
3. GUI Editor and Level Editor save shortcuts no longer function.
4. F11 no longer closes the GUI Editor.
5. T2dScrollObject shows a weird white bar if it's moving and is about to repeat.
If anyone else finds more bugs, please list them here.
#42
03/02/2013 (7:37 am)
@Harry - I actually wanted to investigate a couple of things reported in this thread and a nagging feeling I had about an OS X implementation. I'm now satisfied with what we have available and I will be uploading on Monday. 
#43
Anyway, the game exe that 1.8 makes in Windows will not recognize Intel HD 3000 graphics (at least on my machine). I have both 1.7.6 and 1.8 on here. 1.7.6 has no problems. This is the console file from the 1.8-built version:
I've updated my drivers. Downgraded my drivers to several older versions. Nothing is working.
By the way, my machine is an MBP running Win7-64.
03/02/2013 (5:29 pm)
I thought I had seen someone else having this problem, but now I can't find a thread/post about it.Anyway, the game exe that 1.8 makes in Windows will not recognize Intel HD 3000 graphics (at least on my machine). I have both 1.7.6 and 1.8 on here. 1.7.6 has no problems. This is the console file from the 1.8-built version:
//-------------------------- 3/2/2013 -- 18:08:05 -----
---------------------------------------------------------------------------------
Processor Initialization:
Intel Pentium III, ~2.40 Ghz
(timed at roughly 2.40 Ghz)
FPU detected
MMX detected
SSE detected
---------------------------------------------------------------------------------
Math Initialization:
Installing Standard C extensions
Installing Assembly extensions
Installing FPU extensions
Installing MMX extensions
Installing SSE extensions
---------------------------------------------------------------------------------
Input Initialization:
DirectInput enabled.
Loading compiled script C:/Users/Joe/Documents/MyGames/CFD/common/main.cs.
Loading compiled script C:/Users/Joe/Documents/MyGames/CFD/game/main.cs.
% - Initializing Common
Loading compiled script C:/Users/Joe/Documents/MyGames/CFD/common/preferences/defaultPrefs.cs.
Reading Display Device information...
Primary Display Device Found:
Vendor Id: VEN_8086
Device Id: DEV_0126
Using D3D rendering. Fullscreen: 0
Loading compiled script C:/Users/Joe/Documents/MyGames/CFD/common/gameScripts/xml.cs.
Loading compiled script C:/Users/Joe/Documents/MyGames/CFD/common/gameScripts/properties.cs.
Loading compiled script C:/Users/Joe/Documents/MyGames/CFD/common/gameScripts/common.cs.
Loading compiled script C:/Users/Joe/Documents/MyGames/CFD/common/gameScripts/audio.cs.
Loading compiled script C:/Users/Joe/Documents/MyGames/CFD/common/gameScripts/canvas.cs.
Loading compiled script C:/Users/Joe/Documents/MyGames/CFD/common/gameScripts/cursor.cs.
---------------------------------------------------------------------------------
Video Initialization:
---------------------------------------------------------------------------------
Video initialization:
Accelerated OpenGL display device detected.
Accelerated D3D device detected.
Voodoo 2 display device not detected.I've updated my drivers. Downgraded my drivers to several older versions. Nothing is working.
By the way, my machine is an MBP running Win7-64.
#44
03/03/2013 (5:24 am)
Yay! It's almost ready. :)
#45
1. Completely remove the previously T2D/TGB installations
2. Delete your GarageGames settings folder in the user app data directory (different for each OS)
Let me know if the crash fix is working for you.
03/04/2013 (1:09 pm)
New version is available for download. We simply overwrote the zip file that was uploaded to your accounts previously. The new zip file contains the updates that resolve the fullscreen crash and bugs. Be sure to perform the following:1. Completely remove the previously T2D/TGB installations
2. Delete your GarageGames settings folder in the user app data directory (different for each OS)
Let me know if the crash fix is working for you.
#46
03/04/2013 (5:53 pm)
The crash does seem to be fixed. Screenshot code is still not in the build, and I still get odd "bogus mRemapTable[i] value in OkayD 80" :/ The screenshot is easy to fix, and I'm not sure if the font erros means anything.
#47
03/04/2013 (9:06 pm)
Completely uninstalled 1.7.6, deleted GarageGames folder from AppData folder, and unzipped the new 1.8 package. It won't launch. I get the same error in console.log for T2D that I was getting for the project I was working on. This is the console.log for TorqueGameBuilder.exe://-------------------------- 3/4/2013 -- 22:00:06 -----
---------------------------------------------------------------------------------
Processor Initialization:
Intel Pentium III, ~2.40 Ghz
(timed at roughly 2.42 Ghz)
FPU detected
MMX detected
SSE detected
---------------------------------------------------------------------------------
Math Initialization:
Installing Standard C extensions
Installing Assembly extensions
Installing FPU extensions
Installing MMX extensions
Installing SSE extensions
---------------------------------------------------------------------------------
Input Initialization:
DirectInput enabled.
Loading compiled script C:/Users/Joe/Desktop/Torque2D_1_8/tgb/common/main.cs.
Loading compiled script C:/Users/Joe/Desktop/Torque2D_1_8/tgb/tools/main.cs.
Loading compiled script C:/Users/Joe/Desktop/Torque2D_1_8/tgb/common/preferences/defaultPrefs.cs.
Reading Display Device information...
Primary Display Device Found:
Vendor Id: VEN_8086
Device Id: DEV_0126
Using D3D rendering. Fullscreen: 0
Missing file: C:/Users/Joe/AppData/Roaming/GarageGames/TorqueGameBuilder/commonPrefs.cs!
Loading compiled script C:/Users/Joe/Desktop/Torque2D_1_8/tgb/common/gameScripts/common.cs.
Loading compiled script C:/Users/Joe/Desktop/Torque2D_1_8/tgb/common/gameScripts/audio.cs.
Loading compiled script C:/Users/Joe/Desktop/Torque2D_1_8/tgb/common/gameScripts/canvas.cs.
Loading compiled script C:/Users/Joe/Desktop/Torque2D_1_8/tgb/common/gameScripts/cursor.cs.
Binding server port to default IP
UDP initialized on port 0
---------------------------------------------------------------------------------
Video Initialization:
---------------------------------------------------------------------------------
Video initialization:
Accelerated OpenGL display device detected.
Accelerated D3D device detected.
Voodoo 2 display device not detected.
#48
03/05/2013 (9:56 am)
Thanks for the update, but now I can't open my project. It says "can't open 'Project' files" or something. :(
#49
03/05/2013 (10:03 am)
Oh yeah, and the keyboard shortcuts still don't work. :( 
Torque 3D Owner Harry Durnan
How's it going with this? I've been resisting asking all week, but it did sound like you already had it fixed from the original post.