The 20 EC mini battery pack costs 150 funds, and the stock 100 EC battery pack costs only 80 funds.

See also http://forum.kerbalspaceprogram.com/index.php?/topic/92434-12-sounding-rockets-start-small-dream-big-050/&do=findComment&comment=2835144

Currently the grid fins generate control lift (yellow arrows with F12) and much drag even when retracted. This means the only way to use them to control a landing first stage is by hiding them in a fairing during ascent.

If possible please make it so that they do not generate lift forces (and much less drag) when retracted.

The mini decoupler doesn't have 'fuelCrossFeed = False' like stock decouplers so unfortunately engines steal fuel from later stages. This also causes issues with mechjeb's dV calculations.
This part is more pedantic. It's called a decoupler buts acts like a separator. IE usually decouplers just eject from the top but this ejects at both nodes.
This is with the dev version 0.2.0 pre of course.

Although the smaller booster description says the ISP is greater in exchange for lower thrust, the ISP of both are exactly the same

Actually a second look shows all three boosters have the same ISP curve and this has been that way in previous versions (I thought they were adjusted since thrust and fuel amounts were changed)

Looks to me like the tank dry/wet masses are higher than intended, shows ingame as 0.26t wet for the SR-35A (with about 0.11t fuel?), and 1.35t wet for the SR-625A (including 0.5t fuel). So basically both tanks have a dry mass above the fuel contents mass, which is kind of unexpected.
(And for the 625 tank, even if one changes the dry weight from the current 0.85t to 0.35t, it's still considerably "worse" than the roughly equivalent stock T100 tank, which has the same amount of fuel but only 62.5kg dry weight. But without further information I would assume that could be a design choice based on the "early game" nature of these tanks.)

A short-range data transmitter is required for the avionics package in order to launch the rockets in early career mode (with "require signal for control" enabled in the difficulty settings).

CKAN thinks Sounding Rockets still conflicts with Surface Science Experiments. It did in the past. Since then CobaltWolf has fixed the issue.

It's been compatible with Sounding Rockets for at least a week. It was a typo that was breaking our ScienceDefs which broke any that loaded afterwards. v1.4.1 fixed it.

So I asked on the forum if the CKAN block could be removed and got this answer back

@nobodyhasthis, The metadata for Sounding Rockets is self-hosted by @RoverDude. You'll need to take it up with him to remove the conflict.

Does the Sounding Rockets CKAN metadata block the installation of Surface Science Experiments and can you remove it now that the conflict has been fixed?

Creating new issue because I can't reopen #62.

Unfortunately the issue wasn't fixed in the latest release (SR 0.5.5 USITools 0.8.9).

The ModuleLiftingSurface control interface disappears when the grid fins are stowed, but apparently it isn't enough to disable the module. The yellow lift arrows still appear just like in the old screenshot at http://forum.kerbalspaceprogram.com/index.php?/topic/92434-12-sounding-rockets-start-small-dream-big-050/&do=findComment&comment=2835144.

My testing has indicated that the only way to remove the yellow arrows was to rename the ModuleLiftingSurface to an invalid module name (or remove it entirely).

I'm not sure if there's a way to rename a module or some other way to really deactivate it (can a module be removed in flight?), or if this is a stock bug that it ignores the "isEnabled" property and generates lift anyway. If the latter feel free to close the issue and I'll make a ticket on the stock tracker.

There are no entry costs for the SR. I am currently using this as a patch for the missing entryCost.

P.S. I also lower the cost to be comparable with the stock Z-100.

@part[SR_Stack_Battery]
{
%entryCost = 90
%cost = 30
}

@part[SR_Payload_*]
{
%entryCost = 450
}

The launch stick seems to stick on the rocket for better or worse. (actually it's a pretty darn decent strut!)

But it does exactly what the description suggests it won't do. :) I'd expect it to behave like a launch clamp instead.

This is in a somewhat modded 1.4.5, so please forgive me to not reproduce this just with sounding rockets mod.

Using 0.9.0.0

• SmokeScreen 2.8.0.0
• RealPlume 11.0.0

Other SRB parts from other mods don't have that issue, I guess these parts are special because of their MODULE USI_DropTank - but I'm not sure...

I also had posted here two weeks ago:
https://forum.kerbalspaceprogram.com/index.php?/topic/130576-131-realplume-stock-v110-29118-the-tweakscale-update/&do=findComment&comment=3324383

The 0.35 parachute deployment direction has been fixed, but I am still having trouble with the other sizes deploying at a ~45 degree angle, causing my craft to hang glide where I dont want it to go. (had this issue with other parachutes of yours that have the small pack design)

the current parachute model looks rather large for its size and has no real color. any chance to update the size of the parachute to be a tad smaller and sport maybe some red striping?

Unless SR_Stabilizer is obsolete:

see UmbraSpaceIndustries\SoundingRockets\Parts\SR_Stabilizer.cfg

MODEL
{
model = UmbraSpaceIndustries/SoundingRockets/Assets/SR_Stabilizer
}

Minor detail, but the filenames of the part models don't match up with the names you've given to the parts themselves. Payload01 (meterology) has the model for Payload03 (mini-science) and vice-versa. Same issue with 2 and 4.

Assets/SR_Payload01.mu should be renamed Assets/SR_Payload03.mu
Assets/SR_Payload03.mu should be renamed Assets/SR_Payload01.mu
... or really however the models work, I only changed my config files for the time being ;)

It seems the editor is counting the fully deployed size of the chutes, so adding one adds 10 meters to a craft's height instead of 1 meter or so, as a result only fairly short craft can be launched from an unupgraded VAB. Screenshots as evidence:
http://imgur.com/a/QuAH8

The comparatively tiny Avionics Package costs just as much as the much larger Probodobodyne OKTO, which has reaction wheels, SAS, Kerbnet access, a data transmitter, and built in EC storage.

Here's an MM config that adds a passive antenna to the avionics package:

// RemoteTech_SoundingRockets
// This is free and unencumbered software released into the public domain.
// All the code from RemoteTech is in GPLv2

@part[SR_ProbeCore]:HAS[!MODULE[ModuleSPU],!MODULE[ModuleRTAntennaPassive]]:NEEDS[RemoteTech,UmbraSpaceIndustries]:AFTER[UmbraSpaceIndustries]:FINAL
{
%MODULE[ModuleSPU]
{
}
%MODULE[ModuleRTAntennaPassive]
{
%TechRequired = start
%OmniRange = 100000
%TRANSMITTER
{
%PacketInterval = 0.3
%PacketSize = 2
%PacketResourceCost = 15.0
}
}
}
@part[RTPassiveAntennaTech]:NEEDS[RemoteTech,UmbraSpaceIndustries]:AFTER[RemoteTech]:FINAL
{
@TechRequired = start
}

I started a new career recently and have been playing around with sounding rocket parts, specifically the Meteorological, Aeronomical, Materials, and Engineering experiments. It seems to me like they would be better suited to be one time use only experiments like the Mystery Goo.

With all four experiments being re-runnable, I was able to get quite a large amount of science just orbiting around Kerbin, Minmus, the Mun, and Duna from all the various biomes. Seemed a little too easy to spam these experiments.

Good night RoverDude,

I found a incompatibility with Sounding Rockets and Surface Experiment Pack (http://forum.kerbalspaceprogram.com/index.php?/topic/77858-11-surface-experiment-pack-eva-science-for-kiskas-v14-2742016/).

When both are installed none of the Sounding Rockets experiments work. I can't even right click on them during a flight. Neither Surface Experiments Pack experiments work.

Best regards,
VaPaL

Bug discovered: when setting a solid rocket motor as root, it does not detach. When setting some other part as root, the solid rocket motor detaches.  Tested the SRM-S. Not sure if others affected.

The texture for the gondola appears to be wrong - it's got a cloud with raindrops on it. Wrong part of a shared texture?

Both say they are 0.35m, both have the exact same descriptions for the deployment stats, but the orange one is noticeably thicker. Is this intentional?

EDIT: I'm just getting into the mod, I believe the stats on the orange nosecone are supposed to be 0.625m

I can control the inline probe core without a connection. It looks like it doesn't have the right module.

Sounding Rockets was working for me yesterday. Steam updated to 1.3.1 in the meantime (thanks, valve) and now Kerbal crashes on startup. I removed all mods, and, through trial and error, figured out that sounding rockets would cause the crash with no other mods installed.