Skip to main content
100%

Gist 1ac3ec54b81ccb1992192549bf25cff4

✓ Published0🌍 Public
Aandybak
Last edited Jun 12, 2019
Created on Jun 12, 2019

This example demonstrates a minimal Unity event system triggered by collision detection. A MonoBehaviour script, EventTest, exposes a public Collider field and a UnityEvent. When another collider enters the assigned trigger zone, the OnTriggerEnter callback invokes the UnityEvent, allowing linked responses in the Inspector. The code relies on UnityEngine.Collider and UnityEngine.Events.UnityEvent, showing how Unity’s built-in event and trigger APIs connect gameplay logic without custom messaging.

AI-generated description

Similar vizzes

Loading thumbnail…

Gist 163847197f2c33368934a7c89ba711bc

This example visualizes a particle system and its interactions, built with the Unity game engine. It uses Unity's built-in modules for rendering, physics, and user interface elements, including the TextMeshPro and UI systems. The visualization is driven by Unity's component-based architecture, with a manifest that declares the package dependencies. The work does not use typical JavaScript data-visualization libraries like D3 or Three.js; instead, it leverages Unity's own animation, audio, and particle system modules to create the interactive scene.

Aandybak
59% match
Loading thumbnail…

Gist 55dffaaebad7fbed3efca0439487341b

This example shows a Unity script that tracks when a virtual object is grabbed and released by a user in an Oculus VR environment. It demonstrates how to trigger custom UnityEvents at the start, end, and during a grab, using the OVRGrabbable component from the Oculus Integration SDK. The script polls the grabbable’s `isGrabbed` state each frame in `Update()` and uses boolean flags to fire the `StartGrab`, `EndGrab`, and `WhileGrabbed` events only once per transition. No data source is involved; the visualization is the real-time interaction state of the object.

Aandybak
56% match
Loading thumbnail…

Gist e8a05cce9a76090a14ba06fd8f53a274

This example demonstrates a minimal Unity camera control utility through a static C# class. It exposes the main camera’s position as a property and provides a method to move it by an offset vector, while also offering a property to read or set the global time scale. The code uses Unity’s `Camera.main`, `Transform.position`, and `Time.timeScale` APIs. It shows how to encapsulate common scene-level operations in a reusable static helper, with no rendering or data visualization logic beyond the camera manipulation itself.

Aandybak
53% match
Loading thumbnail…

A simple tidy workflow for handling external 3rd party code in Unity 2018

A simple, text-based workflow for integrating external third-party code into Unity 2018 projects, shown as a set of markdown instructions and shell/JSON snippets. The example demonstrates a manual process using `git submodule add` to clone a repository, then wiring it into the Unity package system by authoring a `package.json` with a unique identifier (e.g., `com.uap.unitytimelineevents`) and referencing it in `manifest.json` via a file path. It also documents licensing guidance for open-source assets, recommending MIT for code and Creative Commons for artwork.

Aandybak
50% match
Loading thumbnail…

Gist 1973ba4fdee5e215ecb28f0db7f0aadb

This example shows a Unity Editor tool that automatically grants internal access to Shader Graph’s assembly during compilation. It hooks into `CompilationPipeline.assemblyCompilationStarted` to detect when the `Unity.ShaderGraph.Editor` assembly is being compiled, then locates its `AssemblyInfo.cs` file and appends an `InternalsVisibleTo` attribute referencing `BovineLabs.Vision.Editor`. The code uses `File.ReadAllLines`, `File.AppendAllText`, and `File.SetAttributes` to modify the file, while skipping the modification if the attribute already exists.

Aandybak
50% match
Loading thumbnail…

Gist 540bb6cf2f6ceada6387cc673f971498

This example demonstrates how to change an object’s appearance and size at runtime using Unity’s core APIs. It shows a script that accesses a GameObject’s MeshRenderer component to set its material color to red, then modifies the object’s Transform to scale it uniformly to five times its original size. The code relies on Unity’s `GetComponent<MeshRenderer>()` and the `transform.localScale` property, with `Color.red` and `Vector3` supplying the new values. The behavior is triggered directly in the `ChangeStuff()` method, illustrating a simple, immediate state change without animation or external data sources.

Aandybak
49% match
Loading thumbnail…

Gist c83bdc4de5e6486850b79ddfc73b899f

This example shows a networked virtual-reality interaction system where objects are grabbable by remote users, with ownership transferred to the grabbing hand. It builds on Unity’s OVRGrabbable and Photon PUN2 APIs, using PhotonView to manage ownership and RPCs like SetKinematicTrue and SetKinematicFalse to synchronize physics states across all clients. The script also triggers custom UnityEvents on grab and release, and optionally hides the hand’s SkinnedMeshRenderer during a grab. The behavior is driven by the hand’s PhotonView.IsMine check, ensuring only the local player’s actions affect the object.

Aandybak
49% match
Loading thumbnail…

prototype for easy and declarative definition of Events that should be present in the EventStore during testing of something

This example shows a fluent C# API for declaratively defining expected events in an EventStore during testing. It uses a builder pattern with `InsertEventsTo(EventStore)` and chained `.AggregateId(...)` calls, mapping aggregate IDs to arrays of `FakeEvent` objects like `ContactCreated` and `TaskCreated`. The code highlights a readable, intention-revealing syntax for setting up test fixtures without explicit event construction logic.

RRestuta
49% match