galagast
My question now is, should I avoid using versioning at the end whenever uploading to Orbolt?
Or is there actually a way to update an asset with my versioning intact?

Hi, we replied to you through the Orbolt messaging system. Great asset BTW! We would advise to avoid using versioning at the end when uploading to Orbolt as the system will do that automatically for you. You can update your current asset galagast::heightfield_terracelerp::1.1 with the versioning intact, but then it will get confusing for users in the future as they will see 1.1 as a suffix but the Orbolt iteration will show as Version 2 or Version 3, etc.

It would be better if you upload the asset without the versioning at the end so any subsequent uploads will be automatically indicated as iterations through our system.

Let us know if you have any further questions!

Hi, just letting you know we replied to you yesterday through the Orbolt message system. The reason why the upload a new file for this asset took you a new asset page and didn't feel like an update to retain your previous asset information, was because the namespace of the asset had changed and therefore the system would consider it as a completely separate new asset. When the namespace stays the same on the upload, it will know it's an iterative update by showing beside the title and retain the information from the previous asset version.

Can you try uploading with the previous namespace and let us know if you run into any further problems?

The later builds have this issue fixed.