Repository navigation
Can someone explain to me why all these float nodes doesn't let me input float numbers? #17426
|
For some reason all these video models need 0.98 as the sweet spot of rendering to get 1344x768 but you always need to get rid of the Resolution Selector node to input the width and height automatically which is a pain if that node controls multiple points in the workflow. adding a float input to the Resolution Selector will also don't work because floats can't work for some strange reason. Who decided this thing? Do we have a name of this guy or woman? Can someone find him and ask him WHY you can't input 0.98 in a node that is really important for all these workflows? This is the most annoying thing I've ever experience ever day, is so range inducing that I can't describe in simple human words. Let me explain better. first one billion workflows use the default resolution selector so you will always be forced to swap it out if you want the 0.98 thing. BUT life is not fair and for example from the one billions custom extensions I was forced to install because each workflow needs to reinvent the wheel, for example I've found two alternatives. Guess what these two don't have? Yes they don't show the resolution you have selected like the default one. The authors of these two extensions if you are around and read this so you obviously decided to improve the default node. good. WHY, like really WHY remove the display that tells you what resolution was selected? What is the reasoning behind this choice you both decided was a good thing? Like same question for the decision to not let float be float. I can't comprehed why not improve something but going sideways. Pic related. |
Replies: 3 comments 1 reply
|
for the built-in selector, i'd set the selector declares a it's a global setting, so it affects other float widgets too |
|
ok thank you so changing the source code could probably work but then I don't know if i can update the app. will that break it? but anyway I've found these options, they appears they work now, don't know why they didn't worked a couples weeks ago because I've tried them. |
|
you're welcome, glad you've got the rounding option set to no source edit needed, those code links were just references to explain the rounding |
|
Nice, this keeps the resolution preview without swapping out the selector. |
for the built-in selector, i'd set
Float widget rounding decimal places [0 = auto].to2, reload the page, then type0.98. the arrows still move by0.1. that keeps the selector and its resolution previewthe selector declares a
0.1step, and the current frontend's auto rounding uses that to pick 1 decimal place, so0.98becomes1.0it's a global setting, so it affects other float widgets too