Forgive me for the lack of dedication to the Revolution, Comrades. I'm afraid I've had some non-milking related work that needed doing. So, while I've gotten plenty done, I've not had time to do a devlog.

Today is a general gripe session, no behind the scenes CCP secrets today, just wanted to share some of the fun that comes from developing for the Meta Quest.

If you've been keeping up with things at all, you know that the Adult Toy I'm developing for is an internet enabled stroker that connects to a remote server for it's instructions. It uses a Connection Key to interact with this server, which means that for at least one part of my app's configuration a keyboard of some sort is required for the user to enter their Connection Key. Because the Meta uses Android, there's a built in keyboard option available that Unity uses. It takes a bit of finagling, But it works.

UNTIL META BROKE IT A COUPLE MONTHS AGO!

Luckily I found a workaround. Kinda.

https://communityforums.atmeta.com/t5/Unity-VR-Development/System-keyboard-not-opening-every-time-in-Meta-quest-3-device/td-p/1179306

Which introduced a new problem. This workaround messes up the input box so it doesn't make the inputted text readily available. Now I have to a manually get the text from the child of the input game object. Fine, I'm doing it!

Today, as I'm working my way through this and having half rewritten my API interface because for some reason, despite getting the Connection Key, it's still not working.

THEN MY APP SUDDENLY STOPS HAVING INTERNET ACCESS WHEN RUN ON THE QUEST!

Hours of troubleshooting later...

OH LOOK, ANOTHER KNOWN PROBLEM!

https://communityforums.atmeta.com/t5/Unity-VR-Development/UnityWebRequest-Not-Working-on-Quest-3-quot-cannot-resolve/td-p/1093537

Apparently when I updated the XR plugin a while ago, the most up to date version available from Unity still has the bug. And months later it just decided to fuck my shit up, fam.

So eventually, I do all the steps, upgrade the XR plugin to non-public version, I reboot a couple times, I manually update my manifest, I get internet back. What a day... My API still isn't working properly when I manually enter the Connection Key. wtf... Then I look at what my settings script is saving and there's some sort of new line or a line break in my JSON. Weird, but fine whatever, hazards of the keyboard workaround. I trim off new lines and returns and whatnot, IT'S STILL THERE!

Eventually, I figure out that for some reason the android keyboard or TMPro is adding Unicode character 8203 to the end of my Connection Key, which is a Zero Width Space character. I don't know what that is, but it's clearly reactionary. So now I'm Trimming that along with \r \n and that does the trick. Suddenly my Connection Key input flow is working. I can now test all the other stuff I've been working on that came to a screeching halt last month.

Bleah. I'll get a "real" OohAah devlog up one of these days. I've done some pretty cool stuff and despite being way past when I want to release the alpha for testing, things are coming along. I've also been buying cheap adult toys off AliExpress for a future project and have been messing around with that when I should really be working on the milker. Turns out using them are not going to be as easy I hoped. Long story short, for some reason the company making them set their bluetooth up in reverse, so they're not pairable and can only be controlled by making your device broadcast an advertising packet or something. Which is not easy in Unity. Bleah, I'll figure it out tho.

Thanks for reading, just had to vent. Hope y'all are doing well.

Hello, fellow Tankies! Welcome back to my continuing adventure of building a lewd VR communist brainwashing experience for Jordan Peterson and his incel masses as per Xi's personal instructions.

Last weekend I finished up the answer selection solution by using the thumbstick to select the diagonal direction and activating a radial slider that corresponds to the answer of that direction. It gives the user a few seconds before locking in the answer. Major props to @aaro@hexbear.net for putting the radial menu of other games in my head and putting me down that path.

I actually had to take apart my Quest 2 Controller to clean the thumbstick as it was sticking so bad that it just got stuck in Down/Right for a while. Cleaning worked but I've lost the touch sensitivity of where your thumb is supposed to rest. I can't think of a time I've actually used that function, that wasn't just novelty, so it can wait for a while before I take it apart again.

Yesterday, I hammered out version 1 of Question serving and Answer handling. As the video shows it now tells you if your answer is right or wrong and then serves up a new question. I've only got handful of questions so far which is why sometimes it looks like the question hasn't changed in the video. I've also made it so the answer is randomly assigned to one of the four answer spots with the wrong answers filled in to the empty spaces afterwards. None of this is set in stone, especially not the graphics or timing or anything, but I just want to get everything working enough for prototyping a full alpha version.

In version 1 of the Quiz minigame I'm not doing any weighting or behind the scenes algorithms, things are purely going to be served according to Random.Range, but in future versions I am planning on building an algorithm that incorporates techniques similar to Duolingo and other learning apps to better encode the brainwashing.

Today I'm gonna clean things up a bit and get the audio manager working so next week I can figure out how best to implement the HIIT style rounds of alternating quiz/lewd stimulation. I may make a NSFW post over in askchapo to see if folks have better ideas than what I'm currently playing around with. I figured this post was clean enough that it didn't need NSFW tagging, but if it does, just let me know, mods.

Previous NSFW post on the app for anyone curious:

So I'm doing a VR experience and today I'm working on using the thumbsticks of the quest controller more like a gamepad to control selection of a UI menu for a trivia game that's going to be in the experience.

Now Unity returns the thumbstick via a Vector2, easy enough. I literally sketch out an XY graph, figure there's a threshold I need to account for for each direction, a much smaller threshold that we can ignore for each plus and minus on the other vector, and if the Vector2 meets all my criteria I can fire off my functions for the direction. So for UP my code looks something like

if(Vector.Y > pressthreshold and (Vector.X < threshold and Vector.X < -threshold){ Print(up!)}

And then I did that for each direction... And it kinda worked. But it was wonky as hell because my quest is old and the thumbsticks drift. So I spent like an hour and a half trying to find just the right thresholds and it just did not want to be consistent...

So I figured I'd ask chatgpt. And it basically spits out: Just take the absolute value of your X and Y and whichever one is bigger is your plane, and then the positive or negative of the value determines your direction.

ARE YOU FUCKING KIDDING ME?

I am in shambles. I have once again overcomplicated the simplest freaking thing.

TLDR: My brain is pudding. Just had to vent.