Anim8or Community

Please login or register.

Login with username, password and session length
Advanced search  

News:

An update to Anim8or, v1.00b, is available with a few bug fixes. Get your copy HERE. See the "ReadMe" file for details.

Pages: 1 ... 7 8 [9]

Author Topic: v1.01 Development Release - Build 1385, June 29, 2020  (Read 48376 times)

Alpha2

  • Full Member
  • ***
  • Posts: 112
    • View Profile
Re: v1.01 Development Release - Build 1384, June 13, 2020
« Reply #120 on: June 21, 2020, 10:27:38 pm »

Alpha2: I've updated the way these settings work in build 1382. See if they work better.
Okay so far IK handles no longer appear in renders unless you were last using the IK tool, so this at the very least makes me happy! They still appear when rendering an image or movie if you had the tool selected but, I guess I'll just have to remember to switch off of it before a render. A locked camera is locked period, yay! I tested by locking both together locking it's properties and individually placing it on a locked layer, scroll wheel or other accidental camera movement does not result in a key frame in either case, thank you!

While testing just now:
I ran across an instance when after a render the scene mode GUI became locked for lack of a better description. I couldn't scrub the timeline and the keyframe button was unresponsive. I escaped this frozen state by rendering an image after which it was fine. My theory in that moment was that maybe I'd tabbed out of a video render while typing this post and when the render was done it got stuck switching back to scene mode, but this seems not to be the case on a attempt to replicate. Might be nothing but thought I'd mention for the sake of thoroughness, and I'll keep trying to repete it.

Also, I don't know if it's ever been brought up: when rendering a range of frames, the Movie spec editor never seems to remember the first frame number even if it's just frame 0. It will remember the last frame, but you always have to re-enter the starting frame number otherwise you get the error "start frame: malformed number". It's not an issue if you always render all frames, just when doing a range. The video resolution also defaults back to 640 x 360  rather than the last resolution I entered for some reason despite the codec setting. If I recall it used to only default between sessions, but it's doing it after every render now.
« Last Edit: June 21, 2020, 10:51:34 pm by Alpha2 »
Logged

bayinghound

  • Jr. Member
  • **
  • Posts: 62
    • View Profile
Re: v1.01 Development Release - Build 1385, June 29, 2020
« Reply #121 on: June 29, 2020, 07:21:55 pm »

I tried downloading v1.01.1385 but get an error saying File too Large.
Logged

bayinghound

  • Jr. Member
  • **
  • Posts: 62
    • View Profile
Re: v1.01 Development Release - Build 1385, June 29, 2020
« Reply #122 on: June 29, 2020, 07:25:18 pm »

Nevermind.
Logged
Pages: 1 ... 7 8 [9]