I have several questions about TGE/TSE.

#1 I'll take a crack:

1. I'm pretty sure it is. It may depend on the exporter you are using to create the DTS, and of course you can probably modify the exporter. In my case, using Milkshape, there is no way to designate a path to a separate texture directory out of the box. Admittedly, the engine itself may not require this.

2. I think some clarification is in order. What do you mean? You can make your own installer, of course.

3. You have the source code!

Lee

#2 You can zip your resource files: jpgs, dts, dif, ogg, etc.
It's in the engine. Do a search and you can find more info.

#3 A simple search found this.

#4 Textures need only be in or above the directory of your dif/dts files. You could put all your dts textures in /shapes, and then your dts files in /shapes/weapons/xxx. Many items may use the same texture after all... Do keep in mind any scripted objects need to be double checked for paths (decalData = xxx).

#5

Quote:I'll take a crack:

1. I'm pretty sure it is. It may depend on the exporter you are using to create the DTS, and of course you can probably modify the exporter. In my case, using Milkshape, there is no way to designate a path to a separate texture directory out of the box. Admittedly, the engine itself may not require this.

2. I think some clarification is in order. What do you mean? You can make your own installer, of course.

3. You have the source code!

Lee

Thank you, you mean I need to have the sourec code of exporter? but I am not good at programming. ;(

#6

Quote:You can zip your resource files: jpgs, dts, dif, ogg, etc.
It's in the engine. Do a search and you can find more info.

A simple search found this.

Thank you, it maybe a lot for me to learn, it touchs the source code and I am not a good coder. ;P

#7

Quote:Textures need only be in or above the directory of your dif/dts files. You could put all your dts textures in /shapes, and then your dts files in /shapes/weapons/xxx. Many items may use the same texture after all... Do keep in mind any scripted objects need to be double checked for paths (decalData = xxx).

I see, Thank you!

#8 If you are zipping and encrypting your resources, then it shouldn't matter since the end user won't know where the resources are anyway. It might matter to you during development, though, but does it matter that much? Enough to rewrite exporters or asset management?

#9

Quote:If you are zipping and encrypting your resources, then it shouldn't matter since the end user won't know where the resources are anyway. It might matter to you during development, though, but does it matter that much? Enough to rewrite exporters or asset management?

Yes, I want to make pack files like American Army and F.E.A.R. that uses can not open the source. not like Q3A/MOHAA/COD, winzip/winrar can open their packs.

I used to make mods on MOHAA/COD, etc., the .pk3 they used can not be encrypted and the mod license is not alllowed to. So I didn't touch any engine level coding or any other conding like write exporters before. Now Torque is a new thing to me because it comes with source. ;)

#10 With TSE, no, it's not important to place the textures in the same directory as the DTS. The material name is a material in TSE, not a bitmap name, like in TGE. The material can specify whatever texture / bitmap it needs and it can specify full path.

As far as encryption, there are several encryption resources, but TSE/TGE doesn't have them built in... it requires a bit of source-code modification, but even a non-programmer should be able to take the resource and implement it... it's not too hard. You just have to have a C++ compiler and a little bit of smarts :P

#11

Quote:With TSE, no, it's not important to place the textures in the same directory as the DTS. The material name is a material in TSE, not a bitmap name, like in TGE. The material can specify whatever texture / bitmap it needs and it can specify full path.

As far as encryption, there are several encryption resources, but TSE/TGE doesn't have them built in... it requires a bit of source-code modification, but even a non-programmer should be able to take the resource and implement it... it's not too hard. You just have to have a C++ compiler and a little bit of smarts :P

Thank you, I will have a good look at on the article. Hope TSE can be released soon and I am smart enough to learn encryption. ;P

#12 Check www.molebox.com

Luck!
Guimo