iPhone OS4 today

Um ... could we all return to using standard fonts and colors? This thread now looks like a kid's painting (well, kind of a fun change after almost 250 pages ;-) ).

 

Sorry about that.

Since it is too emergent critical for me by project deadline.

 

All Apps keep "open" when you press the home button - that's normal:

http://www.macnews.de/news/27372/verbraucht-ios4-mehr-akkuleistung/

(babelfish it)

 

http://translate.google.com/transla...braucht-ios4-mehr-akkuleistung/&sl=auto&tl=en

 

But if the app save game process in OnApplicationQuit(), it will fail when app is killed in Multi-Tasking bar.

 

You have 2 options:

1. as previously noted, just add UIApplicationExitsOnSuspend to get the old style of quite on touch home button
2. add the applicationDidEnterBackground: method to the generated Xcode project to the AppDelegate and save state then.

Method 1 will not support multitasking and method 2 will work with multitasking/fast app switching.

 

I can only use Method 1, because my Unity is indie version.

 

Thats not true. Indie can go either way.

 

Sorry... I can not understand how to do the Method 2.

 

Instead of offenses and insults, it's much more calm this way =) Lol

 

I don't have the Xcode project folder with me right now so I don't know the exact code needed. What you do need to do though is add the applicationDidEnterBackground: method to the generated Xcode project to the AppDelegate. In that method you can probably just call applicationWillTerminate:. I believe that is how Unity triggers the callback to C# but without Unity in front of me it's hard to say for sure. The only other way it could be done is if Unity uses the UIApplicationWillTerminateNotification but I don't think they do. Someone with Unity in front of them can confirm im sure.

 

@uprise78: Yeah, you don't want to call applicationWillTerminate: as that shuts down Unity, which would defeat the purpose of fast app switching (plus you'd have to restart it again manually).

edit: If you're an Advanced licensee, you can do this little trick I just tried:

Code (csharp):

1. - (void)applicationDidEnterBackground:(UIApplication *)application
2. {
3.     printf_console("-> applicationDidEnterBackground()\n");
4.     UnitySendMessage("Some Game Object", "SomeSaveFunction", "Some message.");
5.     UnityPause(false);
6.     UnityPlayerLoop();
7.     UnityPause(true);
8.  
9.     [[NSUserDefaults standardUserDefaults] synchronize];
10. }
11.  

You'll need to move all of your save code into the "SomeSaveFunction" of the "Some Game Object" (and naturally, that object should exist if you want it to do anything). Not the most elegant solution, but it works for now.

edit 2: Added NSUserDefaults synchronizing since that doesn't automatically happen when applicationDidEnterBackground: is called.

 

@jerrodputman

do you know if this is possible in Unity iPhone basic specifically in Unity3? I know you stated it wont work in Unity iphone basic 1.7. Seems to be a very necessary type of technique for iOS4

EDIT: thanks for the info Jerrodputman

 

I don't know if it works in the current beta (haven't tried it), but I know they're allowing native plugins for all license types in Unity 3. But they've also said they're adding iOS 4 specific stuff as well, so this little trick probably won't be necessary for long.

 

I think you misread. donlien didn't want to take part in fast app switching. Your code will fast app switch which isn't the desired behavior for donlien.

 

Ah, I see. Actually, that still probably wouldn't work (it would just shut down Unity, but wouldn't kill the app). Personally, I'm not sure why anyone wouldn't want to support fast app switching.

 

Did you guys notice HiggyB's comment on Vimeo?

Isn't it a bit weird to put that sort of detail in there instead of unity3d.com?

 

I was hoping to have microphone(and camera) access in iPhone basic, this is great news.

 

I guess it's because Mr. Helgason already stated it on the Unity blog monthes ago ?

 

"... we are exposing native Objective-C usage to both Unity iPhone licenses in 3.0 ..."

Sounds good to me.

 

I mean can you imagine the uproar if they made that a pro-only feature?

And honestly I bet that it is a requirement from Apple that any package of theirs that deploys to the iPhone allows native access. So I would wager they couldn't make it a pro-only feature even if they were so inclined.

 

Anyone have an example of how Unity 3 will implement native Objective-C usage? I mean... will Unity allow for Objective-C "scripts" that will actual have as part of the project or will it simple have an enhanced "plugin" functionality? I hope that it treats objective-c as a first class language in the editor.

 

No go on that. Obj-C calls are still dirt slow through the plugin system.

 

Seriously? How do you know?

 

I have the beta.

 

Its just plugins for all, nothing more.
As such all the stuff you know about plugins applies.

 

