Thread 107009312

any day now...

I thought someone already showcased this and it absolutely raped larger textures
like colored cloth came back looking like peeling print

>>107009312 (OP)
Samsung is about to discontinue 8GB RAM production so nvidia has to increase VRAM in later generations.

6050 = 12GB VRAM
6060 = 12GB VRAM
6060Ti = 12/16GB VRAM
6070 = 12GB VRAM
6070Ti = 16GB VRAM
6080 = 16GB VRAM
6090 = 32GB VRAM

unused vram is wasted vram

>>107009312 (OP)
>lower VRAM usage
>15% lower FPS too

>>107009312 (OP)
WOW, ARE YOU TELLING ME PROCEDURALLY GENERATED TEXTURES TAKE UP LESS STORAGE SPACE!? STOP THE FUCKING PRESSES!

2004 called, .kkrieger only uses 96kb.

>>107009536
Aw sweet, 15 years of 12GB here we go.

>>107009755
it would be enough in a normal world, 12GB of vram would be large amount even for 1440p.
game dev is the new webdev, nothing matters anymore beyond monetization, cpu cores are spending an ungodly amount of time idling, waiting for something to do.
game engines are incredibly bad are feeding them with work as they're not designed to exploit hardware anymore, it's very sad to see.
take a few hours to browse stutter engine 5 source code, it's saddening, all these allegedly "godlike" unreal engine engineers doing such a shitty job is mindboggling, something is definitely wrong at this company as I would be fired on the spot if I ever produced such slop.
I'm very happy to not have to work with any open source 3d engines, they're all dogshit

>>107009825
Yeah sure, whatever. Can't get around texture sizes, anyway.

>>107009830
>Can't get around texture sizes
yes you can lmao

>>107009857
not without down sampling and losing quality

>>107009312 (OP)
>neural
>compression
enjoy your artifacts nyidias

>>107009983
> artifacts
but it's neurons made high res version in the first place

>>107009312 (OP)
use case for vram?

>>107010060
wan

>>107010060
cars
>they go vram vram

>>107009490
Lets be real it was never meant to be used for games.

>>107010382
I fucking hate you kek

>>107010382
You don't need a car

>>107009312 (OP)
So whats next from nvidia? So far we have (as far as i can recall)
>fake pixels
>fake frames
>fake inputs
>fake textures

>>107010686
GPUs in orbit

>>107010686
fake games, google is still working on that

>>107009983
>old rendering artifacts GOOD
>new rendering artifacts BAD

>>107009536
Handheld PCs have 16GB+ VRAM. Where are the mainstream desktop versions of that?

>>107010864
Show us a handheld with that much VRAM

>>107010864
The desktop version of that is a CPU with integrated graphics, those handhelds do not have "VRAM" they're just using a portion of system ram which is significantly slower.
They would likely benefit more from this sort of tech than desktop cards due to having so much more compute power on their iGPUs than the memory bandwidth they're paired with, but they're all AMD.

>>107009312 (OP)
why the fuck would you even want that trade-off?

>>107010703
well, anon forgot to mention
>fake ownership

>>107010686
I'm out of the loop but I remember a while back they added runahead to Retroarch.

You know how you can make some emulators rewind/fast forward/etc.? Runahead worked by making is so that when you input something, the emulator rewinds one (or more) frames, enters your input in for that earlier frame, then fast-forwards back to the present.
Just wondering now if you could do that in combination with framegen.

>>107010686
>fake reality
Wait, this might actually be good.

>>107009536
They already have with the upcoming 5000 series refresh. The 5080 Super is going to be 24GB, so the 6080 isn't going to go back down to 16GB.

>>107009312 (OP)
is this like the fx5xxx era where they cheated on 3dmark by forcing textures on being rendered only on 2d structures and called it a win?

>>107009312 (OP)
holy mother of based