weird little numbers bug in 4.11

After intensely testing 4.11 since release, found there's one weird little bug that seems to have infiltrated this Daz version. Often when I try to adjust small numbers, like say move a limb up and down for just 0.04 millimeters or something in the parameters, and I press enter to confirm; Daz just flicks it down to standard 0.0000. Like up/down is at 14.56 and I need it down to 14.51, I type in the numbers and poof: it's a 0 for some reason. Never had this before, it only started to pop-up since 4.11.

Comments

  • SpottedKittySpottedKitty Posts: 7,232

    Are you sure the cursor focus is staying on the parameter field you clicked? If the focus shifts when you're in the middle of typing in a new value, you could get either who-knows-what or nothing entered.

    Something else you can try — number fields in DAZ|Studio can take mathematical operators, so if you click into your number and move the cursor to the end (to the right of "14.56") you can add "-0.04" to the end of the number and the value should come up as 14.51.

  • novastridernovastrider Posts: 208
    edited June 2019

    Yip yip yip, done it al, and restarted and everything, there's no reason for it to behave like this but the program itself. And it's not a consistent thing; like it does this a bit randomly (although when it does it, it does it consistently on the same spot/limb).  I'll try the mathematical trick next time.

    Post edited by novastrider on
  • novastridernovastrider Posts: 208
    edited June 2019

    Interestingly it does work if I do the math trick.

    - So if I change a bugged value from -14.65 to -4.65, enter, it still goes to zero.
    - If I take the same bugged value from -14.65, add -10, enter, it goes to -4.65 like it should.

    Can't really do this forever though, would slow down my work a lot. Can people please keep an eye out if they have this bug too? It's really easy to miss if you're used to quickly changing a lot of numbers and going right on to the next limb, missing that one of the things you tweaked has suddenly reset.

    Post edited by novastrider on
  • mclaughmclaugh Posts: 221

    Interestingly it does work if I do the math trick.

    - So if I change a bugged value from -14.65 to -4.65, enter, it still goes to zero.
    - If I take the same bugged value from -14.65, add -10, enter, it goes to -4.65 like it should.

    surprise

    Not running 4.11 yet but ... -14.65 + -10 should go to -24.65, not -4.65.

  • SpottedKittySpottedKitty Posts: 7,232

    - So if I change a bugged value from -14.65 to -4.65, enter, it still goes to zero.
    - If I take the same bugged value from -14.65, add -10, enter, it goes to -4.65 like it should.

    <nod> That's beginning to sound suspiciously like the "wandering cursor focus" I mentioned upthread. Are you moving the mouse pointer away from the parameter box after clicking into it so you can see what you're typing? That's how it happens to me.

  • novastridernovastrider Posts: 208
    edited June 2019

    - So if I change a bugged value from -14.65 to -4.65, enter, it still goes to zero.
    - If I take the same bugged value from -14.65, add -10, enter, it goes to -4.65 like it should.

    <nod> That's beginning to sound suspiciously like the "wandering cursor focus" I mentioned upthread. Are you moving the mouse pointer away from the parameter box after clicking into it so you can see what you're typing? That's how it happens to me.

    Yup, I ain't moving it. Click the box, type the values, enter. Mouse doesnt even get a chance to move outside the box. And when I do put it outside, it's not a problem with the rest of the parameters that don't have show this random issue. While it might be mouse related (since that's one of the things that got actively updated with 4.11), it's unlikely caused by the user since neither my own behaviour or mouse has changed since the update.

    (@mclaugh, yeah yeah, I meant +)

    Post edited by novastrider on
  • beeaquibeeaqui Posts: 0

    Hey, guys!

    I upgraded the firmware and drivers from AMD and now it's working fine.

    Thanks for the tips and hug to everyone

Sign In or Register to comment.