crazyduck

Possible you did not understand me or i asked wrong. I know it work like i can change shader settings and i do not get any bugs with that. Question is more if there are other commits that still set somethign in background to max shaders . and sure i could dig through the code and check that, btu i thougth asking the peopel who added the new forced settings is easier cause this people should know that . Oh and do not assume others should want anything , but as i said, i reverted 2 commits and it seems to work without issues,. But since Thomas said it would be much work to support different shader settings again , i´m not sure if this commits are everything that must be changed to really remove any forced shader settings in background. And the unpaid time investment for little gain , really not sure about the little gain but also if it does not support it why block the settings? Its a simple thing to remove the blocked setting and let the users decide, that would not be big unpaid time investment that would be few minutes to change that and changing the text telling you you cannot change the setting into something like a warnign also does not take that much time.

Hmm why would it be such a problem to allow 2 shader settings and let the planet pack creators decide if they support both shaders or only 1 setting? I think Planet PAck Authors would offer Packs for different Shader Settings if people ask for such Packs as long as Kopernicus again support to change Settings. And i do not think its outside of User control its the User who will decide to change the Setting or not so the User is in Control and yes some People do not read warnigns but a warning popping up the second you try to change shader settings i think most people would read. So reverting the Commit about forcing highest Terrain and Ocean Quality would be enough to revert the changes with forced Shaders or are there other changes in code hidden somehwere in other commits that must be changed too? If reverting this 2 commits and removing the TerrainQualitySetter.cs is enough i only see it works fine for me , if not would be great if you could tell me the other commits that needs to be reverted.

Ok thats something i understand, but was it different in 1.8 before Kopernicus added this forced setting? i mean before had the Planet Autor control over it or what did change in KSP that in 1.8 and before it was not a problem and after 1.8 it become a problem. I don´t try to annoy you i only try to understand what had changed so kopernicus changed this one option. And why would it as example not be a solution to not lock the setting but add a simple warning dialog something like "changing this Value can cause issues with Planet Packs" this would still allow people to reduce the setting and run the game without lags and at same time warn that it can cause issues.

So you mean people could write own configs for the Planet packs to replace the Materials with lower quality variants? But woudl that not also cause the same problem as you said before? The thing i don´t get is, if i install planet pack XYZ modify the config so it use lower quality Materials, why whould that be no problem but setting the Shader to lower qualtiy would be a problem? Or did i miss something? For me that sounded like Quality setting not on Max = Issues wiht Planet Packs modify config for Planet pack to use lower quality materials = no issues. And as i said before i have it running with spectra mod, to boldy go, scatterer and eve and i can play around with the settings as much as i want i can see no bugs.

I think the way with adding 4 new nodes would be the better solution, not everyone who play KSP has a powerful computer to play with max settings so doing it with the current way it would make the game for many people horrible to play or force them to stay with old kopernicus version and old KSP version or stop using planet packs and Kopernicus. Dont get me wrong i like Kopernicus but forcing Max settings on people sounds more like work around a problem and not solve it or would adding this 4 nodes be some sort of months of work to do?

Link for Gitlab https://gitlab.com/crazyduck33/ksp-kopernicustest

sure give me a moment will upload it to git.

Ok for me i now testet it with Tracking Station too and no Problems for me. All Planets work no Texture issues for me . I use the modified Kopernicus, with Spectra and EVE (from your git) and to boldly go for universe creation. Sure will do, will test it a little bit more today and if i do not find any bugs will do the PR.

I teleportet with Ship to each planet orbit and Surface and did not see any issues, i set quality to medium. Did see planets from far and near from orbit ok Tracking Station i did not test but will do now.

So i recompiled Kopernicus and removed forcing Ultra Settings , i do not see anything different , no bugs as far as i can tell. So can anyone explain me why forcing Ultra Settings is needed? Not a Problem on my computer but i did read at R-T-B´s Git from a user having issues with Ultra Settings and a response that its easier with only ultra settings and somethign about Texture Pack authors. So to be honest, i think its a bad idea to force something like Quality Settings to Users and its even more a bad idea i think if its such a Mod like Kopernicus . So @R-T-B would be really great if you could explain me why you think forcing ultra settings is needed m cause as i said removing it does ot cause any bugs for me.