Did you not run the acemd3 test WU's back in July when the new acemd3 apps were released as beta?

I did. And successfully processed every one of them on all my cards including my RTX 2080's.

If you did not change your GPUGrid Preferences to allow the beta acemd3 app then you did not test the app and receive it from the project.

https://www.gpugrid.net/prefs.php?subset=project

I did and got the app and the test WU's. All they need to do is either continue releasing the test WU's for the beta app or move it out of the beta category to the main apps category.

The acemd3 wrapper app for Linux hosts plain works.

The pertinent threads are:
New app update (acemd3)
Testing acemd3 windows

Did you not run the acemd3 test WU's back in July when the new acemd3 apps were released as beta?

I have all the Windows 10 applications enabled, but I have no record of whether I got any acemd3 tasks or not.

You seem to be assuming that the server application for creating acemd2 tasks can create acemd3 tasks also with no programmer to update that server application first. We may need to wait for more of the project team to return from their August vacations to find out if that is correct or not.

Acemd3 uses OpenMM does it not? It is probably version 7.2 by now. That is the same one that Folding@Home is testing now for Core_22. And they are having problems that need fixing.

I wonder if they are related?

Did you not run the acemd3 test WU's back in July when the new acemd3 apps were released as beta?

I have all the Windows 10 applications enabled, but I have no record of whether I got any acemd3 tasks or not.

You seem to be assuming that the server application for creating acemd2 tasks can create acemd3 tasks also with no programmer to update that server application first. We may need to wait for more of the project team to return from their August vacations to find out if that is correct or not.

The license use with acemd2 just needs renewed on Linux. It expired before Windows but has yet to be renewed. Year after year this happens.

But Toni indicated they wanted to get away from this yearly license renewal garbage they have to deal with and just release the apps as BOINC wrapper apps that take care of themselves.

All they have to do is release work for the acemd3 app we already have. That work would be labeled for the acemd3 app.

Or go ahead and renew the acemd2 license for the old acemd2 Linux app. Why are Linux hosts being punished with no work?

But Toni indicated they wanted to get away from this yearly license renewal garbage they have to deal with and just release the apps as BOINC wrapper apps that take care of themselves.

All they have to do is release work for the acemd3 app we already have. That work would be labeled for the acemd3 app.

Correct. Delay is just a lack of time due to other projects (lots of quality time must be allotted for addressing scheduler mysteries and follow-up problems).

Keith, do not get impatient. We knew, that the lack of WUs would be for several months...

My old GTX 670 is getting some “breadcrumbs” from time to time… and all my LINUX computers help other projects at the moment – they are happy about that, I assume.

My personal conclusion about the lack on GRIDCOIN WUs is again, I should not invest in “special” computer parts just for crunching BOINC. I hope I will remember this, the next time I stand in a computer shop...

Well my frustration wouldn't be so high if there were no work units for anybody once all the licenses ran out. But since Windows hosts get work now because they got a new license but we did not, I come to the conclusion that Linux hosts are considered second class citizens not deemed worthy of attention.

Also, we know the acemd3 wrapper app works. So why no work for a proven system?

I am finishing up the WOW contest tomorrow upon which time all my hosts would normally go into massive catch up mode for all my other projects. But no, that isn't going to happen with GPUGrid is it?

Acemd3 uses OpenMM does it not? It is probably version 7.2 by now. That is the same one that Folding@Home is testing now for Core_22. And they are having problems that need fixing.

I wonder if they are related?

I've forgotten which BOINC recently found problems with the 436 driver. However, you might ask Folder@Home to check whether their problems are also related to the 436 driver.

I got a GPUGRID task today, so the Windows portion of the problem might now be workunits not being created as fast as the users become ready for them.

(lots of quality time must be allotted for addressing scheduler mysteries and follow-up problems).

This sounds to me like Toni has:
miles to go before we're sated,
miles to go before we're sated.

---

This sounds to me like Toni has:
miles to go before we're sated,
miles to go before we're sated.

It just means that it is August in Europe.