I just hit "randomize" several times in my generator and they all look like different people to me. Of course, you need to fill a lot of details which my generator does for you, so you don't have to type anything.
Koto
joined 2 months ago
Yes, it's possible. The correct syntax would be [a = originalList.consumableList.selectMany(2)] . Then, we'll need to make a list of that slice by using createPerchanceTree() with the correct escape characters. The function works like this: [newList = createPerchanceTree("slicedList\n\ta\n\tb").slicedList] [newList]
Flux Kortex is perfect for image to image. I recommend installing it locally, amazing stuff.
https://perchance.org/hm20ndlb7m
Not sure if you meant like this, a dropdown to choose from the list of genres.
In perchance lists, the correct syntax to choose one is [list.selectOne] to choose one. You can assign it to a variable that you can later use, for example:[selectedGenre=genre.selectOne].
Good idea but that would be a hell of a job to track all the pieces across different lists plus specification for each piece where it goes. Since I'm lazy I just did:
Uniform
https://user.uploads.dev/file/53321b33603b8f9f386fb870db73ad65.png
top=batman mask
mid=batman suit with batman logo on the chest, batman gloves, batman belt
low=batman pants, batman boots
rear=batman cape, mask straps on the back of the head
noZoom=[this.top], [this.mid], [this.low], partially visible batman cape on the sides
and then just call it like [Uniform[camera]]. I can easily filter out different actor specifications now.
That's what I'm doing. I'm setting those values to all html elements, as well as using them in the lists. That's why I need to declare them to avoid "undefined" errors in the list section, for the first time users or after a remember(root, forget). Right now I have a long construction with something like this, [actor==undefined?actor="Any":""], it's clunky but it works.
The "optimized" version that I was trying to make and asked help for with FOR construction and window[key] =... actually worked but in the HTML part. You're right it, THIS of course, referred to the function not the document. However, while it works for the elements, somehow the lists "forget" them immediately after the first update(). So, I'm just keeping it as is for now with [if undefined then value].
btw, .some is a neat method, I overlooked it before.
Thanks for your answers! You gave me some good ideas there. But dynamic odds is what I was trying to avoid because I have 200+ suits, not just batman uniform, I can't spell it out in each of them and was trying to make one line rule for them all. Index 0 - png, index 1 is top, index 2 is mid, etc.
the variables are supposed to be a global variables, just like if it wrote [charNum==undefined?chaNum=1:""]. charNum, for example, is the value of a slider. But there are all kind of html elements associated with different variables, from radio inputs to strings.
Try proving a few more details. You can't be vague with the new model, it'll fallback to the basics it was trained in. And it's obvious that the flex females predominantly had lip contouring.
You seem to have pretty good idea what you're looking for. So, put it into words inside a prompt, and tune it phrase by phrase. The new model is quite good at catching the detailed description. The older model had its charm, but let's be honest it was outdated.
view more: next ›
You won't be losing consumable list on that created list, as you can .consumableList it again. Judging by your code, you figured it out!