[1.12.*] Deadly Reentry v7.9.0 The Barbie Edition, Aug 5th, 2021

[Starwaster]

@Starwaster: thanks dude, you're awesome.

maybe. Maybe not. Testing something now to change the inflatables behavior when FAR is installed but I suspect that FAR ISNT seeing the changed geometry when the shield inflates. Which afaik, it's supposed to. If it doesn't then there's nothing I can do.

[Maxwell Fern]

Let me know if I can test anything for you.

[Starwaster]

Round 1 of testing. What I did was apply a patch to remove certain parts of the inflatable shield's modules if FAR was installed. Those modules are the ones that change drag based on the state of animation. What I'm seeing is that cd, BC and reference area don't always correspond with what I expect to see. Reference area seems to increase like it should but cd increases when the shield is deflated rather than when it's deflated, which doesn't make sense. Terminal velocity and BC don't change at all. Net result is that there's no apparent change in drag. I suspect that it's more an issue with the shield's animation, which as I've alluded to in the past has issues that confuse modules trying to read its state. DRE seems to read it ok but maybe I need to re-evaluate that too.

I've also indicated in the past that people might want to use the ADEPT deployable shield would be a better choice than DRE's own inflatable. You can get it here: http://forum.kerbalspaceprogram.com/threads/98178-NASA-Adaptable-Deployable-Entry-Placement-Technology-(ADEPT)-by-OLDD-(26-04-14). I don't have a patch for it yet though. (the patch that strips it of its drag altering modules when animating)

If you want to test the patch that I made for DRE's inflatable, here it is: Edit your DeadlyReentry.cfg file and paste this at the bottom:

