Join a community!

Hey everyone! 

I using Unity 2019.2.14f1 to create a simple 3D game, as you know from previous posts.

In that game, I want to play a sound anytime my Player collides with a gameObject with a specific tag.

The MainCamera has an Audio Listener and I am using Cinemachine Free Look, that is following my avatar, inside the ThridPersonController (I am using the one that comes on Standard Assets - but I have hidden Ethan and added my own character/avatar).

For the collisions, I accessed the Third Person Character script, in order to destroy a gameObject (with a specific tag) when colliding with it, I have added the following:

void OnCollisionEnter(Collision other)
        {
            if (other.gameObject.CompareTag("Present"))
            {
                Destroy(other.gameObject);
                count = count - 1;
                SetCountText();

            }
        }

It is working properly as that specific object is disappearing on collision.

Now, for the Audio, I see two possible ways of making it work.

The first one, by simply adding an Audio Source to the ThirdPersonController (with the AudioClip that I wanted to call) and added GetComponent<AudioSource>().Play(); to the if statement as it follows:

void OnCollisionEnter(Collision other)
        {
            if (other.gameObject.CompareTag("Present"))
            {
                Destroy(other.gameObject);
                count = count - 1;
                SetCountText();
                GetComponent<AudioSource>().Play();
            }
        }

Does the work and it plays the sound when the player collides with the gameObject with the tag "Present".

Another way, and it is the one that I intend to make it work as it is more versatile (and can work nicely with a variety of AudioSources), is the following:

Start by adding a gameObject with the tag that I want to destroy has an Audio Source:

