Hello Guest

Author Topic: SDK version for 2D Toolkit  (Read 9190 times)

MRC

  • 2D Toolkit
  • Newbie
  • *
  • Posts: 4
    • View Profile
SDK version for 2D Toolkit
« on: May 17, 2012, 11:48:32 pm »
Hello,
I'm just bought 2D Toolkit for Unity (I have latest version for both, Unity and 2Dtk) and try to arrange a test project building a couple of SpriteCollection and putting just one Sprite on the scene, using an orto camera setting to 1.

My Mac has xCode 4.2 and I can build project from Unity only setting SDK 5.0 or higher.
Unfortunately, this test project desn't run on my iPhone 3G, while it runs fine on my iPhone 4.

launching it on iPhone 3G it crashs after Unity startup screen.
In xCode I get this kind of error:

OS Version:      iPhone OS 4.2.1 (8C148)
Report Version:  104

Exception Type:  EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00000000
Crashed Thread:  0


Does 2D toolkit need a minimum requirement and it doesn't run on iPhone with 4.x iOS installed?
It could be a problem...

thanks for your support

Marco (Italy)

unikronsoftware

  • Administrator
  • Hero Member
  • *****
  • Posts: 9709
    • View Profile
Re: SDK version for 2D Toolkit
« Reply #1 on: May 18, 2012, 12:24:17 am »
It definitely did work the last time I tested on iPhone3G but that was a long time ago (before Xcode4). Does a basic Unity project with a box or something like that work on the iPhone? 2D Toolkit doesn't have any minimum requirements and doesn't do anything special, and it should run on iPhone3G, if Unity still runs properly on it...

MRC

  • 2D Toolkit
  • Newbie
  • *
  • Posts: 4
    • View Profile
Re: SDK version for 2D Toolkit
« Reply #2 on: May 18, 2012, 07:56:41 am »
Hello,
based on your reply and my other App w/o 2Dtk that running fine on 3G I spent more time and solved the issue.
Maybe yesterday night was too late for all tests...

I compile my 2Dtk test build using 4.2 for SDK version and setting also 4.2 for iOS target version (instead of unknown) and everithing runs fine also on 3G.

Just a couple of last questions:
1- can I delete (or not import at all) the 2Dtk demo folder without any bad issue?
2- how I can import 2Dtk in my project "later", I mean if I want add it in my old project? Must I impot it only by asset store?

Thank you again.
Marco (Italy)

unikronsoftware

  • Administrator
  • Hero Member
  • *****
  • Posts: 9709
    • View Profile
Re: SDK version for 2D Toolkit
« Reply #3 on: May 18, 2012, 09:15:01 am »
Good to hear it works.

1. Should be fine (I think). I used to test it, but I stopped a while ago.
2. You can either import it through the asset store, or register your copy and grab the unitypackage from here, whichever you prefer.

MRC

  • 2D Toolkit
  • Newbie
  • *
  • Posts: 4
    • View Profile
Re: SDK version for 2D Toolkit
« Reply #4 on: May 18, 2012, 09:37:38 am »
Good to hear it works.

1. Should be fine (I think). I used to test it, but I stopped a while ago.
2. You can either import it through the asset store, or register your copy and grab the unitypackage from here, whichever you prefer.

Just registered, thanks.

I would delete Demo root to get the minimum App size possible.
About that do you advice to make few big atlas or many little/medium atlas?

thanks
Marco (Italy)

unikronsoftware

  • Administrator
  • Hero Member
  • *****
  • Posts: 9709
    • View Profile
Re: SDK version for 2D Toolkit
« Reply #5 on: May 18, 2012, 10:03:45 am »
The demo project won't get included when you make a build, so no need to worry about that.
Depends on your definition of big, 2048x2048 atlases are perfectly fine.

dakeese

  • 2D Toolkit
  • Jr. Member
  • *
  • Posts: 50
    • View Profile
Re: SDK version for 2D Toolkit
« Reply #6 on: May 27, 2012, 02:34:50 am »
Is 2048 for sure safe for use on Android?

Thanks.

unikronsoftware

  • Administrator
  • Hero Member
  • *****
  • Posts: 9709
    • View Profile
Re: SDK version for 2D Toolkit
« Reply #7 on: May 27, 2012, 02:55:15 pm »
Depends on the device. Some devices don't support 2048x2048.
Actually, the iPhone 3G doesn't support 2048x2048 either - my recommendation was targeted towards newer devices.