Home Artists Posts Import Register

Content

Despite my attempts this time to drastically solve the data loss problem, some of you have encountered this problem again. As a solution, I can add to HYDRA the option to upload and download data to Google Drive (full auto). It won't take much space, less than 1 megabyte. There is one nuance. Are you willing to enter authorization data? (question of trust in the HYDRA project)

Write your wishes.

Comments

Anonymous

I experienced the latest release and I'm excited about it but during the test phase after 12 hours the PC closed twice on the AMD PBO2 test with an OC carried out at default parameters of the tool and a minimum OC as required by the initial questions of the tool itself. The second time I found the PC turned off I do not know if the data have been saved. Is there a way to tell if a job save has been successful ? It would be good to save test data in the cloud...

Anonymous

Save them in the cloud yes, but it would be better to have a .conf file next to the save so that you can re-download and resume work easily .... I don't know if it can be done but it is a suggestion, maybe even a something more like this ....

Adrian Luff

Sounds good to me. An arbitrary file system path for other cloud sync services would be more universal though.

Anonymous

How it will help if even offline storage not working? Online will take more time to store data

Anonymous

release the lock on the files when writing out thats whats causing the issue to begin with the recovery file should be written to %appdata%\hydra\BLAH.PHNX I have never seen a program loose data like hydra does on a crash something is very incorrect here there is absolutely no reason it should be loosing the data if its being properly written out and saved multiple times unless its being kept open in memory some ware cloud backup sure I have no problem with oauth DO NOT use plain credentials tho use OAUTH

Travis Baptiste

sure oauth and maybe try to code the program to be able to load a file to be able to continue manually

Anonymous

I don't think cloud save is the solution to the data loss and only increases overhead and complexity. I would use two files to save the data to and use them alternating. If the last "savepoint" is lost, use the one before and repeat the testing step. Also I would make sure the data is really written to the media using unbuffered I/O or FlushFileBuffers (and probably also the equivalent for the partition) before continuing. Write data to the first file, close file, (call FlushFileBuffers), open other file, write data, close, sync, repeat. Yuri, thank you for your work and stay safe!

Anonymous

yes that's a great idea

Anonymous

Off topic - the GAME mode activation seems to be using the GPU usage percentage as reported by task manager, and not the utilization percentage reported by afterburner - is this expected? can it be user configured?

Anonymous

i had also same feeling that the value for game mode are not triggered correct and that why i only saw game mode active when 3Dmark benchmarks were running but never in the game. there was one version i was using (i believe it was x.yD pro? or something like that which was running perfect.