Opaque Purple (or Pink) Overlays

[reteo]

When I look at the "Roof Overlay" or when I use the ground penetrating mineral scanner, I get overlays for the appropriate areas, but they are completely covered in a solid purple.  This can be frustrating when attempting to place down a deep drill (since the drill and its range indicator are both covered up).  Is this normal?  If not, any idea what might cause it?  I'm playing the Linux version of the game on Steam.

[BlackSmokeDMax]

When I look at the "Roof Overlay" or when I use the ground penetrating mineral scanner, I get overlays for the appropriate areas, but they are completely covered in a solid purple.  This can be frustrating when attempting to place down a deep drill.  Is this normal?  If not, any idea what might cause it?  I'm playing the Linux version of the game on Steam.

I'm no expert on this, but my first guess would be switch to a different set of drivers. Browse around the forums a bit and you'll find a lot of Linus graphical issues seem to be fixed with this method.

[Calahan]

As BlackSmokeDMax says (thanks for the assist!), several Linux users have reported graphical issues with B18, which they all managed to resolve by updating/changing their GPU drivers. So please try that and report back with the results.

None of them reported having the particular issue you are having, but I suspect it's the same core issue. Which, at an educated guess, appears to be the updated version of Unity that B18 uses is causing some compatibility problems for Linux users with older/certain GPU drivers (but I'm afraid I've never used Linux, and have little to no knowledge on how to troubleshoot Linux based tech issues, apart from the obvious stuff that's universal across all O/S's. Such as checking for updates to various stuff)

[reteo]

Actually, I had the same problem with A17 as well; I just decided to speak up now since B18 did not seem to fix the issue.  As for driver, I'm using nVidia's binary driver, version 384.90, on a GTX750.  I'll update the driver and see what happens.

Just to verify, this is not intended?  For reference, what is the mining overlay and the roof overlay (from the bottom-right corner) supposed to look like?  Interestingly enough, all the overlays from the Architect menu (particularly the zones and construction outlines) seem to be working just fine, it's just the non-architect overlays (and deep mining overlay) that seem to be doing the purple thing.

[reteo]

Unfortunately, when I finished installing the latest nVidia drivers (387.22), the issue continued to persist.  Anything else I can try?

[Calahan]

Unfortunately as I mentioned above I have no knowledge or experience with Linux to be able to offer much help with Linux based tech issues I'm afraid (that aren't fixed with the basic stuff). I'll ask the other moderators if any of them can help, but I don't think there are any Linux uses amongst the moderating team either. If you still can't resolve this I'll either approach one of the devs to take a look, and/or just put up a bat-signal in general discussion to ask if there are any Linux users in the community who can kindly help with this.

To that end it will likely help if you can please post your log file (as an attachment ideally). Details on where to find your log file here: https://ludeon.com/forums/index.php?topic=513.0

I've also attached a screenshot of what the roofing overlay should look like. Although I'm not sure what you mean by the mining overlay. There is no mining overlay that I'm aware of. The seven toggle-able options in the bottom right-hand corner are:

1 - Categorized mode for resources
2 - Auto expand Home Zone
3 - Visibility of roofs
4 - Colonist bar
5 - Environment display
6 - Visibility of zones
7 - Learning helper

So no mining overlay. And nothing even close to it. Are you sure this mining overlay isn't something provided by a mod? And if so have you checked that this mod isn't causing the problems to begin with?

Edit - Ah, just realised you might be referring to the Ground-penetrating Scanner. Which isn't an overlay in the bottom-right hand corner but does appear when you build one and select it. Attached that screenshot in the next post.

[attachment deleted by admin: too old]

[reteo]

The mining overlay is part of the vanilla game.  It's not enabled by the buttons at the bottom right, but by the "Ground Penetrating Scanner" when you click on the scanner, or attempt to place deep drills, while the scanner is powered.

[Calahan]

The mining overlay is part of the vanilla game.  It's not enabled by the buttons at the bottom right, but by the "Ground Penetrating Scanner" when you click on the scanner, or attempt to place deep drills, while the scanner is powered.

You beat my edit. GPS screenshot attached.

And both of these overlays for you just display a purple screen yes? (a screenshot might be useful as a certain pink/purple colour is the colour Unity defaults to when something goes wrong with what it wants to display).

[attachment deleted by admin: too old]

[reteo]

Hmm... so the only time the opaque purple overlay happens is when showing that specific shade of green as an overlay, since other shades of green (growing zones) work correctly.

