JustQubit

8.2K posts

JustQubit banner
JustQubit

JustQubit

@JustQubit

Elbow deep in a bag of Doritos. Out of sheer necessity, I'm vibin'

Washington, USA Katılım Nisan 2012
215 Takip Edilen341 Takipçiler
Sabitlenmiş Tweet
JustQubit
JustQubit@JustQubit·
The only appropriate way to finish a tub of @GFuelEnergy 😌
JustQubit tweet media
English
11
6
147
0
JustQubit retweetledi
SW33TS 🌸
SW33TS 🌸@sw33tz·
How cool would it be to make a massive list or website of streamers who've never viewbotted to send to brands & companies who are looking for real & genuine communites. 😪
English
33
11
286
12.9K
JustQubit
JustQubit@JustQubit·
Look I'm all for competition in the software space, but trying to hype people up for 2 weeks just to release a generative AI tool that: 1. Eliminates work a real code-based overlay developer/creator could've done 2. Costs $20 (or $60!!!) a month for likely superior models and generation ... all while your software still doesn't have stinger transition support? Not a great look in my opinion, and I think the replies reflect that.
Meld Studio@StreamWithMeld

This is your unfair advantage for live streaming. Introducing Meld Spark ✨

English
0
0
0
44
JustQubit
JustQubit@JustQubit·
@Laurent_B @SpawnPoiint Good thing games like Forza Motorsport, Gran Turismo, Asseto Corsa, etc exist then. Seems right up your alley
English
1
0
9
359
Law
Law@Laurent_B·
@SpawnPoiint Fast travel takes too many clicks to reach a race. NFS had cops to spice up the open world. A-to-B drives are my daily kid drop-off—give real races, skip the forced travel!
English
3
0
0
562
SpawnPoiint
SpawnPoiint@SpawnPoiint·
Forza Horizon 6 screenshots I just took. Japan looks awesome. Xbox Series X. No edits:
SpawnPoiint tweet mediaSpawnPoiint tweet mediaSpawnPoiint tweet mediaSpawnPoiint tweet media
English
173
498
11.5K
751.4K
Mountain Dew®
Mountain Dew®@MountainDew·
Who’s the biggest Baja Blast drinker you know?
English
140
33
745
45.7K
lorelai
lorelai@loganleelord·
@CaptainColter @ZacksJerryRig @elonmusk If you taxed 1 billion dollars at that rate… they’d still have 10 million dollars. I don’t think you realise how big a billion is man
lorelai tweet media
English
1
0
0
55
JustQubit retweetledi
Blerp
Blerp@blerp·
Here are your Creator Accelerator Top 400!! 🥳
Blerp tweet mediaBlerp tweet mediaBlerp tweet mediaBlerp tweet media
English
42
29
153
16.1K
JustQubit
JustQubit@JustQubit·
I can't remember if I read that you had tried this already, but is it possible the camera source could be the issue? Has it crashed if you just used the camera source with no filters on it? Or maybe try with no camera at all (not ideal obviously) to try and narrow down the potential causes? Way back when the NVIDIA filters were just released, the background blur really messed with my stuff, but I figured that would've been fixed by now.
Summit, WA 🇺🇸 English
0
0
1
49
WATCHHOLLIE
WATCHHOLLIE@WATCHHOLLIE·
People who have commented on my daily stream crashes that have been happening for 1.5 years Things I have tried with no fix: - New wifi / new Home - New BEEFY PC (100% new everything EXCEPT 5080gpu) - New cables (inside and outside of pc) - New streaming software - New monitors - Fresh windows install - Bios update - Drivers update/retroactive drivers - Clean OBS scenes to run bare minimum - OBS logs and windows activity checked (shows NOTHING) - Furmark stress test - Switched output from GPU to CPU (solves the nvec error) - Obviously theres more but those are the main ones COUNTLESS tech teams have reached out to help with no prevail. What we know: - Happens when streaming/chatting/gaming/NOT streaming with obs/slobs open - Can't play games on PC without major droped frames. - Can't output on GPU only CPU - Memory leak IS happening on 5080 series with OBS/slobs - Can't change scenes sometimes - Can't have any other programs running during stream - tiktok never crashes when I mutlistream. Only twitch I have been troubleshooting for 1.5 years and I'm almost about to quit.
WATCHHOLLIE tweet media
English
92
6
53
11K
Fourthwall
Fourthwall@Fourthwall·
Who wants this notif? 😏
Fourthwall tweet media
English
217
8
528
20.6K
JustQubit retweetledi
Kwik Trip
Kwik Trip@KwikTrip·
starting a no beer challenge february 29-31 please respect my journey
English
44
303
9.3K
271.6K
JustQubit retweetledi
☔
@Whotfismick·
Planets tier list
☔ tweet media
English
186
8.7K
134.5K
1.6M
JustQubit retweetledi
cinesthetic.
cinesthetic.@TheCinesthetic·
Since its release 11 years ago, just one hour and 36 minutes have passed on Miller's planet in Interstellar.
English
186
2.3K
23.6K
10.7M
JustQubit
JustQubit@JustQubit·
@Simon_Hypixel Please tell me that part of Update 2 can be fixing wood direction differences for wood planks and slabs 😅 It's driving me crazy
JustQubit tweet media
English
0
0
0
26
Simon
Simon@Simon_Hypixel·
Community asks? Community receives! New upcoming feature: ability to hide helm/armor! Will be configurable on the server config for PvP/immersion purposes. Hytale Update 2 pre-release coming up this week! Thank you for your constant feedback and suggestions. We have a lot more QoL improvements, fixes, and features coming up!
English
1.2K
1K
18K
693.2K
JustQubit retweetledi
Lucy Pyre😈🍟
Lucy Pyre😈🍟@LucyPyre_·
“the lower RAM limits are gonna make developers learn to optimize!!!” you hopeless romantic. you overly optimistic angel. when will you learn
English
286
7.1K
82.8K
912.7K
JustQubit retweetledi
Simon
Simon@Simon_Hypixel·
We are delivering on our promise and releasing Hytale into Early Access on January 13, 2026, with all the consequences that come with that decision. In just a few weeks, we merged roughly 300 branches, modernized a four-year-old code & asset base, scaled the team from 8 people to 50 core developers plus ~250 helping hands, tracked close to 1,000 bugs and fixed hundreds of them, added Mac and Linux support, and built an Exploration Mode that simply did not exist before. When we started the mission to save Hytale, we made a clear promise: Launch without any delays, at any cost. We are keeping that promise, even though it is a herculean task. In an alternate timeline, the most intelligent production decision would be to delay launch by 3-4 months, complete the obvious work in front of us, and avoid the overhead and distractions of maintaining a live product. The game would objectively be better on day one. That is not what we are doing. Moving this fast also comes with very real downsides, and you have already seen them. We make visible progress every week, sometimes so much that key community members work overtime to keep up with the news - but you have also seen us drop the ball. Some concrete examples: 1- Name reservations were intended to reward longtime fans. Still, we lacked sufficient time and information to verify the email list's integrity, and some longtime fans were missing from it. 2- The username generator produced unintended results, and our name filters failed to catch some unacceptable cases. 3- The payment system continues to report issues. 4- Communication regarding avatar customization, Steam release, modding, and pricing was insufficiently detailed, leading to misinterpretation or confusion. 5- Blog posts and technical write-ups have landed on an unpredictable schedule. 6- Game server providers, server owners, creators, and business inquiries are not receiving responses as quickly as we would like or as they deserve. This is the tradeoff we all have to accept: You can’t make an omelette without breaking a few eggs. We wish we had more time to double-check every step and spend more time on communication, but that time comes at a steep opportunity cost. Extra polishing reduces the overall impression of Hytale on January 13. Our primary focus is the game. The team is in a constant release cycle. Every week until launch is tightly scheduled, and we are doing this with a core team of around 50 people assembled in weeks, not a massive AAA organization. That means we are taking hundreds of calculated risks every day. Most pay off. A small fraction doesn’t - and when they don’t, the impact is very evident. If I could ask for one thing from the community, it’s this: Please keep reminding each other what this pace implies - especially newer players who were not around for the #SaveHytale moment and may not know what the Early Access experience is meant to be for us. Some people will not be able to get their desired username. Some will run into payment issues. Some information will arrive later than it ideally should. This is not because we don’t know better; it’s because we are choosing to keep a promise. For us, Early Access success looks like this: you start a world, and the first impression and immersion leave you thinking, “This is much better than they said.” After more time, you also start to see the rough edges - and still end your first day thinking, “This game has a lot of potential. I’ll come back and keep up with updates,” or get you inspired to get into making maps, content, mods or a minigame server. As you will be playing through the first week of Hytale, we will already follow up with the first patch. We will release updates rapidly in the first few weeks, with pre-releases available more frequently. You start on the 4-year-old archeology project, but within months, you will find yourself in a flow of rapid development, previously unthinkable. We appreciate that the community has high expectations for Hytale, but please remember that we are fulfilling a promise we made early on: to release as soon as possible. That is what the core community asked for. Our biggest fear right now is not criticism - it’s that the story of #SaveHytale gets forgotten during Early Access, and the team ends up wishing we had simply delayed those extra four months instead of keeping our word.
English
378
904
10.6K
817.1K