Hmm so AMD’s confident, could be good.
(EDIT: Well it’s still rumors and marketing so some skepticism as usual but it sounds better than before.)
And with the engineer example GPU that got leaked or shown before possibly they will use 256 bit bus but offset the bandwidth problem by adding a lot of cache memory.
Trying to hit above the 3080 with the higher GPU SKU’s too going to make for some nice reviews and comparisons once AMD has their new graphic cards on the market.
Plus pricing and availability and all that, going to be interesting as well to see how quickly NVIDIA can fill up on availability after this first batch goes…which is going to be like a day or so after launch.
EDIT: Still a bigger lead for NVIDIA as the first two months will be only the 3000 series and Ampere and that’s if AMD can get their hardware out around mid-November.
Upgrade from Pascal, Turing or earlier and on AMD’s side Fury, Polaris and Vega or also the Navi10 GPU’s there’s still a good bit of performance gained from upgrading to a 3070 without the additional cost the 3080 has although that GPU has some good value too for the potential performance increase.
(And with some deals and discounts that could look even better before a 3070 or 3080Ti version is introduced filling the price gaps and performance between NVIDIA’s initial lineup here a bit.)
Meanwhile Crytek is here to tell us we don’t need DXR for real-time raytracing. Don’t know if their approach could become commonly used, i would think so.
It’s not exactly the same as hardware-accelerated ray tracing though and is quite expensive to compute.
It’s a cool technology, but the method alone is not the future. We might, however, see it used in conjunction with other technologies or such to add to the overall featureset.
I recommend Digital Foundry’s latest video on the topic:
I am going to sleep for a few days and then plan to release 0.11.0.49
Tentative Release Notes
0.11.0.49:
-------------------------------------------------------------------------------
( Flip Model + Fullscreen Exclusive is now supported for all D3D11 games! )
This means that HDR can now be used in Fullscreen Display Modes, with Refresh Rate
overrides and (on NV hardware) your choice of signal encoding (e.g. YCbCr 4:4:4).
Refer to the Display menu for more details
==========================================
>> NOTE: Not all of the Signal Encodings listed will work for your current
Refresh Rate (NvAPI -SUCKS- at enumerating Signal + Refresh Support)
+ A ton of tooltips have been added to the D3D11 SwapChain and Framerate Limiter
sections, mostly amounting to "Reduces Input Latency."
* Tooltips will be immproved later, for now pay attention to "Low Latency Mode"
and "Drop Late Frames" in the Framerate Limiter config section.
-------------------------------------------------------------------------------
- Sleepless Window / Render Thread were accidentally enabled by default in 0.11.0.48.
+ Removed Fallout 4 and Dark Souls 3 Flip Model plug-in options, these games will
use the standard SK flip model settings now instead of requiring special config.
+ Unified IDXGISwapChain::Present (...) and IDXGISwapChain1::Present1 (...)
code for better compatibility with Chromium-based games (i.e. CrossCode) and
video players (i.e. VLC).
>> Steam Overlay does not hook/wrap IDXGISwapChain1::Present1 and cannot count
frames or even figure out when to draw in software that calls Present1 (...).
@ (!!) VALVE might want to do something about this at some point :P
ahh so that’s why its freaking storming outside right now lol. I took out trash and recycling around 9PM. lol. Our crazy neighbor is coming back home from hospital tomorrow which my mom found stuck on floor after 2 to 4 days? Was a horror show. Had to get cleaning ppl to come to house.
Edit:
Why is there suddenly so many damn mini hurricanes all over now around Florida and Gulf lol. Its like worst season yet rofl.
Spoke just a tad prematurely. Unreal Engine games are still touch and go, and probably always will be due to the way exception handling works in “viewport.cpp”.
However - for any game that officially has a borderless window mode, turn that on and then SK can start overriding things without any problems. That covers about 99% of Unity and Unreal engine games.
It’s 2020, do not ask questions This is the weirdest year on record.
I actually figure the year is supposed to end with like 2 or 3 Category 5 Hurricanes hitting Florida all at once making evacuation shelters into COVID-19 factories.
So, in my quest to find a mouse with a decent horizontal scroll wheel, I somehow wound up buying this…
And I actually quite like it.
I haven’t used a trackball in ages, and gaming with this is similar to the Steam Controller. Which probably sounds terrible to most people, but I am maybe the only person in the world who loved the Steam Controller while it was a thing. I went through three of them – can you guess what kept breaking?
Drumroll, please ...
The Micro USB port, I am allergic to Micro USB
Sadly this trackball uses Micro USB, but it’s stationary so I expect to only go through 2 or 3 cables a year maybe?
It’s been really great for input latency testing, just thumbing the ball at a constant repeatable velocity.
The tilt action on the mouse wheel is nothing special unfortunately, but I think this will prove more durable than my last mouse in the end since it never moves.
auto constexpr carriagereturn = 0xbaadf00di8;
auto constexpr newline = 0xai8;
auto constexpr crln = (carriagereturn << 8) | (newline);
auto constexpr crln_ = '\r\n';
static_assert (crln != crln_);
Well, that’s interesting.
That assertion should fail in the compiler. Instead, it fails in the IDE’s red squiggly doodad and the compiler thinks it’s valid and I have to write a valid static assertion to get the compiler to generate an error.
Also interesting the compiler doesn’t warn about all the superfluous garabage before 0x0di8. That 32-bit value cannot possibly be cast to (i8) without 24-bits evaporating.
I was wondering about the recent faster than usual deployment for the C++ 2019 runtime figures that matches the SDK updates also being deployed at a fast pace ha ha.
Although if that was anywhere near valid the SDK for C++ would be updated non-stop akin to daily builds from all the error reporting and troubleshooting data Microsoft would be getting their way.
EDIT: Now that must be a interesting little loop breaking the C++ compiler when building the C++ SDK so the fix for the compiler breaking can’t be compiled.
Well that’s why back-ups and rollback is a thing I suppose.
