Adventurous_Step2911

joined 2 months ago

768x768 is pretty new; the documentation is probably outdated. Forcing the resolution with (resolution:::768x512) is working for me. Where do you put it? Try putting it at the end of the Image generation prompt, and make sure it's not mentioned twice anywhere in the prompt.

That being said, the default is 768x768 unless "(resolution:::" is present or any of the following keywords are included: "portrait" or "selfie" for 512x768 or "landscape" or "wide" for 768x512 It will always prioritize the value of "(resolution:::" above any keywords

I think a link to the generator would be helpful

It actually got updated recently. It's now using Fast bigram-based approx token counter. Not an AI guy and no clue what that means, but it's not the old "count/3.6" method anymore :D

[–] Adventurous_Step2911@lemmy.world 2 points 2 months ago (1 children)
  • When you are figuring out how to pull some piece of data out of an object created by a Perchance plugin, how do you figure out what the Javascript name of that object is?
    • Not sure I understand correctly. Do you want to extract a list out of a plugin? Then something like this should do the trick: "root.$moduleSpace["nested-plugin"].world". Or do you want to understand how to find it? I do that through inspecting the root object in the browser console
  • Is there some standard way of figuring out which account maintains a Perchance plugin is if their name is not displayed on the plugin’s page?
    • Not that I know of

Now to your main problem: Afaik, perchance objects are static and don't save their state when they're evaluated. You have to inspect the DOM with JavaScript and traverse the parent elements to gather all descriptions. At least that's how I got it https://perchance.org/ah70cbqlqk#edit

I'm not really good at explaining, please ask if something is unclear. What I've done in the example is, I've overwritten the javascript onclick handler defined in the nested-plugin. This onclick handler is executed when expanding a header element. This allowed me to inspect the DOM that was generated through the nested-plugin. If the currently expanding element is a leaf, it traverses each parent header element and extracts the description of it and overwrites the content with all gathered descriptions.