100% agree. While the visualizer/screensaver is a nice touch, the science is the point so especially now we shouldn't "poke the bear."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.
Volunteering to fix F@H Viewer
Moderators: Site Moderators, FAHC Science Team
-
- Posts: 8
- Joined: Mon Jan 07, 2013 4:22 am
- Hardware configuration: Windows 10 || CPU: Intel i5-6500 3.20 GHz || GPU: AMD Radeon R9 290
Re: Volunteering to fix F@H Viewer
Windows 10 || CPU: Intel i5-6500 3.20 GHz || GPU: AMD Radeon R9 290
Re: Volunteering to fix F@H Viewer
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.
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
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
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
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
Hello,McMelloW wrote:I hope this information is useful for you.
Greetings McMelloW
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.
Working on it.tgillis06 wrote:did this ever happen? I'm running windows, a CPU and a nvidia 2080.. would love to see this protein!
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.
-
- Posts: 523
- Joined: Fri Mar 23, 2012 5:16 pm
Re: Volunteering to fix F@H Viewer
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!tgillis06 wrote: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
@Quantize: Your viewer improvements are great. Being able to disable the Wiggling and using Turbo Mode are nice enhancements.
-
- Posts: 2
- Joined: Wed Mar 18, 2020 3:45 am
Re: Volunteering to fix F@H Viewer
Hi,
Just wondering if this has been resolved yet, and if so, what I need to do on my end to get it working?
Just wondering if this has been resolved yet, and if so, what I need to do on my end to get it working?
-
- Site Moderator
- Posts: 6986
- Joined: Wed Dec 23, 2009 9:33 am
- Hardware configuration: V7.6.21 -> Multi-purpose 24/7
Windows 10 64-bit
CPU:2/3/4/6 -> Intel i7-6700K
GPU:1 -> Nvidia GTX 1080 Ti
§
Retired:
2x Nvidia GTX 1070
Nvidia GTX 675M
Nvidia GTX 660 Ti
Nvidia GTX 650 SC
Nvidia GTX 260 896 MB SOC
Nvidia 9600GT 1 GB OC
Nvidia 9500M GS
Nvidia 8800GTS 320 MB
Intel Core i7-860
Intel Core i7-3840QM
Intel i3-3240
Intel Core 2 Duo E8200
Intel Core 2 Duo E6550
Intel Core 2 Duo T8300
Intel Pentium E5500
Intel Pentium E5400 - Location: Land Of The Long White Cloud
- Contact:
Re: Volunteering to fix F@H Viewer
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
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
ETA:
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time
Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time
Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
-
- Posts: 2
- Joined: Wed Mar 18, 2020 3:45 am
Re: Volunteering to fix F@H Viewer
@PantherX, Thank you for the info and thanks for the warm welcome!