Since the last update, I have noticed large black squares in space in some sectors. I have tested and this does not show up on device with Android, just on PC.
I have heard several others mention the same thing on 100 and Guild chats.

I'd wager its the planets or stars of those systems, right? At least on android, I can ~sometimes~ reproduce this effect when the app is minimized during load, for the start screen anyways. Dunno if thats whats going on here, though.

Mind posting up your PC's specs?

I am experiencing the same problem, I believe it started up with Update 1.8.484.

As to people referencing it:
[100] <ThisisiT> wtf....why i see big black square in every sector?

What hardware, OS version, driver version, please?

Then, which sector(s)? Thanks.

If you change Background settings in Graphics Options, does that affect the problem? As in changing from High to Medium to Low.

Also, if you can post a screenshot of the issue, that will help. As well as the info Incarnate asked for.

I fly with Windows 10. I took a trip around some in UIT this morning plotting around the roid sectors. I found the Black Squares in Nyrius G-2, k-7, K-14, F-6, Dau O-6, L-10, E-15, Azek I-12, C-14, D-11, J-1, Arta M-14, J-12. I did not visit every station. I did not find the Black Squares in any empty sector I went thru or in some WH and Station sectors I visited.
I hope this helps. I have given you several places to start looking. I did not find any on my devices using the Android version of VO.

Can you send us a screenshot, please?
And run the Bug Reporter so it can send us your logs and config files.

We have managed to reproduce this issue. It seems to be specific to low-end Intel integrated graphics controllers. It happens on our laptop with an Intel HD Graphics 4000, but not on a higher-end Intel Iris Pro. We've also seen reports of problems from people who have Intel HD 510 devices.

We still have no idea what causes the problem (chances are, some kind of Intel driver bug), but.. we're continuing to investigate.

We found the issue and released a client patch. Please let us know if you still have the problem.