51–60 of 108 posts
I'm getting security warnings visiting the site, on both Firefox and Chrome (though chrome's could be due to an external check, redirects me to malware.opendns.com). "Error code: SEC_ERROR_UNKNOWN_ISSUER" on FF at least. edit: and seems like I'm not the only one, as there's at least one upvote already. probably worth checking!
Creator of Bevy here. I just announced Bevy yesterday and the response so far has exceeded my wildest expectations. I'm happy to answer whatever questions people have!
I didn't see anything about networking - is that a feature you intend to include eventually?
Earlier quoted context omitted.
1. I want to be ambitious while also being realistic. AAA studios won't even consider using Bevy until it has more features and has stood the test of time. So in the short term our market is essentially "indies and enthusiasts". I want Bevy to cater to those people, but with an eye toward larger projects. We don't want to design ourselves into a "locally optimal" corner that prevents us from appealing to large studio…
As someone who may be tinkering with a game this decade, one big factor which favors “use prebuilt engine” in my thinking is that some of them abstract away the work required to port between different systems. Is this really a very big hurdle in your opinion? And do you see console ports being part of this engine in the future? The API looks great in any case, and I’ll try it out, at least as a starting point to get…
Earlier quoted context omitted.
Video games don't really care about binary size.
On a console every 1mb of binary is one less mb for assets. We ran LTCG on every game I shipped.
Earlier quoted context omitted.
Over C#: * Garbage collectors often scare game developers since they can lead to hard-to-fix latency spikes. * Rust has some cool libraries (specs, rayon, etc.) that let you safely parallelize computation. Over C++: * It's a memory-safe language, which instantly avoids tons of bugs. * Library interfaces are usually higher-level in Rust than in C++, for various reasons (sum types being a big one). * It's a much smalle…
> * It has an easy-to-use package manager, and I'm not sure where C++ is on that front. In the inescapable hell of n+1 competing standards.
Creator of Bevy here. I just announced Bevy yesterday and the response so far has exceeded my wildest expectations. I'm happy to answer whatever questions people have!
I just hope that the `Turtles All The Way Down` philosophy won't hinder game devs from supporting scripting language of their choice. Because at some point someone is going to need domain specific language somewhere.
Creator of Bevy here. I just announced Bevy yesterday and the response so far has exceeded my wildest expectations. I'm happy to answer whatever questions people have!
Earlier quoted context omitted.
I would expect that for most games the vast majority of bytes will be assets (textures, models, sounds, etc.), not code. Even reducing the code size to 0 is unlikely to make much of a difference in the total size.
For AAA titles, sure, but there's a long tail of indies, game jam entries etc. For something retro-styled like Dwarf Fortress or Baba Is You , I can absolutely believe that asset size is relatively minor compared to e.g. a Unity baseline footprint. Harking back to ancient history for a moment, Frontier: Elite II was a AAA title for its day and was basically all code.
Earlier quoted context omitted.
Great start here and a very compelling intro post. A couple of things I wondered about and didn't see answers to: 1. How ambitious is Bevy as an engine? Do you see it as aimed squarely at the casual-game space like ggez, or do you think it could eventually compete with Godot, growing more advanced features like GI? (I appreciate that competing with Unreal is probably, well, Unrealistic for the forseeable future.) 2.…
Video games don't really care about binary size.
Their overlords always stress on developer conferences how install size is the number one reason for users to remove applications and games from their devices.