Playstation Suite US Open Beta Available now!

[SsJVasto]

It would seem if you read the guide post install, that memory allocation can't exceed a total of 96MB, being configured maximum as follows:

managed_heap_size Memory size that can be dynamically allocated within the application Units in Kbyte. Default is 32768 (32MB)
resource_heap_size Audio data or image data Memory size to be allocated to textures, etc. Units in Kbyte. Default is 65536 (64MB)

To some extent, it doesn't seem the Vita is as accessibly powerful as a typical smartphone with such low memory access. Still to see what can be made, it will be interesting. The included sample programs look from very simple, to games that could go for $10 on android or iOs markets. It seems basic C# is the development code used. Gonna go and look for my old coding books and brush up, and give this a shot to see if anything pans out.

I can imagine that this is one of the limitations of the "Garage Dev" package, but it's not that bad... It's more RAM than what was available on PSP (because you had 32MB and 8MN was Kernel-reserved, so 22MB for your programs, and 2 MB of VRAM, IIRC), but with this computing-beast, you can put lower-polygon models and tesselate to make it smooth... The only problem with low RAM is that loading your textures takes a lot of space, so you have to watch out.

[xknight]

The guide after installing speaks of something to remove things from memory after loaded, unless it's residual code that's needed..it's currently over my head, but I look forward to there being a section on here for projects that people have made, and successfully run, and to be tested.

That being said, one of the first apps I'd like to see is a structured and more capable file interface than CMA or even OpenCMA, which at current, I'm not sure still works on 1.67, so I reside myself to staying at 1.61 until absolutely necessary to upgrade via need for homebrew, or new game purchase that isn't already out.

Any one else have any ideas or capabilities as to what they would like converted, or created or attempt to create themselves?

[rafael707]

The guide after installing speaks of something to remove things from memory after loaded, unless it's residual code that's needed..it's currently over my head, but I look forward to there being a section on here for projects that people have made, and successfully run, and to be tested.

That being said, one of the first apps I'd like to see is a structured and more capable file interface than CMA or even OpenCMA, which at current, I'm not sure still works on 1.67, so I reside myself to staying at 1.61 until absolutely necessary to upgrade via need for homebrew, or new game purchase that isn't already out.

Any one else have any ideas or capabilities as to what they would like converted, or created or attempt to create themselves?

cant wait to get home and play with the open beta, see how many flaws sony can have

[SsJVasto]

The first thing to do, IMHO, is to upload a PKG file to see if it's encoded on a per-vita or per-PSN-ID encryption... Like, I'll compile one of the samples for my PSVita at home, then upload it here, and someone will tell me if it works on their PSVita... If every user had his own encryption key based on their userid or something, then things get very complicated to distribute homebrew...

What I'm worried about is how it is written that all the SDK will be removed when the BETA closes, and we sill have to pay 99$ a year to develop. I'm worried that they want to know what we're developping, and every time we compile, we're asking Sony to encrypt it remotely (maybe Sony sends us the encryption key or something)

[StepS]

maybe Sony sends us the encryption key or something

Lol

[DJ_NiveK]

It would seem if you read the guide post install, that memory allocation can't exceed a total of 96MB, being configured maximum as follows:

managed_heap_size Memory size that can be dynamically allocated within the application Units in Kbyte. Default is 32768 (32MB)
resource_heap_size Audio data or image data Memory size to be allocated to textures, etc. Units in Kbyte. Default is 65536 (64MB)

Is that for RAM or the App Size can't pass 96mb?

96mb tops would be shittttttt D:

[m0skit0]

because you had 32MB and 8MN was Kernel-reserved, so 22MB for your programs, and 2 MB of VRAM, IIRC

Standard 24 MiB for user-mode, actually (VRAM doesn't count as RAM). Plus P5 partition (8 MiB? won't count this because it really cannot be used), plus another 32 MiB if you got PSP 2k or higher and unlock this memory, thus 56 MiB total. Plus scratchpad, but since it's 4 KiB only, that won't add nothing worth it, but could be helpful (HBL for example uses this to store its stubs and global data).

[dimy93]

Is it possible to load any kind of file with the beta because i cannot find a library for that ?
Edit : the standart file management seems to work fine but I haven't yet tried on my vita because I want to complete my snooker game first

[m0skit0]

As well, maybe able to learn or find out more about how much of the A9 Cortex SoC is being utilized

I wouldn't count on that. This SDK is for developing CLI (aka .Net) apps.

[AboveAlpha]

This is one of those times where I'm looking at the tools going "OMG" and just want to know how to do it right NOW. I ran the demo's on my vita and that felt impressive. I have the tools and several books needed to get me started. My talent is strong Ideas. I'd love any experienced devs that would be interested to work with me on some great ideas that I have. PM me and we can talk. This is like a nice little holdover for VHBL release too. I'm not refreshing as often right now! lol