1
Support / Re: Disabling fog on tk2d sprites only?
« on: June 22, 2012, 01:07:40 pm »
Ok, thanks for that. I will give it a try.
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.
Pages: [1] 2
2
Support / Disabling fog on tk2d sprites only?
« on: June 22, 2012, 12:04:07 pm »
Ok, so we have just added Unity fog into our game, unfortunately the tk2d sprites are also being fogged off. Is there anyway to turn this off and keep them all full brightness without the fog?
3
Support / Re: Reducing Drawcall rate to 1?
« on: June 07, 2012, 03:15:14 am »
Yes, but I guess what I am saying is, surely it is better to have as many large atlases as possible?
For example I have several 256x256 atlases but surely if I combine them into 1 big atlas then I will only have 1 drawcall instead?
In tk2d you can choose to have multiple atlases within the same name. Now is this really truly separate atlases or is tk2d displaying them as separate but in fact they are all combined into one big atlas atlas in memory. For example is 4 separate 256x256 atlases being stored as one big 512x512?
I guess this is the questions I should have asked in my first post. Sorry about that
For example I have several 256x256 atlases but surely if I combine them into 1 big atlas then I will only have 1 drawcall instead?
In tk2d you can choose to have multiple atlases within the same name. Now is this really truly separate atlases or is tk2d displaying them as separate but in fact they are all combined into one big atlas atlas in memory. For example is 4 separate 256x256 atlases being stored as one big 512x512?
I guess this is the questions I should have asked in my first post. Sorry about that
4
Support / Reducing Drawcall rate to 1?
« on: June 06, 2012, 01:48:26 pm »
Is it possible?
By my understanding of Unity, creating a sprite from a single atlas once or 100 times is going to be 1 draw call.
But 5 sprites each using a different atlas, that is going to be 5 drawcalls even just from 5 sprites.
Am I wrong in this theory or does tk2d have some special optimising?
By my understanding of Unity, creating a sprite from a single atlas once or 100 times is going to be 1 draw call.
But 5 sprites each using a different atlas, that is going to be 5 drawcalls even just from 5 sprites.
Am I wrong in this theory or does tk2d have some special optimising?
5
Support / Re: Dicing with multiple atlases?
« on: May 01, 2012, 05:21:53 am »
So I am not using the tk2dCamera actually. It is our own code. The game playing field is 640x960 and the camera is locked to that. So everything looks ok on the iphone 4, presumably because that is the resolution of that device. In Unity there is a view mode "iPhone 4G Tall (640x960)" so that is presumably why that works.
But the ipad is 768x1024 and older iphones are 480x320, which is presumably why they look a bit strange.
I am getting the screen width using Screen.width and Screen.height in Unity but even after scaling to the right resolution, things don't quite look right.
But the ipad is 768x1024 and older iphones are 480x320, which is presumably why they look a bit strange.
I am getting the screen width using Screen.width and Screen.height in Unity but even after scaling to the right resolution, things don't quite look right.
6
Support / Re: Dicing with multiple atlases?
« on: April 27, 2012, 12:42:33 pm »
Hi Unikron,
Well a tiny update on what is going on. We have been redoing all our graphics and now we have a game resolution of 640x960. Whilst I can't say if the problem has occured or gone away, I am thinking it could be to do with pixel aspect ratio after all.
What I have done is coded the game so a single Unity world coordinate is the same as 1 pixel. Therefore the game runs in 640x960 Unity world coordinates so it should be pixel perfect aspect ratio when rendered on a mobile device.
Whilst everything looks ok in the GUI, once I compile to certain devices the pixels are slightly blurry, same sort of issues I was having before. When sprites move across there is a clear pixel twitching effect.
I have ticked the boxes in tk2d for pixel perfect. Have messed with the camera, I even attached your Tk2d pixel perfect helper script into the camera and messed around with the settings in that, and nothing seems to make any difference. Very odd indeed.
I still can't work out whether this is a fault in Unity, your library, or some mistake that I have missed.
The particle system is using Unity's inbuilt particle system instead of your library since it was faster, but these particles all look fine and have no problems with pixelation at all.
The plot thickens.
Well a tiny update on what is going on. We have been redoing all our graphics and now we have a game resolution of 640x960. Whilst I can't say if the problem has occured or gone away, I am thinking it could be to do with pixel aspect ratio after all.
What I have done is coded the game so a single Unity world coordinate is the same as 1 pixel. Therefore the game runs in 640x960 Unity world coordinates so it should be pixel perfect aspect ratio when rendered on a mobile device.
Whilst everything looks ok in the GUI, once I compile to certain devices the pixels are slightly blurry, same sort of issues I was having before. When sprites move across there is a clear pixel twitching effect.
I have ticked the boxes in tk2d for pixel perfect. Have messed with the camera, I even attached your Tk2d pixel perfect helper script into the camera and messed around with the settings in that, and nothing seems to make any difference. Very odd indeed.
I still can't work out whether this is a fault in Unity, your library, or some mistake that I have missed.
The particle system is using Unity's inbuilt particle system instead of your library since it was faster, but these particles all look fine and have no problems with pixelation at all.
The plot thickens.
7
Support / Re: Dicing with multiple atlases?
« on: April 24, 2012, 02:20:03 am »
Can you compile to iPhone with a Mac?
I am a bit snowed under at work atm but I will try and make something when I have a spare minute.
The easiest way to replicat this yourself is to simply make a camera and 2 sprite collections.
Make the 1st collection with a single 128x128 image in it. Make the 2nd collection with the same 128x128 image in it but also add a second sprite that is something like 1024x1024, basically anything to make a huge atlas.
Now create 2 sprites, one from the 1st collection and one from the 2nd collection, compile to iPhone and look. The sprite bundled together with the big 1024 texture should be blocky and less quality.
I am a bit snowed under at work atm but I will try and make something when I have a spare minute.
The easiest way to replicat this yourself is to simply make a camera and 2 sprite collections.
Make the 1st collection with a single 128x128 image in it. Make the 2nd collection with the same 128x128 image in it but also add a second sprite that is something like 1024x1024, basically anything to make a huge atlas.
Now create 2 sprites, one from the 1st collection and one from the 2nd collection, compile to iPhone and look. The sprite bundled together with the big 1024 texture should be blocky and less quality.
8
Support / Re: Dicing with multiple atlases?
« on: April 23, 2012, 02:50:31 am »
It is the same on a cube, presumably because the problem is texture related and not surface related.
What I have is 98% of my sprites all on the same atlas, the size is 1024x512. However all the sprites look pixelated when I draw them.
So I made a new SpriteCollection and only added one 128x128 sprite. Then I drew them both alongside each other, one from the main sprite collection and then the one that was just the only sprite. There is a considerable difference.
Except on the latest iPhone, which presumably can handle 1024x1024 no problem.
I think the background sprite would a great addition to your library, I look forward to seeing what you come up with.
What I have is 98% of my sprites all on the same atlas, the size is 1024x512. However all the sprites look pixelated when I draw them.
So I made a new SpriteCollection and only added one 128x128 sprite. Then I drew them both alongside each other, one from the main sprite collection and then the one that was just the only sprite. There is a considerable difference.
Except on the latest iPhone, which presumably can handle 1024x1024 no problem.
I think the background sprite would a great addition to your library, I look forward to seeing what you come up with.
9
Support / Re: Dicing with multiple atlases?
« on: April 20, 2012, 12:01:12 pm »
Considering that even the iPhone1 has a maximum texture size of 1024x1024 I am not entirely sure the reason for this sudden drop in quality for even 512x512 textures. I can only assume it is something to do with how Unity compiles to X-Code.
However the fact everything is ok on the latest iPhone, could be a hardware saving thing after all.
Perhaps maybe if you had a new type of sprite "Background Sprite". You could specify the resolution of your target platform and the maximum texture size you would like to have the background segmented at, then maybe it could work. A background sprite would only have a maximum of 1 image only.
Right now, I am still experimenting with various sizes and implementations to see what works best.
However the fact everything is ok on the latest iPhone, could be a hardware saving thing after all.
Perhaps maybe if you had a new type of sprite "Background Sprite". You could specify the resolution of your target platform and the maximum texture size you would like to have the background segmented at, then maybe it could work. A background sprite would only have a maximum of 1 image only.
Right now, I am still experimenting with various sizes and implementations to see what works best.
10
Support / Dicing with multiple atlases?
« on: April 20, 2012, 04:30:37 am »
If there anyway to be able to use dicing but with multiple atlases as well?
For example I have a 450x800 sprite (Android screen size) as my backdrop. Looks ok in Windows or on Mac.
But when I compile on handhelds the sprite goes all pixelated. Looks ok on iPhone4 but earlier iPhones/iPad etc it doesn't look right, big or obscure texture sizes causes the textures to get automatically scaled down and look worse.
If I chop a 256x256 segment out of the backdrop and put that on screen, everything is fine. With your library, you can dice individual sprites into smaller chunks, but only on the same atlas and texture sizes that are smaller than the maximum texture size of the atlas.
I could fix this manually and chop up all my backdrops into 256x256 and create multiple sprites, but it takes time, and then becomes difficult to edit the gfx later since they are all in pieces.
What would be useful is being able to automatically chop up this large image into 256x256 (or however much you specify) and then when you click "Commit" it automatically creates multiple atlases until it has finished.
Is this feature possible, or maybe could be added a future release? Would be very handy for mobile developers not having to worry about texture sizes.
For example I have a 450x800 sprite (Android screen size) as my backdrop. Looks ok in Windows or on Mac.
But when I compile on handhelds the sprite goes all pixelated. Looks ok on iPhone4 but earlier iPhones/iPad etc it doesn't look right, big or obscure texture sizes causes the textures to get automatically scaled down and look worse.
If I chop a 256x256 segment out of the backdrop and put that on screen, everything is fine. With your library, you can dice individual sprites into smaller chunks, but only on the same atlas and texture sizes that are smaller than the maximum texture size of the atlas.
I could fix this manually and chop up all my backdrops into 256x256 and create multiple sprites, but it takes time, and then becomes difficult to edit the gfx later since they are all in pieces.
What would be useful is being able to automatically chop up this large image into 256x256 (or however much you specify) and then when you click "Commit" it automatically creates multiple atlases until it has finished.
Is this feature possible, or maybe could be added a future release? Would be very handy for mobile developers not having to worry about texture sizes.
11
Support / Re: Aligned Text / Real world coordinate size of a TextMesh?
« on: April 11, 2012, 03:49:25 am »
I was actually looking at bounds, but thought maybe that it was internally calculated within the mesh itself. Cheers for the tips, looks like I have some things I can experiment with.
13
Support / Aligned Text / Real world coordinate size of a TextMesh?
« on: April 10, 2012, 10:58:23 am »
If there a way of returning how wide in Unity coordinates how big in width or height?
Basically a ".GetWidth()" function.
What I want to do is make centrally aligned text so I move the text along by half of the mesh width.
Basically a ".GetWidth()" function.
What I want to do is make centrally aligned text so I move the text along by half of the mesh width.
14
Support / Re: Sprite Collection name issue
« on: April 10, 2012, 10:53:32 am »
This is happening to me too. I had 73 sprites and then I changed the order of them and clicked commit, everything works ok but the names of the Sprite in the Inspector window still contains where the images were positioned before I changed them.
15
Support / Re: Changing the prerendered text
« on: April 09, 2012, 01:08:57 pm »
Thanks for the tip on GameObject.active = false. I will still move them off screen since it makes it easier to debug all your stuff sifting through numbers if inactive sprites have fairly large negative numbers.
I am already Instantiating out of various prefabs for everything, I managed to finally change the contents of text.
I have all my stuff working now. Really, big thanks for creating such an excellent library and thanks personally for all your help.
I am already Instantiating out of various prefabs for everything, I managed to finally change the contents of text.
I have all my stuff working now. Really, big thanks for creating such an excellent library and thanks personally for all your help.
Pages: [1] 2