The calculation you are using there is in the shaders for Depth3D, which is fine.
I was talking about the interaxial distance used in the Nvidia Driver and how they calculate and use it, as I am in the process or replicating their driver calculations, so the wrapper works both with 3D Vision and without.
The one described here:)
https://www.nvidia.com/content/GTC-2010/pdfs/2010_GTC2010.pdf
https://developer.nvidia.com/sites/default/files/akamai/gameworks/CN/3dvision_cgdc_en.pdf
The shaders don't need to know anything about IPD as separation != IPD: Separation = Interaxial / ScreenWidth.
Nvidia normally calculates Interaxial based on the Size of the Monitor, but they don't say how exactly. In any case, I think around 55-65millimeters is what seems to be accepted.
Regarding the previous image, 3D Vision actually uses the Right eye first and left eye second (The image posted above, uses L-R SBS. I wonder if this is why you couldn't focus it?)
The calculation you are using there is in the shaders for Depth3D, which is fine.
I was talking about the interaxial distance used in the Nvidia Driver and how they calculate and use it, as I am in the process or replicating their driver calculations, so the wrapper works both with 3D Vision and without.
The shaders don't need to know anything about IPD as separation != IPD: Separation = Interaxial / ScreenWidth.
Nvidia normally calculates Interaxial based on the Size of the Monitor, but they don't say how exactly. In any case, I think around 55-65millimeters is what seems to be accepted.
Regarding the previous image, 3D Vision actually uses the Right eye first and left eye second (The image posted above, uses L-R SBS. I wonder if this is why you couldn't focus it?)
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
[quote="Helifax"].....
Regarding the previous image, 3D Vision actually uses the Right eye first and left eye second (The image posted above, uses L-R SBS. I wonder if this is why you couldn't focus it?)[/quote]
I did wonder about that when I tried to view it :-)
Helifax said:.....
Regarding the previous image, 3D Vision actually uses the Right eye first and left eye second (The image posted above, uses L-R SBS. I wonder if this is why you couldn't focus it?)
I did wonder about that when I tried to view it :-)
Gigabyte RTX2080TI Gaming OC, I7-6700k ~ 4.4Ghz, 3x BenQ XL2420T, BenQ TK800, LG 55EG960V (3D OLED), Samsung 850 EVO SSD, Crucial M4 SSD, 3D vision kit, Xpand x104 glasses, Corsair HX1000i, Win 10 pro 64/Win 7 64https://www.3dmark.com/fs/9529310
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
[quote="Helifax"]The calculation you are using there is in the shaders for Depth3D, which is fine.
I was talking about the interaxial distance used in the Nvidia Driver and how they calculate and use it, as I am in the process or replicating their driver calculations, so the wrapper works both with 3D Vision and without.
The one described here:)
https://www.nvidia.com/content/GTC-2010/pdfs/2010_GTC2010.pdf
https://developer.nvidia.com/sites/default/files/akamai/gameworks/CN/3dvision_cgdc_en.pdf
The shaders don't need to know anything about IPD as separation != IPD: Separation = Interaxial / ScreenWidth.
Nvidia normally calculates Interaxial based on the Size of the Monitor, but they don't say how exactly. In any case, I think around 55-65millimeters is what seems to be accepted.
Regarding the previous image, 3D Vision actually uses the Right eye first and left eye second (The image posted above, uses L-R SBS. I wonder if this is why you couldn't focus it?)[/quote]
Oh, that calculation actually comes from here on page 10.
https://developers.google.com/vr/jump/rendering-ods-content.pdf
It also talks about averages they use for IPD. They default to 64mm So ya I would think anything in that range of 55-65 is fine. :)
Yes, I swapped the image in the first one on the Monitor from R-L to L-R and I was able to resolve the image menus. Had to bring out another monitor for this :D
As for the 2nd image I had to swap it back to R-L to resolve the image.
It's Like in the first image The background is L-R and the menus are R-L.
In the 2nd image, I would assume it's the opposite. Menus would be L-R and the background is R-L now. I hope this helps. :)
Helifax said:The calculation you are using there is in the shaders for Depth3D, which is fine.
I was talking about the interaxial distance used in the Nvidia Driver and how they calculate and use it, as I am in the process or replicating their driver calculations, so the wrapper works both with 3D Vision and without.
The shaders don't need to know anything about IPD as separation != IPD: Separation = Interaxial / ScreenWidth.
Nvidia normally calculates Interaxial based on the Size of the Monitor, but they don't say how exactly. In any case, I think around 55-65millimeters is what seems to be accepted.
Regarding the previous image, 3D Vision actually uses the Right eye first and left eye second (The image posted above, uses L-R SBS. I wonder if this is why you couldn't focus it?)
Oh, that calculation actually comes from here on page 10.
It also talks about averages they use for IPD. They default to 64mm So ya I would think anything in that range of 55-65 is fine. :)
Yes, I swapped the image in the first one on the Monitor from R-L to L-R and I was able to resolve the image menus. Had to bring out another monitor for this :D
As for the 2nd image I had to swap it back to R-L to resolve the image.
It's Like in the first image The background is L-R and the menus are R-L.
In the 2nd image, I would assume it's the opposite. Menus would be L-R and the background is R-L now. I hope this helps. :)
[quote="Helifax"]@rustyk21:
How about this one?
[img]https://forums.geforce.com/cmd/default/download-comment-attachment/75872/[/img][/quote]
Yep, I'm just using the cross eyed method to view the image rather than any viewing software or 3d display.
This one is fine when using that method, sorry if I've confused the issue, that was where I was coming from.. IPD/Separation is still important but I thought that was just a factor as far as maximum separation/depth is concerned.
Excited about what you're doing and glad to see blueskydefender here again too :-)
Yep, I'm just using the cross eyed method to view the image rather than any viewing software or 3d display.
This one is fine when using that method, sorry if I've confused the issue, that was where I was coming from.. IPD/Separation is still important but I thought that was just a factor as far as maximum separation/depth is concerned.
Excited about what you're doing and glad to see blueskydefender here again too :-)
Gigabyte RTX2080TI Gaming OC, I7-6700k ~ 4.4Ghz, 3x BenQ XL2420T, BenQ TK800, LG 55EG960V (3D OLED), Samsung 850 EVO SSD, Crucial M4 SSD, 3D vision kit, Xpand x104 glasses, Corsair HX1000i, Win 10 pro 64/Win 7 64https://www.3dmark.com/fs/9529310
Many thanks guys for helping out with this!
I added all 4 modes : L-R, R-L in SBS and L-R, R-L in TB and I set the default interaxial to 55 mm.
Everything can be configured and changed from the ini file to accommodate every need :)
Thank you for the article, I haven't seen that one before and it is quite an interesting read!
Back to testing and regression testing now ^_^
Many thanks guys for helping out with this!
I added all 4 modes : L-R, R-L in SBS and L-R, R-L in TB and I set the default interaxial to 55 mm.
Everything can be configured and changed from the ini file to accommodate every need :)
Thank you for the article, I haven't seen that one before and it is quite an interesting read!
Back to testing and regression testing now ^_^
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
Getting there with the tests and refining things:)
Now we have "more depth" and a cleaner image where I previously didn't :)
(This is all Stereo Reconstruction - AKA Depth3D. Sure is not as awesome as Geo3D, but still this looks pretty sick! ^_^)
[img]https://forums.geforce.com/cmd/default/download-comment-attachment/75898/[/img]
[img]https://forums.geforce.com/cmd/default/download-comment-attachment/75899/[/img]
[img]https://forums.geforce.com/cmd/default/download-comment-attachment/75900/[/img]
[img]https://forums.geforce.com/cmd/default/download-comment-attachment/75901/[/img]
[img]https://forums.geforce.com/cmd/default/download-comment-attachment/75902/[/img]
[img]https://forums.geforce.com/cmd/default/download-comment-attachment/75903/[/img]
[img]https://forums.geforce.com/cmd/default/download-comment-attachment/75904/[/img]
PS: How many "halos" can you spot at first glance? Now, imagine playing this at high speed. How many will you spot then? :)
Getting there with the tests and refining things:)
Now we have "more depth" and a cleaner image where I previously didn't :)
(This is all Stereo Reconstruction - AKA Depth3D. Sure is not as awesome as Geo3D, but still this looks pretty sick! ^_^)
PS: How many "halos" can you spot at first glance? Now, imagine playing this at high speed. How many will you spot then? :)
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
Awesome, hopefully the new game isn't that much different.
i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
ASUS Turbo 2080TI
Samsung SSD 840Pro
ASUS Z97-WS3D
Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)
[quote="Helifax"]Many thanks guys for helping out with this!
I added all 4 modes : L-R, R-L in SBS and L-R, R-L in TB and I set the default interaxial to 55 mm.
Everything can be configured and changed from the ini file to accommodate every need :)
Thank you for the article, I haven't seen that one before and it is quite an interesting read!
Back to testing and regression testing now ^_^
[/quote]
Thanks you so much, you are the best :D.
Helifax said:Many thanks guys for helping out with this!
I added all 4 modes : L-R, R-L in SBS and L-R, R-L in TB and I set the default interaxial to 55 mm.
Everything can be configured and changed from the ini file to accommodate every need :)
Thank you for the article, I haven't seen that one before and it is quite an interesting read!
[quote="Helifax"]Getting there with the tests and refining things:)
Now we have "more depth" and a cleaner image where I previously didn't :)
(This is all Stereo Reconstruction - AKA Depth3D. Sure is not as awesome as Geo3D, but still this looks pretty sick! ^_^)
PS: How many "halos" can you spot at first glance? Now, imagine playing this at high speed. How many will you spot then? :)[/quote]
Hey Helifax, big fan of your work! Did you ever complete this Depth3D correction of Doom? I've got a 4K LG C6V and the openGL to DX wrapper doesn't work unfortunately(you wouldn#t know how to fix this?). I would love to try play this version if you've got a tester I could try?
Helifax said:Getting there with the tests and refining things:)
Now we have "more depth" and a cleaner image where I previously didn't :)
(This is all Stereo Reconstruction - AKA Depth3D. Sure is not as awesome as Geo3D, but still this looks pretty sick! ^_^)
PS: How many "halos" can you spot at first glance? Now, imagine playing this at high speed. How many will you spot then? :)
Hey Helifax, big fan of your work! Did you ever complete this Depth3D correction of Doom? I've got a 4K LG C6V and the openGL to DX wrapper doesn't work unfortunately(you wouldn#t know how to fix this?). I would love to try play this version if you've got a tester I could try?
[quote="Helifax"]Getting there with the tests and refining things:)
Now we have "more depth" and a cleaner image where I previously didn't :)
(This is all Stereo Reconstruction - AKA Depth3D. Sure is not as awesome as Geo3D, but still this looks pretty sick! ^_^)
PS: How many "halos" can you spot at first glance? Now, imagine playing this at high speed. How many will you spot then? :)[/quote]
Hey Helifax, big fan of your work! Did you ever complete this Depth3D correction of Doom? I've got a 4K LG C6V and the openGL to DX wrapper doesn't work unfortunately(you wouldn#t know how to fix this?). I would love to try play this version if you've got a tester I could try?
Helifax said:Getting there with the tests and refining things:)
Now we have "more depth" and a cleaner image where I previously didn't :)
(This is all Stereo Reconstruction - AKA Depth3D. Sure is not as awesome as Geo3D, but still this looks pretty sick! ^_^)
PS: How many "halos" can you spot at first glance? Now, imagine playing this at high speed. How many will you spot then? :)
Hey Helifax, big fan of your work! Did you ever complete this Depth3D correction of Doom? I've got a 4K LG C6V and the openGL to DX wrapper doesn't work unfortunately(you wouldn#t know how to fix this?). I would love to try play this version if you've got a tester I could try?
Hi guys,
Sorry for the big delay! After my work on this some months ago, I got side-tracked with other things:(
The work on the wrapper is mostly done! I had a few issues that I wanted to fix and address, but then the holidays ended and I didn't have the time to finish it:(
I do plan to finish and wrapping everything in the following weeks:)
I apologise for this delay!
Sorry for the big delay! After my work on this some months ago, I got side-tracked with other things:(
The work on the wrapper is mostly done! I had a few issues that I wanted to fix and address, but then the holidays ended and I didn't have the time to finish it:(
I do plan to finish and wrapping everything in the following weeks:)
I apologise for this delay!
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
Absolutely no need for apologies!
But we can't control our curiosity much longer, so I'm just glad to see that the project is delayed and not dumbed :)
I was talking about the interaxial distance used in the Nvidia Driver and how they calculate and use it, as I am in the process or replicating their driver calculations, so the wrapper works both with 3D Vision and without.
The one described here:)
https://www.nvidia.com/content/GTC-2010/pdfs/2010_GTC2010.pdf
https://developer.nvidia.com/sites/default/files/akamai/gameworks/CN/3dvision_cgdc_en.pdf
The shaders don't need to know anything about IPD as separation != IPD: Separation = Interaxial / ScreenWidth.
Nvidia normally calculates Interaxial based on the Size of the Monitor, but they don't say how exactly. In any case, I think around 55-65millimeters is what seems to be accepted.
Regarding the previous image, 3D Vision actually uses the Right eye first and left eye second (The image posted above, uses L-R SBS. I wonder if this is why you couldn't focus it?)
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com
(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)
I did wonder about that when I tried to view it :-)
Gigabyte RTX2080TI Gaming OC, I7-6700k ~ 4.4Ghz, 3x BenQ XL2420T, BenQ TK800, LG 55EG960V (3D OLED), Samsung 850 EVO SSD, Crucial M4 SSD, 3D vision kit, Xpand x104 glasses, Corsair HX1000i, Win 10 pro 64/Win 7 64https://www.3dmark.com/fs/9529310
How about this one?
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com
(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)
Oh, that calculation actually comes from here on page 10.
https://developers.google.com/vr/jump/rendering-ods-content.pdf
It also talks about averages they use for IPD. They default to 64mm So ya I would think anything in that range of 55-65 is fine. :)
Yes, I swapped the image in the first one on the Monitor from R-L to L-R and I was able to resolve the image menus. Had to bring out another monitor for this :D
As for the 2nd image I had to swap it back to R-L to resolve the image.
It's Like in the first image The background is L-R and the menus are R-L.
In the 2nd image, I would assume it's the opposite. Menus would be L-R and the background is R-L now. I hope this helps. :)
Yep, I'm just using the cross eyed method to view the image rather than any viewing software or 3d display.
This one is fine when using that method, sorry if I've confused the issue, that was where I was coming from.. IPD/Separation is still important but I thought that was just a factor as far as maximum separation/depth is concerned.
Excited about what you're doing and glad to see blueskydefender here again too :-)
Gigabyte RTX2080TI Gaming OC, I7-6700k ~ 4.4Ghz, 3x BenQ XL2420T, BenQ TK800, LG 55EG960V (3D OLED), Samsung 850 EVO SSD, Crucial M4 SSD, 3D vision kit, Xpand x104 glasses, Corsair HX1000i, Win 10 pro 64/Win 7 64https://www.3dmark.com/fs/9529310
I added all 4 modes : L-R, R-L in SBS and L-R, R-L in TB and I set the default interaxial to 55 mm.
Everything can be configured and changed from the ini file to accommodate every need :)
Thank you for the article, I haven't seen that one before and it is quite an interesting read!
Back to testing and regression testing now ^_^
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com
(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)
Now we have "more depth" and a cleaner image where I previously didn't :)
(This is all Stereo Reconstruction - AKA Depth3D. Sure is not as awesome as Geo3D, but still this looks pretty sick! ^_^)
PS: How many "halos" can you spot at first glance? Now, imagine playing this at high speed. How many will you spot then? :)
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com
(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)
Thanks for all your many hours of work with OpenGL
i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
ASUS Turbo 2080TI
Samsung SSD 840Pro
ASUS Z97-WS3D
Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)
Thanks you so much, you are the best :D.
Hey Helifax, big fan of your work! Did you ever complete this Depth3D correction of Doom? I've got a 4K LG C6V and the openGL to DX wrapper doesn't work unfortunately(you wouldn#t know how to fix this?). I would love to try play this version if you've got a tester I could try?
Hey Helifax, big fan of your work! Did you ever complete this Depth3D correction of Doom? I've got a 4K LG C6V and the openGL to DX wrapper doesn't work unfortunately(you wouldn#t know how to fix this?). I would love to try play this version if you've got a tester I could try?
Win7 64bit Pro
CPU: 4790K 4.8 GHZ
GPU: Asus Geforce RTX 2080 TI Rog Strix OC
Monitor: Asus PG278QR
And lots of ram and HD's ;)
Sorry for the big delay! After my work on this some months ago, I got side-tracked with other things:(
The work on the wrapper is mostly done! I had a few issues that I wanted to fix and address, but then the holidays ended and I didn't have the time to finish it:(
I do plan to finish and wrapping everything in the following weeks:)
I apologise for this delay!
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com
(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)
But we can't control our curiosity much longer, so I'm just glad to see that the project is delayed and not dumbed :)
Win7 64bit Pro
CPU: 4790K 4.8 GHZ
GPU: Asus Geforce RTX 2080 TI Rog Strix OC
Monitor: Asus PG278QR
And lots of ram and HD's ;)