61–70 of 143 posts
Earlier quoted context omitted.
Unsafe is not as big of a deal as people make it seem.
Using C alongside static analysis like Frama-C is also quite safe, one could say.
Earlier quoted context omitted.
c++ is a bit more verbose than rust. think about all the stdlib functions that take begin and end iterators for containers. there's an overload for std::set_difference that takes six arguments, five of them being iterators.
Ranges and fold expressions take care of that.
still there's lots of other stuff that's more verbose in c++ than rust, often because it was bolted on much later. think about getting individual elements out of a tuple.
in c++: `std::get(tuple)` for each desired element or `std::tie(elt0, std::ignore, elt2) = tuple;`
in rust: `tuple.0`, not sure if there's an equivalent to the std::ignore/std::tie combo
What I like is that this engine actually have a demo which is more than few cubes and sprite: A full tiny game. Game engine should have more tiny games as it's a good way for newcomers to have something they can start to hack (change gravity/texture/lighting effects) and understand what a game engine is and how it work. The code is quite clean and it also provide scene editor with dedicated UI widgets. https://github…
Earlier quoted context omitted.
It's indeed very pleasing to read. I love rust but one pet peeve of mine is that projects can unfortunately get very hard to follow / libraries very hard to use once too much generics start to get poured into.
Generics, and also heavy use of traits and macros can make code hard to follow IMO.
Earlier quoted context omitted.
That might be true for the most cutting edge 3D shooters. But nowadays that’s not all that matters. I’m sure this can find a niche.
I'm not talking about shooters. I'm talking about what it looks like. The lighting, specifically.
The graphics looks like it's from 15-20 years ago. Modern game engines are so far ahead of this, rg3d has a lot of catching up to do.
I think this comment is slightly disingenuous, I think it's more obvious that the aesthetics of any game (let alone engine) will primarily depend on the quality of the Assets. If you loaded up these quake 3-era meshes and textures into Unreal Engine 4 or something else you'd call 'modern', I guarantee you they'd look the same or similar. The lighting isn't even that bad sans indirect illumination, which unreal only j…
The visual fidelity of a game is a moot argument and the quality of assets is subjective.
looking at the actual engine code, it's still all math and it looks like C++. The programming language here doesn't make the math easier to understand, example : https://github.com/mrDIMAS/rg3d/blob/master/src/renderer/sur... . Better to read some books on computer graphics math : https://foundationsofgameenginedev.com/#fged1
looking at the actual engine code, it's still all math and it looks like C++. The programming language here doesn't make the math easier to understand, example : https://github.com/mrDIMAS/rg3d/blob/master/src/renderer/sur... . Better to read some books on computer graphics math : https://foundationsofgameenginedev.com/#fged1
What I like is that this engine actually have a demo which is more than few cubes and sprite: A full tiny game. Game engine should have more tiny games as it's a good way for newcomers to have something they can start to hack (change gravity/texture/lighting effects) and understand what a game engine is and how it work. The code is quite clean and it also provide scene editor with dedicated UI widgets. https://github…
The game and the editor are massively helps to find right approaches in development. All my previous attempts to write engines (in other languages) were bad because all they had is just some very simple demos with some meshes and lights. You never know which features engine should have until you need them. Many engines trying to have best possible graphics and does not pay attention to other very important things, li…