Quantcast
Channel: Questions in topic: "package"
Viewing all articles
Browse latest Browse all 690

Scenes in my Custom Package with slightly different names are identified as the same scene when I attempt to Import. How can I fix this?

$
0
0
I have several projects that I want to combine into a single project. The main project has multiple scenes that start with **F-** and **U-**. I want to import scenes from another project with similar names but start with **4-**. In all projects I have folders Audios, Images, Materials, and Scenes that are all under Assets.

I created a custom package for my project with assets starting with **4-**. When I try to import that package into my main project, I have a hot mess on my hands. The import window shows that the Audios, Images and Materials starting with **4-** are checked and will be added to those folders as expected. The problem I'm having is with my scenes. It's matching my scenes that start with **F-** or **U-** with my imported scenes starting with **4-**. I expected to see the scenes starting with **F-** or **U-** protected with the entire list of my scenes starting with **4-** with checkboxes checked. There should be no scenes flagged as new starting with **F-** or **U-**. The vast majority of them should be **4-**. The list of scenes should be about double.

![alt text][1]

I could not find anything stating that we cannot use hyphens/dashs in names. It appears that it is ignoring the prefix and matching the rest of the name calling it changed. I even renamed all of the scenes where there are no dashes in the names. I still have the same problem.

I have no idea what to do to fix this. [1]: /storage/temp/139931-unityimportsceneerror.jpg

Viewing all articles
Browse latest Browse all 690

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>