A water pipe is of type oCMobInter and has the following complex GO structure:
Another oCMobInter has this structure:
Nevertheless, the oCMobInter.prefab looks like this to ensure most of this VOB type is handled right now (Wildcard will not match for water pipe):
As both share the same prefab based on type (oCMobInter.prefab), we can't easily distinguish their needs.
Solution idea
If we have VOB types, which can't be fully handled via Prefab-regex logic, we can overcome this by doing the following:
[ ] Remove HVRFocus (and HVRGRabbable) from Prefabs and attach them during creation time on each sub-GO, where there is a MeshCollider existing.
[ ] (Bonus) Chests and some other objects currently highlight their "usable" part only (e.g. chest lid). Of course we can have all of them separately highlighted when pointed towards, but it would be great if the whole object glows when we hover over one of these meshes only. Example from chest:
Background
Right now, we attach our HVRFocus.cs component and the neccessary HVRGrabbable component onto Prefabs via Regex lookup (@see https://github.com/Gothic-UnZENity-Project/Gothic-UnZENity/issues/67). The problem is, that this logic isn't fully fitting dynamic G1 asset needs.
Example
A water pipe is of type oCMobInter and has the following complex GO structure:
Another oCMobInter has this structure:
Nevertheless, the oCMobInter.prefab looks like this to ensure most of this VOB type is handled right now (Wildcard will not match for water pipe):
As both share the same prefab based on type (oCMobInter.prefab), we can't easily distinguish their needs.
Solution idea
If we have VOB types, which can't be fully handled via Prefab-regex logic, we can overcome this by doing the following: