When I refreshed the page, my uploaded package showed up and they asked me to answer a form.
When uploading, it shows this warning: Some assets listed have dependencies that are part of Package Manager packages and these cannot be exported, so those references will be lost if those packages are not present in the importing project.Īfter upload, I went back to the publishing page. I wrote a README.md and set up a sample scene instead of a pdf. It turns out it has to be done from the Asset Store Tools package from Unity. I thought I could just export the file, then upload the. So instead I added a TouchSimulation component to an object in the scene. However, the Debug Touchscreen setting is not embedded in the scene.
How to make unity assets how to#
I made a sample Scene to demonstrate how to use the package. So I'd rather not publish unit tests, so as not to add an extra step for the user. This is because in order to include those test files, the user should tweak their Package/manifest.json, as I had experienced at. Then the unit tests also failed with this error: Assets/wafrat/Gesture/Tests/GestureManagerTests.cs(12,40): error CS0246: The type or namespace name 'InputTestFixture' could not be found (are you missing a using directive or an assembly reference?) Also the user will have to agree for Unity to re-setup the project. So the solution will be to document this in a README. The GUID resolves correctly after installing InputSystem
How to make unity assets install#
I haven't found a way to make Unity propose to install Input System at the same time, but I've experienced the same issue with tutorials, where upon importing an Asset, I had to update a certain Unity Registry asset before it would compile again. In my case, I'm depending on a Unity Registry package, not an asset package. I checked, and it turns out "Include dependencies" will include the assets that the ones you are exporting depend on. Originally the assembly depends on Unity.InputSystem The GUID is preserved but it doesn't know it's Unity.InputSystem
Upon import, I realized that it did not import Unity.InputSystem automatically. It's nice that it kept the hierarchy I had made for it. To check that it worked, I created a brand new project, and imported that package back. Then I went over to my Unity project, reorganized what I wanted to package up, and exported it, and ensured that "Include dependencies" was checked.
0 kommentar(er)