Then, created an empty gameObject to serve as the AudioManager and added a new component (C# script) to it:

using UnityEngine.Audio;
using System;
using UnityEngine;

public class AudioManager : MonoBehaviour
{

    public Sound[] sounds;

    // Start is called before the first frame update
    void Awake()
    {
        foreach (Sound s in sounds)
        {
            s.source = gameObject.AddComponent<AudioSource>();
            s.source.clip = s.clip;

            s.source.volume = s.volume;
            s.source.pitch = s.pitch;
        }
    }

    // Update is called once per frame
    public void Play (string name)
    {
        Sound s = Array.Find(sounds, sound => sound.name == name);
        s.source.Play();
    }
}

And created the script Sound.cs:

using UnityEngine.Audio;
using UnityEngine;

[System.Serializable]
public class Sound
{
    public string name;

    public AudioClip clip;

    [Range(0f, 1f)]
    public float volume;
    [Range(.1f, 3f)]
    public float pitch;

    [HideInInspector]
    public AudioSource source;
}

After that, in the Unity UI, I went to the Inspector in the gameObject AudioManager, and added a new element in the script that I named: CatchingPresent.

Now, in order to play the sound "CatchingPresent" anytime the Player collides with the object with the tag, in this case, Present, I have tried adding the following to the if in the OnCollisionEnter:

• FindObjectOfType<AudioManager>().Play("CatchingPresent");

But I get the error:

The type or namespace name 'AudioManager' could not be found (are you missing a using directive or an assembly reference?)

• AudioManager.instance.Play("CatchingPresent");

But I get the error:

The name 'AudioManager' does not exist in the current context

As all the compiler errors need to be fixed before entering the Playmode, I now need to fix one of these two problems.

I already checked and there isn't another AudioManager class.

I tried reimporting my scripts from the editor (right click in the project folder > Reimport All).

The problem persists, so any guidance on how to make the sound playing after a collision between the player and the gameObject with the tag Present is appreciated.

Best regards,

Gonçalo Peres

Around Storytelling and other fresh ideas for vrml/x3d, a new world came out:

Universe of books ("l'Univers des Livres", "Universo dos Livros")

As described by their authors, the Universe of Books is a unique place, inhabited by very special and eternal people: writers, mathematicians, philosophers and even kings!

This world brings fresh ideas and uses recent improvements in babelx3d/ABNet system. Everyone is invited to the official opening today at 20h UTC/GMT global time (Lisbon/london:21h; Paris; 22h; New York; 4h pm; tokyo: 3h am) and the authors will be available.

The 3D scene can be visited here:
http://www.odisseia.univ-ab.pt/ABNet2/frameset/booksuniverse.htm
See you all in the opening

vcard

Hey everyone! 

One really interesting thing about the Unity Editor is the way it integrates the items properties (Assets, Scripts,etc...) into the Editor interface automatically, improving readability and simplifying setting the values for those properties. After reading how the Inspector window works [1] and how to use Serialization on scripts [2] we decided that these were some very useful and powerful tools and that we should use them to improve the way our scripts interacted with the user in the Editor. One such use was the implementation of some components to simplify the definition of blueprints for the buildable items in the Elf Factory scene.

The factory activity allows the user to create toys, trying to reach the project main objective of collecting 100 presents to save Christmas. These items are created by combining 4 components out of the 16 available in the production line.

Figure 1. Aspect of Elf Factory activity.

Each item that can be created has a blueprint, or recipe, that lists the components it needs: for instance a little mouse warrior plush doll is built using wool, buttons, a zip and a wood plank. Each recipe was made with the intention of having some basic real world logic, but keeping them simple enough to be accessible to our project target audience: children between 5 and 13 years old.

To avoid having to define the blueprints by hand on code, and at the same time allowing us to explore and change them easily while developing the activity we used the auto serialization capabilities of the Unity Editor.

The main classes involved in this process are the ItemComponent class that allows us to mark a prefab as an item component and also set a sound to play when they collide with the machinery and with each other. A BuildableItem class that defines an item as buildable by our machine and which ItemComponents it needs. These classes interact with a MachineController class that provides the game loop for the scene.

The BuildableItem script was attached to a prefab that represent the finished product and defines the name of the item, the image that will be shown when the machine selects the next item to build and the list of components necessary to complete the build successfully.

The MachineController script manages the entire activity loop, defining the item to build, selecting randomly from the Buildable Items list, showing a preview, using the image defined in the item, lighting up the correspondent buttons to give the user a hint of the recipe, checking if the selected items are valid, by matching the instanced components with the components defined in the buidable item blueprint and activating the animations to make everything feel connected and proper to a production line.

The next table shows each class public property definitions and the rendered output in the inspector.

Class	Inspector detail
[...] public class ItemComponent : MonoBehaviour {     // Name of the sound event to trigger     public string soundOnHit; [...]
[…] public class BuildableItem : MonoBehaviour {     public string itemName;     public Texture itemTexture;     public List<GameObject> components; }
[…] public class MachineController : MonoBehaviour {     public List<BuildableItem> buildableItems;     public GameObject buildableItemImage;     public List<ItemButton> buttons;     public BuilderMachine builderMachine;     public Vector3 launchPosition = new Vector3(0.007f, 1.2f, -2.4f); […]

They are not very complex classes but, by defining public properties that the editor will then render as controls in the Inspector interface, provided a very practical user experience during the scene development. The use of these custom classes allowed us to setup the entire machine production using drag and drop actions, without having to make changes to any script code after the logic was finalized.

In the meantime, our project is almost ready to go live: we are now working on the reports and on the website.

As soon as the project goes live, we will update you in our project thread.

Best,

Gonçalo Peres (coordinator)

Eduardo Ribeiro

References

[1] Unity Manual (2020). The Inspector window. Available online: https://docs.unity3d.com/Manual/UsingTheInspector.html (accessed: 15^th January 2020).

[2] Unity Manual (2020). Script Serialization. Available online: https://docs.unity3d.com/Manual/script-Serialization.html (accessed: 15^th January 2020).

V&R Construction World    

This is a place where we can find some information about V&R Construction Worlds. Enjoy your visit !
Portuguese: Este é um local onde podemos encontrar alguma informação sobre Realidade Virtual e Construção. Divirtam-se!

>>> Vintage VRML/X3D World visited using our legacy BabelX3D multi user server. Special conditions of browser settings and plugins are needed to visit this world (please check info).