Okay, so I've been playing the game for about a week now, and these bugs have really started to get to me.
https://imgur.com/a/Si1h7 I wasn't going to act on it until today's update which made the behemoth go all wonky too.

What video card are you using? Are your drivers up to date? You also forgot to mention that you're using a windows 10 machine with the Dx11 driver, which may help the devs. Also could you post your directX 11 logs?

Intel(R) Q45/Q43 Express Chipset (Microsoft Corporation - WDDM 1.1)
No my drivers aren't up to date, because windows 10 wont let me update an old card like mine without downgrading to windows 7, how do I get dx11 logs?

https://downloadcenter.intel.com/download/26813/Intel-Graphics-Driver-for-Windows-15-33-

You should find your CPU listed in the box at the bottom, and if you do you can indeed install the updated driver from Intel.

But yeah, get your dxdiag(version).log in the vendetta install folder, you should be able to open it with wordpad or notepad or whatever you prefer.

assuming you installed VO in the default location, for windows, C:\Program Files (x86)\Vendetta Online\directx11.log

[01/06/18 11:52:19] Setting up Mode List
1024x768: format = 87, s1=0, s2=1, n=65000000, d=1083264
1152x864: format = 87, s1=0, s2=1, n=81624000, d=1360400
1280x600: format = 87, s1=0, s2=1, n=61503000, d=1025056
1280x720: format = 87, s1=0, s2=1, n=74481000, d=1241344
1280x768: format = 87, s1=0, s2=1, n=80136000, d=1335600
1280x800: format = 87, s1=0, s2=1, n=83462000, d=1391040
1280x960: format = 87, s1=0, s2=1, n=108000000, d=1800000
1280x1024: format = 87, s1=0, s2=1, n=108000000, d=1799408
selectedAdapter = 00000000, driverType = 1
CreateDevice: hr = 0 (0x00000000)
Creating swapchain
hr = 0 (0x00000000)
Device description: 'Intel(R) Q45/Q43 Express Chipset (Microsoft Corporation - WDDM 1.1)'.
VendorId: 0x00008086
DeviceId: 0x00002e12
SubSysId: 0x3036103c
Revision: 0x00000003
[01/06/18 11:52:20] Device has 268435456 bytes total.
[01/06/18 11:52:20] D3D11 is valid.
[01/06/18 11:52:20] SetMode(7, "Vendetta");
unknown query
selectedAdapter = 00000000, driverType = 1
hr = 0 (0x00000000)
msaa 0 count = 0, hr = -2147467259 (0x80004005)
msaa 1 count = 1, hr = 0 (0x00000000)
msaa 2 count = 0, hr = 0 (0x00000000)
msaa 3 count = 0, hr = 0 (0x00000000)
msaa 4 count = 0, hr = 0 (0x00000000)
msaa 5 count = 0, hr = 0 (0x00000000)
msaa 6 count = 0, hr = 0 (0x00000000)
msaa 7 count = 0, hr = 0 (0x00000000)
msaa 8 count = 0, hr = 0 (0x00000000)
msaa 9 count = 0, hr = 0 (0x00000000)
msaa 10 count = 0, hr = 0 (0x00000000)
msaa 11 count = 0, hr = 0 (0x00000000)
msaa 12 count = 0, hr = 0 (0x00000000)
msaa 13 count = 0, hr = 0 (0x00000000)
msaa 14 count = 0, hr = 0 (0x00000000)
msaa 15 count = 0, hr = 0 (0x00000000)
msaa 16 count = 0, hr = 0 (0x00000000)
msaa 17 count = 0, hr = 0 (0x00000000)
msaa 18 count = 0, hr = 0 (0x00000000)
msaa 19 count = 0, hr = 0 (0x00000000)
msaa 20 count = 0, hr = 0 (0x00000000)
msaa 21 count = 0, hr = 0 (0x00000000)
msaa 22 count = 0, hr = 0 (0x00000000)
msaa 23 count = 0, hr = 0 (0x00000000)
msaa 24 count = 0, hr = 0 (0x00000000)
msaa 25 count = 0, hr = 0 (0x00000000)
msaa 26 count = 0, hr = 0 (0x00000000)
msaa 27 count = 0, hr = 0 (0x00000000)
msaa 28 count = 0, hr = 0 (0x00000000)
msaa 29 count = 0, hr = 0 (0x00000000)
msaa 30 count = 0, hr = 0 (0x00000000)
msaa 31 count = 0, hr = 0 (0x00000000)
Creating swapchain
hr = 0 (0x00000000)
m_pSwapChain->ResizeTarget hr = 0 (0x00000000)
m_pSwapChain->SetFullscreenState hr = -2005270494 (0x887a0022)
Device description: 'Intel(R) Q45/Q43 Express Chipset (Microsoft Corporation - WDDM 1.1)'.
DedicatedVideoMemory = 67108864
DedicatedSystemMemory = 0
SharedSystemMemory = 1711271936
Feature Level Supported = a000
Initializing Device Objects...m_pSwapChain->ResizeBuffers(1, 1280, 1024, 87, 0x00000002)
backBufferDesc = 1280x1024 87
Error: Failed to load vs[8] shader.
Error: Failed to load vs[9] shader.
Error: Failed to load vs[12] shader.
Error: Failed to load vs[13] shader.
success.
Restoring Device Objects...
success.
Reloading Textures...done.
[01/06/18 11:52:23] failed to find end of shader '//HLSLVS'
m_pSwapChain->ResizeBuffers(1, 1280, 1024, 87, 0x00000002)
backBufferDesc = 1280x1024 87