It could also be the alpha level instead of the color.  I'll have to check the logs, now that I know there are some...

[reteo]

Here's the log I think might be relevant to the problem; I'm assuming the "default shader" is purple and opaque:

RimWorld 0.18.1722 rev1210

(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

-------- Shader compilation failed
#version 150
#extension GL_ARB_explicit_attrib_location : require
#extension GL_ARB_shader_bit_encoding : enable
uniform    vec4 hlslcc_mtx4x4unity_ObjectToWorld[4];
uniform    vec4 hlslcc_mtx4x4unity_MatrixVP[4];
uniform    vec4 __ST;
in  vec3 in_POSITION0;
in  vec4 in_COLOR0;
in  vec3 in_TEXCOORD0;
out vec4 vs_COLOR0;
out vec2 vs_TEXCOORD0;
vec4 u_xlat0;
vec4 u_xlat1;
void main()
{
    vs_COLOR0 = in_COLOR0;
    vs_COLOR0 = clamp(vs_COLOR0, 0.0, 1.0);
    vs_TEXCOORD0.xy = in_TEXCOORD0.xy * __ST.xy + __ST.zw;
    u_xlat0 = in_POSITION0.yyyy * hlslcc_mtx4x4unity_ObjectToWorld[1];
    u_xlat0 = hlslcc_mtx4x4unity_ObjectToWorld[0] * in_POSITION0.xxxx + u_xlat0;
    u_xlat0 = hlslcc_mtx4x4unity_ObjectToWorld[2] * in_POSITION0.zzzz + u_xlat0;
    u_xlat0 = u_xlat0 + hlslcc_mtx4x4unity_ObjectToWorld[3];
    u_xlat1 = u_xlat0.yyyy * hlslcc_mtx4x4unity_MatrixVP[1];
    u_xlat1 = hlslcc_mtx4x4unity_MatrixVP[0] * u_xlat0.xxxx + u_xlat1;
    u_xlat1 = hlslcc_mtx4x4unity_MatrixVP[2] * u_xlat0.zzzz + u_xlat1;
    gl_Position = hlslcc_mtx4x4unity_MatrixVP[3] * u_xlat0.wwww + u_xlat1;
    return;
}
-------- failed compiling:
vertex shader
0(7) : error C7528: OpenGL reserves names containing '__'

Note: Creation of internal variant of shader 'Custom/Vertex Color' failed.
WARNING: Shader Unsupported: 'Custom/Vertex Color' - Pass '' has no vertex shader
ERROR: Shader Shader is not supported on this GPU (none of subshaders/fallbacks are suitable)WARNING: Shader Unsupported: 'Custom/Vertex Color' - Setting to default shader.

[Calahan]

Yep. It looks likely that the error warning at the end of the log is the cause of the issue. But how it's resolved might need some Linux knowledge. Although just Googling the error text might lead somewhere useful.

[reteo]

I dunno... the problem looks to be less Linux-based, and more OpenGL based... note the message: "OpenGL reserves names containing '__'"  And then note the presence of "__ST.xy" and __ST.zw" in the code.  Or maybe it's just the implementation of OpenGL, and maybe Linux is just less forgiving than the Windows or Mac implementations...  it's times like this that I wish I was more than just a "hello world"-level coder.

And that's not the full log; most of the log is simply stuff about loading mods and resizing the window.  I've attached the full log.

[attachment deleted by admin: too old]

[reteo]

UPDATE:

I found the problem wasn't in the vanilla game at all, but in a mod, specifically, Fluffy's "Area Unlocker."  I'll get to reporting on the "Mod Bugs" forum.

***

UPDATE 2:

Nope.  All mods disabled, started a fresh game, and the issue persists.  Problem is definitely vanilla.  Something happened earlier that caused the issue to go away, but I'm not sure what it was.  I'll do some more digging...

[neodc]

I have exactly the same problem with the same error in the log.

I have an GTX 1070 with the driver 384.90 (the last one available to me) on Ubuntu 16.04.

[Corvias]

I have this issue as well.  Linux Mint 18.3, Nvidia GTX 660Ti (yes, I know its an old card) running the proprietary driver series 387.xx (not on that machine atm, so I can't look up the minor version number). Was previously on 384 which did the same thing. I was on 390 for a bit, but rolled back for other reasons. I think it did it on that version as well. Verified steam cache, turned off all mods, etc.