-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does this mod work under Linux? #96
Comments
In theory, it should run under Linux. I have included the shader compilation targets for OpenGL-Core for both OSX and Linux. However, I have no means to test either of those OS's. |
Hello and thanks for your reply. |
Thanks, will take a look at the log; it should tell me if the shaders didn't load for some reason, or if an incorrect API was requested. Currently nothing can be done for testing, but I might have something after reviewing the logs. |
Hello, |
Recoloring is only available by the mods that provide patches/textures for them. I provide some for SSTU, but beyond that, pretty much nobody in the mod scene was interested. SQUAD/Stock doesn't provide any, so there is no information for how to recolor things. For stock recoloring, you can however use TURD -- https://forum.kerbalspaceprogram.com/index.php?/topic/174188-18x-textures-unlimited-recolour-depot/ |
I have a feeling that is somehow related to GPU. I've also got this issue on RX 570 and on laptop gpu (T480s), but I've also got an installation on an older-generation intel GPU which worked (x230, but everything is way too slow). |
Ugh, I've found a solution! Just run the game with Some recap (maybe will help people to find this in the google): if you see black textures under Linux (amdgpu or intel driver) in KSP RO 1.8.1 (specifically, RO engines or RO capsules, for example), just add these flags and it works. |
@derlaft I have similar issues playing on linux but worse is that the debug log spam results in the game crashing some times. Have you tried any other combinations |
Yes, I've tried all the values higher, they don't work. Have not tried any values lower. Can you upload your log? I could not find anything useful in mine. |
Player_partial.log You can see the OpenGL error repeatedly. I did some testing with using only parts that didnt have textures unlimited and the messages go away.
We did a bunch of debugging over in the KSP-RO discord server, which points to an underlying bug in Unity's logging for causing the crash but its induced by multithreaded logging it would seem. So having TU cause OpenGL to spam the log exacerbates the problem. |
@klimburg which GPU are you using btw? I was hoping to also see that in the log |
Ah sorry NVIDIA GeForce GTX 960
|
@klimburg try this workaround instead of launch options, should work on nvidia:
|
Nah that doesn't seem to work textures still look dark and getting the |
Same problem here, KSP 1.9.1 on a Radeon RX 470. The |
Just wanted to chime in that I had the same problem (1.8.1, using an RP-1/RO install as described here https://github.com/KSP-RO/RP-0/wiki/RO-&-RP-1-Installation-for-1.8.1) and that using |
Can confirm, installing MagPie and TU results in logspam (OpenGL errors) and black parts as in @mitko17's screenshot. On top of this -force-glcore42 -force-clamped doesn't work anymore because current scatterer relies on modern opengl features. |
Well, no. Not ready yet to just drop the native client, but I imagine it would work (and also enable TUFX which seems nice to have), and probably open a whole can of other bugs in the process that even fewer people know how to fix. :-/ |
Hello.
This mod was installed as a dependency of KerbalFoundries2 and now all the parts of this mod (landing gears) are just black. Besides it seems to brake another mod (B9 Aerospace Procedural Wings - Fork). The procedural wings are now black as well.
I run KSP 1.8.1 on Linux Mint 19 64 bit
When I run the same under Windows 10 64 bit, all the textures are OK.
Is this mod and all of its dependants supposed to work on Windows only?
KSP.log
The text was updated successfully, but these errors were encountered: