Bug with t2 naval

here´s the Dx.diag file

This guy is experiencing the untextured leviathan/other ships look like leviathans bug that's been around since the start of Alpha but not been fixed because it's so random.

I get this too. Need a DXdiag from me too?

Do you have an Intel HD or AMD card because that's where it seems to be popping up.

I also have the issue.

Yeah, i do.

I have HD graphics too dang it

I bought an nvidia, so I do not have this problem, but I bought my card at the worst possible time, right before AMD released mantle GPUs

I did have this issue with my 4850, 7850, and my intel HD graphics, though.

@bgolus

HD and AMD cards exclusively it seems, any chance you guys could give it another go?

Which means it's probably a driver problem, and something only nvidia has fixed, it seems.

Is this issue ever going to be addressed?

@jables @sorian

Mantle is not so impressive right now, it means a lot for low end cpu and graphic combination through... Still it need more support from game developers.

Aye, DX12 should be better, but we will have to wait and see.

They have addressed it before, but it seems to be very difficult to reproduce.

@bgolus would be your guy for this.

which means Uber is using nvidias
burn the Uber heathens
and me too, because I have an nvidia now

Well no, they should have other devices too, for testing purposes.

But maybe they didn't know it was secluded to certain bits of hardware?

They haven't fixed the AMD brightness bug either, right? So it seems likely that they don't have any or enough AMD test machines.

None of our AMD GPU systems have the brightness problem. I believe we have a few high end HD 6000s, no idea which ones since AMD sent them to us unbadged and they have non-standard memory allocations. We have a two HD 7000s which have no problems, and an A4 APU for a $300 "can it even run?!" system (spoiler: it can ... and it's broken as hell, but also so slow if you try to debug it locks the system).

As for the leviathan bug, we have a couple of Intel system w/o a video card that have had the problem, but so far we've been unable to determine the cause. If I remember correctly the Intel debugger would show that it was displaying the correct model / texture even when it clearly was not.

edit: also, I'm not the person who would actually go about fixing the leviathan bug, or even tracking it down. Unfortunately we only have one person capable of doing that now and he's too busy fixing everything else.

@bgolus - If we come across this, whats the best way to go about helping you guys out? Uploading the dx.diag?