[1.0.4] BoxSat vA.02f - Updated 09/16/2015

[Plusk]

Hi there. First of, mod is looking great and has lots of potential. A.02.b works just fine with 24.2, with only 20% of previous version size! Two things tho:

- Solar panels are vastly op.

1x3 folding panel vs 2x3 stock panel. Yours 13% bigger, 34% heavier, yields 140% more power.

Fixed panel vs stock OX-STAT. Yours 33% bigger, yields 113% more power. Same weight.

- Antenas and probe core lacking RT signal range definitions. Am i missing something?

Looking foward to future updates

Edited October 13, 2014 by Plusk

[Mecripp]

Hi there. First of, mod is looking great and has lots of potential. A.02.b works just fine with 24.2, with only 20% of previous version size! Two things tho:

- Solar panels are vastly op.

1x3 folding panel vs 2x3 stock panel. Yours 13% bigger, 34% heavier, yields 140% more power.

Fixed panel vs stock OX-STAT. Yours 33% bigger, yields 113% more power. Same weight.

- Antenas and probe core lacking RT signal range definitions. Am i missing something?

Looking foward to future updates

Make sure your just running 1 RT MM for it there where 2 in the folder.

[acc]

thanks for updating, just started missing the cute boxes on my fresh .25 save

[Cleric2145]

I apologize if this has been mentioned, I scanned a couple pages back:

Many if not all the parts are just pure white with no textures, I'm using ATM but it shouldn't be causing totally white textures, right?

[Mecripp]

I apologize if this has been mentioned, I scanned a couple pages back:

Many if not all the parts are just pure white with no textures, I'm using ATM but it shouldn't be causing totally white textures, right?

Are you using A.02b of boxsat ?

[orcmaul]

- Solar panels are vastly op.

1x3 folding panel vs 2x3 stock panel. Yours 13% bigger, 34% heavier, yields 140% more power.

Fixed panel vs stock OX-STAT. Yours 33% bigger, yields 113% more power. Same weight.

During development I evaluated the existing solar panels and planned the BoxSat panels using similar performance parameters. All BoxSat panels are based off of the performance of the OX-STAT panel. Here we go with some numbers.

OX-STAT: 0.1818 m², 0.75 EC/s

OX-4L: 1 m², 2 EC/s

Gigantor XL: 13.5 m², 18 EC/s

BoxSat 62cm Static: 0.390625 m², 1.6 EC/s

BoxSat 3x62cm Folding: 1.171875 m², 4.8 EC/s

So why did I use the OX-STAT's performance level? If I had used the OX-4L's performance the stats for both parts would be virtually identical to the existing panels. I opted for stats that would be different from the existing parts so that there would be more variety for the player.

[Cleric2145]

Are you using A.02b of boxsat ?

I am, I installed it over the previous version. Is A.02b a fresh install? I will try a fresh folder the next time I'm around my home computer.

[Mecripp]

I am, I installed it over the previous version. Is A.02b a fresh install? I will try a fresh folder the next time I'm around my home computer.

Yep

Change Log:

Alpha.02b 10/12/2014

-Update for KSP 0.25 (fix texture glitch with scienece and antenna parts). <------ HERE

-Change all textures to .PNGs for disk and memory savings. <---------- HERE

-Boost Remotetech antenna range for tape antennas (old values file has stats from previous version).

-Increase fuel/oxidizer capacity of LFO module.

-add entryCost for all parts.

-fix description for MP and LFO modules.

-add MM config for Kerbal Engineer v1.0.

So the way you installed it you have both textures.

[Cleric2145]

Yep So the way you installed it you have both textures.

Hurr. My bad. I got back from a long hiatus in KSP and had to update a bunch of mods. I didn't look well enough and just mass-updated a dozen addons.

[Pondafarr]

