#subvi

[lostysstuff]

Viviviviviviviviviiviiviviviviiviviv i just love her (individual drawings under)

[luvvlayna]

Swim

minors dni

sub! vi x dom! fem reader

NSFW tags - sub!Vi, dom! fem reader, pussy-eating (vi!receiving), very light fingering (vi!receiving), choking, dirty talk, pet names (baby, sweetheart , whore, etc) 18+ literally no plot just banging :)

whimpers and moans echoed through the decorated apartment. the only thing that slid inside of the seemingly empty house was sunlight from the early morning.

“f-fuck please please..” vi groan out as you kitten lick her wet folds, wetness spreading all over your tounge

giving in to her pleas, you plunge your tounge deep inside her enjoying the taste of her sweetness and feeling her thick, scarred thighs wrapped tightly around your head

you caress her thighs softly as you bring your other hand to her clit, rubbing her softly as you continue you relentlessly thrust your tongue in her, making her wetness drip down your chin slowly

“baby..p-please i’m gonna cum..please let me cum..~” vi yelps out as she grips the sheet tightly, trying to grind her pussy rougher on your lips

you pull away slightly and smack her pussy. violet yelps loudly as you hit her making her sweet juices fly everywhere

”you cum when I tell you you sweetheart..you don’t want to make me mad this early hmm..?”

vi shakes her head no and you lean back down towards her cute pink clit, and lick it softly. while she focuses on the that pleasure, you plunge two fingers into her sopping, wet cunt and begin to thrust into her, groaning as you feel her walls clench against them

you pull away from licking her and stare up at her with hooded eyes as you continue to thrust into her with your fingers, watching as her face contorts with pleasure

“you’re such a slut for me huh baby..? you had to wake me up just to whine how much you needed me just like a cheap whore at the Brothel..”

vi sobs loudly as she keens at the degradation. feeling her orgasm approach, vi grinds down on your fingers matching her pace with the thrust of your fingers

“b-baby..please I’m gonna cum..I need to cum, let me cum p-please..~” vi groans out as she becomes lost in the sensation of your fingers thrusting in and out of her at a punishing pace

You coo slightly as you nod towards her, signaling for her to let all her troubles go and cum on your fingers..After a few more thrust, vi moans loudly as she finishes all on your fingers, coating them with her glistening juices

you continue to thrust softly, making sure to rid her of all her pleasure until vi whine softly from overstimulation.

you pull out softly as you lick you fingers in front of her staring into her eyes. you pat her thigh softly as you get up for a a towel from the bathroom

you walk back into the bedroom, seeing vi back to sleep..you chuckle softly as you wipe her down then throw the towel into the hamper

you pull back the blanket and pull vi underneath with you, wrapping you arms tightly around her waist, enjoying her warmth as you fall back asleep to have energy for the rest of the day..

fist oneshot how’d i do my loves! ;)

[luvvlayna]

Close to You

minors dni

switch! brothel worker! vi x switch! silco worker! fem reader

NSFW tags - switch!Vi, switch! fem reader, strap on use!, fingering (vi!receiving), eating out(r!receiving), choking, dirty talk, brothel worker vi! , foreplay, overstimulation, pet names kinda rough..? Nah it’s rough literally wanna bite her

working for Silco was hard work. every single day was life or death, which added upon the stress that built up inside you

after working nonstop for weeks, Silco takes notice in your clenched jaw and annoyed eyes and sends you off for the day early to take a break

before you can walk fully out the door, Sevika stops you and places a hand on your shoulder, “I recommend the brothel sweetheart..” she chuckles humorously with a smirk

you scoff and throw her hand off your shoulder and walk out the room, rushing past Silco’s goons in the hallway

actually taking Sevika’s advice, you head to the Brothel, hoping to release the stress on a pretty girl. you walk in and check in with Madam Babette.

she takes a look at you and knows exactly who to bring you to, her most popular girl, especially for women, Vi. She leads you to the back of the Brothel and to a room with a pink haired girl wearing a cat mask..

“your ready for another customer vi?” Madam Babette says as Vi nods softly..Madam pushes you into the room, closing the gold and magenta curtain behind you

“so..how do you wanna do this cupcake.?” she says seductively as she stands up, taking off her mask, and undoing the tie of her robe

you stare at her in awe as she reveals a lace bracelet and matching underwear. you move closer to her while admiring the scars along her thighs, the muscles that bulk out from her arms

vi decides to take the lead and wrap her arms around your neck, pulling you in for bruising kiss. You eagerly wrap your arms around her waist and bring her closer

