Caused by this code:

if(!data.prompt) {
d.prompt = data.evaluateItem.toString();
}

It expects the settings object itself to have an .evaluateItem property, which it normally won’t have. Ideally it should handle that too instead of erroring. (I’ve put a failsafe into my advanced plugin for now.)

I think it should always fall back to using “” as the prompt. Which at the very least would stop this error from happening. Though it’s still blocked from generating anything with a message. I also feel like it should still just generate an image, unless there’s something actually bad that will happen on the server-side because of this that I’m not seeing?

  • @wthit56OPEnglish
    1•3 months ago

    I think that fix is fine for now, agreed.

    The talk by Alex? Great one. There’s a couple I think. He’s amazing… (Casey Muratori has a really solid one on SDF too by the way.)

    Yeah, PS4/5 only. And live support has ended sadly, though they’ve put things in place so the servers can stick around for a long time. (In theory.) I was so into that community and platform for a good few years (won some community awards for “most helpful”, youtube channel teaching it, the only full documentation)… I just love helping people learn how to make stuff.

    It falling apart was not good for me though, and I haven’t looked at it since. Properly burned me out over time.

    Perchance is certainly scratching that itch though. And the runner (you) is actually quick on fixing/changing things, and likes doing things for the benefit of the community. Mm (Dreams’ devs) were owned by Sony and had a lot going on behind the scenes, so not so good on that front. Also though, I’m able to straight-up code my own tools others can directly use (with more depth than was possible on Dreams), so that’s also cool 👍