So, I took the basic trays, and made a couple new cfgs. Using the .05 tons of fuel mass shown for LFO and Mono, it equates to 500 units of Xenon. VERY handy for turning this Boxsat into a long range probe (in a standard two-frame setup, I loaded a probecore, a BoxSAS, two batteries, two Mono, 2 Xe trays, and every antenna in the mod, I can load slightly over 5000 dV) Also made a massive cheat my reusing the Probecore model as a science lab (removing the crew requirement of course!) so i can build a SciProbe with a yet-to-be-created Goo tray. Not sure I'll do a Material experiment, but I think I will for completeness. Next will be ScanSat trays.

And, since these are simple config files, reusing the current models, sharing will be easy, if anyone is interested...

[AC656]

I thought that RemoteTech and Mechjeb had problems when installed together is this mod compatible with both at the same time or separately.

[Mecripp]

I thought that RemoteTech and Mechjeb had problems when installed together is this mod compatible with both at the same time or separately.

No they all work together.

[Alvargon]

Hi, I have to say that there are a problem with the MechJeb, well it's not exactly a problem. When you have the RemoteTech the vessels depends of the main base connection, you must have an active connection to have a functional vessel except when this vessel have any MechJeb component installed, because the MJ have priority over the RT. But, with the BoxSat you must install a secondary MJ element to evade this problem. Is this intentional or is a real problem?

[Mecripp]

Hi, I have to say that there are a problem with the MechJeb, well it's not exactly a problem. When you have the RemoteTech the vessels depends of the main base connection, you must have an active connection to have a functional vessel except when this vessel have any MechJeb component installed, because the MJ have priority over the RT. But, with the BoxSat you must install a secondary MJ element to evade this problem. Is this intentional or is a real problem?

No thats not right and, I use RT too and, I run

@PART[*]:HAS[@MODULE[ModuleCommand],!MODULE[MechJebCore]]

{

MODULE

{

name = MechJebCore

}

}

which give MJ to all Command parts and RT as a cfg that give MJ

ModuleSPU

so if you playing with a probecore that not stock yes you can control them with or out a connection.

[orcmaul]

Hi, I have to say that there are a problem with the MechJeb, well it's not exactly a problem. When you have the RemoteTech the vessels depends of the main base connection, you must have an active connection to have a functional vessel except when this vessel have any MechJeb component installed, because the MJ have priority over the RT. But, with the BoxSat you must install a secondary MJ element to evade this problem. Is this intentional or is a real problem?

BoxSat should conform to the normal behavior of RT+MJ. If it is not then this is a bug I would need to address.

My understanding of RT+MJ is that when your vehicle is showing "no connection" mechjeb does not function. This situation is what the RT flight computer is for. I'm uncertain as to how KOS interacts with RT.

[Alvargon]

BoxSat should conform to the normal behavior of RT+MJ. If it is not then this is a bug I would need to address.

My understanding of RT+MJ is that when your vehicle is showing "no connection" mechjeb does not function. This situation is what the RT flight computer is for. I'm uncertain as to how KOS interacts with RT.

When you lose connexion RT which has lost this connexion. Normally, MJ avoids this problem show you "Local Connection". But the BoxSat module prioritizes the RT over the MJ.

How I said, the mod work without problems, the only think is that detail, is a great job

[Mecripp]

RT would be better to run

@PART[*]:HAS[@MODULE[ModuleCommand],!MODULE[ModuleSPU]]

{

MODULE[ModuleSPU] {

}

MODULE[ModuleRTAntennaPassive] {

OmniRange = 3000

TRANSMITTER {

PacketInterval = 0.3

PacketSize = 2

PacketResourceCost = 15.0

}

}

}

Then there probecore CFG and sorry for getting off Topic.

[orcmaul]

Normally, MJ avoids this problem show you "Local Connection".

"Local Control" is the status of a manned vehicle. As far as I know having a mechjeb module should not produce a status of "Local Control".

Edit: I went and looked up the precise phrasing and confirmed that local control is a status intended for manned capsules. Unmanned vehicles should not have the status "Local Control".

Edited October 23, 2014 by orcmaul

[Floppster]

Local Control can happen with probes not made for RT, if a probe core doesn't have a ModuleSPU it counts as manned by RT. I made a MM patch for myself that adds the module to all probe cores discovered so that it wouldn't feel cheaty to use a non-RT core

