... | @@ -33,9 +33,9 @@ The player position is a bit of a special case, as the movement of the HMD only |
... | @@ -33,9 +33,9 @@ The player position is a bit of a special case, as the movement of the HMD only |
|
To do that, we first have to open the level/map, in which we want to log the position: ``File -> Open Level``.
|
|
To do that, we first have to open the level/map, in which we want to log the position: ``File -> Open Level``.
|
|
If the ``VirtualRealityPawn`` actor does not a have a Blueprint associated with it, we have to create one like this:
|
|
If the ``VirtualRealityPawn`` actor does not a have a Blueprint associated with it, we have to create one like this:
|
|
#### Creating a new Blueprint for an Actor
|
|
#### Creating a new Blueprint for an Actor
|
|
1. Select the Actor and click on ``Blueprint/Add Script`` in the ``Details`` tab
|
|
1. Select the Actor and click on ``Blueprint/Add Script`` in the ``Details`` tab<br>
|
|

|
|

|
|
2. We are be prompted with the window seen below. Name and path to where it is saved are not relevant. Example settings are filled in below (I created the folder ``Loggables`` for the actors I want to log). On a technical level, your actor will be replaced with a copy of your actor (an instance of a new subclass to be precise), that behaves in exactly the same way, with the same settings, but it now additionally has all the features defined in the new Blueprint.
|
|
2. We are be prompted with the window seen below. Name and path to where it is saved are not relevant. Example settings are filled in below (I created the folder ``Loggables`` for the actors I want to log). On a technical level, your actor will be replaced with a copy of your actor (an instance of a new subclass to be precise), that behaves in exactly the same way, with the same settings, but it now additionally has all the features defined in the new Blueprint.<br>
|
|

|
|

|
|
|
|
|
|
Now we can edit the Blueprint.
|
|
Now we can edit the Blueprint.
|
... | | ... | |