General Category > Ongoing Anim8or Development

v1.01 Development Release - Build 1403, August 29, 2022

<< < (31/32) > >>

matty47:
Just getting back into Anim8or. It looks great for creating low poly game models. It's also wonderful that you are still developing the program - although the forum seems rather quiet.
What I like is that it is not overloaded with complication - amazing what it can do from such a small package.

selden:
Recently I've been getting an error popup which says
==============================
Initialization message
---------------------------------------
AutoSave in use by another Anim8or session:

Currently unavailable for this session.
==============================
even though no other session is running.

Also, there are no files in the location specified for autosaves,
which is C:\Users\selden\AppData\Local\Anim8or\temp\

How can I clear this error?

Edited to add: when I try to reconfigure Anim8or to not use Autosaves, I get another error popup which says

==============================
Just to you'd know...
---------------------------------------
ReleaseMutex failed: 0x00000120
==============================

Steve:
There might be an old Anim8or that's still running after it closed it's window. Look in the Task Manager and if you see a task named Anim8or you can shut it down. Otherwise rebooting your computer will fix this.

selden:
There had been two other copies of Anim8or still running, although neither of them had windows open. Using Task manager to terminate them was the first thing I tried. I'm sorry I didn't mention it. That didn't help. :(

I wish a reboot weren't necessary for a couple of reasons For one thing, I'm often working on other projects (on separate Virtual Desktops) that I'd have to close first and then restart after the reboot. (I often use Anim8or to modify a model that's being used by them.) For another, restarting those projects after a reboot can take a while. I'm working on scripts (using vdesk) so I don't have to re-open all of them manually, but still....

Is there any chance of a workaround becoming available? Maybe a utility that'd clear the Autosave lock and reset the ReleaseMutex?

selden:
build 1403: mistaken info in the "About -> System Info..." popup.

The popup "About -> System Info..." shows the operating system version as being
OS Version: Windows 8 (6.2) build 9200

However, my computer is actually running Windows 10 22H2 build 19045.2486

Might it be showing the system info for the computer that it was built on instead of the computer that it's running on?

Also, it would be great if the text in the "About" popup windows could be copied-and-pasted.

In build 1403, that's only possible for the text in the "About" popup "License".

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version