Hello Guest

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - DavidFerro

Pages: [1]
1
Support / Re: iOS Deployment Size
« on: December 07, 2012, 12:18:35 am »
We have meta files on, and are using svn. I moved all of the data out of the resources folder through svn, and left the prefabs in there. I am trying to make a build now, but its taking a while which might mean that its still copying stuff over.

I tried to move both the prefabs and data out of the editor but it had problems building to xcode.

2
Support / Re: iOS Deployment Size
« on: December 06, 2012, 11:53:28 pm »
It is a SpriteSwapping Script. The way I remember it working was it would go through each sprite and check its collection name, if there was an hd version of that name, it would swap the sprite to using the hd collection, and set the sprite to be the same id as it was before.

3
Support / Re: iOS Deployment Size
« on: December 06, 2012, 11:10:55 pm »
I updated that way because those were the steps left to me. I will try the normal unity updating.

As for needing the data resource prefab in the resources folder, if i have a public reference in the editor and drag and drop it, that should still work right.

4
Support / Re: iOS Deployment Size
« on: December 06, 2012, 10:30:57 pm »
Hi, Thank you for the excellent response time. There are a couple of things going on here that I think that we will need help with.

You helped out someone else from my office a little while ago with a sprite swapping issue. We made a script to basically swap out hd sprites if we need to. This takes a list of the target sprite collections. If we move these out of the resources folder, but they are still referenced by the scripts, will they still cause the cascade of events that makes unity also copy over the base textures?

One solution that you purposed was updating the version of tk2d. I have basically spent all day doing this with no success. I have opened a new unity project, imported the new version of tk2d toolkit into that, changed the project structure so that it mirrors my other project. Then closed it, and tried to replace the files in my main project.

The main project will then run, and I can even edit the sprite collections with the editor. But the second that I click on a sprite it goes into an infinitely(I let it run for about a solid hour) running loading bar that keeps resetting saying searching project or something like that. Do you have any suggestions as to how to update tk2d toolkit.

Thank you again for all your help so far.

5
Support / Re: iOS Deployment Size
« on: December 06, 2012, 05:52:24 pm »
Hi, sorry for the delayed response. Attached is the build Log. It looks like included dll's are taking up the majority of the space. However it still seems like it is copying over the entire textures folder even though we dont use any of those directly.

Edit: Actually attached the log.

Edit: And by dll's I actually mean textures is taking up most of the space.

6
Support / iOS Deployment Size
« on: December 03, 2012, 05:33:59 pm »
Hi,

So the app that we are building for iOS devices is really big. We are starting to run into problems with the total size of the app. We build the sprite collections with textures that have been imported into unity. Then, if I understand this correctly, when we build Unity coppies both the generated texture atlas's and the individual textures over to the device, essentially taking up twice the amount of space. First are we doing this wrong, and is there some way to use textures outside the unity project to generate the sprite collections so that the textures dont get copied over also. Or is there a way to basically exclude files in the hierarchy from being copied over to the device.

A couple of random things to note:
#1: The entire assets folder of my unity project in finder is only about 219.4MB
#2: The data folder in the xcode project, which has all the levels and assets, is about a gig, 991.7 mb

I have no clue how this is getting inflated so much.

Pages: [1]