stali79

From what i can see there is 1 part in that list that was fully removed and that is the adapter plate, you are the first person i have encountered that ever used them. As for the others i am unsure and will take a look at the archived versions. Beyond that there is nothing i can do without your ksp log.

Cheers man will take a look when i get home.

Not on hand no. Spacedock MAY archive older versions.

I am going to have to check. I may need to rerelease. If parts have the OPT_ preceeding them then something may have gone screwy on my end. I am out all day but will check when i get home. EDIT: making myself late for class today to stay and try to sort this out. Just checked the part file that you used as an example, MM doesn't patch according to file name, it patches according to game name. So while the FILE may be named OPT_c_6m_cargoTail, the actual name that MM is searching for is c_6m_cargoTail. if you notice these lines in the cfg, these relate to the file names online MODEL { model = OPT/Parts/Avatar/OPT_c_6m_cargoTail } But that isn't the name of the part, the parts name is determined by the following line, and it is the name that MM searches for. name = c_6m_cargoTail Download UltraSearch and do a search for the files I said you need to delete. If they aren't appearing in your GameData folder then there is something not going right. Check the following 2 screenshots to see what I am referring to for the KSP.log and those MM files to delete.

Hmmm i cant open that one.

Ksp.log lives in the game's root folder. The output log is great for debugging crashes, but not what happens when the game is loading up. The other files you need to delete will be sitting just below ModuleManager.dll in the GameData folder. If not there then you will need to do a manual search for them in your ksp install.

You sir are awesome for giving me lots of details. Will respond/investigate as best I can (this first bit is BEFORE reading your logs) 1) good lad, I wish more people would do this. 2) something everyone has been wanting to do. 3) yup been using this version in my install for a while. 4) ALL parts were tested working with fuel, this is where checking your logs will come in handy. The fuel configs are in the MM_Patches folder. There is a patch for default resources (no FS IFS or MFT or RF) this should work if none of the others do. That being said, there IS patches for if you use IFS, FS, MFT and RF. 5) Thanks for the info on your debugging 6) Should be. As for renaming is concerned, TECHNICALLY no parts were renamed on the back end, but some parts WERE removed because the alternate parts either looked/performed better or was flat out duplicates. I removed the landing gear from the release so people don't need to worry about them at this stage BUT if someone has an idea how to make them work let me know and I will give you the Github link. The parts you mentioned as having fuel in them were the ones that @K.Yeon initially did for the Stail class parts and they use FSFuelSwitch and FSTextureSwitch commands hence why I didn't touch them. Your suggestions: 1) Will check those tomorrow, one of them at the very least shouldn't have mono as they were designed to have tanks manually attached inside them (the one with 2 sets of doors) 2) That is certainly something to consider, will add this to the suggested features file. NOW am taking a look at the logs. I can't see any issues with your Output log, can you post your KSP.Log please. Output_log.txt is the KSP crash log, the KSP.Log is your initialisations etc, that shows loading errors. EDIT: do me a favour, delete the following files in your gamedata folder. ModuleManager.ConfigCache, ModuleManager.ConfigSHA, ModuleManager.Physics, ModuleManager.TechTree Deleting these will clear ALL MM cached settings and will redo them on your next restart of KSP. EDIT2: What you described to me was something going funky with ModuleManager, as it didn't seem to be applying ANY of the OPT patches, can't confirm though until I see your KSP.Log

Did you copy the new version over your old one to begin with?

@Starwaster can you take a look at the J-92 engine please, the visual FX does appear to be moving forwards instead of in direction of thrust

The craft files you would have been using would have been from BEFORE KSP went to UNITY 5. Back in the day when ALL landing gear worked. EDIT: the ones included in this release are all ones I made myself.

Really odd as i never renamed those. The avatar cargo bay and bicoupler were completely removed. The cargo bay had no fuel capacity and a different textuse and the bicoupler was exactly the same as the c version hence why both were removed. For those unable to use the included ships, install the Mark IV mod I forgot I had the rcs pods from it on the ships.

I opted to NOT use DDS textures due to file sizes. you shouldn't have had to have done that, no parts were renamed on the back end... ok found it. gonna test now.

What parts is KSP listing as missing? Just checked them all on my end, they all seem to have unique names in the Master.

Which part specifically? One will be for the Stail and one for the Juno TECHNICALLY none of the parts were renamed per se, their titles were changed but not their part names. As for the the textures, it COULD have been a result of me halving their resolution. they were 4096x4096 but I dropped them to 2048x2048 in an effort to shave file size. I have never used tweakscale on any of the parts in the past so I have no idea.

The J-81 is nerfed in comparison to what it used to be. It used to hit 10k thrust. It's as efficient as the J-60. At this stage 'cost' is irrelevant.

OPT 1.8.5 is officially released on Spacedock. You MUST delete your existing OPT folder before installing version 1.8.5. Support will only be given for KSP 1.1.3 and ONLY with a detailed support request and accompanying log if required. 1.8.5 Renamed all fuselage profiles Added J-81 Hybrid Turbojet Nacelle Added new model for JSAS module Cleaned up Firespitter MM Patch Cleaned up Connected Living Space MM Patch Created Default Resource MM Patch Created Interstellar Fuel Switch MM Patch Created Real Fuels Patch Created Modular Fuel Tanks MM Patch. Moved common textures to dedicated folder Set texture referencing for affected models Added the people who helped with this project as easter eggs Added Custom KTAV cockpit Removed OLD K cargo bay & bicoupler Humpback cockpit model optimized Added 'tags =' to part configs for easier searching of parts Updated old 'mesh =' to 'model =' Changed Pylon A and Pylon B to Wing Root A and Wing Root B Experimented with inverted textures (looked kinda cool) But put on hold. Added side attach nodes to Juno and Kraken tanks/bays Added Hyomoto's Antenna blade and updated its texture Reorganised folder/file structure. Some models optimized. Adjusted cockpit masses Removed Chimera cockpit Consolidated remaining Chimera parts into Avatar Parts

The reason for adding them is so people can see if they can get them working. I don't know how to set them to be hidden in game EDIT: removed them for the 1.8.5 release.

Guys if you are going to notify of a bug that you have found then please detail EXACTLY the problem, HOW you found the problem and WHAT parts the problem affects. Simply saying "can't fuel some tanks" and "some of the fx is backwards" is completely useless to me. I can't take a look at it if you dont give me any detail. If you have crashes and you think it is related to the mod then show me the logs. EDIT: no landing gear other than stock is working, including the OPT landing gear that will come with 1.8.5

thats all good. when we release 1.8.5 will be bundling the version of Firespitter I have which DOES work for current version of KSP.

@Mycroft: don't forget you are testing 1.8.5 which has IFS compatability in addition to fallback configuration. @MeCripp: it's how K.Yen originally wrote it but the 1.8.5 version has fallbacks as well as IFS, FS and RF compatability.

Are you able to fuel any other tanks?

Is your Firespitter up to date?

Which tanks specifically are you unable to fuel?

Unfortunately at this stage it isn't going to happen, that being said, once @K.Yeon returns to active development in november he will have a nice list of suggestions, including this one.

There is the thought of removing that cockpit altogether as the built in docking port is useless, I suspect that is why @K.Yeon scrapped it to begin with, I will run it by the team.