Stone Blue

@Avera9eJoe I see from the date, that v1.2.3 was most likely released for and compatable with 1.7.+, then since it also works in 1.8.1 (per the SD listing), I was just wondering if you knew for sure how far back in KSP versions that it may be backward compatable with? And I'm also assuming that 1.2.4 is only 1.8.1 compatable due to Kopernicus changes in 1.8.1-1? (ie shaders & stuff)?

Yes, they did. I remember using modded parts with similar function, as well... not just the stock parts... Pretty sure they worked in 1.3.1, as that was the last version I actually did some heavy playing in... I cant remmember when the graphs quit working after that, tho... I want to say 1.4.5 to 1.6.1... vOv... i know they were broke when I tried using them in 1.7.0+...

Interesting... I'm still seeing this error with the link... ?? EDIT: <snipped> my post... issue fixed

Yes... Definately looks interesting....

Just pulling out the shotgun here, as I dont know much at all about how TU works or PBR... Are you replacing with your *own* textures? Are they in .dds format? Could the texture(s) youre trying to use have been forgotten to be flipped vertically in a conversion to .dds at some point? ... vOv

No code necessary.... I just started playing with the buttons/entries in the right hand section of the UI IIRC, "Add", lets you make additional entries. Also, since the entry types in the KSP.log seem to have been changed from one of the recent Unity updates, I had to delete the [ERR & [WRN entries (they dont work anymoar)... I created [ERROR, [WARNING, and then added "exception" (no quotes). For NullRefs, I created one for "nullref" (no quotes)... but on this one, I guess because it shows up in the middle of "System.NullReferenceException", it wont get picked up. So you have to switch the "Search type" setting on this from "normal" to "regex". So far, I am liking this. There are mods I use that throw TONS of warnings that can be ignored, such as incorrect texture resolution, or KSPAVC throwing a bunch of addon binder errors, and tons from Filter Extensions... I just wish there was a way the Analyse Plugin could also *parse* entries... vOv I also kinda wish KSPDev LogConsole could parse by user custom text entries, not just by method... vOv I also would LOVE to parse out the DATE from the log entries, to just using the time. Unfortunately, I havent found a way to do that using KSPDev LogConsole. If someone knows how/if its possible, PLEASE tell me. (the date/time setting in the settings.cfg, is for the date/time in the *filename* for the saved output logs ) I *did* remove the year and seconds from that... I dont know about anyone else, but I dont keep logs around long enuff I need to know what *year* they are from, nor is my computer powerful enuff to start instances of, or run KSP within seconds of itself... ) But I *am* glad the whole setting is customizable, in case my use-case ever changes. Yeah, I can do that, but be aware, I customized quite a few settings. Mainly, I "turned off" MM patch loader logs, as well as the KSPAVC and MiniAVC log flushers. I did this because they all add SOOO much content to the KSP.log, which makes it moar difficult to go thru, and I also know they can be set to create their *own* seperate logs, so i can use those if i need to. It may be redundant, I dont remember, since its been so long, but I also use the MM dont copy logs CLI on my KSP shortcut. **NOTE: with this one, you need to remember when providing logs to peopple for support requests, to either turn it off and start KSP to get a fresh log *WITH* all the MM loader info; or provide the seperate MM log *along with* your KSP.log ... But its prolly best to turn off the CLI commmand, and just do a fresh restart. (I'm guilty myself of forgetting to do this... :face_palm:) Heres the settings.cfg:

@IgorZ Just wanted to say, I LOVE KSPDev LogConsole... Dont know what I would do without it, since I am constantly going thru my logs. It saves me SOOOOO much time. Anyway, I specifically wanted to also say that I commend you on the EXCELLENT documentation you have for ALL of your KSP DevUtilities... (and your mods, too ).

Well, I'm going to give this a try. As a possible alternative, I'll post what I've been doing up to reading this thread. I've been using IgorZ's (of KAS/KIS fame) mod, KSPDev LogConsole , along with opening the logs it generates, with Notepad, not NP++. (Only because Notepad gives me a less cluttered UI, and moar screenspace for the loooong lines of text in the logs (I also turn off wordwrap, as its easier on the eyes, and lines up the timestamps and entry types (ie INFO, ERROR, WARNING, EXCEPTION), nicely.)) So, I have LogConsole set to create a full copy of the KSP.log, and a parsed one that includes ONLY the ERR/WRN/EXC lines. These are two seperate .txt files. I will open them both in seperate windows. I first go thru the parsed log, and when I find an ERR/WRN/EXC I want to investigate, i note the timestamp, switch to the window with the full log, and can quickly locate ALL the relevant lines quite quickly. I dont ever use the output_log/Player.log myself, as I dont understand much of it, and only supply it along with a KSP.log if I'm asking for support on the forums. Note that KSPDev LogConsole, *also* has a nice in-game UI, so you can see whats going on right in-game. I havent bothered to use it tho

no, thats not normal... But I was recently modding on some custom fairings for PF, and had that same exact issue... even had that same pink square. Cant remember exactly what it was, or how I fixed it... I was changing lots of stuff, moving/deleting files, & other *stuff* was going on. Pretty sure tho, it was just a matter of deleting and reinstalling PF... There are several forks out there, none seemingly officially updated for 1.8.1. IIRC, I think i had your issue when I was using Kerbas-ad-astra's fork.. but dont hold me to that. Try this one... its the one I have working in my 1.8.1 dev install: https://github.com/KSP-RO/ProceduralFairings/releases EDIT: Friznit reminded me... yeah, I'm actually using the dev version from the 1.8 branch... my bad

like, how so? One thing I just did, was add an entry for "NullRef"... you can add/edit/delete, then save any entries Thanx for digging this thread up... I'm going to try using this in conjunction with KSPDev Logconsole , which I have been using regular Notepad to read the log files

@zer0Kerbal that would be IgorZ's https://github.com/ihsoft/KSPDev_LogConsole/wiki

idk... try this mebbe? series: ["SensorType.TEMP"], https://kerbalspaceprogram.com/api/class_module_enviro_sensor.html#a409d41fa32ca3b4fdb65244e0df0878b

@RowBear Yup... thats the same behaviour I've been seeing with *only* Telemachus installed... was hoping against hope that mebbe what you did may have somehow fixed it Thanx for verifying

Have you tried getting any instrument readings from any of the stock science parts? namely any of the small sensors?

@damonvv if this is the case, might be worth it to add JNSQ to the list of "NOT yet supported mods" in the OP ... or at least noting it wont work with JNSQ, if you dont plan to support JNSQ... Right now, JNSQ seems to be the hot planet pack, so I imagine a *lot* of people may be looking to try this with it... vOv

@RealGecko Before the thread gets locked, just wanted to THANK YOU for all the great mods you've provided, and for actively & graciously making sure they will continue in good hands. Take Care!

nvm... unecessary reply. sorry

It seems you can change the display order of subtypes, just by changing the order that they are listed in the cfg. It looks like they get displayed from first one listed to last one listed... vOv And I took it to mean, from what I read in the wiki, that the defaultSubtypePriority specifies not just default, but the order based on where the subtype ends up in the techtree/upgrades? vOv

Unless someone gets permission or gets @JoePatrick1 to post an update to the license.. looks like they were on just in late September? vOv

1. You are correct on the three different files. As to whether to install original OPT "Main", and or "Legacy" (they can be used seperately, w/o each other), is mostly a personal choice on which one, or both, that you want. Regarding Reconfig, Jade explains here: 2. Order *shouldnt* matter... all three have their own seperate root folders. 3. Sort of... just unzip contents, however you do it, to make sure the mod root folders are in your /GameData/ folder. ***NOTE however, that original OPT "Main" bundles old versions of Firespitter and ModuleManager. Those can be deleted (unless you are using the Main on KSP 1.3.1 ); ModuleManager needs to be replaced with the latest version for whatever version of KSP you are on. Firespitter does NOT need to be replaced at all, (again, unless you are on KSP 1.3.1 or earlier) 4. Sounds like you have a handle on the other dependencies. ***NOTE however, if you want the IVAs to work, you'll also need these: IVA required Mod: (no longer bundled) RasterPropMonitor, by Mihara, MOARdV ASET Prop pack, by alexustas ASET Avionics, by alexustas I think the last update of Reconfig, Jade fixed something with the IVAs, IIRC... Oh, if you are on KSP 1.8.1, you'll want *this* adopted version of RPM, not the one linked above:

or Supposedly, coming release of KSP 1.9.0 will have some sort of "cheat-craft-into-orbit" function, similar to HyperEdit... No idea if it will only work for placing crafts *in orbit*... or if it might work for things on plannertary surface(s), too... vOv

Thats only because the .version file hasnt been updated. KSR still seems to work in 1.8.1... You should be able to ignore any warnings for compat, as long as you're using the latest KSR version in 1.8.1 vOv need a heck of a lot moar detail than this, for this issue... WHAT textures?... for WHAT mod/stock? vOv If you're talikng about seeing tons of texture errors in the logs from either KK or KSR, *and* everything looks ok in-game, then all those errors can be ignored. If youre missing seeing textures *in-game*, you need to provide a heck of a lot moar detail And Welcome to the forums :waves: A good place to start for reporting issues/asking for help is in this thread. Its a good read

I know this isnt *specifically* related to your original question, but while shopping around for different editors, if anyone finds that it comes down to not much difference between NotePad++ and others, and if you also do a lot of config/MM patchi editing/creating as well as kOS scripting, there's also this superb KSP Config language for NPP which @JadeOfMaar maintains. https://github.com/JadeOfMaar/NPP_KSPlang Just thought I'd throw that out as a variable, towards going with NPP, if for no other reason vOv

I was hoping, but pretty much figured, yeah, you two might start cooking something up together.

@taniwha , or anyone thats had luck with my issue... Frist, sorry if this has been brought up before. I *did* read back about a half-dozen pages, and couldnt find anything. Anyway, I work a lot with models from old mods. And I have *never* been able to get simple emissive animations to export correctly, either on the 2.79 *or*, currently the 2.8 build. I dont know if there's something I'm missing, or if its something with the Importer/Exporter... ?? vOv EDIT: So, I just figured out the last piece (among others I wont go into), on why my emissive animations werent working in KSP after export. Yup... something completely dumb on my part... At least using 2.81 (which I am still not really very well aquainted with), for some reason, I found an emissive color setting that was somehow changed, and overriding an emissive color setting, elsewhere that I was messing with. Sorry for the unecessary tag Taniwha...