Works for me without error. DeepFaceLab_DirectX12 from 18.08.2021 (date of batch files) said:borgie said:Liae-ud res 128 , wf. Works with GTX 1660 TI 6 gb Vram
== ==
== Model name: wf_SAEHD ==
== ==
== Current iteration: 2440920 ==
== ==
==------------------ Model Options ------------------==
== ==
== resolution: 128 ==
== face_type: wf ==
== models_opt_on_gpu: True ==
== archi: liae-ud ==
== ae_dims: 256 ==
== e_dims: 64 ==
== d_dims: 64 ==
== d_mask_dims: 22 ==
== masked_training: True ==
== eyes_mouth_prio: True ==
== uniform_yaw: True ==
== adabelief: True ==
== lr_dropout: n ==
== random_warp: False ==
== true_face_power: 0.0 ==
== face_style_power: 0.0 ==
== bg_style_power: 0.0 ==
== ct_mode: rct ==
== clipgrad: False ==
== pretrain: True ==
== autobackup_hour: 1 ==
== write_preview_history: False ==
== target_iter: 0 ==
== random_src_flip: False ==
== random_dst_flip: True ==
== batch_size: 8 ==
== gan_power: 0.0 ==
== gan_patch_size: 192 ==
== gan_dims: 32 ==
== ==
==------------------- Running On --------------------==
== ==
== Device index: 0 ==
== Name: NVIDIA GeForce GTX 1660 Ti ==
== VRAM: 5.10GB ==
== ==
=======================================================
2.0 , after May 2021 -
This model creates a Python error when I run it.
My DFL works fine with my own models.
I suspect this person put some malicious code into the model...and the overflow bug he is trying to abuse, or what it is, has been fixed in the meantime.
That is my guess.
I double virus scanned the model first ofc.
--------------------------------------------------------------------------------------------------------------------------------------
The first error was a memory error + python error with 10 GB RAM free with such a little model on pretrain data...using default settings (the same as the creator used)
2d and 3d time with 15 GB free RAM it only gave me python error.
I looked at the model files and it looks correct.
My GPU is newer/more powerful than his so mine for sure can run it.
My DFL is version 2, but should work even if his was version 1 it should not matter from what I have read.
************************
>> Be Aware! <<
************************
Maybe you can fix your problem if you raise the amount of virtual workspace of your hd.
sysdm.cpl
Set the amount of your workspace to 64000 MB
""
Give it a try, you can set it back if this don't work for you...