Page 5 of 5

Re: Volunteering to fix F@H Viewer

Posted: Fri Apr 03, 2020 12:46 am
by rplate
Quantize wrote: Thing is: given the nature of software debugging, releasing a core update risks destabilizing the machinery.
And if such were to happen while we're all folding at 1.5 exaflops then everyone's gonna regret that decision.
100% agree. While the visualizer/screensaver is a nice touch, the science is the point so especially now we shouldn't "poke the bear."

Re: Volunteering to fix F@H Viewer

Posted: Sun Apr 05, 2020 2:58 pm
by Quantize
Here's the (draft) Pull Request: https://github.com/FoldingAtHome/fah-viewer/pull/21
Pre-compiled binary here: https://meertronix.com/FAHViewer.exe

Please inform of any bug or instability so that it can be fixed before requesting a release.

Re: Volunteering to fix F@H Viewer

Posted: Sun Apr 05, 2020 5:27 pm
by McMelloW
Using Windows 10 Home Edition,

Just downloaded the binairy FAHViewer.exe. This gives me the following results:
Double click on it shows a fullscreen viewer, with my Current Work Unit information. This is briljant.
However, when it starts on the windows time-out, it does NOt show my Current Work Unit information

Double click on the FAHScreensaver.scr file does show the screensaver, but my Current Work Unit information is NOT shown
In the Windows screensaver settings, I can only choose for fahscreensaver and NOT for fahviewer.

I hope this information is useful for you.

Greetings McMelloW

Re: Volunteering to fix F@H Viewer

Posted: Fri Apr 10, 2020 4:34 pm
by tgillis06
did this ever happen? I'm running windows, a CPU and a nvidia 2080.. would love to see this protein!

Re: Volunteering to fix F@H Viewer

Posted: Sat Apr 11, 2020 5:03 pm
by Quantize
McMelloW wrote:I hope this information is useful for you.

Greetings McMelloW
Hello,
Thank you so much for your report, McMellow.

What you're talking about here is a similar looking but separate system: the screensaver.
The screensaver has it's own code repository and will only be updated IF this FAHViewer.exe proves stable and functional.

In other words: what we've been testing here is solely what happens when you double-click FAHViewer.exe.
Preferably while running a CPU work-unit, so that you can see the actual protein.
tgillis06 wrote:did this ever happen? I'm running windows, a CPU and a nvidia 2080.. would love to see this protein!
Working on it.

You can try out the new viewer with the binary provided here: https://meertronix.com/FAHViewer.exe.
For now it supports only CPU work units. GPU is a bit more work still.

Re: Volunteering to fix F@H Viewer

Posted: Sat Apr 11, 2020 5:50 pm
by iceman1992
tgillis06 wrote:did this ever happen? I'm running windows, a CPU and a nvidia 2080.. would love to see this protein!
You mean did the viewer ever work? Yes it did. Here's a very old screenshot I have of a large protein. Core A4 Project 7808, from 2012!
Image

Re: Volunteering to fix F@H Viewer

Posted: Tue Apr 21, 2020 11:04 am
by Hou5e
@Quantize: Your viewer improvements are great. Being able to disable the Wiggling and using Turbo Mode are nice enhancements.

Re: Volunteering to fix F@H Viewer

Posted: Tue Apr 28, 2020 7:22 pm
by darkfield117
Hi,

Just wondering if this has been resolved yet, and if so, what I need to do on my end to get it working?

Re: Volunteering to fix F@H Viewer

Posted: Tue Apr 28, 2020 8:21 pm
by PantherX
Welcome to the F@H Forum darkfield117,

The latest stable client V7.6.9 seems to have fixed the FAHViewer issue for many Donors: viewtopic.php?f=24&t=34466

Doing an upgrade from an older version of the newer version is fine. If you're doing an fresh installation, you will need to reboot your system/client before you add a GPU Slot.

If you need additional help, please create a new topic with your log file. Guidance is provided here: viewtopic.php?f=24&t=26036 :)

Re: Volunteering to fix F@H Viewer

Posted: Tue Apr 28, 2020 8:25 pm
by darkfield117
@PantherX, Thank you for the info and thanks for the warm welcome!