AmigaForever,

Are you not getting any work for any projects? Or have you not seen a single OET1 results on your computer?

If it's the first question, then that is a whole different issue and you'll need to paste probably the last 25 lines of your event log to the forums for us to help you. It could be anything.

If it's just not getting OET1 work, you might want to try this.
1. Go to My Projects and uncheck OET1.
2. Click save
3. Go back to My Projects page and check OET1.
4. Press save.

These steps will make sure your project preferences are passed down to your device preferences just in case there was a change there.

As others have mentioned about the project still running at low priority. Which means that at any time there are say 1000 results WAITING to be sent to the next host that requests work. Out of these 1000 there may only be 5 results waiting to be sent for OET1, 490 for FA@H, 490 for MCM and 15 for UGM1. Your computer will ask for work and the odds of getting OET1 on that request are 5%. So you can see how this can start very low percentage of chance if you have all projects selected.

There is more that goes into a query, for instance, the feeder is refreshed every 5 seconds. This means that if someone with only OET1 requests work at second 1. and you request work at second 3. They may have claimed all the results for OET1 that were waiting to be sent out. Thus your request odds are then at 0%.

Right now since this is a relatively new project, there are a lot of big users that like to badge hunt. Which means they only have OET1 selected for the time being until they get to a desired runtime for that project. This will get better over time, or we may decide to increase the weight of the project once we can verify that work will be available for a long time.

As you can see, lots of variables go into this. Patience is needed if you want to contribute to all projects. If you want to force getting a work unit, then check only OET1 for a bit and you'll get work. It's there just at the lowest priority.

Thanks,
-Uplinger

ran outta tasks, have to put UGM back on, but i can babysit tonight,
at least i got some!

Got 2 profiles going, UGM+OET+MCM+CEP and UGM+OET+CEP. Not run dry, both projecting 1 day per core computing to be done. The OET sit there with 1:29 hours TTC. Latest timestamp on OET is 06:17:44 UTC received for a batch 330 task, of just 3 in total on one and 8 on the other host.

When checking "my results", then indeed I see there has been a 6-hour gap without OET workunits. The flow has been restored since a couple of hours now thought.

Feeder priority for OET1 must be set pretty danged low. I have both OET1 and UGM (another low feeder priority project) selected, and only picked up one OET1 WU in the past few days. I am going to deselect UGM as soon as I get my ruby badge for that project (which may be this evening).