@PART[6.25_Heatshield]:NEEDS[FerramAerospaceResearch]
{
    !MODULE[ModuleAnimation2Value]:HAS[#valueName[minimum_drag]]{}
    !MODULE[ModuleAnimation2Value]:HAS[#valueName[maximum_drag]]{}
    !MODULE[ModuleAnimation2Value]:HAS[#valueName[angularDrag]]{}
}

EDIT:

Here, I just whipped up one for the ADEPT shield (which really is a high quality product BTW. Not sure if I remembered to link to it in the OP..... if I haven't I soon will)

I'm going to test this myself in a bit but I have to go do a thing.

@PART[NASAaeroShield_A]:NEEDS[FerramAerospaceResearch]
{
	!MODULE[ModuleAnimation2Value]:HAS[#valueName[minimum_drag]]{}
	!MODULE[ModuleAnimation2Value]:HAS[#valueName[maximum_drag]]{}
	!MODULE[ModuleAnimation2Value]:HAS[#valueName[angularDrag]]{}
}
@PART[NASAaeroShield_B]:NEEDS[FerramAerospaceResearch]
{
	!MODULE[ModuleAnimation2Value]:HAS[#valueName[minimum_drag]]{}
	!MODULE[ModuleAnimation2Value]:HAS[#valueName[maximum_drag]]{}
	!MODULE[ModuleAnimation2Value]:HAS[#valueName[angularDrag]]{}
}

Edited December 11, 2014 by Starwaster

[Maxwell Fern]

I'm giving it a try right now.

[Maxwell Fern]

Well, I didn't observe any change... drag and BC only change is something is attached in front of the inflatable shield, regardless of its animation state.

ADEPT's shield seems to be broken, as I can't get it to deploy or decouple...

[Starwaster]

There's an animator dependency. You need to download and install http://forum.kerbalspaceprogram.com/threads/73283-0-23-x-AdvancedAnimator-ModuleAnimateGeneric-upgraded-v1-1-1-2-04-14?highlight=moduleanimator

[Starwaster]

Ok, so testing with the ADEPT shield shows that FAR does properly recognize that it has animated. cd increases and decreases as the shield is deployed or retracted. Reference area though... increases for the retracted state and decreases for the deployed state. I thought reference area was supposed to be the cross section perpendicular to the velocity vector so that doesn't make sense to me. I guess FAR is measuring it along the long axis without regard to orientation? I dunno, but whatever, it looks to me like it's working the way it should.

Not sure it matters but I replaced the references to the advanced animator with the stock generic animator on my install for the ADEPT. I don't think it does...

[miceliux]

Please, add a .version file. It's so util when you have many mods.

http://ksp.cybutek.net/kspavc/Documents/README.htm

[Revenant503]

Possibly a silly question, but what version of module manager is DRE 6.3.2Beta built for?

[Olympic1]

Possibly a silly question, but what version of module manager is DRE 6.3.2Beta built for?

If you install the latest MM you should have no problems, even if DRE is build for a earlier MM version

[Starwaster]

It wouldn't matter even if you used an older version of MM as long as none of its configs use syntax unsupported by the older version. The plugin itself is not MM aware.

In fact you could use any version of MM as long as it runs in KSP 0.25

[taniwha]

Starwaster: the changes to the chutes themselves are a tad annoying. The semi-deployment minimum pressure is probably fine, but 2300m for full deployment? 500m is painful enough even with 4x warp.

Also, it would be nice to be able to disable the chute warning message.

Otherwise, recent DRE is quite nice: I really like that most of my service modules now start exploding rather than just flying out of physics range (makes Jeb very happy and the others jump).

[GunTuga]

Hello, Is there any way to remove the parachute warning messages? They are getting pretty annoying filling the screen and lagging the game

[Starwaster]

Hello, Is there any way to remove the parachute warning messages? They are getting pretty annoying filling the screen and lagging the game

They're not supposed to fill the screen, try the latest beta. That should fix it.

@Taniwha: Thanks for the feedback. I was using Apollo as a guideline for deployment. You can tweak deployment settings in the VAB. (or maybe even in flight.... however (un)realistic that is)

Edited December 14, 2014 by Starwaster

[GunTuga]

I have the latest Beta, the thing is I use stage recovery mod, So for example the solid fuel boosters have a parachute each, so before I decouple I get like 8 Messages on the screen saying parachutes may fail. It gets pretty annoying, I suggest an option to remove the warnings mate

[Starwaster]

I have the latest Beta, the thing is I use stage recovery mod, So for example the solid fuel boosters have a parachute each, so before I decouple I get like 8 Messages on the screen saying parachutes may fail. It gets pretty annoying, I suggest an option to remove the warnings mate

Unable to duplicate your problem.

Latest beta, 8 chutes:

Dunno why you would be seeing 8 messages. Try downloading again?

That fix might not have made it into the last push... if not it will definitely be in the next. I'll have to think about allowing the outright disabling of the message because right now it means fewer support complaints about chutes not working/buggy chutes/ chutes overheating even though the part was at -69,105 Celsius.

Edited December 14, 2014 by Starwaster

[Starwaster]

Pushed latest updates. This will probably be the last beta. Next update will be official.

https://github.com/Starwaster/DeadlyReentry/releases/download/v6.3.3/DeadlyReentry_v.6.3.3.beta.zip

• ModuleManager 2.5.3 compatibility change: Moved difficulty and settings related files to DeadlyReentry/Plugins/PluginData (EasySettings.cfg, DefaultSettings.cfg, HardSettings.cfg and Custom.cfg)
  
• Added virtual keyword to ModuleAeroReentry.Start()
  
• Added override keyword to ModuleHeatShield.Start()
  
• Fixed FixAeroFX() fixes. (was not properly calling coroutine)
  
• Moved crew/chute warning messages to ReentryPhysics
  
• Updated ModuleManager file to 2.5.3
  

(to-do: move per-planet atmospheric data to ReentryPhysics; right now it's calculating that on every part instead of being static on ReentryPhysics. If you don't know what that means don't worry)

Edited December 15, 2014 by Starwaster

[GunTuga]

Oh I thought I had the latest version I didn`t my bad, you were right only one warning now

[Starwaster]

Oh I thought I had the latest version I didn`t my bad, you were right only one warning now

I think I'd only released it as a drop-in update via Dropbox. The official beta with that fix didn't go live until just now. (plus some other minor things)

[theersink]

I'm getting no Ablation on any setting using 6.3.3.

200Km Ap Per set at 27Km, temps reach about 600C. I get the full F/X but no ablation at all on the heatshield using normal setting. Setting to hard makes no difference as well as setting the shockwave exponent to 1.12.

Here is a pic at about 35Km

And the output file:

https://onedrive.live.com/redir?resid=5C2CF5B33E38865E%214018

[theersink]

After more investigating if I set the shockwave exponent within the debug console I definitely get the increased heating but not if I modify the Default config with the value and set in game menu to normal. Don't know if that helps or not. In addition I get almost no heat with the hard setting using the alternate density calc setting, not sure if this is enabled or not yet.

[Sampa]

I'm getting no Ablation on any setting using 6.3.3.

200Km Ap Per set at 27Km, temps reach about 600C. I get the full F/X but no ablation at all on the heatshield using normal setting. Setting to hard makes no difference as well as setting the shockwave exponent to 1.12.

Here is a pic at about 35Km

http://i.imgur.com/gkMbh4b.png

And the output file:

https://onedrive.live.com/redir?resid=5C2CF5B33E38865E%214018

Wow, your screen is cluttered

[theersink]

Wow, your screen is cluttered

I suppose it is. I guess I like a lot of info.

Still getting a feel for exactly what I need for the different times.

[Starwaster]

I found a problem with difficulty settings not being properly saved or loaded, but it's not anything that would stop your heat shield from working. Ablation is working just fine on my end.

I'll have to take a look at your log and see if that turns anything up.

It might help to see a look at your DRE debug screen so I can see the settings.

Also, what shield is that and where did you download it?

[J.Random]

May I suggest removing the "don't open chutes" message? It isn't very readable anyway (especially in the clouds: light green on white... yeah). Can you overlay staging icons? Changing them in flight is possible, but RealChute (and the game itself) already does that, so there might be a conflict. Overlaying it with read cross/triangle/crossed circle or exclamation sign, if possible, would look much better.