I'm currently investigating this issue, but have already fixed the second issue you mentioned (will be in Asset Forge 2.5.1!)