while kissing you, vi takes off your biker jacket and soon rips you tank top off of your body, revealing your full breast. Vi pulls away from the kiss, leaving a string of saliva in her wake

“your tits might be the best thing I’ve ever seen, cupcake..” vi whispers as she grabs one in each hand, rubbing your nipples tenderly

you groan softly as she plays with them, feeling your body shudder in pleasure as your core heats up..

she smiles softly as she turns you around and pushes you onto the bed roughly, she leans over you and kisses down your stomach as your body twitches

“so responsive for me..” vi whispers as she reaches you pants. she unbuckles your belt and pulls down you pants down in one full motion, revealing your soaking wet panties.

vi kisses your inner thighs as she rubs your clit through you underwear, feeling the wetness soak through..you whimper out to her and grab her hand, bringing it the rim of your panties

“please vi..touch me please” you whine out desperately.vi smiles towards you and nods. she pulls down your underwear in one go, revealing your soaking cunt

“your so wet princess..you gonna’ be a good girl for me and let me make you cum.?” vi says as she slowly rubs your clit in small circular motions

“f-fuck yes..” you whimper out as she rubs your soaking pussy. You cry out as she leans down and licks you, feeling her hot tongue on you so suddenly made you close your legs

vi moves her hand from your clit and uses her both her hands to open your legs wider, diving deeper into your wet heat..”don’t close your legs on me princess..let me make you feel good hm?”

while hold your leg apart, vi eats you like it’s her last meal. she sucks on your clit and plunges her tongue inside your hold, making you squirm from the pleasure

feeling your stomach clench, you grind your pussy on Vi’s mouth wanting more of her tongue on you. “please vi ‘m gonna cum..I’m- f-fuck”

you cry out loudly as you release on violet’s face. your legs shake violently as you orgasm crashes into you..you grind on her face more, wanting to milk the aftermath of your orgasm , vi complies, moaning against your sore clit

after a few seconds, you whine with overstimulation as you pull vi’s hair, to move her head away from your swollen clit..she give you a few more licks before sitting up and smiling towards you

you sit up and pull her towards you, taking her lips to yours. she wraps her arms around your waist and pull you closer..

part 2?

[vihigh-blog]

VI High 16 - LabVIEW 2011 New Feature - How to Create a SubVI

We took a bit of a VI High summer vacation (stretching well into fall...) but we're back with several new, shorter videos on new features in LabVIEW 2011. Our first one has to do with the improvements in creating subVIs. For more on learning LabVIEW, check out the Sixclear Lucid LabVIEW Fundamentals Training (formerly Sixclear LabVIEW Fundamentals) course newly updated to LabVIEW 2011: sixclear.com.

Experience Level: Basic

(start transcription) "In LabVIEW 2011, there are some improvements when you create subVI's. So if I were to click and highlight this section of code, go to Edit, and then Create SubVI, my SubVI has been made. I double-click, open up the front panel, and we see that we have a connector pane right here, with our connections already made. So if I click on the terminal, I see the corresponding object highlighted. I can always change this pattern, so the default pattern in LabVIEW 2011 is 4x2x2x4. I can always right-click, go to Patterns, and see other available ones. Though, this is the recommended. If I go to my block diagram, of course, I see the code, or the subVI. Right now, we just have Untitled 1 (SubVI), so I’ll go to Save, and I’ll call it, 'Area of a Triangle subVI 2.'" (end transcription)

[vihigh-blog]

VI High 5 - Reassign Connector Pane Terminals in LabVIEW 2010

In this short episode, we learn about a handy new features in LabVIEW 2010: switching connector pane terminals with a few quick clicks. This video is a brief, direct excerpt from the Sixclear Lucid LabVIEW Fundamentals Training (formerly Sixclear LabVIEW Fundamentals) course offered by Sixclear. To find out more visit sixclear.com. It also makes no attempt at humor, so watch for information and soothing narration only.

Experience Level: Basic

(start transcription) "A useful new feature in LabVIEW 2010 is the ability to switch connector pane terminals. Now, to make it more clear, I’m going to put another control here, a Boolean in this case, put that right there, and I’ll assign the Boolean right here to the upper left. Now let’s say that at some future point I want to switch these terminals. Previously, I would have to right-click on either of them, disconnect and then reconnect them. But now with LabVIEW 2010, I’m going to hover over one of the terminals, hold down control, click and then click on the other terminal I want to switch it with, click, and there we are, a very quick and handy way of reassigning terminals." (end transcription)

