proton_issues
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
proton_issues [2012/04/27 18:53] – Updated Linux support parts aki | proton_issues [2013/07/26 13:30] – seth | ||
---|---|---|---|
Line 2: | Line 2: | ||
=== General === | === General === | ||
- | * Is it beta or not? | + | * What version is it? |
- | * RTPack.exe only available for Windows and Linux at the moment, this command | + | * RTPack.exe only available for Windows and Linux at the moment, this command |
* Samples and docs are, how shall we say, lacking. | * Samples and docs are, how shall we say, lacking. | ||
* Proton internally shares all Surfaces/ | * Proton internally shares all Surfaces/ | ||
Line 10: | Line 10: | ||
=== Windows (supported) === | === Windows (supported) === | ||
* True fullscreen modes not supported, but window resizing and alt-enter to toggle a pseudo fullscreen is (stretches to full current resolution) | * True fullscreen modes not supported, but window resizing and alt-enter to toggle a pseudo fullscreen is (stretches to full current resolution) | ||
- | * Supports three audio systems, Audiere (default) | + | * Supports three audio systems, Audiere (default), FMOD, and SDL_Audio (SDL_Audio only tested with WebOS builds). |
* If _CONSOLE is defined, can be used to create console only apps. (They also work in linux, good for writing a server..) | * If _CONSOLE is defined, can be used to create console only apps. (They also work in linux, good for writing a server..) | ||
- | * DirectX gamepads supported through GamepadManager | + | * DirectX gamepads supported through GamepadManager |
+ | * Probably supports the iCade too, but untested | ||
+ | * Define **RT_WIN_MULTITOUCH_SUPPORT** to support multi-touch input. | ||
+ | * Define **RT_WIN_USE_APPDATA_SAVE_PATH** if you want Proton' | ||
=== Mac OS X (supported) === | === Mac OS X (supported) === | ||
Line 20: | Line 24: | ||
* 64 bit builds might have issues, I'd stick to 32 bit for now. | * 64 bit builds might have issues, I'd stick to 32 bit for now. | ||
* Window rescaling/ | * Window rescaling/ | ||
+ | * No gamepads supported | ||
- | === iOS (supported) | + | === iOS (supported) === |
- | * iPod Touch/ | + | |
+ | * iPod Touch/ | ||
* Supports three audio targets, AudioManagerDenshion (Recommended), | * Supports three audio targets, AudioManagerDenshion (Recommended), | ||
* Only plays .wav and .mp3 formats when using AudioManagerOS and AudioManagerDenshion. | * Only plays .wav and .mp3 formats when using AudioManagerOS and AudioManagerDenshion. | ||
* Supports 60beat gamepad through GamepadManager. | * Supports 60beat gamepad through GamepadManager. | ||
+ | * AudioManagerDenshion gotcha - music MUST be .mp3 or it breaks sfx. Will change this to assert if | ||
+ | * Supports IAP - you must have RT_IAP_SUPPORT defined and InAppPurchaseManager.mm added to the project (see RTAdTest for an example of use) | ||
+ | * If RT_DISABLE_RETINA_ON_IPAD is defined project wide, iPad3 will run at iPad1 res instead of retina (useful if you don't want to update your GUI to the big screen or just want an FPS boost) | ||
+ | |||
+ | If you get a "dyld: Symbol not found: __NSConcreteGlobalBlock" | ||
+ | | ||
=== Android (supported) | === Android (supported) | ||
- | * Precompiled headers not setup, so compiling is slow | ||
- | * Multi-touch automatically enabled on newer devices, but keep in mind some screen HW like Nexus Ones don't support " | ||
* Only plays .wav and .ogg audio formats. | * Only plays .wav and .ogg audio formats. | ||
+ | * If you tell it to play an .mp3, it will convert the file extension to .ogg automatically in AudioManagerAndroid. | ||
* 2D Particle system is slow, the iOS version uses point sprites but they didn't work on Android so it's using a fallback method at the moment. | * 2D Particle system is slow, the iOS version uses point sprites but they didn't work on Android so it's using a fallback method at the moment. | ||
* Doesn' | * Doesn' | ||
- | * If a header changes, you should run rebuild.bat (Clean.bat | + | * If a header changes, you should run Clean.bat |
* glClipPlane is ignored on a G1 and horribly slow on an Nexus One, avoid. | * glClipPlane is ignored on a G1 and horribly slow on an Nexus One, avoid. | ||
- | * Android In-App-Billing supported through IAPManager, | + | * Android In-App-Billing supported through IAPManager, |
* Tapjoy (ads and currency) and Hooked also supported | * Tapjoy (ads and currency) and Hooked also supported | ||
Line 44: | Line 54: | ||
* Doesn' | * Doesn' | ||
* Touchpad supported. | * Touchpad supported. | ||
- | * IAP supported (on OS 3.0+ devices only) | + | * IAP supported (will be functional |
+ | * No longer being developed as webOS seems to be dead | ||
=== RIM/ | === RIM/ | ||
Line 51: | Line 62: | ||
* Note: Playbook supports only 4 touches at once | * Note: Playbook supports only 4 touches at once | ||
* OnEnterBackground gets incorrectly called at startup, this is because the OS is saying "We got thumbnailed" | * OnEnterBackground gets incorrectly called at startup, this is because the OS is saying "We got thumbnailed" | ||
+ | * Warning: I've had reports that builds I did for the Playbook do not work on the Alpha BB10 devices. | ||
=== Linux === | === Linux === | ||
Line 63: | Line 75: | ||
* Based on 1.7.1 beta (GLES branch) | * Based on 1.7.1 beta (GLES branch) | ||
* The Irrlicht 3D example RT3DApp might not be setup for all platforms. | * The Irrlicht 3D example RT3DApp might not be setup for all platforms. | ||
- | * It' | + | * Irrlicht has been modified so it uses the WindowsDevice for ALL platforms for GL, and the iPhone device for ALL GLES platforms. |
* Irrlicht has GLES 2.X support (?) but until Proton SDK adds GLES 2.X support it can't be used | * Irrlicht has GLES 2.X support (?) but until Proton SDK adds GLES 2.X support it can't be used | ||
* It's been modified to support release/ | * It's been modified to support release/ | ||
Line 69: | Line 81: | ||
* You CAN use Irrlicht' | * You CAN use Irrlicht' | ||
* RTPhysics uses Irrlicht, IrrBullet and Bullet to show 3d physics.. the sample projects are only setup on Win and iPhone I believe. | * RTPhysics uses Irrlicht, IrrBullet and Bullet to show 3d physics.. the sample projects are only setup on Win and iPhone I believe. | ||
- | * | ||
- | === Symbian === | ||
- | * Not yet available. | ||
- | === Browser | + | === Flash === |
- | * A definite possibility through Adobe Alchemy (Flash) or NaCl. Hope to play with this when those technologies mature a bit. | + | * All non-Irrlicht examples are now compiling and running in Flash - although actually the latest Flash player seems to break input slightly so clicks go to the wrong place, need to investigate and update to the latest SDK. But isn't Flash dying now? Not sure if it's worth the time. |
+ | |||
+ | === NaCl or Html5 === | ||
+ | * Thinking about it | ||
=== Windows Phone 7 === | === Windows Phone 7 === | ||
* Only if they ever release a C++ capable NDK. Switching to C# would be more of a rewrite, don't want to do that. | * Only if they ever release a C++ capable NDK. Switching to C# would be more of a rewrite, don't want to do that. | ||
+ |
proton_issues.txt · Last modified: 2018/07/28 21:32 by seth