To make this work you'll have to start playing around with firmware writing. I know people have done similar projects using a pi pico to handle the translation, but I don't know if they did it with a ps2 controller.
Dude... Your talking about mixing ancient technology with space age hardware. What comes next? Watching VHS on the switch?
Good luck getting your setup to work. The drivers for PS5 are completely open sourced by Sony so I think it would make your life much easier by investing in a new controller 😅
I had to build a game in phaser 3 for my "html" course and I swore I would never try to game dev in js again.
I know we were using a very old version and we had very minimal guidance... have I missed something big that makes it tolerable to work with or do i just need more js experience?
The way you put it, it sounds that you have issues with the language. I can relate to that, but JS is what browsers understand natively. Probably using TypeScript is a good alternative, as static typing helps you keep afloat as the project grows.
As for Phaser itself (can be used with TypeScript), it depends what kind of game you're making. Even older versions of phaser have the typical programming affordances to make 2D games like assets and physics. Having said that, it's fair that other engines have visual editors, and possibly more tutorials and other resources.
But yes, phaser is hardly HTML, so weird choice for the course.
As a hobbyist, Godot is probably the most "fun" engine I've worked in. The software itself feels like a toy, similar to Gamemaker (at least from what I remember when I used it like 10 years ago as a kid lol). Coming from C# background, using GDscript wasn't as bad as I thought, and making small projects in a weekend has really itched the problem-solving part in my brain. I'm trying to re-create popular flash games that I remember playing back in the day and seeing what improvements I can make.
Professionally in Unreal 5. Hate it with a passion. Not only is the engine a shared state leaking piece of s*it but the language(s) that come with it make the whole mess even worse.
In my free time I worked with Bevy which is really promising in my opinion. I hope their editor will be as amazing as the rest of the framework.
Recently I also tried Fyrox. It is nice, probably usable for some smaller things, but damn it feels a lot like Unreal again with going a OO-like paradigm. Of course little to no memory-safety issues it being developed in Rust as well (+ a runtime borrow checker they implemented on top to check on shared writes to Resources, Nodes, etc.), but compared to ECS it feels terribly clunky.
ECS just feel sooo right!
Also, if someone needs a more mature engine than Bevy, don't go for Unity or Unreal - Take a look at Godot. It's FOSS and even supports Rust bindings (and I do think Rust the shit and will be a big deal in the future).
I'm a senior non-game developer, playing at game development in my spare time. I used to use Unity, but I've quit them a few times, and I think this time is for good. UE4/5 didn't really fit my work flow or design style.
So I'm playing with Godot now, and I'm pretty impressed. Some things like 3d imports and animations could use some love, I think... But otherwise, I'm pretty happy with it.
The point in the article isn't bad, but what he is forgetting is whatever version of Unity his engine depends on, will always be available. It's not actively being worked on really, unless you intended to update to a later release but most don't need to. Doesn't matter if Unity goes down, they will always have a product, they'll just get smaller and privatize which isn't a bad thing.
Unity made a gazillion dollars and wasted it all on acquisitions it had no business managing. They poofed a billion easy on those and people got extremely profitable payoffs and retirement plans. All this while they play is for fools.
As a Unity employee who was recently let go I know it's still a total shitshow, and we're all better off cutting our losses and not planning improvements on the Unity version of our games. At least Unreal isn't bleeding money and backtracking on a bad business model.
True, except that you need to be able to compile for the latest SDK, etc. Google and Apple now require that your app is compiled against the current or immediately previous SDK, and will actually hide your app on the store if it isn't now. Perfectly good games just disappear from the listings for some BS reason.
And the old version of your game engine often won't compile against newer SDKs, especially if it's more than a couple years old.
I experienced something similar with my game that I made using Unity and the Chromecast plugin for it. Google stopped updating the plugin, and the new Unity didn't work with the old plugin, and for some reason I needed to use a newer Unity version. (It's been a while and my memory is hazy on it now.) I could not compile my game for modern devices anymore. Luckily, it wasn't even a game I had published, so I didn't screw over any users with that, except my own family.
Game Development
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.