(09-07-2014, 04:47 AM)talkingmime Wrote: [ -> ]Quote:When it comes to the performance on high-end iDevices, like the iPad Air, the emulator should run at ok framerate, not much different from shield tablet, possibly faster.
I'm all for the port to iOS and would gladly help if I had an iDevice for testing, but you can't seriously think any latest iDevice can stack up against chips like the K1. The latest iPad is pretty powerful, but it's definitely slower in several ways than any of the best Android-sold tablets (namely with overall CPU power and IPC). Their GPUs can't really stack up either. The best performance you'd be getting on any high-end Android-sold device, expect as much as a two-fold decrease in performance on an accompanying iDevice competitor (at least in the near future). The sole reason being that no iDevice is made (to the best they can be) for overall powerful, fast computing. This may change in the next year and so on, but until then the best framerate on the latest iPad/iPhone is going to be not too much greater than on an HTC One.
Its true, there is no iDevice that can compare to the shield tablet right now. In general the k1 will win over the A7 in most, if not all benchmarks(i have 5 videos comparing k1 & A7 on my YT channel). But when it comes to Dolphin its not really the same as many other emulators. Dolphin runs on 2 cores, even if the shield tablet is 4 cores(thats why we will see up to 100% performance increase with the k1 denver, its a dual-core device). The single threaded performance of the A7 is very good(Geekbench 3.0 goes into more details), its not far from, and could even be better than the shield tablet. But the multi-core performance of the shield tablet is noticable higher than the A7, and that will show clearly when using different apps that can take advantage of all the 4 cores.
What i am trying to is that what is more important when emulating dolphin is that the device needs to give as much power as possible with 2 cores to see good framerates, and part the A7 does very good.
(09-07-2014, 08:54 AM)EverythingPortable Wrote: [ -> ] (09-07-2014, 04:47 AM)talkingmime Wrote: [ -> ]Quote:When it comes to the performance on high-end iDevices, like the iPad Air, the emulator should run at ok framerate, not much different from shield tablet, possibly faster.
I'm all for the port to iOS and would gladly help if I had an iDevice for testing, but you can't seriously think any latest iDevice can stack up against chips like the K1. The latest iPad is pretty powerful, but it's definitely slower in several ways than any of the best Android-sold tablets (namely with overall CPU power and IPC). Their GPUs can't really stack up either. The best performance you'd be getting on any high-end Android-sold device, expect as much as a two-fold decrease in performance on an accompanying iDevice competitor (at least in the near future). The sole reason being that no iDevice is made (to the best they can be) for overall powerful, fast computing. This may change in the next year and so on, but until then the best framerate on the latest iPad/iPhone is going to be not too much greater than on an HTC One.
Its true, there is no iDevice that can compare to the shield tablet right now. In general the k1 will win over the A7 in most, if not all benchmarks(i have 5 videos comparing k1 & A7 on my YT channel). But when it comes to Dolphin its not really the same as many other emulators. Dolphin runs on 2 cores, even if the shield tablet is 4 cores(thats why we will see up to 100% performance increase with the k1 denver, its a dual-core device). The single threaded performance of the A7 is very good(Geekbench 3.0 goes into more details), its not far from, and could even be better than the shield tablet. But the multi-core performance of the shield tablet is noticable higher than the A7, and that will show clearly when using different apps that can take advantage of all the 4 cores.
What i am trying to is that what is more important when emulating dolphin is that the device needs to give as much power as possible with 2 cores to see good framerates, and part the A7 does very good.
The bottom line is that ... you're totally right. I was considering doing some preliminary work on an iOS port (I actually just got an iPad Air and iPhone 5) and see if maybe I can get the ball rolling. Note that I probably can't do much of anything without some minor help (from developers, specifically about the JIT/dynarec), some (probably) Objective-C code refreshments, lots of experimenting, and probably Mac OS X. But this whole talk about the new iDevices has genuinely got me interested in this now. So I'll see what can be done from the Android source/ARM dynarec/etc. to try and make the magic happen on iOS.
That would be awesome. The new iPhones were announced today, but no solid info on the new A8, just that it's "faster"
50% faster gpu than the A7 puts it below the K1 be lucky if it even reaches 20fps in gfxbench.
While the GPU is important, Dolphin is more reliant on the CPU, so the 25% faster CPU is most likely not as great as the K1, but we'll have to see the results once the reviews come out
I see what your saying about it not being strong enough for running past 20 fps but that's with ogles isn't it? What if it can run on metal? Like clearly a significant amount more work but it's easier on resources for apple products.
(09-11-2014, 01:36 AM)Masterdj0 Wrote: [ -> ]I see what your saying about it not being strong enough for running past 20 fps but that's with ogles isn't it? What if it can run on metal? Like clearly a significant amount more work but it's easier on resources for apple products.
Up until now low level API'S like metal and mantle have been investigated, but aren't worth the effort.
(09-07-2014, 08:17 AM)KHg8m3r Wrote: [ -> ]Yes, I'm pretty up to date with the other emulators on iOS. Unfortunately all we currently have is speculation and rumors. Last year the 64-bit A7 came out of left field, so who knows what we'll get this time.
And my contract goes up for renewal at the end of October, so I'll be upgrading to a new 2-year contract with the new iPhone 
(yes, I like being in a contract, and yes, I like AT&T. We used to be a Cingular customer, and then merged into AT&T, and haven't had any issues)
I'll learn how to code for iOS and Dolphin just to work on porting.
If your serious about doing it use swift with xcode (so you dont have to learn and use the abomination called coca.) Reason i say swift is everything from the 4s and up is getting ios 8 which migrates from there old api to swift.. (saving u rewrite times.)
https://developer.apple.com/library/prerelease/ios/documentation/Swift/Conceptual/Swift_Programming_Language/GuidedTour.html
^^^ will get you used to changes in swift to make your life easier.
also note your going to want to read some guides on working with json and mantle if you want to go that route with a ios port of dolphin.. Feel free to hit me up as i have had extensive dealing with ios and android for app's and full operating system rebuilds..
(09-11-2014, 05:30 AM)Nintonito Wrote: [ -> ] (09-11-2014, 01:36 AM)Masterdj0 Wrote: [ -> ]I see what your saying about it not being strong enough for running past 20 fps but that's with ogles isn't it? What if it can run on metal? Like clearly a significant amount more work but it's easier on resources for apple products.
Up until now low level API'S like metal and mantle have been investigated, but aren't worth the effort.
They are worth it to people that want to invest in a rewrite of dolphin.. The less overhead we have in emulation the better the end result is..
to bad GX OGL isn't more well documented.. If so it could be easy implemented in native ogl without the need for any emulation. Not sure how much of the WII's and GameCube GX GL is actually emulated in software as apposed to hardware i assume alot of it is not emulated do to the fact most gpu's have very little overhead with there graphics subsystem.
Xcode looks similar to the c++ and java, just different syntax. Shouldn't be too hard to get simple programs built and running, but porting code is another story
Just a thought, but can't you only program for iOS on a Mac?
(09-13-2014, 12:46 AM)KHg8m3r Wrote: [ -> ]Just a thought, but can't you only program for iOS on a Mac?
Yer