Jump to content

[1.3.1 <= KSP <= 1.12.5] KAX - Kerbal Aircraft Expansion KAX — Under Lisias' Management — v2.8.1.1 [2024-0704]


Lisias

Recommended Posts

I am having a issue with the propellers turning black when fully spooled.

Modlist:

Spoiler

KSP: 1.12.5 (Win64) - Unity: 2019.4.18f1 - OS: Windows 10  (10.0.0) 64bit
ClickThroughBlocker - 2.1.10.21
Harmony - 2.2.1
Toolbar - 1.8.1.1
ToolbarControl - 0.1.9.11
AIES_Patches - 0.0.1.3
ASET Consolidated Agency - 2.0.2
ASET Consolidated Props Pack - 2.0.7
Astronomer's Visual Pack - 4.1.3
B9 Aerospace Procedural Wings - 0.45.1
BetterTimeWarpContinued - 2.3.13
Chatterer - 0.9.99.2788
Contract Configurator - 2.9.2
DE_IVAExtension - 1.2
Distant Object Enhancement (DOE) /L - 2.1.1.16
Environmental Visual Enhancements - Redux - 1.11.7.2
Firespitter - 7.17
ForScience - 1.6
FreeIva - 0.2.18.4
RasterPropMonitor - 0.31.13.4
KAX - Kerbal Aircraft Expansion /L - 2.8.1
Kerbal Engineer Redux - 1.1.9
Kopernicus - 1.12.1.206
AdvancedFlyByWire - 1.8.4.1
KSP-AVC Plugin - 1.4.1.9
KSPCommunityFixes - 1.35.2
ModularFlightIntegrator - 1.2.10
Docking Port Alignment Indicator - 6.10
PlanetShine - 0.2.6.6
Procedural Parts - 2.5.9
ReStock - 1.4.5
ReStockPlus - 1.4.5
Shabby - 0.3
ButtonManager - 1.0.1.1
SpaceTuxLibrary - 0.0.8.6
VesselModuleSave - 1.0.1.2
Alternate Resource Panel - 2.11
TexturesUnlimitedFX - 1.0.7.1
VesselViewerContinued - 0.8.9
Waterfall - 0.9
WaterfallRestock - 0.2.3
Waypoint Manager - 2.8.4.2
[x] Science! - 6.0.2

 

Link to comment
Share on other sites

Posted (edited)
2 hours ago, Nophallus said:

I am having a issue with the propellers turning black when fully spooled.

Modlist:

<....>

Well, if KAX works fine wihout a 3rd party mod installed, and then works bad with that 3rd party, usually the problem is that 3rd party mod. :)

But I can try a quick check, it's probably someone mangling with the propellers textures.

Can you send me your KSP.log, the MMPatch.log and the ModuleManager.ConfigCache using DropBox or similar? With a bit of luck I can detect who is doing it without having to install everything and trying myself, what would demand some more time than just checking these logs looking for the KAX textures being mangled.

Cheers!

--- -- - POST EDIT - -- ---

Add a screenshot with the problem too, just be absolutely sure about what I'm going to diagnose!

Edited by Lisias
POST EDIT
Link to comment
Share on other sites

Welp, it seems to have fixed itself after I installed another mod (OPT).

I had restarted the game few time and they were still turning into black discs, then I installed that other parts mod and now they look fine.

 

Here is a screenshot of what it looked like:

Spoiler

 

ngvM8LR.png?1

 

Logs:

 

Link to comment
Share on other sites

Posted (edited)

<please ignore. hit Save by accident>

Edited by Lisias
MOVE ON! Nothing to see here!
Link to comment
Share on other sites

Posted (edited)
On 7/3/2024 at 2:37 AM, Nophallus said:

Welp, it seems to have fixed itself after I installed another mod (OPT).

 Thanks for the feedback. I don't use anything from OPT, and I really doubt OPT would use anything from KAX - so apparently OPT "fixed" the problem by collateral effect. Or perhaps something else that you had installed together OPT, but since you were intending to install OPT, you associated the fix to OPT.

In a way or another, I'm giving this a peek. Thanks for the report.

=== == = POST EDIT = == ===

Opened a ticket: https://github.com/net-lisias-ksp/KAX/issues/18

Didn't found anything on the latest release that triggered the problem that bit you (DXT3 textures). I found a mishap on the package, but it wasn't the source of the problem for sure.

--- -- - POST POST EDIT - -- ---

@Nophallus, it's a bug on KSPCF.

By some reason, KSPCF is thinking it's a good idea to overwrite KAX's DDS's with their own regenerated versions (from the PNG file). But they are doing it using DXT3 by some reason beyound me.

Why installing  OPT induced KSPCF to fix the problem it created it's beyound me. :)

In a way or another, this is a bug on KSPCF, and it's beyound me to fix it. I don't think it's a good idea to overwrite 3rd parties assets as they are doing. I really think they shouldn't be doing it.

And why using DXT3 at first place? KSP doesn't like it...

=== == = POST POST POST EDIT = == ===

I WAS WRONG!!! ("surprisingly"... :P)

The DXT3 textures are on my shoulders. KSP was silently ignoring them, loading the PNGs files instead. KSPCF change the loading process by ignoring PNGs files when a DDS file is present, unmasking the problem.

So, yeah, I shoot the messenger by accident.

Why OPT fixed the problem is still a mystery - but, anyway, this is something I need to fix.

Ping @Nophallus

Edited by Lisias
POST POST EDIT
Link to comment
Share on other sites

Posted (edited)

KAX 2.8.1.1 is on the wild!

Changes:

  • Fixes a pretty stupid mistake I let pass trough related to duplicated textures in different formats.
  • Closes issues:
    • #18 There’re DXT3 textures on the distribution (errata: on the fillesystem - errata’s errata: is really on the distribution), but KSP likes DXT1 and DXT5 only

Thanks to @Nophallus for the report that leaded to this fix!

 

=== update ===

 

SpaceDock was updated (I forgot to do it on the WeekEnd). I will work on a CurseForge release ASAP.

 

=== update² ===

 

Now also on CurseForge!

Edited by Lisias
All your distribution channels are belog to us!
Link to comment
Share on other sites

This thread is quite old. Please consider starting a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...