DCL Neurolink N1
Wearables
DCL Neurolink N1
- Description: Your link to the metaverse!
- Rarity: legendary
- Category: earring
External Image
Link to editor
DCL Neurolink N1
The collection has been assigned to Sango
Hey, does a button need to be pressed to activate the ui? i cant see anything in the test area
There should be an Icon in the bottom right of the screen. However, Shibu and I are working with the Dapps team on a possible bug for recently uploaded smart wearables. I’ll post here if / when we find the culprit!
@Sango we just uploaded a new zip, if you could check that!
This collection has been approved.
@Sango hi there! we just updated the software for the Neurolink N1.
The update will allow for custom bookmarking of places inside decentraland
Updates have been pushed
hey @Sango we pushed an update to the code base for this smart wearable.
Updates have now been pushed
we just pushed the smart wearable update
Is anyone assigned to this wearable anymore?
The collection has been assigned to AndreusAs
There is an error on the item approval:
Please, delete the said file from the item archive and re-upload it.
Cheers!
updated.
as a note, the npm run pack to generate the smart wearable .zip file auto adds this errant file. please foundation fix.
additionally, the warning inside the CLI tells users your zip file is greater that 2mb which is not the correct limit for a smart wearable file.
Hey! Another error:
Here is structure of a smart wearable, that was approved with no errors. Let’s make the structure of your .zip similar to it.
Cheers!
I don’t have a male directory in the zip. The wearable has been a smart wearable for 2 years and the structure of the folder hasn’t change at all - just the code files so I don’t know what the new npm run pack or your deployment process is doing differently.
It looks like for some reason the wearable.json was omitted on pack maybe? @Lastraum @AndreusAs
I mentioned the .crdt file to Nico E a few days ago regarding npm run pack. Something’s def funky with it.
nope it’s there in the screenshot
I think its possibly extra glb files in your assets folder, those need to be mentioned in the wearable.json under contents, so the script can read it and use it properly.
like so:
"contents": [
"assets/first.glb"
"assets/second.glb"
"assets/third.glb"
],