#quicktest
Explore tagged Tumblr posts
Text
TMS8828 multi-zone time-of-flight sensor from ams OSRAM 🔍🤖🌐
We stock many ST VL5 series ToF sensors (https://www.adafruit.com/search?q=VL5), but it's always a good idea to peek at what else is available on the market. Here's a multi-zone Time of Flight sensor from ams OSRAM - the TMF8828 (https://www.digikey.com/en/products/detail/ams-osram-usa-inc/TMF8828-1AM/16285671) with 8x8 zones and up to 5 meters detection. Here's a quick QT breakout for this sensor and the support circuitry so we can try it out. Coming soon.
#adafruit#timeofflight#amsOSRAM#tmf8828#multizone#tofsensor#sensorstock#detectiontech#qtbreakout#quicktest#electronics#sensortechnology#distancemeasurement
5 notes
·
View notes
Text
🔒 How Secure Is Your Property? Take This 5-Second Test! ✅
Is your property truly secure? 🏠💼 Take this quick 5-second test to find out!
1️⃣ Have you had any break-ins or thefts nearby? 2️⃣ Do you have clear surveillance coverage of all entry points? 3️⃣ Can you monitor your property remotely? 4️⃣ Are your cameras high-definition & night-vision enabled? 5️⃣ Do you feel confident in your current security system?
If you answered NO to any of these, it’s time to upgrade your security! 📞 Call 310-901-4972 for professional CCTV installation in Los Angeles & Orange County today!
#PropertySecurity#QuickTest#CCTVInstallation#HomeSafety#BusinessSecurity#LosAngeles#OrangeCounty#DigitalSurveillance#StayProtected
0 notes
Note
Found a bug!
maisontarset line 145 non existent variable boy
woke up from a dead sleep and saw this, divine intervention for real. quicktest has failed me, it said everything was gucci, dammit.
i'll have that fixed later today, along with some typos. thanks for the report!
25 notes
·
View notes
Text
Curse my coworker who refused to mask even tho she had a nasty cough
#I masked but alas#I caught whatever she had#Quicktest said negative thankfully#But my sinuses are fucking killing me#Blease mask and stay at home if you're sick#Shout out to my boss who sent me back home and told me to take of myself#Thank u
2 notes
·
View notes
Text
The Next Update Date
Hey everyone! I said the next post I made on here was going to be about the update, and here I am! I only have *checks notes* 3-4 more scenes left to write in chapter 2! 🥳
Given my progress, I feel confident announcing that I'll be posting chapter 2 on July 31st at 9pm EST. I'll be running the demo through quicktest, my fingers are crossed Dashington doesn't decide to hate my subroutines again.
100 notes
·
View notes
Text
Орлёнок Demo Release
Finally, the demo is here! It's not exactly January anymore, but better late than never, right?
You can play it right here!
I also made a post on the CoG forums, if you want to check it out: Link
Features include:
Meeting your family! And getting bullied.
Getting executed!
Rising from the dead!
Celebrating life by slaughtering some rebels!
(Being extremely miserable!)
Feedback:
This is, quite obviously, a work in progress. It is made available so that you, the reader, can give feedback that improves the game.
So, while you can - and should - obviously tell me whatever you want, a specific list of what I need most in terms of feedback can be found here:
Language. English is not my first language (actually, not even my second one), and I mostly read non-fiction academic works when I read in English, so my writing is certainly not at the level it should be. If you have any concrete issues, please tell me, and I'll try to learn how it can be improved.
Spelling. I don't expect much in the way of outright errors, but I do know that I mix up British and American English all the time. The intended style is American English, so please point out spellings that are wrong in that regard.
Inconsistencies. There are a lot of variations between scenes, and I'd like to make the story as immersive as possible; so, if a phrasing, a character's behaviour etc. feel like they don't fit into the choices you previously made, please tell me. In detail, if possible, otherwise I won't be able to amend it.
Sensory descriptions. AuDHD makes my brain process sensations, including visual impressions, very differently, which means I often end up forgetting those exist. Please tell me about scenes that lack description in that regard. (My first grade elementary school report card called my writing 'efficient and devoid of feelings', and I'd very much like to move past that.)
Technical problems. The code should be pretty solid, but with how complicated it is, it'd be weird if there weren't at least some problems. If you find them, please try to include as much detail as possible when telling me about it. (CS Quicktest and Randomtest are not usable due to the complexity of the code, lol.)
You liking the story. I remain thoroughly convinced that I am a worthless person who isn't able to, nor deserves to create anything, and currently my only motivation to continue this project is derived from pure stubbornness. So, if you, for some reason, actually like this demo, please tell me. It won't change my mind about how bad I think it is, but it will force me to continue in order to avoid being even more of a disappointment.
Additions. If I like your idea, I'll probably add it right away; if I'm unsure, I'll do a poll. You can get me to do almost anything if you say you're sad if I don't do it.
Formatting. Although I try to playtest as much as possible, it's not that easy with how many variations there are, and in VS Code it's sometimes hard to see how well or badly readable text passages actually are.
CWs/TWs (v0.0.1):
Graphic violence and gore
Attempted sexual assault (against the player, avoidable, f!MC only; also against an NPC if massacre route is chosen (is dealt with quickly))
Suicide attempt (by the player, avoidable; f!MC only)
Loss of loved ones
Massacre of civilians and/or PoWs (avoidable)
General misery
(please let me know if you think this needs additions)
As of yet unfinished content:
Autistic variations do not exist yet for the latter part of the demo
Only one of three locations for taking a walk available for now
Tooltips are incomplete
Asexual is not available yet, as it requires a lot of additional scene variation text
Special (psychopath) routes are missing from some scenes as they were added late in development
Choices that are locked and marked as (WIP) are unfinished
Interaction routes for Semyon/Selena, Mikhail/Marina and Leon/Leah. They are top priority for the first set of updates
It is recommended that you play this with a stable state of mind. If you choose the suffering paths because it's relatable and/or as a coping strategy, please make sure you have support available and avoid triggering yourself too much.
The whole point of this game (apart from the dress-up part) is that, no matter how bad things get, you shouldn't stop fighting. It's your enemies who deserve destruction, not you.
Please keep in mind that I am both literally insane and pretty reasonable, so: if there is anything you find grossly offensive, don't assume I meant anything bad by it. Just explain to me why you think it shouldn't exist, and if I am convinced, I will amend it.
96 notes
·
View notes
Note
Hello I just informing that I've tried the second demo and it's come with error " chapter1 line 4231 non existent variable 'allchildrenborn' " And when opening reputation tab something about Dread is missing.
Thank you very much for bringing this to my attention. I just spent the last hour traumatized by looking over the Alpha version, shaking my head at my past self lmfao
It's all fixed now! I ran it through quicktest, randomtest x100, and looked over the reputation tab and didnt get anymore errors. I even found other ones that you guys wouldve ran into and fixed those too lololol, fucking made me stressed xD
46 notes
·
View notes
Text
there's nothing better than when you're playtesting and it says QUICKTEST PASSED and you have no errors
213 notes
·
View notes
Note
ran into this bug: chapter_three line 449: invalid @{} at letter 1; missing closing parenthesis ) when trying to select that buildings don't move
Ahhh tysm, Nonnie! Great reminder that I should actually run quicktest before uploading bugfixes in case I break something in the process of fixing something else 😭
This should be fixed!
13 notes
·
View notes
Text
Coding is donnnnne omg finally!
I fixed some mistakes I found in the additions, filled in some blanks, added the variables and their adjustments- now I just have to pray and test. Tbh, I always expect something to be wrong. The rare times I don't catch anything or quicktest tells me it's fine, I'm so sus.
Ahhh this means I can update today, thank god. My hand is cramping today, what's the deal with that-
18 notes
·
View notes
Note
Hi! So I'm also an author and I've had the same error. This error is not supposed to pop up when you have implicit_control_flow set to true (which you do, I checked your code).
I've posted about it on the forum. The author of Fallen Hero then posted with the same problem. I'm not sure it's exactly the same issue, as for me it popped up when running quicktest/randomtest. But the fact that it happens *sometimes* makes me think it might be. From a developer POV errors that aren't systematically reproducible (happen only some times and not others) are the WORST.
Anyway, it might be a good idea to let the CSIDE developpers know? Something strange is going on and I don't think it's something we as authors are doing wrong.
Technical stuff here for game devs :D You can ignore this post if you aren't an IF writer.
In my case, I figured out what was causing it, but yes you are right that this is no error on our part, it's just a weird bug in the ChoiceScript code. I couldn't find it at first because the error isn't even on the line that the error mentions, but the line before that, which is definitely a hassle to comb through and it should be fixed in the ChoiceScript base code itself.
But yes, so, the problem was that on the line before that, I was using *if commands and no *else at the end. Which shouldn't be a problem. But sometimes ChoiceScript freaks out because it thinks that if I use only *if's and not *else, then I didn't think of every possibility in the *if statements and if I continue with that, it will put the game into an infinite loop and it will break the game 😱
...It won't. But sometimes ChoiceScript gets confused with *if prompts. So I fixed it by simply replacing the last *if with an *else in the line before the error, and now everything is good. It should've been good before too, but yeah man, it's frustrating...
Edit: the problem wasn't even the indent. It was the *if's. So the error message lied on 2 accounts 😂
This is not a CSIDE error though. When I ran it through the normal ChoiceScript randomtests, outside of CSIDE, it sometimes still produced the error, but only on the randomtests. So it's a bug in the ChoiceScript base code itself, and I don't know if we can do anything about that, except trying to find workarounds to a problem that shouldn't even exist in the first place...
Frustrating.... Very frustrating.... 👺🔪
10 notes
·
View notes
Text
5 March 2024 Update Log
Major Changes
Added Kean's Part 2 (6763)
Added Grim's Part 2 (4622)
Fixed a code error where hangouts (aka the RO sections) were inaccessible outside of the Select Chapter menu
Minor Changes
If you're using the Select Chapter menu, you will be reminded to finish Chapter 0.0 to set your character up (input a name/surname, choose pronouns, and select a creature type)
If you haven't finished the Prologue but used the Select Chapter menu to read an RO's part, you can now select which chapter to go to afterwards. This is not another Select Chapter menu as it only includes the main story as options
A lot of bug fixes and reworked code
The opening sequence to Chapter 0.2 is no longer skipped
Notes
I had this hopeless moment while writing Kean's Part 2 because it was taking a while to write. Usually I get these done in one or two days, Kean took four. Then I noticed that that's pretty good and anxiety was just talking. Gotta get better about that lol
In Grim's chapter, you can have a panic attack! So that's fun 👍
Coding has been a nightmare and I somehow figured out how to view previous code mistakes that weren't picked up by Quicktest, so I got to fix a lot of previous chapters
I'm considering going back to the Prologue and changing the prose, just so character voices remain consistent now that I have a better grasp on all of them. I will probably do that later on when I'm further in though.
Previous Word Count: 107.5k
Current Word Count: 122k
→ or 110k without command lines
→ or 33k per playthrough
Difference: +14.5k words
All feedback is appreciated!
#if wip#the truthkeeper if#interactive fiction#interactive novel#choicescript#fantasy romance#writeblr#creative writing#writers on tumblr#writing
20 notes
·
View notes
Text
past!me: Oh, it's perfectly fine using different naming conventions for certain relationship variables. I'll remember them!
Quicktest:
Error: masquerade line 2853: Non-existent variable 'rel_dion'
Error: masquerade line 2746: Non-existent variable 'rel_mal'
Present!me:
16 notes
·
View notes
Note
Hiii 👋, I was playing mirror flower but when I chose the neutral option the game bugged, I dont know if its not just there yet or its just me 🤷♂️
thank you, idk how that snuck past quicktest but it's fixed now
3 notes
·
View notes
Note
That's also how I keep track of moon phases, I just look at it like some medieval astrologist.
"Ah yes, I shall be receiving word from Lady Truelove on the morrow."
You sound so fancy! 💙
Meanwhile, here I am, hunched over a laptop, by the light of the full moon:
"Quicktest FAILED?! WHAT DO YOU MEAN?! IT WAS FINE YESTERDAY! I'M UPDATING NOW! DON'T DO THIS TO ME!"
Every full moon...
51 notes
·
View notes
Text
The demo FINALLY passed through quicktest I'm sobbing, I've been working through bugs forever 😭
Now I just have to work through typos and I should be all good!
50 notes
·
View notes