/vt/ - Virtual Youtubers

>>13560482
redstone

>>13560482
Java Edition can't handle anything because Mojang was just a couple nerds in a basement who didn't know shit about programming.

>>13560482
Theirs a metric shitton of NPCs in the server on top of red stone red stone contraptions and such. Kanata had so many chickens that it lagged everyone in the general vicinity to the point of dropping the FPS to around 15 frames.

>>13560482
Spigot is not the fastest software

>>13560482
???? I get like 15 FPS on a good day playing Minecraft and you're complaining about 45? God you PC freaks are fucking obnoxious. The human eye can't even see past 24FPS

>>13561056
Based

>>13560482
On top of all the looping redstone contraptions that they can't be assed to turn off, the oopa loopa craze also made it heavy as fuck since a bucketed oopa loopa doesn't despawn, thus cluttering the server with more and more entities and on top of it some of the girls didn't have the heart to just burn all the non-blue oopas they bred.

>>13561056
I had to quit playing because of 3 fps or less...

>>13561093
Or they set them free in one of the resource maps

>>13561056
> The human eye can't even see past 24FPS
that's a myth though

>>13561093
Axolotls in a bucket count as entities? Since when?

>>13560765
I remember minecraft barely running on a dedicated gaming rig.

>>13561056
Oh my... This myth kills me more than any other out there, due to having such a vested interest in PC gaming. This is such a common myth that it honestly makes my head hurt.

I'd like to correct this and if only 4 people walk away after seeing this thread and know better, I'll feel great. I'm going to keep this simple.

Myelinated nerves can fire between 300 to 1000 times per second in the human body and transmit information at 200 miles per hour. What matters here is how frequently these nerves can fire (or "send messages").

The nerves in your eye are not exempt from this limit. Your eyes can physiologically transmit data that quickly and your eyes/brain working together can interpret up to 1000 frames per second.

However, we know from experimenting (as well as simple anecdotal experience) that there is a diminishing return in what frames per second people are able to identify. Although the human eye and brain can interpret up to 1000 frames per second, someone sitting in a chair and actively guessing at how high a framerate is can, on average, interpet up to about 150 frames per second.

The point: 60 fps is not a 'waste'. 120 fps is not a 'waste' (provided you have a 120hz monitor capable of such display). There IS a very noticable difference between 15 fps and 60 fps. Many will say there IS a noticeable difference between 40 and 60 fps. Lastly, the limit of the human eye is NOT as low as 30-60 fps. It's just not.

The origin of the myth: The origin of the myth probably has to do with limitations of television and movies. Movies, when they were recorded on film reel, limited themselves to 24 frames per second for practical purposes. If there is a diminishing return in how many frames people can claim to actually notice, then the visual difference between 24 fps and 60 fps could not justify DOUBLING the amount of film reel required to film a movie.

With the advent of easy digital storage, these limitations are mostly arbitrary anymore.

The numbers often cited as the mythological "maximum" the eye can see are 30 fps, 40 fps, and 60 fps.

I would guess the 60 fps "eye-seeing" limit comes from the fact that most PC monitors (and indeed many televisions now) have a maximum refresh rate of 60hz (or 60 frames per second). If a monitor has that 60 fps limit, the monitor is physically incapable of displaying more than 60 fps. This is one of the purposes of frame limiting, Vsync and adjusting refresh rate in video games.

tl;dr: The human eye can physiologically detect up to 1000 frames per second. The average human, tasked with detecting what framerate he/she is looking at, can accurately guess up to around 150 fps. That is, they can see the difference in framerates all the way to 150 fps.

Phew.

A quote to leave off on:

The USAF, in testing their pilots for visual response time, used a simple test to see if the pilots could distinguish small changes in light. In their experiment a picture of an aircraft was flashed on a screen in a dark room at 1/220th of a second. Pilots were consistently able to "see" the afterimage as well as identify the aircraft. This simple and specific situation not only proves the ability to percieve 1 image within 1/220 of a second, but the ability to interpret higher FPS.

>>13561093
BTW, ever since Cover beefed up the servers for the Sports Festival, the lag in Holoserver is fixed now! Also, the automatic contraption at the ice road course was switched off (one of the suspects for the lag)

