@vlusky_husky In terms of how many people use it, yes, it's still the 3rd most used engine in the industry and the FOSS reference in its category: the kind of engine designed to cater to a lot of people out of the box, relatively accessible, with a graphical editor.
To everyone using AI to write issues or features requests:
- It's hard to read
- Half of it does not make sense
- It's not productive!
It was way better when you explained things yourself in brief, even slightly broken English, or using auto-translation. A minor bug report or wishlist item does not need pages of text and made up justification.
Templates you can use:
Bug report: "X doesn't work. Here are the steps to trigger the bug: A, B, C"
Feature request: "I'd like X to do Y in my project"
It will often take you the same or less time than generating text and give everyone a better experience than messages written by, and, more importantly for machines and not for humans.
@GameUnionTV I feel it's actually happening more with experienced people and even seniors than younger ones (but can't be sure). At least the younger people among our students, they're doing things themselves because that's how you learn and few send generated text.
I would say yes and no, you still need people to be really engaged and critical of the content. The root issue to me is when people stop thinking and trust the output because it's seemingly good. I've also seen shorter reports that were misleading or worse than no reports because people didn't even verify repro steps, they apparently just threw an AI at the repository. Feels like a blind trust kind of thing?
Yes, you can use the compatibility renderer to increase the range of hardware that can run your game (openGL-based rendering backend).
The rest depends on your game code, assets... But generally speaking even affordable computers and tablets are very powerful and can run a game powered by an engine like Godot no problem.
It depends on what you mean by a potato and if you mean for building things with the editor vs running games.
Running games made in Godot, depends on the game, but it can run on old devices.
The editor can generally run on a relatively low-end Android tablet, or a laptop from 10 years ago. It runs on raspberry pi 5 too to give you an idea.
@c1leleo@ashlee3dee It's all scriptable; actually the entire Godot editor uses Godot's UI framework and it's all done in code. My teammate prefers to do it this way and often prototypes UIs in GDScript + uses this addon to generate UI themes programmatically: https://t.co/nTYFdZsMve
Despite much of our team being at GodotFest this past week, there was still a healthy amount of progress made on our handful of remaining release blockers
Now's the time to find any new bugs/regressions with our latest snapshot: #GodotEngine 4.8 beta 3!
https://t.co/KBBpqvJ1tK
I do feel there's truth to that. I just don't know how broadly the "against the market" and "at a financial cost to yourself" applies.
I've found that a lot of people have pushed the bar up with great financial success.
There are many markets rather than a market, and certainly a lot of people eager to get high quality things made with care, and often willing to pay more than average for that too. Especially if it answers a need.
But it's certain that quality and care don't necessarily pay off, and it can be painful. If you're only driven by financial gain you probably won't look to do anything with care because it takes more time and is less likely to pay off quickly.
That's what editing the contribution file is about. On top of that you'll always have to deal with people who don't read or respect things. A lot of people may simply not know, not realize, not check, or even believe that AIs write and explain things very clearly and that it's helping.
@raysan5 Btw the canned response is also not just for the person sending big AI generated posts or spamming the repository, but it's actually more for everyone else participating and/or AIs probing your repository.
I would do a mix of:
- Adding a short bullet list of do's and don'ts in the README and CONTRIBUTING files
- Closing on sight
- Banning accounts that repeat
- Optionally writing a short canned response to educate people for when closing issues
The last point is because a lot of people doing this might think the writing or work is better with an AI or that they're helping, not realizing that you could do that better yourself if that was actually useful/what you wanted.
I still answer personally on my end and I've found despite having the same kind of experience that people were taking it well and understood.
@valigo Isn't it risking getting worse long term? E.g. ending up with more code output and shipped total, with fewer people understanding what's happening?