OWO 2.1.1

There is a newer version of this package available.
See the version list below for details.
dotnet add package OWO --version 2.1.1
NuGet\Install-Package OWO -Version 2.1.1
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="OWO" Version="2.1.1" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add OWO --version 2.1.1
#r "nuget: OWO, 2.1.1"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install OWO as a Cake Addin
#addin nuget:?package=OWO&version=2.1.1

// Install OWO as a Cake Tool
#tool nuget:?package=OWO&version=2.1.1

OWO SDK Documentation

OWO is a new haptic technology that allows developers to add the sense of touch to their games. Using OWO, users can feel in real-time when playing videogames. They can feel sensations like the wind, a shot, a hug and many more. Adding OWO’s SDK to a game is very simple:

  1. Establish the communication: Game - OWO App.
  2. Choose a sensation or create it.
  3. Send it to one or more muscles.
  4. #Feelthegame.

Connection

There are two ways to establish a connection with OWO:

1. Manual connection: The user must enter the IP that the OWO App provides during the games scan. To establish this connection you have to use the Connect method of the OWO class.

//The ip is provided to the user by the owo app.
OWO.Connect(ip);

2. Automatic IP: Through the AutoConnect method, the OWO class will begin to search for the OWO App through the local network and it will establish a connection. This may not work if there is an App like OpenVPN opened or if the network does not allow this type of connection (broadcast).

OWO.AutoConnect();

Add sensations to your project

OWO has created over 30 different sensations for you to use in your game. There are many different types of sensations that we have divided in: impacts, interactions, experiences and alerts. You can:

  1. Use OWO’s previously created sensations.
  2. Develop your own sensations to create your own experience.

We invite you to use your imagination, don’t just stick to the name we give each sensation, be creative and maybe you’ll find new ways to apply the existing sensations!

How to send sensations

Once the connection is established, you can send sensations using the Send method.

OWO.Send(Sensation);

How does a sensation work?

A sensation is composed of one or more microsensations. A microsensation is the base, the smallest unit users can calibrate. To create micro, you have to modify 6 different parameters:

  1. Frequency: The frequency is the number of pulses per second the microsensation sends to the player.

    • A micro with frequency equal to 1hz will send one pulse per second, which would feel like independent impacts (e.g. dart).
    • A micro with a high frequency, 100hz for example, will result in a “continuous” sensation (e.g. wind, bleeding, etc.).
  2. Duration: The amount of time (in seconds) that the microsensation will last. For example, if you create a sensation with Frequency: 1Hz; Duration: 1 sec, you will feel a dart after 1 second. On the other hand, if you create a sensation with Frequency: 10Hz; Duration: 0.1 sec, you will immediately feel a dart.

You cannot establish the frequency of 1Hz in less than 1 sec.

  1. Intensity percentage: Each user calibrates their maximum intensity level (100%) during their calibration process in the OWO App. You can assign the intensity percentage that users will feel. E.g: 50% of the users calibration, 75%, etc.

  2. Fade in: How long it takes for the microsensation to progressively go from 0 to the assigned intensity percentage (in seconds), the maximum is 2 seconds.

  3. Fade out: How long it takes for the microsensation to progressively go from the assigned intensity percentage to 0 (in seconds), the maximum is 2 seconds.

  4. Exit time: The additional time in seconds between one microsensation and the next one to play.

How to create your own sensations

You can create sensations in several ways:

  1. Create a sensation and save it in a variable:
var ball = SensationsFactory.Create(100,0.1f,100,0,0,0);
  1. Create a sensation, then assign muscles:
var ballWithMuscles = ball.WithMuscles(Muscle.Pectoral_R);
  1. Create a sensation, then assign muscles with overrided intensity:
var softBall = ball.WithMuscles(Muscle.Pectoral_R.WithIntensity(50));
  1. Create a sensations sequence:
var sequence = daggerEntry.Append(bleeding);
  1. Parse a sensation from a raw string:
var ball = (Sensation)"100,1,100,0,0,0,Ball";

Develop new sensations

You can use the sensations designed by the OWO team or create your own sensations by modifying five parameters.

Sensations Creator

Newest version: Sensations Creator.

The sensations creator is a tool with which you can experiment and create your own sensations.

OWO Visualizer

Newest version: OWO Visualizer.

With the OWO visualizer you can see, in real time, what the user will be feeling while playing your game without using the OWO Skin.

If you have any questions, contact us! We'll be happy to answer them. You can send us an email to devs@owogame.com or join our Discord server. We look forward to chatting with you!

Product Compatible and additional computed target framework versions.
.NET Framework net45 is compatible.  net451 was computed.  net452 was computed.  net46 was computed.  net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
2.4.2 86 4/22/2024
2.4.1 76 4/22/2024
2.4.0 88 4/5/2024
2.3.14 113 2/12/2024
2.3.13 114 1/12/2024
2.3.12 140 12/12/2023
2.3.11 136 11/29/2023
2.3.10 173 9/15/2023
2.3.8 120 9/15/2023
2.3.6 105 9/14/2023
2.3.5 122 9/13/2023
2.3.4 95 9/13/2023
2.3.3 124 9/5/2023
2.3.2 180 7/17/2023
2.3.1 138 6/20/2023
2.3.0 130 6/12/2023
2.2.1 127 6/5/2023
2.2.0 127 5/30/2023
2.1.2 167 4/26/2023
2.1.1 152 4/21/2023
2.0.3 205 3/23/2023
2.0.2 190 3/22/2023

Async connection addition