[vihigh-blog]

VI High 4 - Using Property Nodes in a SubVI to Enable and Disable Controls in a LabVIEW State Machine

In this episode, we finish up our discussion of using the Disable subVI by examining how it should be placed in a state machine. We explore how our basic state machine works and where the Disable VI would first disable and then re-enable controls. We then explain alternate programming methods, such as using event structures and type defs, depending on how complex and maintainable our application should be. Though I say "part B" at the beginning, it's really just a continuation of VI High #3.

Experience Level: Intermediate

For more on LabVIEW training, visit sixclear.com.

(start transcription) "This is part B and it’s more at the intermediate level. Are you ready? We’ll examine using the disable VI in a state machine and some considerations for state machine usage. Let’s take a look at a state transition diagram. I start and go to the Begin state, which could also be called my Idle state. From here, I can go one of three places. To the Basic Test, by clicking the Launch button, to the Advanced Test, but clicking on the Advanced button, or I can end, by clicking on the Stop button, that’s implied. If I go to the Basic Test you see that I always go to Advanced Test and then back to Begin. And if I go straight to Advanced Test, I’ll just go back to begin. If nothing is pressed, I remain in the Begin state. Let’s run my state machine first. I’ll click on the run button, when I launch I go to Basic Test, then Advanced Test and back to Begin. If I click on Advanced, I go right to Advanced and back to begin. And stopping, means I stop. And here’s my block diagram, showing the infrastructure of a state machine. A while loop, with a case structure inside, a shift register, with the output of the shift register going to the case selector terminal of the case structure. Typically, we also see this enum constant. I’ve already created the array of controls that we’re going to selectively enable and disable. Let’s review the logic of this state machine. Here’s my Begin state, and in my begin state I’m constantly polling my Launch button every 50ms to see if it’s been pressed. If it has been pressed, we go to the Basic Test, if it’s not we check to see that the Advanced button has been pressed. If it has, we go to Advanced Test. If not, we stay in the Begin state. If we go to the Basic Test state, we perform the Basic Test and move on to the Advanced Test. The Advanced Test is remarkably similar. We perform the Advanced Test and move back to the Begin state. Now let’s suppose I have the same requirement as I had previously that these controls on my front panel be disabled when the test begins and re-enabled when the test finishes. Where shall I put that disable VI in my state machine? It makes sense that I would place it either after the Launch button had been pressed, and after the Advanced button had been pressed. And again, after the Advanced Test has finished executing. There are a few ways of executing this, we’ll execute first the simpler method, and then later explore a more modularized, maintainable solution.

We’ll take our disable VI and place it in here. Take my array of controls, and pass it right in, move this over and we’ll essentially do the same thing, Ctrl+C, if this Advanced button had been pressed. Rather than this Select function, it makes more sense to have another case structure. We’ll need a bit more space. So I’ll hold down Ctrl, click and drag, to create some space. Ctrl+V to put my disable VI in the correct place. Another Ctrl+click drag. Move to my other case, and remain in the Begin state. When it’s time to reenable the controls. I’ll go here to my Advanced Test, and just put the disable VI in here and enable instead of disable. We’ve kept this state machine simple, so we have not employed any error handling. So we’re not using the error cluster, typically a bad idea, except for instructive videos, where we make a concerted effort to remain simple. However, to enforce execution order I will connect the error cluster from here to here so that the disable VI executes after the test. And now we’ll go to my front panel and run my VI. When I haven’t launched anything, I can manipulate my controls. But when I do launch, I can’t, until the test is finished and they’ve been re-enabled. Perfect.  As I mentioned, we went with a simpler path, for implementing these disable VIs. I added these Disable VIs within the Advanced Test and the Begin states, assuming that I would never have another state in between clicking on one of these test buttons and then disabling the controls. Also that I would always re-enable after the Advanced Test. However, I may have needs in the future to modify my application and then those assumptions may no longer by true. Therefore, in a better modularized application, it would be wise to have enable and disable in their own states, that way I can change the order of states around without editing other states. That’s just smarter, but I would have needed to add those enable and disable items to this enum, and that enum definitely should have been type defined, otherwise called a type def. I would add separate enable and disable states in the state machine. Again, I didn’t do that, just to be simple. Additionally, this very simple state machine is relying entirely on user interface actions to drive the direction of the state machine, so it would have been better to place an event structure in the Begin state. But again, you probably guessed the reason I didn’t do that, the answer is simple." (end transcription)