Skip to main content

News

Recent Posts

1
Engine Development / Re: Sphere 5.6.2 (neoSphere, Cell, SSj)
Last post by mezzoEmrys -
Stellar work once again!
2
Engine Development / Re: Sphere 5.6.2 (neoSphere, Cell, SSj)
Last post by Fat Cerberus -
For anyone who still cares: Sphere 5.6.2 is available for both Windows and macOS.
3
Engine Development / Re: Sphere 5.5.2 (previously miniSphere)
Last post by Fat Cerberus -
The rebranding of miniSphere to Sphere is now fully complete! https://github.com/fatcerberus/sphere

The engine itself has also been renamed, to neoSphere.  But unlike with miniSphere, that name no longer takes center stage: It's simply the name of the engine implementation, to differentiate it from other implementations of the Sphere API such as Oozaru.
4
Engine Development / Re: Sphere 5.5.2 (miniSphere)
Last post by Fat Cerberus -
I'm currently working on TypeScript integration for Sphere 5.6. This will make it so cell init creates a TS-enabled project. Initial experiments are going well, though there remain some kinks to work out. It doesn't seem like it will be too painful though, and most of the work was already done with my earlier ts-sphere project. The goal is to get it to behave as much like native tsc as possible, without the need to install Node.js or npm first. Just a tsc() call in your Cellscript.
5
Engine Development / Re: Oozaru: Sphere for the Web
Last post by Fat Cerberus -
It uses WebGL, performance seems pretty close to desktop Sphere as far as I can tell.  I had a perf issue a while back where it was really slow on Apple platforms, it turned out it just didn't like me reusing VBOs for Shape.drawImmediate(), even when they were created with the dynamic flag.  It ended up being way faster just to throw away the vertex buffer and create a new one next time.  But otherwise, there are no performance issues that I can see, and even that issue has since been fixed.

There are a few undocumented hoops you have to jump through in order to ensure your code runs as-is in both miniSphere and Oozaru, mainly having to do with module import conventions (they won't be undocumented for much longer, and I'm planning to add a compatibility mode to enforce them), but as long as you don't touch the Sphere v1 API, as long as your game runs on the desktop it should run fine on the Web too. That was, after all, my main goal for Oozaru.  ;)
6
Engine Development / Re: Oozaru: Sphere for the Web
Last post by Radnen -
I have been playing a game called CrossCode lately and it's clearly HTML5 based engine, but they had console releases, which gives me hope on Oozaru... I might think about using Sphere again. I was toying around with Game Maker, but I think it may be easier to build the game in Sphere? How's the performance?
7
Engine Development / Re: Oozaru: Sphere for the Web
Last post by Fat Cerberus -
Here's the above demo, now available directly on the SphereDev website:
https://oozaru.spheredev.org/
8
Engine Development / Re: Sphere 5.5.1 (miniSphere)
Last post by Fat Cerberus -
Just thought I'd give a quick heads up, there's an effort underway to make Oozaru a first-class member of the Sphere toolkit. In a future version the plan is that you will continue to be able to test your game on miniSphere with full debugging support etc., but the final distribution target will be fully Oozaru-ready.
9
Engine Development / Re: Sphere 5.5.1 (miniSphere)
Last post by Datomas -
I don't know if anyone still even uses the forums anymore, but...

 O:)
10
Engine Development / Re: Sphere 5.5.1 (miniSphere)
Last post by Fat Cerberus -
The next big feature I want to work on is Oozaru integration. Not sure how that's going to go yet, but the basic idea is to do something where Cell can include a copy of Oozaru with the compiled project. Then you just need to find a place to host it and you're good to go.