Has anyone profiled this to find out where the bottleneck is with regards objective c plugins?

I mean it shouldn't really be all that complex, accessing a library usually is very few assembler calls (just function pointer, move, branch).

 

Unfortunately, it's a bit more complicated than that from my limited understanding. Check out the mono docs: http://www.mono-project.com/Interop_with_Native_Libraries

Jumping from managed to non-managed will always have a performance hit and then you have to deal with not being able to pass back and forth anything more than UTF8 strings, raw data and value types. Throw the fact that it won't work in the editor and you can't debug it into the equation and they are all but useless except in the most dire times of need.

 

Well, that means the calling overhead is slow, wouldn't this mean that if you code a significant portion in Obj-C and call into it through only one call the performance hit is manageable and you have the best of both worlds - a C++ game with a a good editor.
Of course, this is assuming that you can still get through to the data once you are in C++.

Kaj

 

You can debug it in Xcode. It's not a very good debugger, but it works.

 

My take on it is that you should only use the plugins to talk to external accessories and functionality that Unity hasn't exposed.

If you have native code that does something significant than go for it, but Unity docs say that the overhead is so great, that you should try limiting plugin calls to only one per frame. In a game I worked on, I had to make a few per frame, and I didn't see the framerate drop, but it shows how expensive Unity believes the calls are.

I don't think it's viable to code a game inside of a plugin.

I could be wrong. It's happened before.

 

I actually like Xcode/GDB just fine. Please do share how you can debug a plugin. It would make plugins orders of magnitude more useful for me if I could debug them.

 

Hi, now the new iOS 4 has been rolled out and all of us were asked to accept the new TOS 3.3.1/2 agreement before uploading new apps for approval. Has anyone of you got approved by using Unity after accepting the new TOS? Thanks!!!

 

I haven't checked this thread in a while, but it seems to have wandered off topic in the last 50 pages or so. Is there any news about whether or not we can still use Unity under the new Apple TOS? Or has it just become a non-issue?

I'm starting to get the impression, after several months with no news, that we will never get a definitive answer one way or the other. No way we would go this long without an answer, unless no answer is forthcoming. I'm interpreting this non-response from the Unity team as them telling us, "Move along, nothing to see here." That we should just keep doing what we've been doing until or if Apple starts rejecting Unity apps. Which is pretty much all I can do, as I can't just put everything on hold for months for an answer that may or may not ever come.

 

Well, Apple changed their TOS and it looks like Unity is fine (to me at least), but there's no official "you can use Unity" from Apple. So it's still down to interpretation, but personally I'm not worried anymore.

 

Yes, I understand. I have another Unity game submitted on June 21 after I accepted the new TOS. Today I just received the status change notification from Apple, stating that is "In Review". Let's see how it's going....

 

Just set a breakpoint in the Objective-C code. It'll trigger just fine.

 

After seeing this http://www.youtube.com/watch?v=fzza-ZbEY70 I think Unity should support Java.

Heck, if Steven Jobs himself saw this video he'd make sure ipods/iphones would get native Java support ;-)

 

Java? you should be burned alive for even suggesting it. C# is bad enough.

 

Someone didn't watch the video before commenting.

 

good news - iPhone sales numbers are still managing to keep up with the page-count here

 

I saw it last week. I work in the corporate world (.NET) and the entire video could just have references to Java be replaced with .NET. The hammer developer (thinking .NET is the perfect solution for every problem) part in the beginning was pretty funny though. I work with a bunch of them.

 

Great news! my Unity game "3D Island War" submitted on June 21 just received "Ready to sale" from Apple! Share with you all! Unity is the best!!!

 

Has anybody submitted a Unity app made with Unity iPhone Basic (with the "Powered by Unity" logo in the startscreen) under the new TOS ?

I believe that Unity Team has to rethink about this mandatory logo for the Basic users. We are now digging our graves with such an indiscreetness!

 

Me! I submitted it with unity basic under new TOS

 

Wonderful news!

(I am still believing that it would be safer without the Unity logo)

 

@radical - I have set breakpoints in the ide and they don't seem to trigger.

What's your trick?

 

Getting rid of the logo is simple. Even I can do it.

Step 1: Open wallet
Step 2: Pay UT for their hard work and excellent software.
Step 3: There is no step 3.


Terry

 

Java and C# are fantastic, OOP too much for you huh?

Anyway, regarding the video, "Java is the future," it's funny how they're saying that since 1995, re-donkulous.

Also, Java will not get you a girlfriend.