Dre nice to see u fam thanks for coming by we will have your channel running soon and thanks again for taking time to pass by the forum after hearing we was delayed on the update of channel which included your channel as well. We will keep you updated or you can look here daily to see any updates from @fabeeobreen or myself here on the issue.
We really hope that this wearable can be updated in time to bring more functions.
Because this is a platform for us to display to the outside world.
We need this platform.
At the same time, there is also a need to be more open to the size of smart wearable devices. 3M cannot meet future demand.
For different wearable devices, corresponding permissions should be opened. As far as this wearable is concerned. I need them to be visible to non-owner players.
This is really for display
3 Likes
Would like to point out a few problems I encountered while trying to execute this update that I feel should be addressed.
As an example, installing a fresh smart wearable (the cube spawner example) lets me run and test the wearable, but i cannot compile it unless I execute npm install @dcl/asset-packs. This was not the case when we published the 1.2 update. Did the command npx @dcl/sdk-commands init --project smart-wearable receive an update where @dcl/asset-packs was accidentally excluded? Since this is not mentioned in the documentation site, it was not easy to find. Once I did this, the wearable was able to compile successfully.
Speaking of the documentation site, it states that the file size limit is 3Mb, as fabeeobreen has mentioned above, but this is actually not the case. Per the publication website, the limit is now 2mb. Is there any way that this can be updated so that new users don’t get misleading information?
If I compile the wearable without first creating a backup, I’m screwed. Luckily I found that out real early so it has not been an issue unless I forget to make a copy. This makes the source code unreadable. Is this normal? I am not very seasoned with compiling code. I can’t imagine this is normal. This also makes it so that if you do npm run start it shows you the live version of the smart wearable instead of the version you are trying to test. (may have something to do with the wearable id). None of this can possibly be normal. I was going a little crazy wondering how a smart wearable I compiled was showing me images that were not in the folder.
Once I finally had it compiled to my liking, knowing that the pre-compile source code works and can be tested but the post-compile source code is jacked we proceeded to the publication website. There are two ways to edit the wearable, inwhich we tried both. The window pops up, we upload the smart-wearable.zip file and the next window is the video. We upload that and the third window says that the file is too large and exceeds the 2MB limit.
This was the smallest I could get the size of the wearable with images. As you can see on the left is the size of the zipped file and on the right is the size of the unzipped file.
If this is an On-Going bug, who knows about it? What is the file limit? Is there anyone else trying to update a smart wearable or are we the only ones?
If we are the only ones is this put on low priority?
If the suggested problem is Size on Disk it actually isn’t because I tried one that was 876 kb unzipped by linking the images to a website instead of having them in the wearable.
If the video showcase doesn’t really need to change for this update, I wonder why we are still forced to upload a new video instead of being given the option to skip.
If packaging the code to a px and just have my wearable launch the px, how small does the file need to be for the site to accept it with this on-going bug where there seems to be a sweet spot?
Is there anyone actively working on this, are none of these things reported yet?
Will publishing a brand new wearable instead of updating make a difference? If so I’ll just drop a new wearable with a different GLB and call this one a loss.
I just want it to work and would appreciate any help. It does not seem like I am doing anything wrong, but if I am, I would love to know
2 Likes
As a new holder I was looking forward to the event we have planned in a few weeks. VTATV has created something unique and we the community need it hitting on all cylinders with no delays. Too many important things are happening for us to have delays. Please update and correct the issue so we can all get back to doing what we love.
2 Likes
thank you mozay for the support and being one of our channel holders. We have faith in dcl that they will fix this issue asap. We hope this can be resolved prior to your big event for freedom fest irl which was suppose to be aired in dcl smart wearable. For the note all vtatv functions are active including the smart wearable but is at its earliest update due to the limitation of the issue we cant add the updated version. overall the vtatv network is still live without the latest channel updates.
1 Like
Based on this smart wearable, I also have my own plans, but currently, due to file size restrictions, my plans have been disrupted. I am very much looking forward to the launch of this smart wearable device.
Relevant staff and officials are requested to update and correct such problems as soon as possible;
At the same time, I also hope that the authorities can release relevant permissions for such devices in the future. For example, when playing video content, the owner can choose whether to make it visible to other non-owner players.
This device is our platform for demonstrating DCL. It is also our hope for extradition.
I hope the officials will pay attention! Thanks!
1 Like
Thank you oao as one of our channel holders as well we truly appreciate the love and support you always give us. We look forwards to seeing the support team help us asap and resuming to our daily routine as usual. We are also undergoing some upgrades and improvements once the issue has been addressed we will be able to drop the updates back to back. We have noted your request and value your feedback as a valuable holder we have added the updates in the recent coming. Have a bless and positive day. We will keep you updated feel free to keep an eye on this forum to stay connected with results in resolution towards this situation. 
Love this wearable, wish all the best!
1 Like
Hello @BioMETA , @bitfiend !
The fix is been deployed. Please try again updating your zip and let me know if you have find any problem.
Thanks a lot for your patience
1 Like
so far so good I have published the new update with the 14 channels the system accepted it and now waiting for approval. XD
1 Like
thank u meta gami mall much love and always happy to still be your media service provider going on almost 1 year now straight OXOXOXOXOXO
1 Like
very happy. Early this morning, I found that the smart device is available. So happy.
And also added my channel.
Thanks to the support of the official community, this smart wearable can be put into use so quickly.
There will be other questions later. Ask you again!
small update added more channels
1 Like
Collection approved! @BioMETA
1 Like
thank u very much for the rapid response and approval
Minor update to text. Once approved text changed and was out of boundaries. We have fixed issues and corrected the file update here.
1 Like
Alright! Collection is enabled @BioMETA
1 Like
thank you very much very appriciative for the rapid response
1 Like
this wearable after 2 years is now ready as well for its mass update