Me1_base

download the source, change sm target from 5.0 to 3.0 and build your own asset bundle may solve the problem.

No, b9pw will calculate the aerodynamic values such as span, swept, chord from geometry then them pass to FAR. There is no voxel approach.

Release Version bump · tetraflon/B9-PWings-Modified (github.com) would you help me to test it？

IF you installed FAR, normally there will be no blue arrows on the CoL mark if there is no stock lifting parts. Have you tried to fly the plane and test if there are any lift?

Plugins can be used across different versions of KSP given that the version of game engine doesn't change and there is no modification on the part the plugin is working on.

Yo buddy, still alive?

which version of b9pw and ksp are you using, and what is your operation system?

It is for texture unlimited but it is obsoleted since TURD released a patch for it.

Good to know that problem resolved

Hello? Still having the issue?

maybe a few screenshots to illustrate the problem?

code editing is needed but why would you want such small wings?

last time i checked for the situation for which width and thickness to be 0 will create some rendering bugs, thus I add a minimum cap to it.

You asked in the right place, down below

updated, have it a check https://github.com/tetraflon/B9-PWings-Modified/releases/tag/0.42

Yes if you mean "relative lifting area" for "lift" Will add actuator speed in next update. B9Pwings performs as good as stock delta wings in terms of lifting area to weight ratio.

I haven't tested it myself. 2 mass slider.. must be something related to FAR @PART[B9_Aero_Wing_Procedural_TypeA]:NEEDS[ferramGraph] { !MODULE[ModuleLiftingSurface] {} MODULE { name = FARWingAerodynamicModel MAC = 4 MidChordSweep = 0 b_2 = 4 TaperRatio = 1 } } You may need to change B9_Aero_Wing_Procedural_Type* to your new part names.

Oh, too complicated, never ever touch the mesh part.

Good method, never thought about that. You can actually do it by yourself, by copying the config and modify the part name a little bit. I would include a patch in the new release when i have time. There is no API for procedural wings to know whether or not Texture Unlimited chose the legacy texture. The two texture will stick together and create glitch if both activated at the same time. Thus the author of TURD chose to include a default colour B9PW for switching without the colouring mask. I thought TU can serve as a replacement of the default colouring thus I disabled the default palette of B9PW if TU config is detected. I believe you should redirect the request to TURD thread, which part for TU to recolour is decided by TURD not B9, I don't know much about texturing in TU.

Yes https://github.com/tetraflon/B9-PWings-Modified/releases/tag/0.41b Never encountered that problem, a few screenshot of this issue would be appreciated. Note that the coloring of TU and B9PW cannot coexist, thus the coloring of B9PW is automatically disabled if a TU config is detected.

YES

https://github.com/tetraflon/B9-PWings-Modified/releases/tag/0.41a have it a try and report any bug you encountered

I could do that if that's what you want

Hello you should download the releases insteat of the whole git.

Hello where do you install the mod from? Could you plz provide me the link of download for me to test?