texture compression problem
- Thread starter nobond
- Start date
OpenGL guy
Veteran
No. The great thing about DXTC is that it's trivial to decode, encoding it (with good quality) is much more difficult.can render targets be stored as dxttextures ???
OpenGL guy
Veteran
Actually, you do. Multisampling can certainly benefit from compression, and it can even be lossless (like our current MSAA compression).
thanks=)
i'd rather have transistors for something else, though.
OpenGL guy
Veteran
Like what? Without compression, MSAA would use the same bandwidth as SSAA and would greatly impact your performance.
3dfx style aa's performance hit is fine with me.
without benchmarks people would never know the difference in theoretical performance in a lot of cases.
just b/c it reduces the fill rate drastically, doesn't automatically mean it will decrease the enjoyment of the game you're playing.
without benchmarks people would never know the difference in theoretical performance in a lot of cases.
just b/c it reduces the fill rate drastically, doesn't automatically mean it will decrease the enjoyment of the game you're playing.
25 in most cases, except make that avg.
Occasional dips down to 17 fps are fine if the iq is better and if it's a fast moving game.
i got used to the 3do version of doom quite easily, and the constant access pauses were worth the high quality redbook music, imo, and i like the saturn version of mk2 better than the arcade version, and hope to revisit it soon.
it was unusual for a saturn game to have those frequent access pauses, but i guess probe had already done so many ports of mk2 by that time, that they just got lazy.
although, if it's a not very fast moving game though, sometimes i'll care about frame rate. alone in the dark 2 for 3do was hindered by it's constant access pauses, making the saturn version the best. don't listen to anyone who says the saturn version has the worst control. the ps1 version sucks like the 3do one does, although the 3do version has better graphics than the saturn one. BTW, the saturn and ps 1 versions are named one-eyed jacks revenge. i don't know why thq changed the name.
i know i'm crazy, but i'm different from everyone else.
by the way, i prefer compatibility and iq equally, then heat, then i really couldn't give a fuck less about "a few extra fps."
with fans i prefer the highest cfm, i don't give a fuck about how noisy a fan is. long life, a good pattern of airflow and the highest cfm possible. i also like molex connectors and plugging them into the psu rather than 3pin for mb dickheaders.
what i like is never popular, and often never made.
Occasional dips down to 17 fps are fine if the iq is better and if it's a fast moving game.
i got used to the 3do version of doom quite easily, and the constant access pauses were worth the high quality redbook music, imo, and i like the saturn version of mk2 better than the arcade version, and hope to revisit it soon.
it was unusual for a saturn game to have those frequent access pauses, but i guess probe had already done so many ports of mk2 by that time, that they just got lazy.
although, if it's a not very fast moving game though, sometimes i'll care about frame rate. alone in the dark 2 for 3do was hindered by it's constant access pauses, making the saturn version the best. don't listen to anyone who says the saturn version has the worst control. the ps1 version sucks like the 3do one does, although the 3do version has better graphics than the saturn one. BTW, the saturn and ps 1 versions are named one-eyed jacks revenge. i don't know why thq changed the name.
i know i'm crazy, but i'm different from everyone else.
by the way, i prefer compatibility and iq equally, then heat, then i really couldn't give a fuck less about "a few extra fps."
with fans i prefer the highest cfm, i don't give a fuck about how noisy a fan is. long life, a good pattern of airflow and the highest cfm possible. i also like molex connectors and plugging them into the psu rather than 3pin for mb dickheaders.
what i like is never popular, and often never made.
The compression used for render targets is lossless. For static textures there might be interest in a DXT-like compression scheme for HDR data. There's no consensus that that's neccesary though, because you can achieve decent HDR compression with existing formats and a couple of math instructions. In DX10 there's also the RGB9E5 and R11G11B10_FLOAT, with the latter being available as render target as well, which may be good enough for most cases.
What? Like doubling the size of the caches and the bus just to compensate for you banning texture compression?
And doesn't make much sense, either. Basically you are saying you want to go back to the inefficiencies of yester-hardware. Oooo goody. What you suggest be thrown away is what makes it possible to make current and future games. Your ideas wouldn't improve quality, they would reduce it and performance.
I think 3DO scarred you for life.
A low-end 486 can run Doom better than 3DO. Uhg.http://en.wikipedia.org/wiki/Versions_and_ports_of_Doom#3DO_Interactive_Multiplayer
"Many fans consider this one of, if not the worst console port of DOOM.. Its updated soundtrack, which features remixed and original music, is considered its one redeeming feature.." lol
Further more, for a rendering, it looks like both ok for you traverse the pixel in the triangle or traverse the texture and map them to the screen space. Intuitively, looks like the former is the natural one. Is it right?
