Question BoundingVolumeHierarchy switched to internal in 1.0

Hello,

I see BoundingVolumeHierarchy switched from public to internal class in the 1.0 version. Why change that? It may be useful for custom collision handling.

As a matter of fact, I was using it for a bullet collision system :

• Bullet to Physics collision detection is handled by ray/sphere casts
• Bullet to Bullet is handled by a custom algorithm to get precise impact position & time (within the frame)

I used the BoundingVolumeHierarchy to feed potentially intersecting bullet pairs to this Bullet/Bullet algorithm.

 

Perhaps you can put your relevant code in a folder with an assembly definition reference?
https://docs.unity3d.com/Manual/Scr...finitionFiles.html#reference-another-assembly
https://docs.unity3d.com/Manual/ScriptCompilationAssemblyDefinitionFiles.html#create-asmref

 

It won't work, internal classes are only accessible inside the assembly they're built in.

 

Their suggestion means to create an asmref targeting the physics asmdef. You can then add a file with InternalsVisibleToAttribute for the assemblies you need to use that type from. This is pretty common practice when dealing with unexpected API surface changes. (The user seems to be suggesting putting code interfacing with that type in the original assembly, which is another way you can go about it).

 

asmref (notice it's ref, not def) lets you add to an existing assembly, so internal is accessible. I have done this with Unity.Collections and it works.

I have not used that attribute, but it looks ideal to handle this situation.

 

Awesome thanks