DUSTBORN / ダストボーン

DUSTBORN / ダストボーン

データを表示:
dustborn glitches
Is anyone running into this glitch. I am playing and literally the prologue and the 1st chapter played with zero glitches but ever since I got to this camp in Pax hometown it's been glitchy as hell. As the exploring gamer I am it was a moment before I met my sister they allowed me to send someone to "unlock" the kitchen but I only realize now that wsn't even supposed to happen until after I met her so now she is in this kitchen and because I already did it the gme doesn't register it to do again and because it autosaves only ONE file I can't even go back to not do it so my game is literally softlocked ALREADY because of a stupid glitch.....I was having fun but I will return this game before i restart it all over because of a glitch. :steamfacepalm:
< >
16-30 / 34 のコメントを表示
Red Thread Games  [開発者] 2024年10月24日 1時38分 
Unknown Samurai の投稿を引用:
I haven't encountered anything game breaking yet. Just minor visual bugs here and there. I am curious though, if I may ask, what are the kind of things that usually get reported if this is uncommon?

Oh speaking of visual bugs, this also happened during that same session from issue #5.
This one might be plant specific, I didn't realise which one Mr. Planty was until my partner pointed it out the following day. It's not game breaking, just another minor visual bug.

QA reports everything they find, including visual bugs, and though the dev team can't fix everything, we do review and triage every reported bug. We can't recall coming across some of the bugs you are reporting — but that's to be expected. There's only so much a small QA team can do, even if they play the game over and over again! That's why we appreciate players reporting the bugs we find, because we might discover/uncover previously unknown issues.

As for Mr Planty: that's another one. This has worked for us in the past. We've forwarded your video to the dev team and they'll look into it. And while it is "just" a visual bug, it's something that should be fixed…if it's reproducible!

EDIT: This bug has been fixed, and the fix will be in the next patch. It was caused by a wrong flag on a mesh, making it static rather than dynamic. (I don't know what that means, I'm just repeating information passed on from the developers!)
最近の変更はRed Thread Gamesが行いました; 2024年10月24日 2時45分
Red Thread Games の投稿を引用:
Thanks for the save! Our developers have looked into this bug and the other bug you reported, but they're not able to reproduce.

Could you please tell us which version of the game you're playing, and where it was purchased? The version number is visible on the title screen. The game has been updated twice on Steam (as well as the other competing PC store); on release day, and again a few weeks after release. Both of those patches included content updates and bug fixes, and the day one patch should have addressed the bugs you reported in this thread.

My version is 1.2

What version is it on Steam?
Red Thread Games  [開発者] 2024年10月24日 8時09分 
Houseman の投稿を引用:
My version is 1.2

What version is it on Steam?

Steam (and other stores) is currently on v1.7. Where did you acquire the game? You'll need to turn auto-update on in your Steam or Epic launcher in order to stay updated.

Version 1.2 is from launch day, and contains a number of bugs that were fixed in a day one patch, and in a patch around ten days after release.
Red Thread Games の投稿を引用:
We'll look into it, but it feels like something that may be difficult to reproduce.
I may have messed around with the Wave Runner and it seems more easily reproducible than I thought. It appears just playing the game well is enough the lock the ME-EM into a debug state in about 30 seconds. Even got some nice place holder text at the end of the video.
https://youtu.be/b-Xb9lusMow?si=Mv0cAcPqlq7MDEzA
Red Thread Games  [開発者] 2024年10月24日 8時51分 
Unknown Samurai の投稿を引用:
Red Thread Games の投稿を引用:
We'll look into it, but it feels like something that may be difficult to reproduce.
I may have messed around with the Wave Runner and it seems more easily reproducible than I thought. It appears just playing the game well is enough the lock the ME-EM into a debug state in about 30 seconds. Even got some nice place holder text at the end of the video.
https://youtu.be/b-Xb9lusMow?si=Mv0cAcPqlq7MDEzA

Good work! We should hire you to do QA in the future…

The video has been shared with the developer of this feature. A fix won't make it into the next patch, but we'll hopefully address in the near future!
Red Thread Games の投稿を引用:

Good work! We should hire you to do QA in the future…

The video has been shared with the developer of this feature. A fix won't make it into the next patch, but we'll hopefully address in the near future!
All good, thank you. I haven't intentionally tried breaking certain aspects of the game yet. But perhaps on future playthroughs I'll mess around some more.
Red Thread Games  [開発者] 2024年10月24日 9時04分 
Unknown Samurai の投稿を引用:
All good, thank you. I haven't intentionally tried breaking certain aspects of the game yet. But perhaps on future playthroughs I'll mess around some more.

We're both thrilled and horrified at the prospect...
Red Thread Games  [開発者] 2024年10月24日 9時07分 
Red Thread Games の投稿を引用:
The video has been shared with the developer of this feature. A fix won't make it into the next patch, but we'll hopefully address in the near future!

The developer of the mini-game responded on Slack:

"I love how he is making his own mini-game to try and figure out why that's happening!

"That mini-game had a win / lose condition way back but the UI for the MEEM was changed and we don't have score or player hp indicators anymore. I think he is 'winning' by collecting sound waves and destroying echoes (it is impressive that he is intuitively doing that correctly) but since the UI is missing I suspect it hits a null ref when he 'wins' and that is what breaks the MEEM.

