Crzyrndm

Both appear to be caused by the FAR geometry overrides (that were being used for reasons I can't recall now...). Removing that file appears to fix the issue in my test install (but I don't particularly feel like removing it without knowing what it was required for...)

The same method that works in the editor is supposed to be available in flight

I would be very surprised if FE fixed the search derp since it has nothing to do with it currently and I don't see it as likely to be an easy fix...

I see the issue, looks like you've somehow got multiple icons with the same name (png and dds versions?) which I should probably be checking for but...

No hardcoding involved. They do need to be 32x32 in dimensions, have a unique name (at that size), and either match the resource name or have a set icon .cfg entry, but that should be the only requirements @SpaceFoon I'll take a look in a couple of hours. Merging folders shouldn't be the issue itself since this has only one hardcoded path (the icon for the space centre settings button), but until we know whats actually happening... *shrugs*

v0.11.1 * Updated fuel switching to use defined volumes * Fix for FAR voxelisation issues

Filter Extensions v2.6.0 * Add "exact" check modifier - matches only parts that have every item listed and nothing more * Settings window uses Unity 4.6 UI * Bulkhead profiles updated by Kerbas_ad_astra * Internal cleanup of various items Exact example: CHECK { type = resource value = LiquidFuel, Oxidizer exact = true // Match parts that have ONLY LF and Ox }

@Tokamak I'll have a look at Kerbalism. Most likely the life support and other related categories aren't updated for it @SpaceFoon Need logs and ModuleManager cache. That sounds like something exploded

That really should be blocked in the editor as well. It's only used for flight setup stuff

@01010101lzy I have only a single mention of EditorLogic.SortedShipList, and it's not anywhere near onload so I don't know why this would surface from a merge. If it's neccesary for something, just add a scene check (HighLogic.LoadedSceneIsEditor) so it oesn't run outside the editor

@ferram4 It's being done. Now that I've gone through most of the issues with the B9 version (current version should be fine for voxelisation) it shouldn't be too difficult

Any chance you can actually verify the analysis numbers for AoA in actual flight. It's not wings clipping into the body, but wings clipping into each other that doesn't seem to be accounted for. I trust ferram's flight model more than the analysis tools where clipping is involved. (I would suggest using Pilot assistant or MJ to hold a set speed/altitude)

That's because the check type is an AND (to be used when you want group and operations, eg. A && !(B && !C && !D) ). For an OR, you want something like: FILTER { CHECK { type = custom value = adapters, multicouplers } } FILTER { CHECK { type = title value = Nose Cone,Multi-Point Connector } }

Previous versions on the releases page exist for a reason...

https://github.com/Crzyrndm/B9-PWings-Fork/releases

Melfice is correct. The two links in my signature are separate mods, I just happen to be a current maintainer of both of them

1) My (admittedly very) quick test with two wing parts appears to indicate that ref area isn't accounting for overlapping wings at all. 2) Slight differences are to be expected and I'm not certain without taking more time to test how FAR treats the wing edges in that analysis. A 4x4 square board with no edges does come out at 16.0m2 though

2.5.1.0 in the log file is my fault (forgot to change the number *before* release...) Aero and FuelTank don't work because I did something that is possibly very very stupid and used the ingame category names and they are different from what is in part .cfgs (I'm kicking myself right now...). The current names are: Pods, Engines, Fuel Tanks, Control, Structural, Aerodynamics, Utility, Science, and None. I'll add the .cfg names as alternatives for the next release because that makes sense... Also, for the fuel tank category, it would be simpler to write it like this (part has a resource other than ("NotAResource" or "IntakeAir") and is not (an engine or Command part)) SUBCATEGORY { name = Fuel Tanks icon = stockIcon_fueltank FILTER { CHECK { type = resource value = NotAResource, IntakeAir // I figure you don't really want Intakes being classed as fuel tanks contains = false // we're looking for any resource that *isn't* listed } CHECK { type = moduleName value = ModuleEngines, ModuleCommand // No need to list ModuleEnginesFX invert = true } } }

I've probably done something really silly with the math...

If they do, I'm going to be poking over it at some point. I tried to write the plugin to cover the case of something already using the thrust curve, but never did test that bit...

Check right near the start of the log, there's a full list of all the plugin .dlls that are loaded and the only thing I can think of is that yours hasn't for some reason (one of the reasons mod authors always like full log files, not "relevant snippets") Possible reasons for this: .dll isn't inside GameData, .dll is inside GameData but is also inside a folder named PluginData, duplicate .dll's, ...?

As the github version appears to be functioning well, I'll move it to an official release now Procedural Wings v0.11.0 KSP 1.1.2 compatible Added fuel switching capabilities

Can you please remove trajectories and get a log without that. It's spamming exceptions enough to make it difficult to find anything useful

All of which are just housekeeping warnings and will have no effect on your experience (I've just fixed them ready for next release)

uh, yea I guess I should add that to the list >.> (I was intending to do it after merging the two pwings plugins, but that being on the back burner currently...)