Recent content by Mintmaster

I think borderless phones are a bad idea. When you hold them, your flesh folds over and generates touches accidentally. It already happens occasionally to me with my thickish-border phone, and I'm a skinny dude, too. I can only image what fleshier hands would do when holding a phone like this...

I don't see how sort middle has any hope of becoming reality now that we're way past the single tri per clock era. It could have been done before, but now there's too much data at that stage. I think object level sorting is the only route to getting rid of AFR, and if XBox 360 wasn't enough...

I dunno, some of those results are unexpected to me. In BF3 the Ti is 30%+ faster than the base 780. The power consumption is off the charts, too. 150W more than the 290X in 3DMark.

Again, I'm accepting your claim that HS output may warrant going off chip. And latency is exactly why I think UV streamout can cause stalls. But once HS data is read back, it makes no sense for high tessellation-factors to have reduced triangle throughput over low factors. The HS overhead...

http://www.valuewalk.com/2013/11/apple-samsung-contribute-to-surge-in-global-smartphone-market/ Nothing unique to Lumia there.

Bingo. This is why AB tests are stupid. There are some things I can tell without any reference image, like plasma vs. LCD black levels. As long as the picture has a few swaths of black and I'm not in a very bright room, I can tell without side by side comparison. But for things like the...

My mistake. Ignore what I wrote in that paragraph. But sustaining 1000 control points is silly for a shader without texture loads in a load-balanced system (even if it does initially issue that many), and even if you're right that the tens of kB needed to buffer enough control points is too...

It doesn't need to be large. Your calculations were dependent on having 1000 HS wavefronts, which is at least 50x too many. It's extremely rare for a HS to need texture access. BW wouldn't be an issue (4 verts/clk is < 24 GB/s), unless there is an internal restriction. Latency and/or extra...

Of course they implied it. The G2 was compared to the Note3 throughout the review, including the benchmark section, so harping on Samsung without saying a thing about the G2 is a clear implication that Samsung is dirty and LG is clean.

First of all, that's a failure in optimization if AMD is sacrificing high-factor performance to improve low-factor performance. Their own devrel material suggests not using tessellation at low factors, and poor HS performance won't matter then anyway. The DS is where displacement mapping...

That's what I meant by patch data. I was giving a suggestion for even avoiding the UV calculation in the tesselator, but if AMD does do it, then that's great. The problem is that their data flow management for tessellation sucks if it needs off chip storage. I don't see how this is so different...

It's not just Tessmark. You see it with AMD's DirectX SDK example as well.

If you design the tesselation unit properly, there's no need to generate all the DS verts at once. The hardware tessellator should have access to patch data (maybe a few wavefronts so that the case of zero amplification doesn't cause excessive slowdown) and create wavefronts of DS verts as...

I'm still disappointed in AMD's tessellation implementation. http://techreport.com/review/25509/amd-radeon-r9-290x-graphics-card-reviewed/6 Multiply NVidia's score by the tests' tessellation factors, and you get a roughly constant number, i.e. tris/s is constant. AMD, OTOH, loses throughput with...

Really? Then why bother increasing performance at all? Or do you have some way of telling the difference between 10% difference from BW and 10% difference from the GPU? Irrelevant. They sell overclocked 670's, too. You're not very good at counting. Any reason why you snipped out the part where I...