"If my suspicion is correct, it should be a quick fix."
Red Thread Games の投稿を引用:
Red Thread Games の投稿を引用:
The video has been shared with the developer of this feature. A fix won't make it into the next patch, but we'll hopefully address in the near future!

The developer of the mini-game responded on Slack:

"I love how he is making his own mini-game to try and figure out why that's happening!

"That mini-game had a win / lose condition way back but the UI for the MEEM was changed and we don't have score or player hp indicators anymore. I think he is 'winning' by collecting sound waves and destroying echoes (it is impressive that he is intuitively doing that correctly) but since the UI is missing I suspect it hits a null ref when he 'wins' and that is what breaks the MEEM.

"If my suspicion is correct, it should be a quick fix."
Oh that's quite interesting actually. That would explain why it locks after a certain objective happens.
最近の変更はUnknown Samuraiが行いました; 2024年10月24日 9時30分
Red Thread Games  [開発者] 2024年10月24日 9時45分 
Unknown Samurai の投稿を引用:
Oh that's quite interesting actually. That would explain why it locks after a certain objective happens.

More real time follow-up (the team's working overtime):

"Yeah, that is what is happening. I'll sub a fix that removes the win condition until we get some time to finish up the mini-game!"

And a suggestion from another developer:

"Could I suggest making this an endless runner but displaying score and gradually make it more difficult? Since we dont have much to win here at least The player can try to get as good a score as possible and brag about it?"

No promises, but we'll add it to our growing list of ideas for the next content update!
Red Thread Games の投稿を引用:

More real time follow-up (the team's working overtime):

"Yeah, that is what is happening. I'll sub a fix that removes the win condition until we get some time to finish up the mini-game!"

And a suggestion from another developer:

"Could I suggest making this an endless runner but displaying score and gradually make it more difficult? Since we dont have much to win here at least The player can try to get as good a score as possible and brag about it?"

No promises, but we'll add it to our growing list of ideas for the next content update!
I'm genuinely looking forward to the content update whenever it goes live.
I feel kinda bad though, most people already seemed to have played their fair share of Dustborn and moved on. Similar to other streamers and content creators (I'm probably one of the few people that still regularly goes live with stuff related to Dustborn). Even the guys who were coming here to laugh in the discussions are now few and far between.
I'm really impressed that you guys are still putting in work and polishing your game. I just wonder if more people will get a chance to know this side of the development team, and not the story that's be publicized all over the internet
Red Thread Games  [開発者] 2024年10月24日 10時30分 
Unknown Samurai の投稿を引用:
I'm really impressed that you guys are still putting in work and polishing your game. I just wonder if more people will get a chance to know this side of the development team, and not the story that's be publicized all over the internet

Thanks!

Of course we hope that some past players will come back to revisit the game — although most definitely won't. There are just too many games, and even if someone enjoyed Dustborn, there's very little chance they'll come back for another go. But maybe, and for those who do come back, the game will be a little bit better. Or maybe a lot better, a year or two from now.

Red Thread's previous games have been slow starters and steady sellers, with 75-90% of copies sold more than six months after release. Will that happen with Dustborn? We don't know! The market is always changing, but that's the only data we have. Other companies and games will differ, of course. So for those (theoretical) future customers, we're making sure they get a better experience.

But here's the most important reason to keep working on the game: we want it to be as good as it possibly can, for our own sake. If we can fix the things we don't like, or the things players complain about, we'll do it — to make the game better, even if "no one" sees it. WE see it. And we want to be able to look back on Dustborn and say we did the best we possibly could. Even if it doesn't always make financial sense.

The current plan is to keep working on Dustborn for a year, to hopefully get to a point where the game is significantly improved in all ways. Maybe we'll do more, maybe we have to do less — we're a small team and we're working on other things, too — but we're not abandoning Dustborn any time soon.
Houseman 2024年10月24日 14時06分 
Red Thread Games の投稿を引用:
Steam (and other stores) is currently on v1.7.

Thanks, I've updated!

That would be cool if there was a chapter select feature, or some kind of timeline so I could go back and make different decisions and see all the content!
Red Thread Games  [開発者] 2024年10月25日 0時16分 
Houseman の投稿を引用:
Red Thread Games の投稿を引用:
Steam (and other stores) is currently on v1.7.

Thanks, I've updated!

That would be cool if there was a chapter select feature, or some kind of timeline so I could go back and make different decisions and see all the content!

I'm not supposed to talk about what's in the update that's coming very soon…but there MAY be a way to go back to an earlier save-point in the next version 😬
Red Thread Games の投稿を引用:

I'm not supposed to talk about what's in the update that's coming very soon…but there MAY be a way to go back to an earlier save-point in the next version 😬
By the way, you guys mentioned a thread to submit feedback or suggestions for certain parts in the game. Would you be able to make something like that? This probably isn't the best thread to discuss things related to dialogue lines and other things. But I do have a suggestion related to Ziggy in chapter 3. It's not a glitch or bug, just one line of dialogue related to character choice.
< >
16-30 / 34 のコメントを表示
ページ毎: 1530 50