Provide a rollout flag under workspace: We could temporarily provide a developer-controlled rollout flag under the workspace so that developers have a significant period of time to adjust to the change. That would be a breaking change because the size of the physics and render geometry for existing nonuniformly scaled unions in places would change. Release as-is: If the impact to places is very low, we could release with the current beta behavior. Currently, this beta reinterprets the scale of those existing unions, such that they now fill the bounding box rather than being letterboxed. This means that there are some non-uniformly scaled unions out there. With this method, you don’t need to name the uploaded module (model) “MainModule”, and can instead name it whatever you like, provided you / your game has ownership of that model.While working on models with the beta enabled, let us know which option ends up being more useful and if the popup gets in the way.Īs pictured at the start of the post, you can actually nonuniformly scale unions right now, it just applies often undesirable letterbox scaling. Where the variable “Module” is the actual module that you want to use. Local module = InsertService:LoadAssetVersion(moduleLastId):GetChildren() Local latest = InsertService:GetLatestAssetVersionAsync(MODULE_ID) Local InsertService = game:GetService("InsertService") This is actually possible, however this will only work on a live server (Within a place published to the site).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |