How to decrease deployment "data ZIP" folder?

[domi]

I noticed that the data compressed folder in the build directory puts the entire asset library including unused elements.

 

How can I build with only the assets used in a game?

For now my basic test map is over 258 MB.

 

this is what it looks like

[Josh]

Please see here:

http://www.leadwerks.com/werkspace/blog/1/entry-1381-selective-file-inclusion-beta/

[domi]

Hello Josh

Thanks for helping

Is this also available for the Indie Version?

[Josh]

Yes, but you have to opt into the beta to get it.

[domi]

OK, but won't allow me

It asks for BETA access code

Where do I get that from ?

[DerRidda]

Nope, that password field is always there you don't need to enter anything there. The drop down menu above the password field has the beta branch which you simply need to select.

[domi]

Done it, but now my game is always crashing

it gives me the Windows crash dialog box

I roll back to 3.3

[Josh]

I really can't debug anything unless you provide your game. All my tests worked fine.

[domi]

Can I upload that here?

[Josh]

Yes, if it will fit.

[domi]

OK it's here

BETA.zip

[Josh]

Ah, I see. The FPS player constructs the name of the foot step sound files programmatically, so they are never included:

    for n=1,4 do
       self.sound.footsteps.concrete.step[n] = Sound:Load("Sound/Footsteps/Concrete/step"..tostring(n)..".wav")
   end

[Imchasinyou]

my other topic started this process and can be found here

 

http://www.leadwerks.com/werkspace/topic/11392-published-game-wont-run/

[domi]

I'm patient

For now I rolled back and design first, so it's not ready to be worried about file size issues,yet.

[YouGroove]

self.sound.footsteps.concrete.step[n] = Sound:Load("Sound/Footsteps/Concrete/step"..tostring(n)..".wav")

 

That's programmer coding, the sounds should be clearly named and put on a table, this to keep program clear and editor able to list the assets used.

It reminds be very bad C coders, making code unreadble and unmaintanable : bad practice.

 

I don't think there is some program on earth able to detect assets used by programs like that

Sound = "MySound"

i = 0

i +=3

Sound += i

y=10

Sound += "track"

Sound += y

LoadSound(Sound)

 

 

It seems the more Josh gives you guys , the more you go crazy and ask for impossible

[AggrorJorn]

It is not weird at all Yougroove. It would be bad practice to manually having to specify every single sound in this case. I my case I have a complete soundpack called "naturesounds". All sounds go from naturesound1.wav to naturesound186.wav. What a nightmare that would be if I had to manually specify each sound.

 

 

I also don´t think it is Leadwerk´s responsibility to detect whether such 'dynamic' named files are being loaded. It would be very hacky the least and you will always have some sort of exception to the case. The bulk of the assets are already being loaded via the ways Josh has described in his blog and I personally think those methods are just fine.

 

 

When files are used like in the example above, a 'simple' option to select folders or files with a certain extension for export would be a good solution.

Something like below would do the trick. Not only does this give Leadwerks a unified way of detecing export folders, it also gives the programmers a way of creating dynamic variables without having to worry about missing export errors.

ExportInclude "Sounds/Player/Footsteps"

[Gonan]

As all scripts are scanned and exported, and programmatically generated content is not exported, can we create a myexports.lua.

Even if myexports.lua isn't attached to any maps or entities I presume it will still get scanned and exported.

 

So my question is what is the minimum code that I need to put into myexports.lua to make the export scanner include content that has been programmatically referenced elsewhere in the program.

Do I have to code every file used, or can I code a path to include all files, and will that include subfolders and their files too?

 

eg. if subfolders were not automatically added. Would the following work or would every programmatically referenced file need to be listed.

 

-- helper for publishing

 

local soundexp="Sound/Player" -- entire contents of Player folder added to export

local soundexpFootsteps="Sound/Footsteps"

local soundexpFottstepsConcrete="Sound/Footsteps/Concrete"

local zombiesounds="AddOns/Zombie Character Pack/*.wav" -- just the .wav files added to the export

-- or would this be required to specify each individual file

local zombiesounds1="Addons/Zombie Character Pack/alert.wav"

local zombesounds2="Addons/Zombie Character Pack/idle.wav"

[Josh]

It seems the more Josh gives you guys , the more you go crazy and ask for impossible

Yes! This is why users do not design Leadwerks directly, and I say no to a lot of things.

 

Anyways, there's some more info and an update here:

http://www.leadwerks.com/werkspace/blog/1/entry-1383-selective-file-inclusion-continued/

[Ma-Shell]

I don't think there is some program on earth able to detect assets used by programs like that

(...)

 

It seems the more Josh gives you guys , the more you go crazy and ask for impossible

 

There was no one who asked for a program to detect that. The only thing that was asked was that one could also get a chance to force the editor manually to include those files, which was implemented now by the option to not use the new selective inclusion

[abyssus]

The only thing that was asked was that one could also get a chance to force the editor manually to include those files, which was implemented now by the option to not use the new selective inclusion

 

Glad to see Josh made the right decision despite earlier reservations. Good job and keep up the good work.