[Helix935]

Hello, how's development because its been awhile since an actual update and i know that DasPenguin85 was/is sick but just wondering?

[Joshwoo70]

I wish they could change to allow modpacks

[orcmaul]

Hello, how's development because its been awhile since an actual update and i know that DasPenguin85 was/is sick but just wondering?

Sorry about the lack of updates. DasPenguin has had a hard road to recovery from illness and is still not in a place where he feels he could resume the pace of work he prefers without adverse effects to his health. We had been hoping to get back to development in November but his recovery just hasn't been as speedy as we had hoped. He is making progress and we do hope to resume normal development at some point.

[Helix935]

Sorry about the lack of updates. DasPenguin has had a hard road to recovery from illness and is still not in a place where he feels he could resume the pace of work he prefers without adverse effects to his health. We had been hoping to get back to development in November but his recovery just hasn't been as speedy as we had hoped. He is making progress and we do hope to resume normal development at some point.

oh thank god i thought this was abandoned and also great to hear that DasPenguin is all right and recovering, we will practice our patience as he continues recovery

we can wait

@DasPenguin85 if you're reading this than get well soon from all of us here in the forums d:cool:b

[drtedastro]

Best wishes and get well........

Mod updates can wait... Health CAN NOT....

Cheers...

[MonaBabii]

Hey Just downloaded and tested this, and it's amazing ^^, for some reason I have so much fun with modular things, makes me feel like a rocket scientist to put legos together and play astronaut

I do have 1 single request: Could it be possible to make a variation of the Maintenance Hatch that maybe has some tiny explosive bolts on the corners? so you could, say, open the hatch from a command pod or via a signal from a probe module? There wouldn't be a need to even make this variation "grabbable" via KAS, because the one reason I'm suggesting this is so the box could be used for other things. For instance it would be amazing to use it to deliver stuff, maybe tiny rovers and such? I know it's probably not what the mod was intended for but right now this mod provides the most awesome delivery crate out there xD and if it wasn't for the fact that it needs a kerbal to open it, it would be perfect! Even more so than it already is in any case

Either way, thanks a ton in advance and keep it up Get well soon! And thanks a lot for the mod =D

EDIT: I edited both the Frame and the Hatch parts to increase their crash tolerance to 80 from 8 and 3 respectively (same tolerance as the squared metal plate part thing, as these parts look even sturdier ) and then added the following to the Hatch's config. file:

description = This is a service hatch to cover the modules in your BoxSat. [B][I]It now also comes built-in with tiny explosive bolts designed to jettison the panel remotely. Note for Jeb: Stop angling the frame towards the ground before triggering the charges; this is not a toy![/I][/B]

crashTolerance = 80

fx_gasBurst_white = -1.16832, 0.0, -0.0826454, -1.0, 0.0, 0.0, decouple
sound_vent_large = decouple
[I]//Not savy enough to properly modify the specific numbers/location for the smoke particles upon decoupling, but looks fine as is. Copied from one of the stock mini decouplers.[/I]

MODULE
{
    name = ModuleDecouple
    isOmniDecoupler = true
    ejectionForce = 150
}
[I]//150 ejection is a little much when you're using the default mini size for the frame unless you turn S.A.S. on xD but I plan to use it for slightly bigger things, so it's no biggie [/I]

The result: the hatch is not only grabbable as it was before but can now be jettisoned like any decoupler or shroud

Still, would be great to see this native in the mod itself as an alternate model for the hatch

---

A little something to report on the side: When testing if the decoupling tweaks would work I found that if I grab the box's Frame as the first part of the craft/root part, and then tweak it's scale, whenever I launch the craft the Frame's size will revert to the tiny default. This is likely an issue with TweakScale, though I don't know, I've no clue about programming and such Just mentioning it because I seem to recall reading somewhere that you mention picking that part first and then the probe module. Might have been the quick-start in the read-me. Nothing major though can circumvent it by not having the boxsat parts being picked first.

Cheers!

Edited November 8, 2014 by MonaBabii
Added things.