Anim8or Community

Please login or register.

Login with username, password and session length
Advanced search  

News:

Ian Ross has just released a book on Anim8or. It's perect for a beginner and a good reference for experienced users. It contains detailed chapters on every aspect, with many examples. Get your own copy here: "Anim8or Tutorial Book"

Pages: 1 ... 7 8 [9] 10 11

Author Topic: v1.01 Development Release - Build 1403, August 29, 2022  (Read 202534 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

  • Full Member
  • ***
  • Posts: 210
    • 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

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

Nevermind.
Logged

JSmith_DumDumDumDumDum

  • Jr. Member
  • **
  • Posts: 52
    • View Profile
Re: v1.01 Development Release - Build 1390, August 9, 2020
« Reply #123 on: August 30, 2020, 06:46:27 pm »

In v1.01390, I can't free-rotate x-y-z while in object mode; or any of the modes, for that matter. Also, the middle-click for finer zooming is also gone.

The rotation system in this most current version is isolated to view-x, view-y-, view-z, which we can only rotate singularly at a time. When I rotate view-y and then rotate view-x, the camera angle of view is unwantedly tilted; which renders rotation in .01390 completely useless.

The rotation/panning/zooming features were much treasured, productive and efficient from previous downgraded 1.01 versions. Please bring them back.

Also, in the current version I'm using (a downgraded 1.01 version; not sure which), the program regularly crashes when I undo and redo spline-work. Whole projects will then be thrown the the sewer, and I would end up extremely frustrated, putting my project away to not touch again for hours, days, or even weeks.
« Last Edit: August 30, 2020, 07:09:50 pm by JSmith_DumDumDumDumDum »
Logged

AlecJames

  • Full Member
  • ***
  • Posts: 240
    • View Profile
Re: v1.01 Development Release - Build 1390, August 9, 2020
« Reply #124 on: August 31, 2020, 04:03:15 am »

Do you mean arc-rotate has changed? 

If so, look at  Options-->Debug-->Use original arc rotate.  I have this checked, does this fix it or have I miss understood?
 
Logged

AlecJames

  • Full Member
  • ***
  • Posts: 240
    • View Profile
Re: v1.01 Development Release - Build 1390, August 9, 2020
« Reply #125 on: August 31, 2020, 04:57:44 am »

On the crash issue, can you make a simple project / procedure that reproduces the issue? 

While I've never used it, there is an autosave feature https://www.anim8or.com/learn/manual/2_basics.html#auto_save.  (I must try it out :) )

I save regularly and my save location is synced to ms one-drive.  In the one drive web interface I can restore a previous version.  I need to know roughly when I did what, but its saved me a few times.  (I think this works with the free version of one drive.)
« Last Edit: August 31, 2020, 04:59:35 am by AlecJames »
Logged

JSmith_DumDumDumDumDum

  • Jr. Member
  • **
  • Posts: 52
    • View Profile
Re: v1.01 Development Release - Build 1390, August 9, 2020
« Reply #126 on: August 31, 2020, 06:14:59 pm »

Thank you, Alec James. Let me check out your suggestions in a day or two, when I get better rested than the last 3 nights.  8)

Do you know if in .01390 the spline undo-redo error has been resolved?

Also, yes, Arc-rotate is exactly what I mean. I simply forgot that that's the technical terminology. (Despite the fact that I've known it long!  :-X :-X :-X lol)
Logged

AlecJames

  • Full Member
  • ***
  • Posts: 240
    • View Profile
Re: v1.01 Development Release - Build 1390, August 9, 2020
« Reply #127 on: September 01, 2020, 06:39:54 am »

I tested adding spline segments and then using undo / redo in 1390 and 1391 and I don't see any problem.  But the problem will likely be in the detail - there will be some difference between my procedure and yours.
Logged

Old Codger

  • Full Member
  • ***
  • Posts: 145
    • View Profile
Re: v1.01 Development Release - Build 1395, January 5, 2021
« Reply #128 on: January 12, 2021, 10:49:06 am »

Just saw the mention in the regular forum about 1395 and I FREAKING LOVE IT! The rotation and movement available from the alt key are super! Now I just have to edit my desktop shortcut to run it rather than the older version.

I've said it before and I'll say it again, Steven, YOU . . . . . . DA . . . . . . MAN!!!!!
Logged

Steve

  • Administrator
  • Hero Member
  • *****
  • Posts: 2126
    • View Profile
Re: v1.01 Development Release - Build 1395, January 5, 2021
« Reply #129 on: January 12, 2021, 12:33:56 pm »

:)
Logged

2020 Hindsight

  • Jr. Member
  • **
  • Posts: 80
    • View Profile
Re: v1.01 Development Release - Build 1395, January 5, 2021
« Reply #130 on: January 16, 2021, 01:52:57 pm »

Bug report:

Just got an "assertion failed!" message when rendering an image with the attached script files.
I had just changed my script to try an idea for a 'V' wake effect. It was a failure, and the water was very spiky - pointy waves, but not massively tall.

I get the same message from "Anim8or_1395.exe"

Message:
Assert failed!

Program: ...\Anim8or_1394_plus.exe
File C:\Users\rstev\MyApps\Anim8or\src\VArray.h
Line: 83

Expression: !"array index out of bounds"

To trigger the assert, I load "ThirdWaveTest.an8" go to Scene mode, And select Render->render image
After clicking OK I get the assert.

Here are the offending files:
Logged

Steve

  • Administrator
  • Hero Member
  • *****
  • Posts: 2126
    • View Profile
Re: v1.01 Development Release - Build 1395, January 5, 2021
« Reply #131 on: January 16, 2021, 02:08:49 pm »

OK I'll check it.
Logged

Steve

  • Administrator
  • Hero Member
  • *****
  • Posts: 2126
    • View Profile
Re: v1.01 Development Release - Build 1395, January 5, 2021
« Reply #132 on: January 17, 2021, 10:47:43 am »

2020 Hindsight I found the problem. Your script is producing Z values of infinity. If you start a new project and click-drag to add a ThirdWave object the middle row has values like this:

+      points[2112]   {x=0.0320000015 y=0.0320000015 z=1.#INF0000 }   Point3

This causes other issues within Anim8or which produce the assertion.

Note: The variable "points" is from Anim8or's internal representation, not a variable in your script.
Logged

2020 Hindsight

  • Jr. Member
  • **
  • Posts: 80
    • View Profile
Re: v1.01 Development Release - Build 1395, January 5, 2021
« Reply #133 on: January 17, 2021, 11:35:14 am »

Sorry for the wild goose chase! I thought I was doing you a favour passing the report on.

I thought my script protected against getting large values.  But looking at it I see the new code bypasses the test!
Logged

johnar

  • Hero Member
  • *****
  • Posts: 1025
  • Make it, Move it--Give it Life
    • View Profile
    • youtube vids
Re: v1.01 Development Release - Build 1395, January 5, 2021
« Reply #134 on: February 01, 2021, 01:03:05 am »

Hi.
 Unable to download build 1395.
 Clicked on both links, just takes me back to same page with no download occuring.  :(
Logged
%
Pages: 1 ... 7 8 [9] 10 11