Website A place to upload poses/scalers/resources

[anna]

Just adding this here for everyone who has complained about it but never suggested it (and for those who did suggest it but didn't post it here).

Absolutely zero idea how I would want to tackle this, but I know I would want it separate from the mods. One page for mods, one page (or multiple?) for non-mods.

 

[sleepybnuuy]

Also I know it would probably be a ton of dev work but a basic 3D preview of bone locations could really be nice (think dots and lines like vfxedit uses) View attachment 68(vfxedit animpreview)

this is a neato idea but would probably require a lot of work to implement on the web, compared to in a plugin which can directly reference the game's skeleton files or full character appearances. for context, I work on Ktisis and we've been exploring some cool solutions this month to expose the content of a pose file before applying it during GPose - Brio has also recently added some thumbnail/image previewing tmk. clarity of what a pose actually looks like while going through your local files is definitely a problem that other devs are working on smoothing out, so it may not be an immediate priority for HS to manage.

as a developer, if extra files could be typed to specific kinds of content (such as .pose, C+ template, LivePose data, etc), this would open up a lot of cool avenues for cross-plugin integration via the heliosphere plugin, which currently only has IPC to Penumbra. being able to click once on browser to load a pose or scaling ingame would be pretty sick, as would uploading a pose directly from the game, but definitely a follow-on feature compared to just manual downloads.

C+ strings are interesting to think about if not being created as templates via IPC - not sure if more users would prefer them copied straight to clipboard when 'downloaded' or instead converted to a .txt and copied from there to C+ instead.

 

[anna]

i’m wondering if sections of the forums could be made to host certain things instead, since they’re already here? particularly things like c+ scalers, which are just walls of copy-pasted text.

guides are already here, though a means by which to link guides on the forums to our main pages on helio would be grand since otherwise it’s difficult for people to know they’re here. since the first image included in a forum post is already considered the “preview” for the post, could there perhaps be some sort of hook from the forums to the main site (as an example, when you look at a person’s profile, categories can be separated by mods/guides/etc. based on who has posted where, using the same link setup that mod previews do, but linking here instead of a particular mod page on the main site)?

i’m reminded of older forums as well, where the media capable of being uploaded was far more expansive (namely being able to upload .zip files on forums, which is usually how things like poses and presets are packed). imo it would be a nice way to keep things separate while also integrating the forums into the helio community at large. idk how much more infrastructure this would take to build out vs. what you have planned currently, but hopefully some food for thought! ‍

I do like this idea, but I have plans for things that would be easier to do if I didn't have to tie it to the forums and PHP. Things I don't want to say because people will get their hopes up or think I promised and didn't deliver, but they're cool and would be a massive pain in the ass to hack into forum software.

Linking forums and main site... maybe. If it's easy.

 

[ShiverMyDear]

Since the framework is built around mods, my suggestion would be thus:

If feasible, when an upload is flagged by the system as a pose: it greys out the plugin download button, and bumps the manual download button up in size. That way users cannot mistakenly click it thinking the plugin will handle the download. A little banner at the top saying "This is a pose file, which requires a posing tool such as: Anamnesis, Ktisis, or Brio to use." That way it's also highlighted to the user that it is further divorced from the main plugin, Helio.

Pose files already follow the .pose format universally, unless it's the ancient .cmp; which in my opinion should be upgraded before uploading. So if you want something to flag, that would be what I'd tell the code to track. For scalers with Customize, that can be .txt since it's a string of numbers and letters. Encouraging users to actually save it with Notepad for uploading purposes, will make it more streamlined. Just having a gibberish of numbers and letters below an initial post can lead to confusion in my opinion.

But this is my two cents on ideas for implementation. I haven't coded a website since 2010, so I have no clue what your back-end and workflow looks like. Thank you for your hard work as always.

 

[Alloragamer]

Adding to this with my 2c (made an account to bump the thread). Having a way to upload non-PMP/TTMP items is one of the biggest hurdles for me. Some mods consist of only raw files, and therefore cannot be uploaded to heliosphere (i guess these would be considered resources?). I'm not sure how these items would be categorized and have some concerns about them being sequestered away, as unlike devkits, the idea of a loose file mod would be to add to your own setup. (for example, a makeup mod that is an overlay to ensure compatibility with someone's existing face textures or scales; or an eye mod that just contains the eye diffuse, as the material, normal, and mask are not needed to be changed). I'm not sure what a good solution is for mods like this that would allow for them to still have proper visibility, and not be lumped together with resources like devkits, or raw files that are not meant to be used as-is (ie not meant to be chucked into penumbra without further tweaking via the add overlay in advanced editing).

As already mentioned, posemakers are a huge subset of people that still cannot move to heliosphere due to the current restriction of the "main" file requiring a PMP/TTMP, but I also worry for modmakers who want to post mods consisting of raw files for easier use with existing mod setups, as well as people who simply do not want to split thier download into mod file and resources files. And I worry about reduced visibility and confusion of mods that are not in the pmp/ttmp format if they are lumped together with resources such as devkits.

not much else to say since I'd be repeating myself, but yeah. I think in the mean time, shiver's suggestion of if a post is flagged as a "non-mod" the plugin download being greyed out and the manual download button being more visible, and some kind of banner warning that it is not a standard mod would be sufficient at least for me; but I don't know what the backend of heliosphere looks like and how feasible this would be to implement, as well as how easily anything with this flag could be transferred to the sub-site when that is complete.

 

[nyanya]

Also made an acccount just to comment here, mainly to voice that it's absolutely something that would be appreciated. The state of uploading or searching for poses elsewhere is kind of miserable

 

[anna]

Locking this thread for the time being. I know that it's a wanted feature, and I will unlock and update this thread when there is more to report.