Suggestions

[#1]

I would and many others on this board who develop with Unity 3D would like to see a plugin be created to support Unity created games for Android it should be possible and if the PS Suite SDK team agree's all of us developers can help you guys write it with a simple GUI wouldn't be hard the main function would allow .apk files to be opened in the UI Composer and to set the appropriate API's and C# scripting for Playstation Consoles.

Or to make it simple create a tool to convert .apk files over to the files needed to open in PS Suite..

Also I would and I'm sure many other people who have joined this BETA would like to see some Video Tutorials on how to use the software and also how to develop games and applications with the PS Suite along with some Example Files that you can open up and play around kinda like how Unity3D.com has there software setup you can find tons of tutorials,tools,examples,video's,pdf's on how to use there software PS Suite SDK Provides the software and this forum which has nothing on how to actually use the software people need video tutorials C'mon Sony stop being lazy you want to open your console to both Indy and Pro Developers we need the tools to get us there this software is very new yet at the GDC 2011 Conference you had a few demo's can we get those games and apps as example files...?

Ok another thing I'm wondering about is, is Sony opening there platforms up to the community because the Homebrew Scene has been developing homebrew on the PSP for years along with making there own Custom Firmware Updates like the famous Dark_Alex is this how you end the Homebrew Scene but wouldn't this software make it easier to make Official Firmware Updates that are Hacked in a way of a Custom Firmware that someone created to play pirated games I would think this would be a major issue because to the hackers in the homebrew community your giving them a way to sign everything they create whether it be malicious or not doesn't this concern you...?

[#2]

Please do not do this. I (and I hope most everyone else here) would prefer if time was spent building/maintaining features and producing referencable documentation.

The examples which have been provided give plenty of insight into how many of the relevant APIs should be tied together. I would say that the comments would be more useful globally if they were in english; this is a somewhat minor nit, as the variables and methods have somewhat intuitive naming semantics.

I do not belive that Sony should be responsible for teaching me how to write code or write games. I ask for nothing more than providing thorough documentation and simple examples. If tutorials are needed, they can be provided by the community or some other agency.

[#3]

I got it figured out with Unity 3D....   No need to do any other work Unity will support PS Vita so I ain't trippin because my studio's has a 1st party license..

[#4]

I made some enquiries a few months ago, however Unity hadn't announced Vita support. Has this now changed? And if that's the case do you have costing details NinjaGameStudios? Is the license cost dependant on whether you are developing a boxed title for retail or a digital only title, as it does with PSN vs. PS3. I should really get back in contact with them.

[#5]

Unity will (or does) support the Vita, but probably not PS Suite. That means you'd require a license from Unity and Sony for the Vita specifcally.

I'd like to port the Unity engine to PS Suite, though. Might be a fun project.

[#6]

The Vita title Escape Plan has been created with Unity, so Unity already can be used to author content for the Vita even if not officially.

As for Unity supporting Playstation Suite? Forget that. AFAIK Unity needs more low level access, that's also the reason why they do not support Windows Phone 7. Also with Unity already supporting Android and Vita, there's little reason for them to support Playstation Suite.

[#7]

Unity's engine and library can be rewritten in C#, there's not much about it that needs native code in order for it to be mostly functional (native plugins would be out of the picture for sure). The only real concern would be performance.

In fact, Press Play recently released an open source plugin for Unity that will export your Unity projects into a C#/XNA solution and have successfully used it in several games in the Windows Phone 7 Marketplace right now. It's up over here https://github.com/fehaar/FFWD

I've already had most of the UnityEngine library assembly implemented, but no actual functioning engine. I can probably work on FFWD until it outs PSS compatible code.

[#8]

The Unity engine is made in C/C++, not C#. Its just that it provides a Mono (.NET) environment on top of its C/C++ code, for game developers to use. The UnityEngine library is simply a "link" that exposes Unity's internal C/C++ code to the Mono (.NET) side of things.

If you created your own version of the UnityEngine library that instead of being linked to Unity's C/C++ code, is connected to the PS Suite or XNA (maybe what FFWD did), essentially fooling your C# scripts into thinking its still using the Unity library, that can perhaps work.

But the question is does every piece of code used in the Unity library have an equivalent in PS Suite or XNA? FFWD suggests it does for XNA. I'll need to dabble with FFWD to find out.

[#9]

To answer the question about Sonys motivations for creating Playstation Suite. To say that Sony only created a portable app market to try and convince hackers to stop breaking their systems would be extremely naive consider they are just now catching up to modern times. Apple has AppStore, and Google has Google Play. Sony is just submitting their own competing model. However you can definitely see technology choices that suggest Sony is legitimately concerned about hackers breaking their systems. For instance the fact they are using Managed Code, statically compile the API and they have altered the mono runtime to not allow any unmanaged code to be executed by the user.

[#10]

Now can we please drop this Unity3D discussions. Its nonsense because Unity3D works perfectly fine already, and to assume that Sony will create a plugin to use a competitors SDK ontop of their own without permission is ridiculous.

[#11]

I know the Unity3D engine was written in C++, I was saying that it's possible to write a pure C# version of the engine. Most of the functions in the UnityEngine assembly reference to native functions, but are not really difficult to reimplement them in C#.

Completely rewriting the UnityEngine assembly in itself will not work for sure, though. PS Suite/XNA are too low level to plug both APIs together. You'd have to create the engine that would utilize scenes and components created from Unity with update and drawing loops that acts similarly to the native Unity engine. FFWD itself just implemented that engine with C# and XNA, nothing was really direct about it.

EDIT: Not clamouring for Sony to provide Unity support with PSS, just discussing that people can write the support for it themselves and something that I'd like to explore.