Open Ahmadre opened 1 month ago
Particular editor doesn't know the structure of your assets file in your project. so it generates default path for images.
You can change textureFileName
value to your own path, in the configs.json file.
"textureFileName": "images/particle_cover.webp"
In addition considering add embed tag in pubspecs.yaml
assets:
- assets/images/
Particular editor doesn't know the structure of your assets file in your project. so it generates default path for images. You can change
textureFileName
value to your own path, in the configs.json file."textureFileName": "images/particle_cover.webp"
In addition considering add embed tag in pubspecs.yaml
assets: - assets/images/
Then you're not creating particles with your editor...I'm confused...
I think the editor uses this asset file as the texture, so you need to copy-paste it in your project.
But I think it would be a good idea to put the assets in the package itself, then you can access the 3rd party assets in the app using this method. This way, users don't need to copy-paste the texture in their projects.
Particular creates a JSON
file that contains one or several particle layers. Each particle layer has a textureFileName
field. The textureFileName
field refers to the path of an image asset in your project. You can copy your uploaded image in the editor to your project.
In the next version, the option to download the layer texture will be available. Future versions may include options for image data
, image asset
paths, or image URLs
in the editor. However, in the initial steps, we only have the image asset path option.
I have a simple example and downloaded a configs.json file and I get this, when I start the app:
The editor only gave a json file 😓
I don't know why I need a texture.png?
Init Code: