Search Issue Tracker
By Design
Votes
0
Found in
4.1.0b2
Issue ID
522779
Regression
No
When selecting a reference of type SpawnBubble, nothing shows up
Steps to reproduce :
- open the project attached "New Unity Project 134"
- open the scene
- select s1 and go to the inspector
- in the S1 open the selector, select assets and notice that nothing appears
Explanation :
he object selector will not find components inside prefab assets. Doing so would not be scalable, as it would require loading all prefabs to see what kind of components they contain. You can only see objects in the current open scene or objects which are themselves assets. It is still possible to drag prefab instances into the object field, however, to create references to prefab components.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- TransformAccessArray.Add behaves differently when the argument is null and the argument is an int
- [iOS] App crashes when trying to use WebCamTexture depth data on back triple camera
- [Mobile] Only second base Camera out of two base Cameras with priority 1 and -1 is rendered in the Player
- Highlighter.Highlight does not find window when using class name as window title
- Highlighter.Highlight highlights a different component when multiple components have the same property path
RElam
Jun 10, 2015 22:47
This is bad reasoning. A user's ability to find the object he wants also scales poorly. I have a reasonably sized project and scripts that load all things, and iterate over them. Sure, it takes time, but WAY, WAY less time than me having to find the things manually.
We should have some option for doing this. A fairly simple option would be an attribute for components that allows it to be selected as such, and just indicates that the prefab is always loaded if that component is at a referencable level. This ensures that the functionality is opted into, and the chance if it causing any sort of issue even on the largest of projects is VERY remote. It will assuredly be a net win.
Right now, with no ability to even supply selection list, I guess my only way of doing this is by some asset label hack that might work, but will likely be a bug spawner and certainly wicked clunky... or rebuild the entire object selection window... Surely these are not the solutions UT expects people to use.