Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow entering of any value to Actor Scale numberbox #893

Closed
BigMunsBuns opened this issue Mar 25, 2022 · 8 comments
Closed

Allow entering of any value to Actor Scale numberbox #893

BigMunsBuns opened this issue Mar 25, 2022 · 8 comments
Labels
Enhancement New feature or request UI

Comments

@BigMunsBuns
Copy link

The recent update added a cap to the maximum actor scale/height available to users, both in and out of gpose. This can be extremely limiting to specific content creators and general creativity.

I request the hard limits on actor scale be removed. Ideally, a player would be able to manually value above the slider's cap like they could in versions past. If a happy medium needs to be reached, perhaps "a use-at-your-own-risk" delimit checkbox would serve well for those wanting to work outside of the would-be soft caps?

@BigMunsBuns BigMunsBuns added the Enhancement New feature or request label Mar 25, 2022
@Yuki-Codes Yuki-Codes changed the title Changes to actor scale values? Actor Scale upper limit is too low Mar 25, 2022
@Yuki-Codes
Copy link
Contributor

We should implement exponential slider values and increase the max scale value to 1024 to cover this case.

@Yuki-Codes Yuki-Codes added the UI label Mar 25, 2022
@BigMunsBuns
Copy link
Author

Would restoring uncapped, manual entry be viable? It would cover the broadest range of use.

I'm told 1024 is the maximum value before one needs to modify camera FoV and distance to see an actor. If there needs to be a cap I would advocate for one much higher than 1024.

For the slider values, I think whatever fits the most general users or use cases would suffice — ten is fine, honestly. Those who work with bigger scales have used and may prefer the granular to-the-hundredth/thousandth control of manual entry.

@AIIiz
Copy link

AIIiz commented Mar 26, 2022

Personally, I'd love to have this limit uncapped back.

Having the slider capped at 2 limited a personal project I was in the middle of (project I spent some money in already). I don't necessarily use or expect the 100% of the uncap back (most definitely couldn't use above a certain number, 15 being the max) but could definitely use a bigger cap than 2.

@AliceApplez
Copy link

Having it uncapped on manual entry again would be perfect... This change is really limiting :(

@Karendefined
Copy link

Having it uncapped on manual entry again would be perfect... This change is really limiting :(

This would be nice, I like the sliders and the min/max is fine.
But on the off chance I'd like 200 boob size then this would be amazing!

@Yuki-Codes
Copy link
Contributor

Sounds like general consensus is just to allow exceeding of the max value for scale when entering values via text.

Shouldn't be too hard to add a CapValueEntry property to the NumberBox control and set it to false just for the TransformEditor scale.

@Luminiari
Copy link
Contributor

Luminiari commented Mar 28, 2022

Just a heads-up to let you know that we'll be pushing an update to address this and other issues on Sunday (03/04/21 Australian time).

EDIT: Due to work commitments and health issues the aforementioned update will be delayed. why have people stopped wearing masks I s2g covid isn't magically over

@Yuki-Codes Yuki-Codes changed the title Actor Scale upper limit is too low Allow entering of any value to Actor Scale numberbox Mar 28, 2022
@Luminiari
Copy link
Contributor

Quiet bump for edited comment about the next update

Yuki-Codes added a commit to XIV-Tools/XivToolsWpf that referenced this issue Mar 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement New feature or request UI
Projects
None yet
Development

No branches or pull requests

6 participants