Optrix Pty. Ltd.

You would just have to ensure that any modification like this is **completely optional** - we run most of our VR applications in locations with no internet access (for security...

We've also modified the system to use our laser-pointers instead of mallets too. You can make the keys work with almost any collider or raycast. In your **OnColliderEnter** or when...

The basic idea is to just place gameobjects with simple colliders (SphereColliders, most likely) on the tip of the object you want to use to strike the key. Then on...

We can't put in some conditional compile directives? I'm using the LTS version of 2018.4, and I can't use the package either. I LOVE the updates to XR devices in...

The performance of the Light-Weight Render Pipeline on VR in 2019 is very nice, and controller input is SO much better with the 2019 API. LWRP also appears to work...

The major issues seem to be mostly about controller input - you might be able to use preprocessor directives to have a single branch that supports both. For example, in...

Note that this has nothing to do with multi-threading and will happen in a single-threaded application. In fact, I can easily replicate it in a very small app. [MemLeak.zip](https://github.com/bradbase/xlcalculator/files/7955796/MemLeak.zip) I'd...

OK - one massive source of the issue is the **lru_cache** directive found in eval_cell. This is causing an unlimited number of EvaluatorContext objects to be kept in memory. Setting...

Removing the **lru_cache** directive has one unexpected side-effect - the cycle detector in **EvaluatorContext.eval_cell** starts throwing up unexpected and incorrect cycle exceptions when you've got a formula that references the...

Fixes issue #54