[devel] Creating Hi-Res/Low-Res App in Cocos2D v0.99.4 and v0.99.5

cocos2d for iPhone » Programming » cocos2d internals

[devel] Creating Hi-Res/Low-Res App in Cocos2D v0.99.4 and v0.99.5

(194 posts) (42 voices)

Started 1 year ago by ishadow
Latest reply from luky300

Tags:

« Previous 1…345…7 Next »

Matt Rix
Member

The @2x trick is great for iPhone/iPod but what about universal apps? I want to use my "2x" graphics on iPad, not the low-res images. I don't have a whole lot of graphics so I'm only doing one universal target.

That's why I decided to use my own "HD" suffix instead of @2x, because it just feels weird to manually specify the @2x extension, and the @2x extension causes some weird issues. *Maybe* their system will be smart enough to look for @2x graphics, but I doubt it. In fact, I doubt the Retina iPad will be next, I'd give that at least another year. 2048*1536 is just waaaay too many pixels to be pushing around the screen.

Posted 1 year ago #
mrTortex
Member

@Matt Rix: Thanks, I hadn't noticed that change. However, with it comes another problem. Now everything starts half way across the screen, so the left half is black.

I've altered the code to be:

float w = s.width;// / 2;
float h = s.height;// / 2;

Which then works, but I'd like to check with you that that won't mess with your code.

to answer a previous question, I started from your demo project and implemented it into my game.

Posted 1 year ago #
riq
Key Master

I started the "retina display" support on the "retina-display" branch:
http://github.com/cocos2d/cocos2d-iphone/tree/retina-display

So far:
- winSize returns Points
- CCMenu works OK.
- CCSpriteBatchNode works OK.
- CCNode works OK.
- Position is in Points (actions works)
- CCLabelTTF is in Points
- CCColorLabel is in Points
- Effects is in Points but it is not working properly

TODO:
- Hook CCFileUtils to return @2x images if they exist, and retina display is ON
- Fix the effects.

I need some help with the testing:
- I need some the following 1x and 2x files:
- a BMFont sample (1x and 2x)
- a TMX sample (1x and 2x)
- a spritesheet (zwoptex file) (1x and 2x)
- a simple image (1x and 2x)

thanks.

UPDATE: Effects working OK.
UPDATE 2: MotionStreak & RenderTexture working OK.
UPDATE 3: Transitions working OK.
UPDATE 4: contentSize working OK
UPDATE 5: particles working OK

Posted 1 year ago #
riq
Key Master

Question: contentSize, should be in Pixels or Points ?

I guess that it should be in Points.

UPDATE: Added contentSizeInPixels. Useful when using textures.

Posted 1 year ago #
riq
Key Master

@Matt-Rix: Regarding the "@2x" suffix, it seems that there is another bug on iOS 4.1 (or feature, but it is incompatible with cocos2d).

on iOS 4.0, images loaded with [[UIImage alloc] initWith...] weren't loading "@2x" images.

on iOS 4.1, it loads the "@2x" images, OK. But the problem is that it loads them all the time, on iPhone 4. But it doesn't matter if the device in "retina display" mode or not.

So, "@2x" images should be avoided in cocos2d.

The "HD" suffix is a possibility.

Posted 1 year ago #
Matt Rix
Member

Yep, contentSize in points makes sense. RenderTexture was one of the trickier things to get working, so it's good that you've got it going.

I chose the HD suffix because of the problems you had with @2x images. I also had weird issues with the device caching @2x versions of images in memory even AFTER uninstalling the app from the device(seems crazy, right?). Perhaps the suffix itself could even be stored in a constant, so that if people want, they can change it to @2x or anything else.

Here's a zip with a couple of things you can use to test... There's .fnt files for 1x and 2x, but the 2x(HD) one is the exact same as the 1x but it points to a different image(the HD image). Once the CCFileUtils thing is done, that won't be necessary anymore.

http://struct.ca/files/hires/HighResStuff.zip

Posted 1 year ago #
jptsetung
Member

Here are .fnt files for sd/hd with different offsets for the sd and hd pngs.

http://demo.ovh.com/fr/36f57f9cafa7999ca3086c7787e15fec/

I also vote for HD suffix.

I've never used Git, but I've searched for the "ccPointToPixel" in the branch but didn't see it. Did you give up this approach ?