I tried updating my drivers, many times. All kinds of ways.

This thing? released in 2008? If true, i'm... a tad suprised to see it with a DX11 driver. go down to the DX9 driver and see if that helps.

Thanks for the input. Actually, how do I change to 9? It was at 11 from the start and I can't find anything in the options.

Options>Video>Change Driver Button

That's not in there. https://imgur.com/a/4jEZT

Oh, no shit - turn off Simulated VR mode! Actually, can we get anyone to confirm this isnt a bug with a real VR headset too? Though IIRC I have proper textures when I'm in SimVR mode, which I did somewhat recently for a few videos... whoops for not realising that before!

A VR user isn't going to be running an Intel GMA 4500 Luxen, an occulus would just laugh at it and say no. That aside I do think turning off Virtual VR, and using dx9 is probably the answer here.

Regardless of this, I'm guessing something in the way VO sets video modes is failing to detect cards that have dx10.1, but not dx11 as in the last thread where this bug was present (and I got told off) that install had also opted for dx11 when it really should not have done.

Are you guys checking for Supported Feature Level? Or just seeing if a DX11 surface will work, and if it fails fall back on DX9?

Yeah so I switched to Dx9 and that fixed the issue, while also (not surprisingly) upping my framerates. Thanks for the help.

Are you guys checking for Supported Feature Level? Or just seeing if a DX11 surface will work, and if it fails fall back on DX9?

VO's DX11 requires a report of a full DX 11.0 feature-set to be implemented before it will utilize the driver, and it falls back to DX9 if that's unsupported.

So, either something is wrong in our detection code (possible, but.. surprising? We've done a lot of testing on aged Intel integrated GPUs), or something is wrong in Intel's drivers (possible as well). Either way, not-cool.

We have to detect on feature-level, because we use a number of "real" DX11 features, including BC7 texture compression, which is probably the source of this particular problem (GPU reporting support, but then failing to actually decompress the texture, leaving the ship "white").

DX9 is a much faster driver overall. The DX9 renderer is not as pretty, but probably a net-positive experience overall for an older Intel GPU.

For awhile there we were defaulting all Intel GPUs to DX9, but the Iris Pro stuff is not entirely terrible, so we started doing things more selectively by detected feature-set.