1.4 Problems
by Afrim Kacaj · in Torque Game Engine · 12/06/2005 (1:19 pm) · 2 replies
Hi All,
Just wanted to note some problems that ive been having so far with 1.4
I am at my day job right now so wont be able to offer specific details.
World Editor problems:
Problem 1:
If your terrain has a block size of 8, try changing that to 2 or 4, or I guess to any valid value. If using the torquedemo.exe that came with the fps demo, after changing the value and clicking out of the field, torque will just exit (super fast i might add). I experienced the same thing when i tried to implement teams. If a player decides to switch teams i have to call the player.delete() function. Every time i did that the program would just exit without any warnings or any hints in the log.
Problem 2:
When switching to world editor F3/F4 sometimes do not work.
Problem 3:
When using texture painter. I noticed that when using the 6th texture I get black boxes around the brush that i am painting with.
The defects remain there on the terrain, the only way to get rid of them is to use one of the other textures and paint over them. I have tried swapping out the jpg file with another one and still the same problem.
Problem 4:
You can not edit the terrain if the tiled check box is not checked. I need to create a world where tiling presents a problem. However in order to do that i have to switch to tiled mode, create the world then switch back to untiled. Not sure if this worked in 1.3 since this is the first time that I had to do it.
Compiling problem:
When I first tried to compile i got hundreds of errors regarding a winnt.h file. After searching the forums I found a fix in a totaly unrelated topic. In the WinNT.h file you have to search for #include and replace the brackets <> with quotes "" I cant remember the exact name of the include file i think it was stdinput.h or something with std in front.
Now that I have finally compiled the exe file that i get is actually larger than the one that comes with the demo. I think the demo version is 1.4 mb while the one that i have compiled is 2.4xMB. Just curious where did the extra megabyte come from, especialy since the SDK does not include the Lighting Pack but the demo does. Nope I am not compiling in debug.
Also note that for the above world editor errors that i noted. Now that i am using my own compiled exe, i actually get an error message when performing those tasks instead of torque just exiting.
Whoa that was alot, I hope I didnt miss anything. If I did ill be sure to post.
Just wanted to note some problems that ive been having so far with 1.4
I am at my day job right now so wont be able to offer specific details.
World Editor problems:
Problem 1:
If your terrain has a block size of 8, try changing that to 2 or 4, or I guess to any valid value. If using the torquedemo.exe that came with the fps demo, after changing the value and clicking out of the field, torque will just exit (super fast i might add). I experienced the same thing when i tried to implement teams. If a player decides to switch teams i have to call the player.delete() function. Every time i did that the program would just exit without any warnings or any hints in the log.
Problem 2:
When switching to world editor F3/F4 sometimes do not work.
Problem 3:
When using texture painter. I noticed that when using the 6th texture I get black boxes around the brush that i am painting with.
The defects remain there on the terrain, the only way to get rid of them is to use one of the other textures and paint over them. I have tried swapping out the jpg file with another one and still the same problem.
Problem 4:
You can not edit the terrain if the tiled check box is not checked. I need to create a world where tiling presents a problem. However in order to do that i have to switch to tiled mode, create the world then switch back to untiled. Not sure if this worked in 1.3 since this is the first time that I had to do it.
Compiling problem:
When I first tried to compile i got hundreds of errors regarding a winnt.h file. After searching the forums I found a fix in a totaly unrelated topic. In the WinNT.h file you have to search for #include
Now that I have finally compiled the exe file that i get is actually larger than the one that comes with the demo. I think the demo version is 1.4 mb while the one that i have compiled is 2.4xMB. Just curious where did the extra megabyte come from, especialy since the SDK does not include the Lighting Pack but the demo does. Nope I am not compiling in debug.
Also note that for the above world editor errors that i noted. Now that i am using my own compiled exe, i actually get an error message when performing those tasks instead of torque just exiting.
Whoa that was alot, I hope I didnt miss anything. If I did ill be sure to post.
#2
Problem 3 has nothing to do with TGE errors, it's because you are painting a texture which does not exist in the F8 menu and TGE is struggling to blend the new texture. Try and plan ahead when doing terrain work and in the F8 menu, add all the textures you plan to use, including those you plan to paint with. Those "painting" textures should be placed by height and then move all the sliders down to about 1cm above the bottom line so that they form a kind of level horizontal line near, but not at, the bottom of the slider grid.
Doing that places those textures on the terrain, evenly, but at a very low alpha value and therefore the colors wont really interfere with the textures you want to have visible on the terrain. If you now paint with those "low level" textures, the black block patterns wont be there anymore.
I have not experienced the other problems you mention but have had many weird GUI editor problems and suspect a memory leak in that code.
12/11/2005 (2:54 am)
The exe in the demo is compressed which is why its half the size of the version you just compiled.Problem 3 has nothing to do with TGE errors, it's because you are painting a texture which does not exist in the F8 menu and TGE is struggling to blend the new texture. Try and plan ahead when doing terrain work and in the F8 menu, add all the textures you plan to use, including those you plan to paint with. Those "painting" textures should be placed by height and then move all the sliders down to about 1cm above the bottom line so that they form a kind of level horizontal line near, but not at, the bottom of the slider grid.
Doing that places those textures on the terrain, evenly, but at a very low alpha value and therefore the colors wont really interfere with the textures you want to have visible on the terrain. If you now paint with those "low level" textures, the black block patterns wont be there anymore.
I have not experienced the other problems you mention but have had many weird GUI editor problems and suspect a memory leak in that code.
Torque Owner Skylar Kelty
SkylarK
compiling problem:
are you using vs 2005?