Thanks for reporting! I was able to reproduce the issue, it'll be fixed in the upcoming version Asset Forge 2.1.0 (expected this month)
