iPhone4 problems with hi-res support

cocos2d for iPhone » Programming » cocos2d support (graphics engine)

iPhone4 problems with hi-res support

(16 posts) (8 voices)

Started 1 year ago by graphG
Latest reply from smasher

Tags:

graphG
Member

Hello,

Apologies if this has been covered (I can't find a definitive answer when searching).

I have a problem, when trying to support the retina display in .99.4.

I create an EAGLView as per Riqs documentation and all seems well i.e

/
EAGLView *glView = [EAGLView viewWithFrame:[window bounds]
pixelFormat:kEAGLColorFormatRGBA8
depthFormat:GL_DEPTH_COMPONENT24_OES
preserveBackbuffer:NO];

However....

I detect the hi-res screen by examining the UIScreen scale property. It correctly identifies as 1.0 for iPad and old gen iPhone and identifies as 2 for iPhone 4 hi-res. This all seems to work as expected and allows me to change my layout as required (and set the GLViews content scale factor).

The problem is that the Window bounds are still set to 320x480, this makes sense and is to be expected, however the problem occurs when I try and adjust the GLView bounds.

if I multiply the [window bounds] by the content scale factor before creating the GLView my content is displayed offset. it seems to be offset by 480px vertically. If I adjust the bounds to have an origin of 0,-480 then my content is perfectly scaled and displays correctly.

What am I doing wrong? Surely I shouldn't have to move the GLView frame origin? and if so why is it moved by exactly -1.f*screen.height?

Has anyone got this working on an actual device? I am only able to test in the simulator at the moment...

Thanks in advance.

Posted 1 year ago #
klicktock
Member

I submitted my game yesterday and had it approved today. I just grabbed V0.99.4-rc2. With that it's already been set up. You don't really have to do anything other than set the content scale factor as you described.
Just create a new project from the V0.99.4-rc2 template, then grab the appdelegate as described.

Posted 1 year ago #
graphG
Member

Thanks @klicktock

I'm not quite sure that I understand:

In the simulator my content is cropped. i.e I have a 320x480 surface rendered bottom left, so if I position something screen centre it gets cropped. Unless I adjust the EAGLView frame.

Setting the content scale alone does not adjust the drawable surface. i.e what if I want to draw at 321,481. without the frame resize,re-position I cannot see anything past 320,480.

Am I missing something obvious?

Thanks for your help.

Posted 1 year ago #
CraigVella
Member

All I did for my game to update to hi-res is change the content scale factor. Then depending if it's iphone4 or not load the correct graphics, and made some Macros called DYNAMIC_PADDING(x) to automatically double some static numbers i had going on depending if it's iphone4 as well.

Posted 1 year ago #
graphG
Member

This is weird, are you guys testing on the device and or simulator?

Posted 1 year ago #
graphG
Member

Hopefully this screenshot will help explain my problem:

If I just set the contentScaleFactor to 2 then my glview is centred middle bottom. Shouldn't it be centered bottom left allowing me to use the full 960x640 res?

Posted 1 year ago #
jandrad
Member

Are you setting the EAGLView contentscalefactor or the director's?

Posted 1 year ago #
graphG
Member

Hi @jandrad

I'm setting it on EAGLView

I've just tried it on CCDirector and it works, so thank you very much.

Just so I understand this correctly though, where should I be setting it, clearly Director works, but should I also set it on the GLView?

Thanks ever so much for your help.

Posted 1 year ago #
jandrad
Member

When you set it to the Director it also sets it to the EAGLView. You can check this in the CCDirector class.

Posted 1 year ago #
graphG
Member

Awesome, thanks dude.

Posted 1 year ago #
blake8086
Member

I'm still running into a similar problem. I couldn't actually find documentation on how to use contentScaleFactor, so I just added this to my code:
[[CCDirector sharedDirector] setContentScaleFactor:0.5];
Like graphG, my content is all squished down into the lower right.

Posted 1 year ago #

blake8086
Member

Ok, I read more code examples on these forums and changed to:

- (void) applicationDidFinishLaunching:(UIApplication*)application
{
	CC_DIRECTOR_INIT();
	CCDirector *director = [CCDirector sharedDirector];
	[director setContentScaleFactor:[[UIScreen mainScreen] scale]];
	[director setDeviceOrientation:kCCDeviceOrientationLandscapeLeft];
	[director setDisplayFPS:YES];

	EAGLView *view = [director openGLView];

	[view setMultipleTouchEnabled:YES];
	[CCTexture2D setDefaultAlphaPixelFormat:kTexture2DPixelFormat_RGBA8888];

	//"Smooth transition from Default.png"
	CCSprite *sprite = [[CCSprite spriteWithFile:@"Default.png"] retain];
	sprite.anchorPoint = CGPointZero;
	[sprite draw];
	[[[CCDirector sharedDirector] openGLView] swapBuffers];
	[sprite release];

	[[CCDirector sharedDirector] runWithScene:[IntroScene scene]];
}

Now I have some of it working and some of it is weird. Is there a recommended way to address screen coordinates in high-res mode? I feel like some of my sprites are anchored with a 480x320 coordinate system and some with a 960x640, but I can't tell why.

Posted 1 year ago #

smasher
Member
You could set the scaling factor for your scene and keep using old (320x480) coordinates, right?

I set contentScaleFactor when the app starts, then I did this in my scene init:
```
// get director, scale this scene so we can use small-win coordinates for everything
CCDirector *director = [CCDirector sharedDirector];
self.scale = [director contentScaleFactor];
self.position = ccp(0,0);
self.anchorPoint = ccp(0,0);
```
It's working great so far. You will still get strange behavior if you're relying on window.size, which will now be larger, or the contentSize of your sprites. The contentSize will change when you load big vs small art.

EDIT: if your touches no longer register correctly, make sure you're using convertTouchToNodeSpace and not convertToGL. convertToGL will not scale the coordinates.
CGPoint location = [self convertTouchToNodeSpace:touch];
Posted 1 year ago #
quano
Member

// get director, scale this scene so we can use small-win coordinates for everything
CCDirector *director = [CCDirector sharedDirector];
self.scale = [director contentScaleFactor];
self.position = ccp(0,0);
self.anchorPoint = ccp(0,0);

Does that really work? Wont the high-res images get too big if you do it like that?

Posted 1 year ago #
Joey Pepperoni
Member

I managed to get it working last night. Seems to be okay in both iphones using the @2x suffix on all resources.

http://www.cocos2d-iphone.org/forum/topic/7922#post-46288

Posted 1 year ago #
smasher
Member

// get director, scale this scene so we can use small-win coordinates for everything
CCDirector *director = [CCDirector sharedDirector];
self.scale = [director contentScaleFactor];
self.position = ccp(0,0);
self.anchorPoint = ccp(0,0);

Does that really work? Wont the high-res images get too big if you do it like that?

Yes, if you load a high-res image you'd have to set its scale to 0.5f. It'll still use the whole high-res texture when rendering. That should be easier than mucking with two systems of coordinates, though. You'll only care about the screen size when you're adjusting the scale of a sprite.

Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.