If contentScaleFactor is 2 and if the HD bitmpa is not provided, will it still work with the SD bitmap (like in UIKit) ?

Posted 1 year ago #
riq
Key Master
@Mat Rixx @jptsetung Thanks for the files. May I include in cocos2d ? Under which license ?

@jptsetung: everything is in points. But you can access / set everything in pixels if you use the InPixels suffix. eg:
```
[sprite setPosition:ccp(x,y)]; // in points

[sprite setPositionInPixels:ccp(x,y)]; // in pixels

[[CCDirector sharedDirector] winSize]; // in points

[[CCDirector sharedDirector] winSizeInPixels]; // in pixels
```
pixels == points in every configuration except when you put the director in "retina-display" mode:
```
[[CCDirector sharedDirector] setContentScaleFactor:2];  // retina display mode.
```
If contentScaleFactor is 2 and if the HD bitmpa is not provided, will it still work with the SD bitmap (like in UIKit) ?

It's not implemented yet, but yes.
Posted 1 year ago #
jptsetung
Member

That's just perfect.
About the fonts, I used Arista 2.0 ( http://www.zetafonts.com/collection/8 ) which is licensed under CC non commercial.

Posted 1 year ago #
sabshire
Member

@riq now that it is in points, what are the dimensions of the display in points?

Posted 1 year ago #
sabshire
Member

Maybe we should rename this thread since it is now dealing with updates to 99.5 and not so much 99.4

Posted 1 year ago #
riq
Key Master

now that it is in points, what are the dimensions of the display in points?

An iPhone4 app in retina-display mode has a display dimension of 320x480 (or 480x320) in points.
In pixels is 640x960 (or 960x640).

Posted 1 year ago #
slipster216
Moderator

Which reminds me; UV coordinates output from Zwoptex should likely be floats instead of pixel values; that way we can scale a texture without breaking the sprite sheet..

Posted 1 year ago #
Matt Rix
Member

@Riq for the files, I'm not sure they can be used, the font is DIN, so I *think* it's free to use (http://dinfont.com/downloads/). The images are just random images I grabbed from google images, so I guess they probably can't be used.

Posted 1 year ago #
codeman9
Member

I thought that the pixel to points ratio wasn't required to be 2. If I remember correctly, during one of the WWDC videos, a contentScaleFactor of 1.5 was discussed as a good alternative to 2 if performance was a concern. Should we be trying to constrain cocos2d to scaleFactor of 2 only?

Edit: Real question is whether or not the final solution being discussed will allow for "seamless" use of different scaleFactors?

Posted 1 year ago #
riq
Key Master

@codeman9: can you develop further the idea of using contentScaleFactor == 1.5 ? Is it possible to use any resolution ?

@Matt-Rix: thanks.

@slipster216: Actually you'll have to create 2 .plist files (as well as 2 .png files), one for SD and another for HD. (see below).

@all:

I've just created a sample using retina display BMFonts that works OK with and without retina display.

Basically you DO have to create a new set of config files (@Matt I've noticed that you were reusing the .fnt file).
If you want to create a SD and an HD version of a BMFont, then you have to create 4 files:

eg: Create an SD version using a font of size 32.

1. MyFont32.fnt
2. MyFont32.png

Then you MUST create another 2 files, but this time using size=64. But you must save them as 32-hd.
3. MyFont32-hd.fnt
4. MyFont32-hd.png

cocos2d won't parse the .fnt file (nor any other config file) and scale the bitmaps according the content scale value. Instead you should create 2 different config files, one for SD and the other for HD.

Another example:
If you have an spritesheet in SD, then you MUST have another .plist file in HD.

eg: spritesheet in SD
1.spritesheet1.plist
2.spritesheet1.png

spritesheet in HD
3.spritesheet1-hd.plist // <-- The coordinates in this file might be completely different than the SD version.
4.spritesheet1-hd.png

Why ?
1. Basically I think it much easier to maintain and extend if cocos2d doesn't "scale" the data files. The logic is in the data, not in the code.

2. An SD data file might be completely different from the HD version, so it would be impossible to "scale" the SD data up to HD.

I think that everything is working OK:
- I've tested allmost all the cocos2d objects, and they are working OK in SD and HD
- I've tested the CCFileUtils hook, and it is working OK.

Regarding the suffix, the default one is "-hd", but you can modify it from ccConfig.h.

If something is not working, or it is not clear, please let me know.

For the moment everything is in the "retina-display" branch, but I'll merge it soon to the "develop" branch.

Posted 1 year ago #
finder39
Member

awesome can't wait for finished stuff :)

Posted 1 year ago #
riq
Key Master

the "retina-display" branch was merged into "develop" branch, that's why the I've deleted the "retina-display" branch. From now on, in order to test this feature use the "develop" branch.

Posted 1 year ago #
finder39
Member

so it will be in the next release? nice!!!!

I wish i could have contributed more to his.

On a side note, I am making a nice shell script for making audio converting a lot easier that i plan on sharing when complete.

Posted 1 year ago #
sabshire
Member

@riq just went to get it and found out you merged it... nice! Going to test it out. Thanks!

Posted 1 year ago #
jptsetung
Member

I agree on the 2 different config files (bitmap fonts or sprite sheets). And with this method, you still can use the same config files + double bitmap size, by duplicating the sd config files and reanming it with -hd suffix.

It seems that things have been done correctly for retina display support now.

Now I'm thinking about the post of @slipster216 (1 page ago) about the iPad. Being able to display HD graphics in the x2 mode in iPad is deinitely great. But that's true that it would have a much important commercial impact if the app was tagged "universal". People will not be aware that an app will show hd graphics on tehir iPad without this. An easy mechanism to make our hd apps universal would be simply awesome. BUT, I'm not totally sure Apple would accept this.

Posted 1 year ago #
finder39
Member

just curious, with this -hd thing, i can have some that have hd fiels and some that do not correct? and it will automatically use the correct fiels in the correct situations?

Posted 1 year ago #
riq
Key Master
@jptsetung I guess you'll be able to do that by modifying a few lines on the director... perhaps doing only this is enough:
```
__ccContentScaleFactor = 2;
```
@finger39: Sorry, I didn't understand your question. Could you develop it a bit further ?

@all: I still need the following files. If someone has them, could you send them to me ?

- an SD tmx map (both the .tmx and .png files)
- the same TMX map, but in HD (both the .tmx and .png files)

- an SD Zwoptex spritesheet (both the .png and .plist files)
- the same Zwoptex spritesheet, but in HD (both the .png and .plist files)

Also, it would be great if you allow me to include them in the cocos2d distribution.

Thanks.
Posted 1 year ago #
finder39
Member

@riq ya im sorry. say in my game i have a background image (bg.png), and a sprite (sprite.png)

if i include a bg-hd.png in my resources, but do not include a aprite-hd.png, will it grab the hd one of the background and use the standard one of the sprite? or do i need to include -hd of all resources if i want to work with it?

Posted 1 year ago #
riq
Key Master
@finder39: when Retina Display is enabled, it will try to load files with the "-hd" suffix. If the file doesn't exist, then it will try to open the file without the suffix.

Suppose that you have these 3 files in your game:
sprite.png
sprite-hd.png
sprite2.png

If you are in retina display mode then:
```
// it will open sprite-hd.png because your are in retina display mode, and the file exist
CCSprite *sprite = [CCSprite spriteWithFile:@"sprite.png"];

// it will try to open sprite2-hd.png. But it doesn't exist, so it will use sprite2.png
CCSprite *sprite2 = [CCSprite spriteWithFile:@"sprite2.png"];
```
Posted 1 year ago #
finder39
Member

@riq awesome!!!!

one more question. would i be able to ahve a Default.png, Default-hd.png, and a Default@2x.png or would that cause issues?

that way i can have the actual splash be a retina display image as well

Posted 1 year ago #
Matt Rix
Member

Hey Riq, sorry, I don't use TMX or Zwoptex spritesheets, so I won't be able to help there. I'm sure someone here will have some though.

Posted 1 year ago #
Dragyn
Member

@riq: In your example, just to clarify, then sprite2 (the lo-res image, loaded in a high-res context) would be the original pixel size, not automatically doubled. Is that correct? Or do you plan to have it double the lo-res images if you're in retina display mode so they would be the same physical size on screen?

Posted 1 year ago #
jordo
Member

Zwoptex spritesheets work.

Posted 1 year ago #
hima
Member

So does this still work with 99.4 like the topic name suggest? Or the retina display support is now implemented in the develop branch of cocos2d?

Posted 1 year ago #

RSS feed for this topic

« Previous 1…345…7 Next »

Reply »

You must log in to post.