JadeOfMaar Posted January 19 Share Posted January 19 SXT doesn't need a batch file. It needs a restockwhitelist file. Mk2 Expansion has one. Quote Link to comment Share on other sites More sharing options...
Drew Kerman Posted January 19 Share Posted January 19 7 hours ago, JadeOfMaar said: SXT doesn't need a batch file it does, because it's pulling textures and stuff out of the zDeprecated folder in /Squad that ReStock can't (or doesn't) touch Quote Link to comment Share on other sites More sharing options...
Squirrel Slapper Posted January 20 Share Posted January 20 On 1/19/2025 at 6:07 AM, evileye.x said: I have both Restock and SXT working without problems, have you tried to use Windows_CopyTextures.bat located in \GameData\SXT ? Yeah I can see it, how does one "use" it? Do I just need to move it into \GameData\SXT\Patches ? Quote Link to comment Share on other sites More sharing options...
evileye.x Posted January 21 Share Posted January 21 15 hours ago, Squirrel Slapper said: Yeah I can see it, how does one "use" it? Do I just need to move it into \GameData\SXT\Patches ? Just run it once. It will create copies of SQUAD textures, required for SXT to work properly. Quote Link to comment Share on other sites More sharing options...
linuxgurugamer Posted January 21 Author Share Posted January 21 On 1/19/2025 at 7:27 AM, JadeOfMaar said: SXT doesn't need a batch file. It needs a restockwhitelist file. Mk2 Expansion has one. Sadly, the way Squad updated the parts with new models/textures broke several mods by putting the textures into a directory which isn't loaded at all. This requires copying the textures (by hand) from the depreciated directory to a new location and then patching the parts to use the new location. Among them: BetterScienceLabsContinued FlexoDocking Kerbonov KSP_Flexible_Docking NecroBones Fuel Tanks Plus I have patches for all of the above. In all cases, the fix is to copy the missing textures and patch the parts to point to the new locations of the copied textures Quote Link to comment Share on other sites More sharing options...
JadeOfMaar Posted January 21 Share Posted January 21 7 hours ago, linuxgurugamer said: putting the textures into a directory which isn't loaded at all. Ohhh. I vaguely remembered that this was a thing. Sorry about that. Quote Link to comment Share on other sites More sharing options...
linuxgurugamer Posted January 21 Author Share Posted January 21 33 minutes ago, JadeOfMaar said: Ohhh. I vaguely remembered that this was a thing. Sorry about that. Yes, it's a pain. If we were allowed to include their texture files in our mods, I'd be able to eliminate that step. Quote Link to comment Share on other sites More sharing options...
M5000 Posted Thursday at 02:14 AM Share Posted Thursday at 02:14 AM Hi @linuxgurugamer - Thank you for maintaining this and many other quality mods first and foremost. I would like to report what I believe is a few separate issues. I've ordered them by (my opinion) severity. A zip with screenshots labeled in association with their respective issue and log files will be appended at the bottom of this post. These are all reproducible in a stock installation of KSP with only the mod and its hard dependencies installed, assuming that CKAN is trustworthy for cloning and cleaning a stock instance from Steam, which I do believe it is. I've spent all night last night and so far tonight reading through current and old threads and troubleshooting, and I've not had a ton of luck making progress. I hope that my report is formatted in a useful manner so that it might help you and others. This by no means makes the game unplayable, but I believe these are outstanding issues that have yet to be properly reported and thus fixed. If I'm wrong and there is an existing fix I'm not aware of it. 1) Kerbolyov "Tsar" (Soviet N1 Rocket) Fuel Tank Oddity This issue is one of two scenarios, and I am not sure which it is. If you look at the Kerbolyov "Tsar" fuel tanks that would be used to re-create an N1 rocket, you can see that they slowly taper in size as you move up the stack, which is to be expected. However, there is an unexpected tank that is larger than even the first stage when placed in game. It has a massive amount of fuel, probably an appropriate amount for the volume of the tank? In any scenario, this large, massive tank shares the same name and description with the smallest Kerbolyov tank - What I believe to be the "real McCoy" - The "Tsar V" - The problem comes from what this larger tank is supposed to be (and the fact that it is sharing a description with another part) - Is it supposed to be a large massive tank that goes on the bottom of the stack, or is it supposed to be a smaller tank that you'd stack toward the top, and the fuel values are also wrong? I believe it might be the latter, because the attachment nodes appear to be way out of line as well with the actual model of the part. If you place a basic Mk1 command pod, then attach the large tank to it via the node, the command pod is completely engulfed in the part. Plus, the textures don't appear to be scaled such that they look correct at the size it is. So I believe there's a missing title, description, and scaling configuration of some sort to this tank. To reproduce: Spin up a stock instance of the game with SXT continued installed with its dependencies, go to the hangar or VAB, and view the parts in the catalogue or place them in the assembly area. Issue should present itself readily. 2) Missing Textures on RT-3 Gnat, Clamp-O-Tron XL Docking Port, and (maybe: Tycho Magnetic Assembly) I understand this mod to be a stockalike mod. These 3 parts appear to be missing textures. It might just be the first two, as I'm not sure what the Magnetic Assembly is supposed to look like. If it's supposed to look like the 2001 Monolith, then it's functioning as intended... The other two though appear to be quite off. The RT-3 Gnat booster and Clamp-O-Tron XL seem to have some very basic textures/colors that do not appear to be part of the game at all. I checked through the rest of the catalogue in the stock game and didn't see anything else jumping out at me. I noticed it first in my modded cesspool of a main installation. However, in that instance, the parts were simply black. OK - I have a lot of mods installed so I used a clone of a completely stock instance to install just SXT and see if the issue presents itself again. That is when I found the textures still missing, but instead of being completely black they did at least have some color. The Gnat has some white with yellow but not much texture and the Clampotron has a blue-ish hue with some yellow, and red EVA handles...Zip will have screenshots of what I'm talking about. So an issue appears to still be present with these 2 parts, and, again the Tycho, I'm not sure what to think about that one. I am 100% sure I ran the batch file (I went ahead and ran it again just as I typed this to be 101% sure) because I saw it mentioned countless times in various research I did over the past couple days trying to narrow this down. I know the batch file works, because I didn't RTFM at first and saw no texture on the Dontstayputnik sphere immediately...ran it, that got fixed...But these two remained. Thought it might be a ReStock issue - Checked the part config, found the files it refers to, whitelisted all of that, no change. Checked my logs. Nothing was failing to load that made sense. So that's when I spun up a stock instance and installed ONLY SXT and its dependencies, ran the batch file, and was able to get the results you see in my screenshots. Saw something in this thread about some old textures that flat out got removed from the game and you couldn't re-distribute them, I downloaded an old Beta version of KSP from Steam and pulled those files over, no change. No change. Did it again just now to be 101% sure, but this time copying the entire Squad directory and merging it, leaving any existing "current KSP" files but putting anything the Beta had that current didn't into the appropriate directories under Squad. No changes. The black parts in my modded install could be deferred rendering or any other one of the mods I have. I don't expect any focus to be put on to these parts' issues in my modded installation, but I imagine that if they're fixed in this stock instance, they'll be fixed in my modded install, too. If there's nothing to fix, well, then I suppose that's just fine too. To reproduce: Spin up a stock instance of the game with SXT continued installed with its dependencies, go to the hangar or VAB, and view the parts in the catalogue or place them in the assembly area. Issue should present itself readily. Logs, Screenshots: https://files.catbox.moe/z9y8sh.zip System Info: OS - Win 11 24H2; CPU - Ryzen 7 5800XT; RAM - 32GB DDR4 3200; GPU - RTX 3090; Original KSP Distribution Method - Steam; Reproduced Issue KSP Distribution Method - CKAN Instance Clone from stock Steam install Sorry for the long winded post, but I wanted to get everything in I could think of... Thanks in retrospect for the work you've done for this game, and thanks in advance if any fixes come down the pipe. Quote Link to comment Share on other sites More sharing options...
linuxgurugamer Posted Thursday at 03:20 AM Author Share Posted Thursday at 03:20 AM 1 hour ago, M5000 said: I would like to report what I believe is a few separate issues. I've ordered them by (my opinion) severity. A zip with screenshots labeled in association with their respective issue and log files will be appended at the bottom of this post. These are all reproducible in a stock installation of KSP with only the mod and its hard dependencies installed, assuming that CKAN is trustworthy for cloning and cleaning a stock instance from Steam, which I do believe it is. Thanks for the report. I've opened a new issue for this on github and copied everything into it. No promises, but I'll see what I can do. Quote Link to comment Share on other sites More sharing options...
M5000 Posted Thursday at 02:09 PM Share Posted Thursday at 02:09 PM Thanks for taking a look, let me know if you need me to test anything or more information on my end. Quote Link to comment Share on other sites More sharing options...
linuxgurugamer Posted Thursday at 04:11 PM Author Share Posted Thursday at 04:11 PM 2 hours ago, M5000 said: Thanks for taking a look, let me know if you need me to test anything or more information on my end. If you have a github account, you can comment here: https://github.com/linuxgurugamer/SXTContinued/issues/86 That way I will be able to get in touch with you Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.