One of the key things missing for those trying to write powerful Homebrew Games is proper open-source documentation and samples of coding for the very powerful RSX 'Reality Synthesizer' graphics processor found inside everyone's PS3 Console.
Up until now, all currently released Homebrew has been making use only of the CELL Broadband Engine with its many SPU's, so the graphics have been limited to basic emulators and very simple games.
Now thanks to amazing team of developers over at Gitbrew.org (http://www.gitbrew.org/) and those that recently donated to make this happen, they have released the RSX Documentation, along with many working samples, so now the various homebrew authors and scene developers can sit down and study it, and you will see some vastly improved updated homebrew and better emulators and hopefully some new fancy high-res powerful games released over the up coming months now for your PS3 Console!
This is just one step in a long line of great PS3 releases to be coming out from Gitbrew group, so as always stay tuned to the PS3Crunch channel for more scene breaking news!
NEWS SOURCE: http://twitter.com/gitbrew
stock2255
08-08-2011, 03:44 PM
Although I'm a little iffy about the idea of not releasing til a certain donation amount is met, I found myself donating to the cause, because they are really doing some good work out there. Besides, I had a feeling they were going to release the documentation within a day or two, regardless of the donations received. I'm just hoping it doesn't set precedent where they set up a system where certain works or features are held until a certain amount is released. For example, if we receive donations in the amount of $1000 in the next week, we will release a working method for connecting CFW ps3s to PSN. While I don't think its wrong on inappropriate, it just seems a little off.
On the other hand, which the miniscule amounts I saw donated to DeanK, as well as the miniscule amount of donations I'm sure GitBrew received prior to this, it may be the only viable system out there to both advance the scene forward, and reward those who are releasing good work. It's gotten to the point where I wouldn't be surprised if people wouldn't pay $100+ for a software way to downgrade from 3.56 or above, or for a full-blown custom firmware. Or a system where you could "donate" for a 3.60 or above game fixed to work on 3.55. Send $10 in paypal, receive fixed eboot, sprxs, etc. to play the game. Not that either of those solutions are practical or possible at the moment.
I'm rambling. I'm curious to see what comes from this. Garyopa, is there any way you could give a more technical explanation of how exactly this could help homebrew? Say, the difference it could make to say Showtime, or various emulators. If we had a working, but slow (hypothetical) n64 emulator that operated strictly on SPU's, than optimized for use of both the SPU's and RSX.
GaryOPA
08-08-2011, 03:55 PM
I'm rambling. I'm curious to see what comes from this. Garyopa, is there any way you could give a more technical explanation of how exactly this could help homebrew? Say, the difference it could make to say Showtime, or various emulators. If we had a working, but slow (hypothetical) n64 emulator that operated strictly on SPU's, than optimized for use of both the SPU's and RSX.
We know more later this week, once the PS3Wiki is updated with more layman's terms and information taken from this pure-source RSX documention, it is very hard to understand at the moment.
The only problem I see is alot of the "project coding" is designed for the later Visual Studio 2010, which only interfaces to the PS3 on v3.60 or higher, whereas the ones running v3.55 and v3.41 or lower were using VS2008 as the project interface, so there going to be more information needed to bridge the older VS up to speed, or better yet a workable v3.60 CFW -- hehe!
xPreatorianx
08-08-2011, 04:06 PM
We know more later this week, once the PS3Wiki is updated with more layman's terms and information taken from this pure-source RSX documention, it is very hard to understand at the moment.
The only problem I see is alot of the "project coding" is designed for the later Visual Studio 2010, which only interfaces to the PS3 on v3.60 or higher, whereas the ones running v3.55 and v3.41 or lower were using VS2008 as the project interface, so there going to be more information needed to bridge the older VS up to speed, or better yet a workable v3.60 CFW -- hehe!
Well you should be able to put all the solutions into VS2008 and "downgrade" them. If there is any problems compiling, simply work out the errors. Now keep in mind that the RSX documentation is C++ so I have no idea how long it will take to "port" it to VS2008 and fix any errors, but with things such as C#, it can be as simple as altering a few lines due to API changes. But for an experienced C++ programmer it should be easy as hell to get it fully working on VS2008. It should actually be easier than going from VS 2008 - > VS 2010. I'll put a list of errors from a compile after at the bottom of this post. I have both VS 2008 and VS 2010 fully installed including all language additions. So I'll see what errors, and warnings come up.
EDIT: I can see already that some of the solutions have both a VS2008 edition and a VS 2010 edition. So it should be a piece of cake.
EDIT2: What SDK do I need to get all the required project files for this release to compile? Can anyone link a quick guide or something? I haven't messed with any PS3 related coding in VS.
erexx
08-08-2011, 05:03 PM
This sounds like a path to proper RSX driver support... is that correct?
Post jaibreak many were saying a RSX driver wouldn't be needed because Linux would magically fix this.
But those who were investigating the RSX push before jailbreak insisted that it would need a driver, that no one has, even if it was unlocked.
Thelostdeathknight
08-08-2011, 05:28 PM
nice article!! also you have a typo going on garyOPA documetion -should be documentation. the typo it is in the title
GaryOPA
08-08-2011, 06:08 PM
nice article!! also you have a typo going on garyOPA documetion -should be documentation. the typo it is in the title
Thanks, should be all fixed up now. -- Go figures I got a F in my last year of school for spelling, and I had to hire a private grammar tutor just to be able to get a B+ in English, but for Math / Science / History and everything else A was the highest level they could give, since by time of normal grade 9 school-age, I had already completed grade 12, so I am messed up in some areas and advanced in others. -- Oh'well.
Thelostdeathknight
08-08-2011, 06:39 PM
np, spelling isn't my strong suit and dyslexia makes it harder. anyways i made the same typo >_<
xPreatorianx
08-08-2011, 07:41 PM
Thanks, should be all fixed up now. -- Go figures I got a F in my last year of school for spelling, and I had to hire a private grammar tutor just to be able to get a B+ in English, but for Math / Science / History and everything else A was the highest level they could give, since by time of normal grade 9 school-age, I had already completed grade 12, so I am messed up in some areas and advanced in others. -- Oh'well.
I'm the same way. All my other classes are straight A's while my composition/writing class is a B. The screwed up thing is that I need that composition class to finish my associates. I'm on my last two classes, an advanced computer class and composition. I've always been horrible at writing and in all honesty I'm surprised I have a B. That B hasn't been easy, i've been staying up late every night hammering home everything related to the class.
Writing, spelling, and grammar has always been my worst subject, and that's coming from a native English speaker. I think English is the only language that people will go to college to major in, even when they are completely fluent.
(Ya I know my grammar sucks online. I don't plan on changing that part of my writing skills. I spend too much time editing my college work. So I don't feel like doing the same thing on the net.)