- May 22, 2015
- 8,653 (4.18/day)
|Processor||Intel i5-6600k (AMD Ryzen5 3600 in a box, waiting for a mobo)|
|Motherboard||ASRock Z170 Extreme7+|
|Cooling||Arctic Cooling Freezer i11|
|Memory||2x16GB DDR4 3600 G.Skill Ripjaws V (@3200)|
|Video Card(s)||EVGA GTX 1060 SC|
|Storage||500GB Samsung 970 EVO, 500GB Samsung 850 EVO, 1TB Crucial MX300 and 3TB Seagate|
|Audio Device(s)||Audioquest Dragonfly Red :D|
|Power Supply||Seasonic 620W M12|
|Mouse||Logitech G502 Proteus Core|
|Software||Arch Linux + Win10|
You're in luck, I was able to dig this up: https://www.cryengine.com/news/view...-ray-traced-reflections-in-cryengine-and-moreKinda defeat the purpose of vendor agnostic ray tracing when one vendor can render ray traced images better than the other ain't it . Also could you kindly point me to where the developers admit they were cutting corners ?
Also the torchlight reflections from the drone with AMD is quite jarring.
Look for the section where the guy explains their use of voxels which will artifact in some (known) circumstances.