Integrating AvaLove into your AVsitter2 furniture takes only a few simple steps.
To let users connect their toys and get the HUD, add the following button lines to your AVpos notecard.
All buttons are optional. Include the ones you want to offer your users. Change the order and button captions (the text after the BUTTON keyword) as desired.
| Notecard Config | Function |
|---|---|
BUTTON Lovense|91001 |
Shows the "Lovense" menu to connect/disconnect toys. |
BUTTON Attach HUD|91002 |
Rezzes and attaches HUD to the user's screen. Note that rez rights are required for the user, and the user must accept the "attach" permission. |
BUTTON Get HUD|91003 |
Gives HUD to user. |
Adding the AvaLove License Key to the AVpos notecard is only required when you're using the
Creator Edition for AvaLove.
Important: you must be the creator of the furniture, as your AvaLove license key is verified
against the creator of the object the AvaLove script is in.
If you use the Personal Edition of AvaLove, omit this step.
AVALOVE ...).AvaLove lets you define two diffrent kinds of pattern types: static patterns that activate motors at specific intensities, and timed patterns that activate all motors following an intensity curve.
The easiest is to use the AvaLove HUD to define your patterns, and copy-paste the generated AL_PATTERN lines into your AVpos notecard:
Note that the supported functions (vibrate, rotate, fingering, etc.) depend on the Lovense device; devices typically don't support all functions. It is advisable to add vibration to each of the patterns in "Function" mode, as this is the only function supported by all devices.
Once you have defined patterns, you map them to poses as shown below. When the end-user switches to a particular pose, the mapped pattern is activated on the connected Lovense device.
AL_POSE {PoseName}|{FemalePattern}|{MalePattern}
Note that {PoseName} is the "display name" (the name that is shown in the AVsitter2 menu)
you associate with an animation inventory name, e.g., by means of an AVsitter2 configuration line
POSE {PoseName}|<{InventoryName}
in the AVpos notecard.
Example:
The notecard line
AL_POSE Kiss 1|Gentle Wake-Up|Spiral Storm
associates the female pattern named "Gentle Wake-Up" and the male pattern "Spiral Storm"
with the pose named "Kiss 1".
You don't need to map every single pose in your object.
Use the following line to define default patterns, which engage when there is no pattern
mapped explicitly to a pose:
AL_DEFAULT {FemalePattern}|{MalePattern}
Example:
The notecard line
AL_DEFAULT Gentle Wake-Up|Spiral Storm
associates the female pattern named "Gentle Wake-Up" and the male pattern "Spiral Storm"
with any pose for which no pattern was defined explicitly.
Here is an example configuration for your AVpos notecard:
# AVsitter2 AVpos Notecard with AvaLove Integration
# Main menu
POSE Kiss 1|Anim_Kiss_1
POSE Kiss 2|Anim_Kiss_2
POSE Kiss 3|Anim_Kiss_3
TOMENU Lovense
# Define the Lovense menu
MENU Lovense
BUTTON Lovense|91001
BUTTON Attach HUD|91002
BUTTON Get HUD|91003
# 1. License Line
AVALOVE {license_key_here}
# 2. Define Patterns
AL_PATTERN FEMALE|Gentle Wake-Up|Vibrate:5,Thrusting:10,Stroke:30;4;2;30
AL_PATTERN FEMALE|Tease & Please|Vibrate:10,Fingering:15,Suction:12;3;2;30
AL_PATTERN FEMALE|Deep Dive|Thrusting:18,Stroke:80,Depth:2;10;5;45
AL_PATTERN MALE|Spiral Storm|Vibrate:15,Rotate:10,Pump:2;6;3;45
AL_PATTERN MALE|Steady Hand|Vibrate:10,Stroke:50;0;5;30
# 3. Define Global Defaults
AL_DEFAULT Gentle Wake-Up|Spiral Storm
# 4. Define Pose Overrides (must match pose names exactly)
AL_POSE Kiss 1|Gentle Wake-Up|Spiral Storm
AL_POSE Kiss 3|Tease & Please|Steady Hand