Danny Limanseta (@DannyLimanseta)
@cursor_ai의 클라우드 에이전트가 본인이 만든 Godot 게임을 플레이테스트하는 모습을 보고 매우 놀랐다는 내용입니다. 첨부된(속도조절된) 영상에서 에이전트가 게임을 플레이하며 점차 게임 구조를 학습하고 익숙해지는 과정이 관찰되었다고 설명합니다.
Very pleasantly surprised to discover @cursor_ai cloud agents can playtest the godot game I built. See the (sped up) video below of the agent playtesting the game. As I was watching it play the game, I can see the agent slowly learn how the game works and familiarise with the
Bạn đam mê game? Kiểm tra tựa game trên PC & Mobile, nhận $5‑$15 cho mỗi nhiệm vụ, thậm chí lên tới $2,000 cho dự án hoàn chỉnh. Thời gian linh hoạt 15‑30 phút mỗi lượt, chỉ cần máy tính hoặc điện thoại. Tham gia ngay để kiếm tiền! #gaming #gameTesting #kiểmtrađồichơi #tiềndong #làmviệclinhhoạt
Back home on the boat! ⛵
Weekly game testing update: 8 games tested across Epic & Prime Gaming - Monument Valley+, Civilization IV, D&D Ravenloft classics & more, all Steam Deck compatible 🎮
Full details: https://www.junkstore.xyz/blog/games-tested-sep-08/
Artificial intelligence (AI) has become a transformative force in game testing, offering innovative solutions to identify bugs, optimize performance, and enhance overall gameplay quality. AI-Driven automated testing AI-powered tools have revolutionized the testing process by automating repetitive tasks and simulating real gameplay scenarios. AI-driven bots can explore various game paths,
Seeking testers for wlroots-git atomic modesetting tearing: Basically, you need a 6.9.x kernel or newer, and maybe also wlroots-git and labwc-wlroots-018-git, both from the Arch User Repository. You'll also be testing whether or not it functions better or worse with the following Merge Request:
https://gitlab.freedesktop.org/wlroots/wlroots/-/merge_requests/4746
Basically, I've found that the whole atomic modesetting tearing functionality merged into wlroots-git is completely broken, due to how the kernel functions and limits the use of async commits.
I made a change to make it function, but it doesn't necessarily function 100% of what a user who wants tearing would expect. Basically, it sees the commit failures, and re-sends the commit immediately, as a synchronized commit, to allow the property changes that the kernel is blocking on.
This is likely because I have hardware cursors enabled, because the thing that the kernel blocks on every time, is changes of the framebuffer of the hardware cursor planes, which apparently must be synchronized.
My workaround tries again on failure, synchronized. Further commits without any cursor bitmap changes, or just flipping the primary plane, should be asynchronous proper.
I've been told this isn't the correct approach. Perhaps it needs a different one, at the compositor level. Or perhaps a way for the library to notify the compositor that it synchronized a commit because async failed. Whatever everyone can agree on.
Either way, I'm sticking with this hack in my personal use until a proper solution can be reached. I'm looking for someone, anyone, to test these things and make sure they work. Apparently it's not enough to expect the wlroots developers to test the results of the original async commit patch for atomic modesetting, as they would have found it completely broken at the outset.
Looking for ways to find GAME TESTERS / PLAY TESTERS for a liminal indie horror game in the similiar style of another indie horror game called
"Exit 8" - PC only, early development, not many jumpscares, small team, first time finding people to test the game slated for later this year.
Please drop a comment and share!
#gamedev #playtesting #playtester #games #horror #horrorgames #liminalhorror #indiehorror #indiegamedev #pcgames #gametester #gametesting #help #fedihelp
sayzard
Reddit Tech VN Bot
Junk Store
daromi
PUPUWEB Blog
Ricardo Antonio Piana
SeleniumConf
Christopher Snowhill
Hiisikoloart
Sumit Singh