Are you asking of changing where the directories get read (ie same directory as .exe) and how to change that (ie from a seperate directory all together, or do you want to load more .tre archives?
Basically, in the SWGEmu's case (But it doesn't matter ultimately, you can just use any .cfg I believe under [SharedFile]), you'll want to open swgemu_live.cfg and add a subfolder in front of the .tre path (Should work with a completely different path, too).
From:
To:
This would then read the .tre files in SWGEmu/tre, rather than in SWGEmu.
Then if you'd want a completely different directory, away from SWGEmu, for example c:\test\, you'd do:
In case you just want to add more .tre's that the client should read, add them here.
Basically, in the SWGEmu's case (But it doesn't matter ultimately, you can just use any .cfg I believe under [SharedFile]), you'll want to open swgemu_live.cfg and add a subfolder in front of the .tre path (Should work with a completely different path, too).
From:
Code:
[SharedFile]
maxSearchPriority=26
searchTree_00_25=default_patch.tre
searchTree_01_24=patch_sku1_14_00.tre
searchTree_00_23=patch_14_00.tre
searchTree_01_22=patch_sku1_13_00.tre
searchTree_00_21=patch_13_00.tre
searchTree_01_20=patch_sku1_12_00.tre
searchTree_00_19=patch_12_00.tre
searchTree_00_18=patch_11_03.tre
searchTree_01_17=data_sku1_07.tre
searchTree_00_16=patch_11_02.tre
searchTree_01_15=data_sku1_06.tre
searchTree_00_14=patch_11_01.tre
searchTree_00_14=patch_11_00.tre
searchTree_01_13=data_sku1_05.tre
searchTree_01_13=data_sku1_04.tre
searchTree_01_13=data_sku1_03.tre
searchTree_01_13=data_sku1_02.tre
searchTree_01_13=data_sku1_01.tre
searchTree_01_13=data_sku1_00.tre
searchTree_00_12=patch_10.tre
searchTree_00_11=patch_09.tre
searchTree_00_10=patch_08.tre
searchTree_00_9=patch_07.tre
searchTree_00_8=patch_06.tre
searchTree_00_7=patch_05.tre
searchTree_00_6=patch_04.tre
searchTree_00_5=patch_03.tre
searchTree_00_4=patch_02.tre
searchTree_00_3=patch_01.tre
searchTree_00_2=patch_00.tre
searchTree_00_1=data_other_00.tre
searchTree_00_1=data_static_mesh_01.tre
searchTree_00_1=data_static_mesh_00.tre
searchTree_00_1=data_texture_07.tre
searchTree_00_1=data_texture_06.tre
searchTree_00_1=data_texture_05.tre
searchTree_00_1=data_texture_04.tre
searchTree_00_1=data_texture_03.tre
searchTree_00_1=data_texture_02.tre
searchTree_00_1=data_texture_01.tre
searchTree_00_1=data_texture_00.tre
searchTree_00_1=data_skeletal_mesh_01.tre
searchTree_00_1=data_skeletal_mesh_00.tre
searchTree_00_1=data_animation_00.tre
searchTree_00_1=data_sample_04.tre
searchTree_00_1=data_sample_03.tre
searchTree_00_1=data_sample_02.tre
searchTree_00_1=data_sample_01.tre
searchTree_00_1=data_sample_00.tre
searchTree_00_1=data_music_00.tre
searchTree_00_0=bottom.tre
Code:
[SharedFile]
maxSearchPriority=26
searchTree_00_25=tre\default_patch.tre
searchTree_01_24=tre\patch_sku1_14_00.tre
searchTree_00_23=tre\patch_14_00.tre
searchTree_01_22=tre\patch_sku1_13_00.tre
searchTree_00_21=tre\patch_13_00.tre
searchTree_01_20=tre\patch_sku1_12_00.tre
searchTree_00_19=tre\patch_12_00.tre
searchTree_00_18=tre\patch_11_03.tre
searchTree_01_17=tre\data_sku1_07.tre
searchTree_00_16=tre\patch_11_02.tre
searchTree_01_15=tre\data_sku1_06.tre
searchTree_00_14=tre\patch_11_01.tre
searchTree_00_14=tre\patch_11_00.tre
searchTree_01_13=tre\data_sku1_05.tre
searchTree_01_13=tre\data_sku1_04.tre
searchTree_01_13=tre\data_sku1_03.tre
searchTree_01_13=tre\data_sku1_02.tre
searchTree_01_13=tre\data_sku1_01.tre
searchTree_01_13=tre\data_sku1_00.tre
searchTree_00_12=tre\patch_10.tre
searchTree_00_11=tre\patch_09.tre
searchTree_00_10=tre\patch_08.tre
searchTree_00_9=tre\patch_07.tre
searchTree_00_8=tre\patch_06.tre
searchTree_00_7=tre\patch_05.tre
searchTree_00_6=tre\patch_04.tre
searchTree_00_5=tre\patch_03.tre
searchTree_00_4=tre\patch_02.tre
searchTree_00_3=tre\patch_01.tre
searchTree_00_2=tre\patch_00.tre
searchTree_00_1=tre\data_other_00.tre
searchTree_00_1=tre\data_static_mesh_01.tre
searchTree_00_1=tre\data_static_mesh_00.tre
searchTree_00_1=tre\data_texture_07.tre
searchTree_00_1=tre\data_texture_06.tre
searchTree_00_1=tre\data_texture_05.tre
searchTree_00_1=tre\data_texture_04.tre
searchTree_00_1=tre\data_texture_03.tre
searchTree_00_1=tre\data_texture_02.tre
searchTree_00_1=tre\data_texture_01.tre
searchTree_00_1=tre\data_texture_00.tre
searchTree_00_1=tre\data_skeletal_mesh_01.tre
searchTree_00_1=tre\data_skeletal_mesh_00.tre
searchTree_00_1=tre\data_animation_00.tre
searchTree_00_1=tre\data_sample_04.tre
searchTree_00_1=tre\data_sample_03.tre
searchTree_00_1=tre\data_sample_02.tre
searchTree_00_1=tre\data_sample_01.tre
searchTree_00_1=tre\data_sample_00.tre
searchTree_00_1=tre\data_music_00.tre
searchTree_00_0=tre\bottom.treThen if you'd want a completely different directory, away from SWGEmu, for example c:\test\, you'd do:
Code:
[SharedFile]
maxSearchPriority=26
searchTree_00_25=C:\test\default_patch.tre
searchTree_01_24=C:\test\patch_sku1_14_00.tre
searchTree_00_23=C:\test\patch_14_00.tre
searchTree_01_22=C:\test\patch_sku1_13_00.tre
searchTree_00_21=C:\test\patch_13_00.tre
searchTree_01_20=C:\test\patch_sku1_12_00.tre
searchTree_00_19=C:\test\patch_12_00.tre
searchTree_00_18=C:\test\patch_11_03.tre
searchTree_01_17=C:\test\data_sku1_07.tre
searchTree_00_16=C:\test\patch_11_02.tre
searchTree_01_15=C:\test\data_sku1_06.tre
searchTree_00_14=C:\test\patch_11_01.tre
searchTree_00_14=C:\test\patch_11_00.tre
searchTree_01_13=C:\test\data_sku1_05.tre
searchTree_01_13=C:\test\data_sku1_04.tre
searchTree_01_13=C:\test\data_sku1_03.tre
searchTree_01_13=C:\test\data_sku1_02.tre
searchTree_01_13=C:\test\data_sku1_01.tre
searchTree_01_13=C:\test\data_sku1_00.tre
searchTree_00_12=C:\test\patch_10.tre
searchTree_00_11=C:\test\patch_09.tre
searchTree_00_10=C:\test\patch_08.tre
searchTree_00_9=C:\test\patch_07.tre
searchTree_00_8=C:\test\patch_06.tre
searchTree_00_7=C:\test\patch_05.tre
searchTree_00_6=C:\test\patch_04.tre
searchTree_00_5=C:\test\patch_03.tre
searchTree_00_4=C:\test\patch_02.tre
searchTree_00_3=C:\test\patch_01.tre
searchTree_00_2=C:\test\patch_00.tre
searchTree_00_1=C:\test\data_other_00.tre
searchTree_00_1=C:\test\data_static_mesh_01.tre
searchTree_00_1=C:\test\data_static_mesh_00.tre
searchTree_00_1=C:\test\data_texture_07.tre
searchTree_00_1=C:\test\data_texture_06.tre
searchTree_00_1=C:\test\data_texture_05.tre
searchTree_00_1=C:\test\data_texture_04.tre
searchTree_00_1=C:\test\data_texture_03.tre
searchTree_00_1=C:\test\data_texture_02.tre
searchTree_00_1=C:\test\data_texture_01.tre
searchTree_00_1=C:\test\data_texture_00.tre
searchTree_00_1=C:\test\data_skeletal_mesh_01.tre
searchTree_00_1=C:\test\data_skeletal_mesh_00.tre
searchTree_00_1=C:\test\data_animation_00.tre
searchTree_00_1=C:\test\data_sample_04.tre
searchTree_00_1=C:\test\data_sample_03.tre
searchTree_00_1=C:\test\data_sample_02.tre
searchTree_00_1=C:\test\data_sample_01.tre
searchTree_00_1=C:\test\data_sample_00.tre
searchTree_00_1=C:\test\data_music_00.tre
searchTree_00_0=C:\test\bottom.treIn case you just want to add more .tre's that the client should read, add them here.
First number is the expansion number, but irrelevant really as far as I know. If you look at NGE .TOC's, you'll notice you have 4 of them, sku0-sku3, 0 being the base game, 1 being JTL, etc.
So then, searchTree_01 would indicate that it's for JTL related things.
But yeah, ultimately irrelevant I think. Only important part is maxSearchPriority, its variable and that the .TRE links are in correct order.
So then, searchTree_01 would indicate that it's for JTL related things.
But yeah, ultimately irrelevant I think. Only important part is maxSearchPriority, its variable and that the .TRE links are in correct order.
wow, great info..
related question please... is there a maximum number of .tre files that can be loaded? I have a couple of reasons I am asking:
1. small very frequent interim releases as a person develops (the file count might stack up
)
2. is there an advantage (client and or server performance or other wise ) to have say 5 custom .tre files vs. 1 .tre or vice versa?
I this has been answered before, can you point me to that discussion thread? (I am a noob here, so be gentle)
oh ... and Merry Christmas / Boxer Day and Happy New Year!
May the Force (and dreams of JTL) be with you fine folks!
Dax
related question please... is there a maximum number of .tre files that can be loaded? I have a couple of reasons I am asking:
1. small very frequent interim releases as a person develops (the file count might stack up
)2. is there an advantage (client and or server performance or other wise ) to have say 5 custom .tre files vs. 1 .tre or vice versa?
I this has been answered before, can you point me to that discussion thread? (I am a noob here, so be gentle)
oh ... and Merry Christmas / Boxer Day and Happy New Year!
May the Force (and dreams of JTL) be with you fine folks!
Dax
Client wise, i think there should be no problem with a lot of .tre's and performance differences shouldn't be too hard. But it's a good question that I've never tried to fully investigate and benchmark.
Server wise, I have no idea, but would assume there shouldn't be a problem.
No need to be afraid!
Merry Christmas to you too!
Sorry that my answer is kind of vague.
Server wise, I have no idea, but would assume there shouldn't be a problem.
No need to be afraid!
Merry Christmas to you too!
Sorry that my answer is kind of vague.
Like Timbab, I've never benchmarked this, but I have noticed if the .tre files are excessively large, the client and server can take fractionally longer to load..... and I do mean fractionally, but it was noticeable.
Sounds like you've just volunteered for a holiday project
From a Server POV, little and often versus big updates? Well SOE released stuff as they made it for the most part, apart from the big publishes/game updates..whatever you want to call em.
Depends how you patch the client for your server. If its a dev server then it really doesn't matter. If it's a play server then you need an auto patching launchpad or you have to rely on the players knowing there was an update and hoping they'll DL the necessary files.
Either way NGE had 200+ tre files, Pre-CU 50+, not sure there would be a cap though.
Happy christmas
Sounds like you've just volunteered for a holiday project
From a Server POV, little and often versus big updates? Well SOE released stuff as they made it for the most part, apart from the big publishes/game updates..whatever you want to call em.
Depends how you patch the client for your server. If its a dev server then it really doesn't matter. If it's a play server then you need an auto patching launchpad or you have to rely on the players knowing there was an update and hoping they'll DL the necessary files.
Either way NGE had 200+ tre files, Pre-CU 50+, not sure there would be a cap though.
Happy christmas
two years ago I started merging .tre data to limit the number .tre files I had to keep track of. I managed to get the entire 14.1 library down to 2 .tre files, one was 1.8GB, one was 725MB... I still have them actually, but I don't use them, I use the MTG .tre's now.
Anyway, I found that client & server load times were much longer when using the two consolidated .tre files, as opposed to using all 30 of the original. Not sure why to be honest. by much longer I mean 5 times longer maybe? long enough to walk downstairs and make a beverage, and by the time I returned it would still be loading the last bit... change the live file to use the original .tre files and it goes back to loading in 15-30 seconds.
BTW, it was the first load that took forever, subsequent loads worked super fast as long as I didn't kill the client.
-Duff
Anyway, I found that client & server load times were much longer when using the two consolidated .tre files, as opposed to using all 30 of the original. Not sure why to be honest. by much longer I mean 5 times longer maybe? long enough to walk downstairs and make a beverage, and by the time I returned it would still be loading the last bit... change the live file to use the original .tre files and it goes back to loading in 15-30 seconds.
BTW, it was the first load that took forever, subsequent loads worked super fast as long as I didn't kill the client.
-Duff