Little trick with FFX

Newtek Lightwave 3D (exporter developed by holocube, Integrated Plugin developed by juanjgon)

Moderator: juanjgon

Post Reply
User avatar
promity
Licensed Customer
Posts: 363
Joined: Sun Dec 19, 2010 7:59 am
Location: Russia

I never liked the way hairs created with FFX look like - at best, like a wire, very thick, etc. I used a transparency trick (gradient on the parameter Fiber V) which softened the look of the hair. Nevertheless, the hair remained rather coarse. Since the smallest thickness that can be assigned to hair is 0.0001. Which is equivalent to 100 um.
But the other day I accidentally entered the value 0.00005, and although this value immediately began to be displayed as 0.0001, the effect was made precisely from the value 0.00005. Accordingly, there is only a limitation of the LW interface, but the values ​​may be less than the LW interface can display. As a result, I can finally get more interesting hair with FFX.
Good luck!
Screenshot_1.png
AMD Threadripper 1950X/64gb ram/RTX 3080 Ti + RTX 2070/Samsung SSD 870 EVO 500 gb/
Lightwave 3d
User avatar
scooternva
Licensed Customer
Posts: 88
Joined: Thu Jul 04, 2019 6:13 pm
Location: Suburban Washington DC
Contact:

Huh... nice find!

Also a slightly worrying find. Most of the numeric fields I use day-to-day allow specifying values in μm as well as mm, and the ones that don't will just round up to the nearest millimeter. Now I'm wondering whether LW really IS keeping more precise values under the user interface and we just can't see them. It would certainly explain some of the weird polygon errors that can occur when you're doing something that involves math (especially things like creating radial arrays, clones, etc.)
Octane 2020.2.3.1 | LightWave 2019.1.5 (3134) | Win10 Pro 19041.1052 | 2 x Gigabyte AORUS RTX 2080 Ti Xtreme w/NVLink | Gigabyte AORUS Xtreme X399 | AMD Ryzen 2950X | 64 GB RAM | SSDs: Samsung 970 PRO 512 GB + Seagate FireCuda 510 2 TB | blog.gammans.zone
Post Reply

Return to “Lightwave 3D”