Copy link to clipboard
Copied
I'm so feed up with your company and your software. You can't imagine how much I hate to work with, but I still have no choice for now. but we are beginning the transition to some other softwares.
It's the same here. Bugs take sooo much time to be fixed, or never fixed. That's insane for 60 euros per month per subscription. Adobe moves your a..... instead of satisfying your shareholders.
And WHERE IS THE MULTIPROCESSING???!!!!!
Windows 10
latest AFX 16.1.2 (build 55)
i9 9900K
64GB RAM
3 Monitor
2 RTX 2080ti
1 GTX 1080ti
Copy link to clipboard
Copied
There was a major bug update about a week / ten days ago, amongst the listed fixes was this very issue. Are you running v16.1.2 and still experiencing this issue?
FWIW I wasn't surprised given the apparent relatively few numbers of affected users that this needed to wait until the first major bug fix roll-out - in the grand scheme of things, the time taken for the fix to appear doesn't strike me as overly egregious. That's not to say it wasn't an irritating problem for me - but by the same token it wasn't a showstopper which I felt warranted any delay to a more comprehensive bug-fix release by devoting resource to an exclusive emergency fix any earlier.
Copy link to clipboard
Copied
Hi Motioncraft,
As I mentioned, I'm running the latest version 16.1.2.