Eskandare

Your mod is great. I know it is WIP but I think tweakable bay doors would be a good idea and perhaps some work on reducing the memory footprint of the textures.

I noticed some mods aren't compressed. Not sure if this have been answered, but is there a way to get them to compress? EDIT: Never mind I figured it out, but is there anything I should be aware of while writing config files? I'm trying to get coffee industries to compress, but some textures disappear and become black.

One thing I noticed is that the textures are smaller in size. So far as I've seen, they load up smaller too and make KSP less laggy when using the FusTek parts. My beef with FusTek is that when I am completing a rendezvous, there is a lot of lag when my station is being taken off the rails.

Quoting myself Is the cloud shadow layer suppose to hover above the ground? It looks as if it is hovering 30m AGL.

It seems a little glitchy; there is a layer of dark that acts like a cloud or atmosphere layer.

Is there a reason why the FAR toolbar icon doesn't show up?

I think InfinateDice did something like that. http://kerbalspaceprogram.com/infinitedice-strongstruts-v1-1-2/ Perhaps you can install the KAS code into the InfinateDice's code?

It's not from the LES to my knowledge, unless the LES is somehow providing thrust while still on the stack but not activating animation, FX, or sound. I'll keep looking into this and focus on the debug log to see if it is generating 'magical' thrust. Edit: Just to add I felt it being extremely odd because my very first flight with the pod was a complete success. Then all the odd behaviors happened. I'll see if I can roll back EL to the previous version to see if something else in EL is completely screwing up command pods. Edit 2: Okay, so I tested it with first my orange tank, main sail, and then with my 3 orange tank 3 main sail, test rockets. I, so far so good... but the log repeated [Log]: Skipped frame because GfxDevice is in invalid state (device lost) I doubt it has anything to do with Taurus HCV. There were a few other errors, possibly associated with other mods or KSP itself. So for, rolling back EL to the previous version has corrected the problems and keeping the ExWorkShop reference rem'ed out seems to make taurus work just fine. I'm going to test on my bigger rocket to see if it still wants to pitch down. Edit 3: The log error also appears to be an anomaly, it hasn't come up again.

Just quoting myself from before. Rem'ing out the EL command moduel reference in the EL/MM config file seems to have done the trick. Doing more testing. Edit: Okay so that did work, but for some reason the capsule is asymmetrical in mass. All my test rockets list off to one direction. This is what I did in the MM config in EL. //@PART[*]:HAS[@MODULE[ModuleCommand],!MODULE[ExWorkshop]] //{ // MODULE { // name = ExWorkshop // command pods are a tad cramped and are really meant for other // purposes (like flying) // ProductivityFactor = 0.25 // Unfortunately, due to MM limitations, probe cores get a workshop too // IgnoreCrewCapacity = false // } //} It seems to have fixed the problem. Edit 2: There is either an asymmetrical drag or mass issue. I continued rigorous testing, trying various weights to see if the mass would get corrected. it is odd, because it seems to have an off balance of sorts that was only slightly fixed by a 0.03 ton object over the window side of the pod.

I'm testing EL with the MM reference to command pods rem'd out to see if there is any difference.

I read that EL causes engines built into the command pod to automatically ignite. The two command pod mods I use started to have problems. Is there a way around this without uninstalling EL or not using the command pods? Also I put workshops into some of the parts I use but they always have a production of 0.

Hey Lack, they MEM has a problem with the engine auto igniting. I have a feeling that the game has a problem with having engines built into the command module. The Taurus HCV mod has the exact same problem. Perhaps make the engine for the MEM command pod be a separate part? Also is there a decoupler for the MEM?

I think that the game has trouble with engines built into the command module part. I found that Lack's MEM module from his SXT add on has the exact same problem where it ignites automatically. Lack's MEM also has the engine built into the command pod part. I believe all engines should be separate parts from the command module. This would remove the problem of auto ignition.

rbray89, this absolutely beautiful! You did a great job!

I added ExWorkShop to LLL structure sections via MM, but no production. I have the large 4x2 parts 10 production rating (because with that much space why not?). Question is, does the part have to be read as a capsule for the work shop to work?

May need to update for v.23.5 struts no longer hold together. : /

I had wondered... BTW, great mod! Really fun to see my Kerbals get awards for their suffering. Also works well with crew manifest for those custom named Kerbals.

A while back I created an EBM (Electron Beam Melter) for a LLL (Lack Luster Labs) extension I was going to call Jool Mining Corporation. However I hadn't done too much to update it. For more on what an EBM is here is a wiki: http://en.wikipedia.org/wiki/Electron_beam_melting If anyone has any modeling experience (or spare models I could use) I would certainly love to revive my EBM extension to EPL. I'm decent with creating textures I just don't model much. On another note, a new 'animated' auger would be nice. I've been tempted to copy and rewrite the config to make the large Kethane drill into a temp auger.

That was a bug I saw occurr in previous versions. I'm not having any trouble putting things of any size into LKO.

As I wait for B9's update (He's busy with that, other things he's doing for Squad, and his personal life), meanwhile I've decided experiment with conventional KW engines to put stuff into space. 72 tons is not too bad. I'll have to try and rebuild my 3 orange tank monster.

I seem to have a problem with strong pitching up. The COL is positioned just after the COM as it should in weight and balance when regarding lift. For some reason while flying the physics act as if the COL is being placed before the COM. Any ideas?

Bac9, I understand that. Is there a way to trick, fork or expand the the code in some way? I haven't gotten into making plugins yet. Rubber Band Caterpillar tracks managed to have what appeared to be multiple rolling wheels on tracks. Would it be possible to do the same for the landing gear but have the tracks "invisible" to simulate multiple axle gear?

I agree. I certainly feel that quad and six wheel gear would add a lot to B9 aerospace. Something similar to these.

I should see what I can do with interstellar for my standard deployment methods. My only issue is that the reactors are very heavy. When it comes to weight and balance it provides quite a problem. It lowers the payload I can carry due to the thrust to weight ratio. The problem is the larger the craft, the heavier the ramp weight, and the longer takeoff/landing roll. I recently had that problem with my small SSTO. It was too heavy and it's landing gear collapsed on takeoff once I reached 100 m/s.

I think they came with Lack Luster Labs. Edit: I could be wrong. I have 60 mods installed and have them all working thanks to the compression plugin.