iPhone 4 version on iPad « cocos2d for iPhone

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

iPhone 4 version on iPad

(9 posts) (6 voices)

Started 1 year ago by johannth
Latest reply from johannth

Tags:

johannth
Member
Hi you all!
Because of budget constrains we don't have money or time to develop a specific iPad version of our game but we would nevertheless be able to create an universal application.

I was thinking of using the -hd graphics of the iPhone 4 version and display the game in a 640x960 frame on the iPad and making the device think the window size was 320x480 in points.

I used the following code to reframe the view:
```
CGRect bounds = CGRectMake(64, 32, 2 * 320, 2 * 480);
EAGLView *glView = [EAGLView viewWithFrame:bounds pixelFormat:kEAGLColorFormatRGB565 depthFormat:0];
```
and tried setting contentScaleFactor as 0.5 on the iPad to fake the winSize but then the device loads the low resolution graphics

I was wondering if someone could nudge me in the right direction or show me how to force the loading of hd graphics on the iPad. Or maybe suggest a different approach...

Thanks
Jóhann
Posted 1 year ago #
TBBle
Moderator

contentScaleFactor == 2.f is the test cocos uses to decide to use -hd assets instead, as I recall so you either need to change cocos2d or build your EAGLView setup such that that is true.

There was also an experimental branch of cocos2d ("iPadHD" I believe) which attempted to load the -hd assets when an iPhone app was running in 2x zoom on an iPad. Probably not what you want, but it might be an easier approach than a universal app for you.

Posted 1 year ago #
robseward
Member
This is a less simple solution but I'm using a singleton to store all the image names. That way I won't have to touch the cocos codebase. Each scene gets its own dictionary of filenames.

Here's the code: http://gist.github.com/810493

I use it like this:
```
NSDictionary *imageNames = [[ImageNameManager sharedManager] mainMenuDict];
groundSprite = [CCSprite spriteWithFile:[imageNames objectForKey:@"ground"]];
```
And it uses DeviceDetection.h, which I got from here: http://www.cocos2d-iphone.org/forum/topic/8107
Posted 1 year ago #
Nico...
Member

have a look at CCFileUtils.m (in the Support folder), and specifically getDoubleResolutionImage:
that's where the decision is made to load hd files or not.
If you decide to implement your own naming convention, don't forget to look at
ccRemoveHDSuffixFromFile too.

I've been tweaking those in order to load -sd files when running on < iphone4 devices,
and it works fine !

Posted 1 year ago #
beyondtool
Member

Helpful ideas. Our app has just been rejected because it does not adhere to ipad interface guidelines. Thats a real challenge for us as we dont even have an ipad to test with! All apps must work in the ipad now to Apples satisfaction it seems even if you dont want to support it. Our biggest problem is that game elements appear half onscreen and off screen. I assumed that the ipad would just place a window around the app, but instead it is showing elements off the screen. We are looking for the fastest fix.

Posted 1 year ago #
sabshire
Member

@robseward, I like the idea. Thought about converting this for use with spritesheets? Seems like it would be straightforward. I may do that. If so, I'll post the code back here. I'm working on a game that I want to work on iphone 3gs, iphone 4, and ipad, and I want to use the full scale of each device.

Posted 1 year ago #
TBBle
Moderator

@beyondtool: If your app is marked as iPhone-only, then it should have been running in a frame on the iPad, and not expected to adhere to the iPad UI guidelines. If you've made it universal, then you'll need to support the iPad correctly.

So is your app universal, or has something else gone badly wrong?

Posted 1 year ago #
johannth
Member

I've managed to load the -hd graphics by messing with getDoubleResolutionImage but I still haven't figured out how to fake the point calculations. I would prefer to simply work in one coordinate space (320x480) but when creating a framed view as above the point calculations are wrong. Should I mess with the CC_RECT_PIXELS_TO_POINTS and CC_RECT_POINTS_TO_PIXELS macros?

The best case scenario would be to treat the iPad as a iPhone4 retina enabled device with the main view as a 640x960 frame (320x480 points) with a subview underneath drawing some simple border to fill up the remaining space.

Posted 1 year ago #
johannth
Member

I'm still having problems with changing the point coordinate system. I don't want to redefine CGPointMake and CGRectMake but it almost seems like that is the only "easy" way to fake the new coordinate system on the iPad.

To redefine my problem:

I've developed the game with iPhone4 in mind by creating -hd graphics and working in the point coordinate space of 320x480. I want to create a very simple iPad version by redefining the EAGLView so its boundary is (64, 32, 640, 960), loading the -hd graphics but keeping the point coordinate system to 320x480.

I've tried messing with contentScaleFactor and I've tried creating a custom base scene with scale = 2 but no approach is optimal.

Any ideas?

Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.