Closed parhamgholami closed 7 months ago
I suggest to be very positive for each of them and also I like the idea you mentioned notable strength. Maybe each engine should have listed 10 top notable strengths with some content around it. And if you would like to list more, then equally you should add more points to others :)
Been working on this on and off in a limited capacity due to other obligations, but here are some notes I have so far:
Open 3D Engine (Written in C++, Supported Languages: Lua)
Godot (Written in C++, Supported Languages: GDScript, C#)
Bevy (Written in Rust, Supported Languages: Rust)
I'm open to feedback! Planning to work on Stride next. After that, I'll expand on the notes over next week or so, find some good showcase projects/titles, and then approach the communities of each engine for feedback.
Don't worry. We all work only when we can š. @Aggror, what do you think? Content seems ok?
I (finally) spent some time today writing a draft of the introduction and setup. I tried to approach it with the assumption that the person reading the post might not know what FOSS entails or the general advantages of choosing a FOSS game engine. I'm going to work on filling out the engine-specific information next.
As always, I'm open to any feedback or constructive criticism. š
I am definitely ok with the approach that someone (like me) doesn't know what FOSS is and it is nice to have our blog posts explaining these terminology as we can target more audience. There are many very experienced C# devs, with no game experience, so we are also helping this audience if they come around. Like me š¤£.
@dotnet-policy-service agree
Added an entry for Bevy. I'll probably do O3DE or Godot next.
Even though it's still a work in progress, I'm open to feedback on the work so far (especially if there are any inaccuracies). š
At later stage and if appropriate, you can also add some links here and there. Definitelly, internal Stride Web and Stride Docs links are welcome, with external, we can be more cautios. For example if we are going to list some Stride features and manual is aviable, we can link it.
That's a good idea. Once I get more of the text content in, I'll start adding links for each section.
Finished my first draft of the O3DE section. Will likely work on Godot next.
Edit: Will also work on implementing some of the feedback given earlier on Discord.
Nice update!
Finished the first draft of the post. Now I'm going to start the process of fact checking everything. Ideally, I'd like to reach out to folks from each community to make sure the post is accurate and doesn't misrepresent any of the engines.
Committed the latest draft. Reached out to folks from the O3DE community to get their feedback.
It looks good. So we published the latest website updates, so anytime you would like, we can publish also your post once you are ready :)
Received some great feedback so far from all the communities I've reached out to. Going to work on integrating them into the post over the next week or so. The Open 3D Foundation also offered to share the post once it's live. š
I still haven't been able to talk with anyone from Godot (a maintainer, contributor, or experienced user) to get their feedback yet, but I'll put more of an effort into that this week.
Thank you for the update!
Thank you @adamscott, @m4gr3d, and @bruvzg for the feedback! I added the suggested changes to the current draft. š
Other than some potential additions to the acknowledgments section, the text content is pretty much done. Just need to add some images and links. Then it's ready to go live!
Yes, please, I will publish it to staging, so you/we can do additional review :)
Added links as well as banner images for each engine. Just waiting on a response from one of the fact-checkers and then it's ready. š
Good to go to staging!
Thank you @parhamgholami
Following up on a conversation in the #marketing channel on Discord, we could put together a blog post that briefly describes the current FOSS game engine options for folks who want to dive into this space and need help figuring out where to start. This post isn't intended to compare Stride with alternative engines but to spotlight the wider FOSS game development community.
Each section will summarize the engine as well as identify the engine's notable strengths/features, supported platforms (for both development and building projects), the language it's written in, the supported scripting languages, and a link to a video of a finished game made in that engine.
The goal is to encourage developers to find the tools that best fit their needs. Aside from helping foster a positive environment in the FOSS game dev community, that willingness to be transparent and impartial could encourage more folks to check out Stride.
Currently, these are the engines I had in mind for the post:
I'm also open to adding more (like Cocos2D, Armory, MonoGame, and Murder) if we think more should be added.
All of this is open to feedback and constructive criticism, so please let me know what you folks think. I'm aiming to start putting together an early draft sometime next week, but if someone is eager to dive in sooner, then I encourage them to do so. As we get closer to a completed draft, it would also be good to solicit feedback from folks involved in the other engines to fact-check the post before going live.
If it's done right, there's a strong possibility the post could get a reasonable amount of traffic and help get more eyeballs on Stride.