I sure hope he isn't.

You're not addressing my main point.

Also “Fleeing because they're scared they'd get falsely prosecuted” probably makes a good percentage of that number.

The data just doesn't support that my guy. And gaslighting and acting like something that actually never happened (Ironically Biden still has deported more people than Trump at this point), will only make the cracks in the institutional problems in immigrations worse

When the actual problems causing illegal immigrants in our nation is actually our own immigration court's systemic failures. We're just sending ICE out to scare people for fun while wasting taxpayer dollars on a fight they'd never win.

ICE has it's purpose, but ICE is literally fighting a battle that will end up (and for some, already is) a waste of taxpayer dollars as they are currently being used as a attempt to treat a problem that has a far deeper root in it that itself can't (without authoritarian overreach) solve

So, if we want to actually solve the problem instead of fighting a war that will never end. Reforming our Immigration courts and Immigration-Extension/VISA systems will be the route to do it in a more permanent/actionable manner.

Actual advice, if you want to actually help the immigration problem...why not do reform and help solve the actual source of "illegal Immigrants"?

AKA how the vast majority of "Illegal Immigrants" are just VISA overstays who are in limbo due to it taking years to get a VISA extension case heard.

Hello Alex, just going to put some questions/pointers/corrections in a chain here (curious to your thoughts on some of them though as some of it I do feel is important or at the very least interesting)

I've said this multiple times, durability. Writing data (which includes "erasing" is intensive on NAND. Which is why drive transfers are the most health/draining operation a NAND drive can do

I'm just confused what you're asking at this point to be honest? 😅

Like, holding back write speeds is a common strategy to save durability. And copying between drives is going to be held back by the slowest drive in the set 9/10 times.

Becuase the floor of the mSDE card is way above the Game Carts?

Just becuase sure, the UFS may be up to 1.5GB/s by my guess. Doesn't make the 800MB/s lower for the mSDE cards "slow" it's just slower in relation to the UFS?

And the worst mSDE is twice the speed of the best game carts

Well, that is just an example of the inherit speed difference between the UFS and mSDE cards? The UFS is faster so it can be read faster.

The mSDE is slower so the system reading it to write to the UFS is slower

Not sure what the problem is then, must have misinterpreted your first comment

Read speeds are not the same as write speeds for one. And for two, durability is probably something Nintendo is trying to maintain as much as possible for writing (which is what drains said durability faster)

Wonder how fast the switch 2 game cards are

One can assume based on the rated speeds of the SD Express cards that the UFS internal storage is >1GB/s (1.2-1.5?). mSDE cards obvs are 800-900MB/s

Does Outlaws have problems on SATA SSDs on PC? (~500MB/s)? As 400-500MB/s was my guess for the Game Cards

If you send me a bug report on a game I’ve made because you’re using this device, I will make it my personal mission to hunt you down and ensure you cannot inflict your corruption on anyone else

And considering the development of this title seems to be pretty tight timeline wise, and how consoles are the predominant market, I can see the prioritization of gameplay and using the old rendering style for time saving and getting performance headroom for scale/density.

We do have to remember, these consoles are 6-7 Core (Not counting the OS Reserved ones) Zen2 CPUs with butchered cache setups relative to their PC counterparts.

Now, one could argue "just not do RT on consoles" sure, but then that'd be time and money put in the PC version exclusively

Like, fair in some regards. But the fact they have the apparent CPU headroom so far on the console's unlocked modes for 80-100FPS is impressive, although I'm not sure if stuff like RT (which would require a relatively complex BVH to compensate for destruction) would be in-budget CPU side?

If it's some form of cubemap, it's def an advanced deployment of it from my take? Something more akin to what Starfield does with its reflections if not further?

Unless something there indicates it's something else or even RT Reflections somehow.

So @dark1x.bsky.social
DK Bananza seems like it may have some level of advanced reflections on some surfaces?

Whatever it is, it's enough to catch out of screen space info with a good level of perspective correctness and more curiously catch geometry changes to deformation by the player

And like I pointed out, the DK Direct does have notably improved image quality versus the release version DF has looked at which may indicate they are working on implementing it with DK Bananza or at least played around with implementing it but decided not to for whatever reason.

Well, for cases like MK World and even Banzna. DLSS's flaws may be more apparent due to the higher motion in MK world and complexities implementing satisfactory motion vectors/data management for the temporal data in Bananza?

ModuleSystem hasn't had a TAA system yet, so DLSS would be the first.

I say actually in-use considering well, just because ModuleSystem has SMAA/FSR1 in the copyright terms, doesn't mean a specific game is using it?

Not saying Banzna doesn't in the build you played. Just pointing that out as some erroneously use that solely as a validator.

Besides that though, i feel the hate on FSR1 is a bit excessive at this point. Like, sure, it's not as good as DLSS or FSR2 at upscaling an output. But like....it's still better than Bilinear/Nearest Neighbor? And Nintendo's implementations of FSR1 have been the best for it when it's actually in-use

I will ask, was this recorded with that 1.1.0 patch?

Asking as the Direct had much better IQ vs here. The AA looked so smooth in-motion and on inner-surfaces that I thought it was DLSS. Makes me wonder if they were going back and forth, or if DLSS/ a TAA+FSR1 method? will be added in a future patch

I will note on the UFO test. The container is busted apparently? It's SDR only and the color space out of whack specifically due to errors in the browser. Could that influence the results of tests for response time?

At the very least it's stuck in 60hz mode vs 60fps in a 120hz container which does?