I am new to VR applications design and development and need your expert opinion. Will Ocusdk work on google cardboard, after specially with a release of oculus mobile sdk ( which is used in samsung vr-gear) or cardboard only works with Cbsdk? Thanks in advance.
As per the license, you cannot use the oculus mobile sdk for cardboard apps.
The Oculus Mobile SDK may not be used to interface with unapproved commercial virtual reality mobile or non-mobile products or hardware.
link to the license
Related
Would Google VR SDK work on Samsung Gear VR (Oculus) or am I bound to Oculus SDK? Or are there any other alternatives (preferably open-source)
Google's VR SDK will work fine on devices that you plug into GearVR with a normal cardboard headset. If you want to use the GearVR headset as a cardboard alternative, then it is also possible - you have to disable Oculus home and GearVR service.
This is said to work: CB Enabler for Gear VR (did not check by myself)
While you'll still need to have the Oculus SDK in your project, a library like VRTK can help you abstract away a lot of the pain of working with multiple headsets. It supports both Daydream and Oculus (as well as a host of others).
I would like your input, so that i can make a good decision on whether I should use Cirrious MvvmCross or Galasoft MVVM Light Toolkit?
I am going to be developing 2 applications using Universal Apps (Windows Phone 8.1 and Windows 8.1) in XAML/C#. I am not new to developing windows phone and windows 8 apps however i am new to developing MVVM apps and thus would greatly appreciate you into in this?
Should i use Cirrious MvvmCross or Galasoft MVVM Light Toolkit, (should I use something else) what are their strengths and weakness?
Thank you for your time and your help!
Is there an added benefit for using MVVMCross in your app? Will you be developing an Android or IOS APP? If the answer no, then there is no need for MVVMCross or such. The new WinRT API should have 95% of what your app needs. You can add a portable class library to the solution and share third party libraries between the apps as well.
Good Luck.
MvvmCross is the best way to cross-platform work with xamarin for exemple but you can work with it just for create windows and windows phone app.
MvvmLight is really good to implement mvvm pattern in your project.
Just for create ms app, you should work with mvvm light.
MvvmLight does not have support for iOS yet. Support for Android was added in version 4.0 in May 2014. More info here : http://blog.galasoft.ch/posts/2014/05/mvvm-light-v4-4-with-xamarin-android-support/
MvvmCross does not support Universal Apps (yet).
More info here :https://github.com/MvvmCross/MvvmCross/issues/656
A ray of hope here : http://www.microsoft.com/en-gb/developers/articles/week05jun14/mvvmcross-support-for-universal-apps
Looks like you have two options -
MvvmCross allows you to share code with Windows Phone and Windows 8 also. Just not via Universal App project. If the objective is to share code - you can go with MvvmCross. You wil get your WinPhone and WinStore apps along with Android and iOS also.
Start with Mvvmlight on Universal App and hope for Xamarin.iOS support soon.
http://blog.galasoft.ch/posts/2014/04/building-a-universal-application-for-windows-phone-8-1-and-windows-8-1-with-mvvm-light/
I want to develop an cocos2d-x game for android & iphone. I don't know from were to start my development. I know there is an template available for iphone, but after creating it on iphone how build it for android platform?
And what if i want to develop game form the eclipse itself rather then developing on iPhone and then migrating to android
I had already tried various tutorials of ray wenderlich, tutorial on cocos2d-x.org, http://paralaxer.com/cocos2d-x-project-setup/, http://www.multigesture.net/articles/how-to-setup-cocos2d-x-windows-and-android/, http://www.jesusbosch.com/2012/06/how-to-set-up-android-and-win32-cocos2d.html, http://gameit.ro/2012/01/creating-an-iphone-and-android-cocos2d-x-hybrid-project-updated/
From all of the above tutorials i am not able to get any proper solution.
Also tell me should i have to develop(code) on iPhone and then build for android?
Thank You in advance
simple :
-> Framework : cocos2d-X
-> Editor : Xcode
-> Language : C++
once you complete your Game for iphone then You can port your this game to any platform like Android or Windows. you already have all useful links . still follow this :
Setting_up_Android_Development_Environment_on_Mac_OSX :
http://www.cocos2d-x.org/projects/cocos2d-x/wiki/Setting_up_Android_Development_Environment_on_Mac_OSX
How to port your project to win32,iPhone and Android
http://www.cocos2d-x.org/boards/6/topics/3001
Integrate Cocos2d-x (C++) into an Android application (Java)
http://jpsarda.tumblr.com/post/26000816688/integrate-cocos2d-x-c-into-an-android-application
-> You just have to convert this native code using some JNI or say NDK .
-> using Cocos2d-x u can Develop games on Windows, Mac OS and Linux .
Personally if you are deploying to multiple platforms your best bet is to use a gaming engine. Currently Unity3D, UDK, and newly released Havok's Anarchy Engine supports deployment to these platforms and more. This way you can develop once and deploy to multiple locations. Cost is free for Havok, UDK if you are a small company, and I believe Unity3D now has free licensing to iOS and Android for their non-Pro versions.
I think going this route is far more promising than using cocos2d
The method I use is to use the templates for both iOS and Android that create projects for Xcode and Eclipse respectively. When you have this, you remove the Classes and Resources folders in for example the Eclipse project and replace those folders with links to the Xcode folders Classes and Resources.
What you now have is two projects, one for iOS and one for Android, that both use the same C++ code and resources. You can now choose which of Xcode and Eclipse that you prefer to use when developing and just switch to the other to compile for that platform and do testing and releasing there.
Hope that helps. :)
Look in cocos2d-x folder under /tools/project-creator/create-project.py , you should run that and it will create project for many platforms already set-up and from there you can just code in XCode, and platforms will share same source code.
I was curious to know what development tools do Xbox 360 and PS3 game developers use (I know that there are expensive SDK's to access professional development on these consoles).
So, do Xbox 360 devs use Visual Studio? And what version?
And what about PS3?
And what is the graphics API used on the PS3? Is it a variant of OpenGL?
Thanks.
Professional XBox 360 development is done with Visual Studio.
PS3 uses a proprietary compiler and IDE developed by a Sony subsidiary.
There is an OpenGL-like graphics library available on the PS3, but most major games use a lower-level API that speaks directly to the graphics hardware instead.
for ps3 development you need to buy ps3 dev kit, which is cost around $2000. it includes hardware and software for development. the software includes sdk where you can code in c++ ( or some other languages sony specifies ). and the graphics library to use is PSGL ( PlayStation Graphics Library ). that is a combination of OpenGL-ES and the CG programming of NVIDIA. and later to release the game you need to become sony licensed developer. for that you should contact sony through mail. that license is given only to developers or developer team which is having enough previous understanding in game development.
and now (around the feb '12 ) sony is going to release playstation suite by which developers can able to develop applications and games for playstation certified devices ( ps3, playstation vita, some android mobiles, etc ). there you have to use c# to code. but afaik it will not be a better sdk for full fledged AAA game development for ps3. Because it uses a virtual machine which translates the code dynamically to the underlying hardware platform where it runs, which may affect the performance. and the sdk is now in closed beta test for developers in us, uk, japan. you can get results regarding this from google with query 'playstation suite closed beta'. and its beta is expected to be released in the coming feb with the release of playstation vita.
for microsoft xbox 360 better place to start is xna game development. and after some time getting better knowledge in game development, you can approach microsoft to get the sdk for xbox 360 game development. the games developed with xna will not be much faster as games developed with the sdk given by microsoft. but getting the sdk for xbox is also having lots of procedures as getting sdk for ps3. the xna coding will be in c# with directx and direct3d as graphics library.
and later news tells that microsoft is migrating to metro style apps from xna. metro is going to be released with windows 8. now its beta version is bundled with windows 8 beta release. and microsoft doesn't show any support for xna in future ( it is not clear still ). now xna is only available for dircetx9. but metro is going to be released with directx11. microsoft didn't give any word about xna support in future. in metro apps, you need to be code in C++ with directx and direct3d graphics libraries.
Check CryEngine 3 Free SDK. http://mycryengine.com/
Allows you to develop for PC, Xbox 360 and PlayStation3.
The Unity3D engine also ports to PS3, XBox and Wii :]
You need Playstation SDK or Xbox360 SDK. Both include hardware and software. Normally only companies can gain them and it costs a lot of money. For Xbox360 you can also use XNA.
in response to what somebody said above, are we not all past the JIT compiler debate.
with proper coding techniques, microsoft and other companies have produced virtual machines which are far more powerful than anybody gives them credit for.
back in the day when we have VERY LITTLE memory to work with, C++ was a video game development standard due to the fact that we could directly manage our own memory when needed, and working with a lower level programming language just seemed "right"
i still enjoy developing both games and software in C++, but there is no reason that this playstation SDK which is using a JIT compiler and C#, will not be able to produce efficient code for developing video games.
I am building an enterprise application using HTML5 for Blackberry OS 6.0. I am planning on using PhoneGap for developing the application. I found out that Blackberry also has something similar called WebWorks.
What are the differences between WebWorks and PhoneGap?
PhoneGap-BlackBerry-Widget uses the BlackBerry Widget SDK to support BlackBerry OS 5.0 & 6.0. WebWorks is basically Widget SDK 2.0 and it is intended to support OS 6.0 specific features.
The advantage of using PhoneGap-BlackBerry-Widget over WebWorks is that you can port your application to other platforms that are supported by PhoneGap.
You can still port an application that was written using WebWorks/Widget SDK, but you will need to switch out the BlackBerry-specific JavaScript bindings for the PhoneGap JavaScript bindings (e.g. invoking Geolocation, contacts, or accelerometer).
Looks like WebWorks is specifically for BlackBerry while PhoneGap is attempting to support multiple mobile platforms.
I haven't looked too deeply into WebWorks, it appears to be more tightly integrated with a specific device, a Blackberry
WebWorks is a specific development tool managed by RIM for BlackBerry, while PhoneGap is in the MEAP (mobile enterprise application platform) space where they represent the next generation of mobile development. You develop your app with PhoneGap and it helps you to deploy across all major platforms such as iPhone, Android, Windows Mobile and BlackBerry. If you're a developer then it opens the doors to more phone models and increased opportunity for app sales.
webwork vs phonegap
both are used for build application .using webwork u get for feature for specially blackberry....using phonegap u can use same code for multipal phone like iphone,android..
but i prefer webwork because phonegap add unwanted code to your applicatio due to application very slow ....phonegap + wework in blackberry 5.0 take too much load...it's min size is around 600 kb......
so for blackberry webwork is better than phonegap
One issue to consider is testing and compiling applications.
When testing on devices and simulators it is possible to compile/sign once and access/edit your JavaScript and HTML5 from a remote location, such as the SD Card or a local server. While PhoneGap and WebWorks are both using JavaScript to access native functions, I have found the 'compile once' method doesn't seem to pick up and utilise PhoneGap - this is also the case with the Ripple emulator. In my experience, using PhoneGap requires multiple, time-consuming compilations and launches when testing an application. If testing on a Blackberry device, you need to factor in the time it takes to have your app signed prior to each test and the time it takes for the device to reboot. I'm talking 2+ mins on a simulator or 4+ mins on a device, per each change to your code.
I'm working with webworks for Blackberry and phonegap for iPhone. Not sure whether the problem is with webworks or underpowered handsets but we've had to spend a lot of time ripping features out of the webworks app to get any kind of robustness or performance when running on the device. Static google maps and thumbnail photos had to go.
All webworks apps on a handset share the same pool of memory, about half of the memory available to the BB browser. Webworks also leaks memory. There's a thread a year old on the webworks forum about the memory leaks and no solution forthcoming from Blackberry, just "workarounds". We had to alter the webworks sdk to make the garbage collection more aggressive to stop the app running out of memory all the time. But if other webworks apps are running on the handset and haven't had this GC tweak you will still get grief with memory.
Don't know if phonegap is any better than this but it'd have to go some to be worse than webworks.
If you want to do a webworks app keep the design simple, package all the graphics and assets in the deliverable (we were trying to get icons from an api but have ended up storing them base64 encoded in localStorage) and get it onto a handset asap so you don't waste time adding features that the handset can't cope with.
To sum up, webworks is pretty poor.
PhoneGap : is an application with a webview control that renders your HTML5 and JS. PhoneGap has diferent versions or say release for different platforms like Android, iOS, BB, WP8 etc.
WebWroks : is conceptually the same thing as PhoneGap just that it is owned and developed by Blackberry (Previously RIM) themselves.
Also one most important thing in the context of the question is that, for Blackberry Phonegap uses WebWorks as its base, that is why while developing PhoneGap Apps for blackberry you need to download WebWorks SDK first, the build process is also the same as WebWorks so the benefit of using Phonegap for balckberry is that the same HTML5 + JS Code that you used for say Android will work on Blackberry as well.
However BB OS 7 and below do not have the best WebView Control, BB 10 and playbook are MUCH MUCH Better.