-
-
Notifications
You must be signed in to change notification settings - Fork 2
Glossary: FAQs
Yes, Assetify is a fully independent library developed from the ground up, thoroughly tested for performance and reliability.
No, all assets provided by Assetify are additional add-ons that complement the existing models tho we got support to replace native models as well!
No, Assetify features an advanced integrated downloader tool powered by assetify.webserver. There's no need to specify assets within the library's meta.xml or to manually synchronize models.
You can utilize the following API on the client side to check the status:
local isAssetifyLoaded = assetify.isLoaded()
Alternatively, you can set up a handler using the scheduler
that will execute on the client side once the library has been successfully loaded:
assetify.scheduler.execOnLoad(function()
print("Assetify has been successfully loaded.")
end)
Certainly! Just make sure removeWorld is set to false
.
Moreover, you can manage this feature directly through assetify.clearWorld and assetify.restoreWorld.
No, our implementation includes sophisticated occlusion and streaming methods for custom objects, ensuring performance that surpasses expectations. By default, MTA does not provide occlusion support for custom objects, including Levels of Detail (LODs), which often leads to suboptimal performance. We have rigorously tested this process for over a month. However, it is important to note that lag may also be affected by factors such as model quality, polygon count, collision topology, chunk size etc.
We do not recommend employing a single scene asset for larger maps. Instead, it is beneficial to segment your map into multiple scenes, which allows for improved control.
We offer a built-in feature to encrypt your models using the encryptKey
& encryptMode
asset property as indicated below:
"encryptKey": "yourSecureKeyHere"
"encryptMode": "aes128"