I'm running mac os 10.13.6, boinc 7.12.0. I've notice with the latest app 8.04, I can no longer display graphics, when I click on the "show graphics" button nothing happens. The app appears to be working fine. Has anyone else seen this behavior?

---

You are right.. It works for Einstein @ home but not for Seti. WTF?

---

Thanks for confirming! Probably a bug. I don't use the graphics that often but I do like to look at them every once in a while. Hopefully fixed soon.

---

Yes, same issue here, (running on OS 10.11.6) Shame as I rejoined to show my class SETi as part of their science STEM project!
Any update or work around?

Not sure. Been so long since I ran the project on my mac but I believe the screen saver was disabled as it was slowing down or causing issue with work units on the graphics cards.

For the CPU work units, I believe the graphics might still work.

edit...

Nevermind, I looked. Everyone here is running CPU work units. So, no. The graphics portion is not working on the CPU apps. Currently only TBar is developing applications for MAC but he's busy compiling the cuda apps for the GPUs. Since each new version of OS from apple seems to break the previous cuda, he's having a very hard time with it. Which leaves no time for the CPU apps as they work, just not with the graphics.

---

Thanks for the update!
Still very happy to keep supporting SETi, will use a screen shot of graphics instead!

Hi, all … same problem with me. Just after updating to 7.12.0 graphics failed. Uncool - downgrading to previous version may help ?
Greets - Ralf -

what version were you on when it was working?

It's not the BOINC version that broke it, it's the new Seti application that did. As https://setiathome.berkeley.edu/apps.php shows, v8.04 was just released on the 29th of August. Any work you had before with older applications would still have had the graphics/screen saver. Any newer will not.

But that's always been the problem here at Seti, since they gave the community the chance to build the science applications. There's just one volunteer developer who decides for all that the graphics are no longer needed, and thus they're removed. Same thing happened with the Windows (GPU) apps. You apparently have no say in this, another user decides for you.

I don't agree with that and have written a complaint about it to the admin of this project.

---

yep, I just found this out the hard way! -installed 6.12.10 no graphic!

keep us posted if you have any luck!

+ happy to help if you think it will help... should I send a complaint a well? And who to?

Charlie Fenton found the problem. The executable bits weren't set on the setigraphics_8.04 binary. If you go into the BOINC directory and change them manually it should work. Or you can reset the project and it should download new executables.

---

@SETIEric@qoto.org (Mastodon)

Thanks Eric. And excuses for being wrong in my previous post.

I'm running Mac 8.04 and graphics display NOT working.

My show graphics has stopped working as well.

I'm running SETI@Home on an iMac, macOS High Sierra version 10.13.6, the SETI@Home version is v8 8.04

I've tried reseting the project as suggested but that didn't bring back the graphics.

I'll keep supporting SETI@Home but the graphics would be nice to have back.

Best Regards
Carl

---

I would caution all users on laptops and desktop, might want to restrict the number of threads running. Macs tend to overheat as they have poor airflow.

I also tried to reset the project and use terminal to reset the properties without any luck so not sure what the issue is.

---

Hi Zalster

Thanks for the tip, how do I set the max number of threads ?

Best Regards
Carl

The easiest way is to use the preferences in BOINC manager. There is 2 ways of showing BOINC. The simplified view and the advance view. Click on View and change it to advance (you can always go back and change it to simple later if you want). Then click on About Boinc Manager and a pull down show appear. Click preferences. A new window should appear. Click computing.

At the top is Usage limits

Use at most XXX % of the CPUs

Depending on your CPU Chip, this value will vary. Example If you have a 4 cores/8 threads, set this to either 50% (4 work units) or 25%(2 work units). Keep in mind, if you are running any work on a GPU, the gpu will always have priority over a cpu work unit.

So in the example above. If you limit it to 50% of a 8 thread, 4 work units will run.
That could be 1 nvidia gpu, 1 intel gpu and 2 CPU work units. (My MacPro has both an intel Iris graphic and a nvidia graphic) You can tell seti not to use either the Intel or nvidia graphics from your member page in the middle section marked Seti@home preferences. Just unselect the one you don't want. I unselected Intel as it's not that great at running and really you shouldn't use the built in graphic on your chip anyway.

So for my case since I deselected the intel, I actually have 1 Nvidia work unit and 3 CPU work tasks.

Same goes for 25%. 1 GPU and 1 CPU work tasks. If I run out of GPU tasks, then a second CPU work tasks starts up.

Change the value to what you want, then click save. Then go to Options pull down and click on Read local prefs file. Boinc manager should see the changes and restrict how many threads are used.


Hope I have not confused you with this. By the way, don't use this method when someone tells you to "save a core" for your graphics card. This is not how to do that. That is a totally different topic and has to be done in a totally different way.


Happy Crunching....

Zalster

---

So, I tried resetting the project and checked all the preferences, still no graphics. What is the exact path to setigraphics_8.04?

I'm on an iMac 27 mid-2011, i7 3.4GHz, 32GB, and the Radeon 6970M w/2GB memory, 10.11.6, and the setting for no GPU or use GPU makes no difference.

---

The path to the location of the setigraphic_8.04 is

Macintosh HD > Library > Application Support > Boinc Data > projects > setiathome.berkeley.edu


To set the properties for setigraphics requires a terminal at that level and

sudo chmod +x NameOfFile

But is you are not familiar with terminal commands, I would not recommend trying this.


Zalster

---

Thanks Zalster, that fixed the problem for me.

---