>>13561184
My bad, by bucketed oopas I meant oopas that were bucketed and then respawned somewhere else like that one hidden space made by Kanata below a stand in the summer festival area.

>>13561325
EN server is plagued by "egg zombies". Does JP have the same problem?

>>13561233
It's honestly difficult to tell the difference after 100-ish FPS, at least for me.

>>13561325
Either way, they need to holocaust those little fuckers, along with half of every other animal on the server.

>>13561233
But we are not fighter pilots. We are common people. Many with glasses, and shit eye sight without them.

You need at least this setup if you're serious about Minecraft.

>>13561354
No, I don't recall seeing an infestation of egg zombies in JP server. Most of the causes of the lag are purely made by the girls themselves.

>>13561233
But anon 30 fps its enough to enjoy the games? games like Minecraft

>>13561438
You joke, but a geforce 1080 is probably bellow the (real) minimum system requiremens for minecraft. How does such a fucking ugly game end up being such a huge resource hog?

>>13561056
Poorfag can't run minecraft properly... Sad

>>13561535
1080 is slightly slower than a 3060, but in current year that's slow. I mean, you need a Threadripper rig just to play fucking Roblox now!
https://www.youtube.com/watch?v=gH_c4sGDrPg

>>13561535
>>13561679
Not one but two 1080s

>>13560482
because it's minecraft, and they've built a shitload of stuff. minecraft is a code disaster that shits the bed when you start having loads of "complicated" things to render, redstone and npcs or not. even with a rig only nasa could afford to build, you'll run into trouble when there's enough shit around.
it had trouble back when notch made it, and it still does now that jeb and dinnerbong have tried to remove notch from minecraft history because they're even more inept than he was.
>>13561233
>peddling this much lie to justify retardedly high gpu-melting framerates that people can't see a difference with
take your fuckin' meds, you stupid frogposter. stop drinking the poisoned koolaid.
>>13561535
spaghetti code held together with bandaids and spitwads, mostly.
the real version of minecraft is made in java. minecraft needs lots of memory management and handling all kinds of shit with rendering and all, and java is dogshit for all of it. even if it was coded really well it'd have serious problems because of java's limitations. bedrockbottom edition is coded in some variation of C, and works much better... except it lacks a ton of stuff that's been done with the real version and is also made in such a way that modding is far more trouble than anyone is willing to go through, and that includes server-side shit like spigot, which hololive's stuff depends on for their inter-map shenanigans.

>>13561512
agreed. it's literally impossible to tell the difference between 30 and 60+ FPS with the naked eye

>>13561679
>>13561438
>mfw still unironically using a 1080 from 2016

>>13561840
Screw you buddy, I'm using a 960 because my Rx 580 decided to die on me after its warranty ended.

> poorfags can't tell the difference between 30fps and 60fps

>>13561233
I thought 120 thing was myth until I tried it in rhythm games. Maybe it matters in fps too but I'm too bad at those to have a proper opinion.

>>13561056
>The human eye can't even see past 24FPS
Then explain how I can tell the difference between 30 and 60 FPS and how it bothers me like hell.

>>13561993
Did you really fall for that ancient bait

>>13560482
JPs not bothering to kill their axolotls and everyone playing with chunks set to almost max combined with the game rendering them even though they're offscreen.
It's a combination of every party being retarded.

It's actually a combination of several things, but it's mostly the amount of entities, e.g. the oopas, banners, the absurd amount of item frames with map art on them, small animal pens that force constant collisions. Also, redstone machines that are running constantly.
There's also a small portion of it that's just because of the sky minecart rails, mainly because the way sub chunks load, thats honestly just because the game is poorly coded.

>>13561807
And so, their solution is to outsource the problem to everyone needing to buy upgraded PCs. Oh wait, everyone does that

>>13562069
Fuck you gurafrog poster.

>>13561827
> it's literally impossible to tell the difference between 30 and 60+ FPS with the naked eye
I dont think is impossible but for this type game is useless bc +60 FPS doesn't improve the game experience. For games like online shooter maybe

dead frog a day keeps the cancer away

>>13560482
Minecraft is 12 years old, not surprising it shits the bed

>>13561512
Only if you haven't experienced 60fps