[1.2.2] Stock Part Revamp, Update 1.9.6. Released Source Files!

[Spanier]

The pod is still 24 sided.

Oh, i wasn't speaking clearly, I meant the hitbox.

But when you try to attach something diagonally to to the pod in stock, it doesn't snap to a propper orientation.

[BudgetHedgehog]

First time I've used the stock wings in ages. The SP+ wings break off too easily but the stock ones work fine - only thing holding me back from using them was how ugly they were but you fixed that

[TeddyDD]

Your mod should become stock just like SpacePlane+ Amazing work! Thank you

[Sauron]

Would be great to redo the hitchhiker model and a lab with less hideous windows

[Ven]

Would be great to redo the hitchhiker model and a lab with less hideous windows

It's on the list, It getting remade is entirely dependent on me not getting sidetracked. Speaking of sidetracking:

Javascript is disabled. View full album

Unfortunately some of the parachutes went nuts, so these new parts will be posted tomorrow.

Edited September 21, 2014 by Ven

[Taverius]

I've been bashing my face trying to figure out what your mod was doing that was messing with TVPP, when I realized you replace the stock .cfgs instead of using MM.

Never do this.

I'll have a file that resolves that tomorrow

P.S. Some notes:

• radialLiquidEngine1-2
  
  • You changed the part origin and the node, and that's fine - but you didn't then set CoMOffset to set the part's CoM back where it was. Fixed cfg-side.
    
  • Changing the FxOffset is a bad idea - mods that change that engine to ModuleEnginesFX (like HotRockets!) will have FX that's in the wrong position (clipping the nozzle, I imagine). Move the thrust vector instead.
    
  • ModuleAnimateHeat was missing its closing bracket, Fixed.
    

Edit I lied ahaha: link

Edited September 22, 2014 by Taverius

[Riverey]

New Mk1-2 cockpit looks good but now it doesn't fit with SDHI aerocap because crew hatch is finally in it's normal position=(

[Guest]

Does it work with SXT? It uses stock textures, so any stock reskin will affect it, too. I'd like to know if it's for better or worse in this case.

[Mach_XXII]

Does it work with SXT? It uses stock textures, so any stock reskin will affect it, too. I'd like to know if it's for better or worse in this case.

No it doesn't work with SXT, some reskins work with SXT like the mk1-2 pod but the lander can reskins won't work with it

[Whirligig Girl]

I actually really like the red arrows on the decoupler, please don't change them black.

[Lexx Thai]

I've been bashing my face trying to figure out what your mod was doing that was messing with TVPP, when I realized you replace the stock .cfgs instead of using MM.

Never do this.

Taverius, stock .cfgs replacement (as well as the textures and models) is better practice sometimes - KSP still loads any textures and models to memory, even unused.

[Taverius]

Taverius, stock .cfgs replacement (as well as the textures and models) is better practice sometimes - KSP still loads any textures and models to memory, even unused.

I'm not arguing about not replacing the models - no need to have useless assets in memory.

I'm arguing about not replacing the .cfgs, and doing the little that is necessary via MM.

[Lexx Thai]

But sometimes MM .cfg is extremely difficult to understand (i.e. like yours editions in TVPP). Hehe, two words - "Renegade Modder"

[OrbitusII]

I also think that having it replace the models outright is better for RAM usage. It won't load the original models at all that way so it's effectively a non-issue. On that note, it might be nice to have a "revert to stock" download so it's not a problem if you forget to back up the original parts.

[fried_rice]

But sometimes MM .cfg is extremely difficult to understand (i.e. like yours editions in TVPP). Hehe, two words - "Renegade Modder"

MM .cfgs are important when you're looking for compatibility with many different mods. It lets you set the modifications before or after certain other mods, or conditionally on the presence or lack of mods.

It's worth spending some time learning about it. I can't do much with it, but it helps to understand what others have done with it.

I also think that having it replace the models outright is better for RAM usage. It won't load the original models at all that way so it's effectively a non-issue. On that note, it might be nice to have a "revert to stock" download so it's not a problem if you forget to back up the original parts.

One can hope we get a better asset-loader. Regardless, I think a 'revert to stock' download might violate licensing.

[Taverius]

Nah, you're allowed to redistribute stock assets and code so long as its only for KSP mods and you clearly state its by Squad and they have the rights to it.

[BudgetHedgehog]

Also, I'm not sure that being able to understand a MM cfg is important to mod users. Absolutely important to the mod creators, but to users, it's by no means necessary (not denying it's helpful though). To quote The Matrix, 'comprehension is not a prerequisite for co-operation'

[Taverius]

Anyways, any MM for this mod is pretty straightforward:

@PART[Mark1-2Pod] {
    @author = Ven

    MODULE
    {
        name = ModuleLight
        lightName = Lightpod
        useAnimationDim = true
        lightBrightenSpeed = 1
        lightDimSpeed = 1
        resourceAmount = 0.01
        animationName = Lightpod
        useResources = true
    }
}

Only the radial engine requires any real knowledge of the syntax to follow:

@PART[radialLiquidEngine1-2] {
    CoMValue = #$node_attach[1]$
    @CoMValue *= -1
    %CoMOffset = #0, $CoMValue$, 0
    !CoMValue = DELETE

    @node_attach = #$node_attach[0]$, 0.0, $node_attach[2]$, $node_attach[3]$, $node_attach[4]$, $node_attach[5]$

    @MODULE[ModuleEngines] {
        @fxOffset = 0, 0, 0.15
    }

    MODULE
    {
        name = ModuleAnimateHeat
        ThermalAnim = Heat
    }
}

I feel in a lecturing mood, so lets go

First, we take the second value of the default node_attach, and store it in CoMValue

CoMValue = #$node_attach[1]$

# at the start of the right-hand-side tells MM we're going to do a search-and-replace.

$node_attach[1]$ says we want the second (0-index) value of node_attach. Strings are split with , by default.

Then we flip its sign

@CoMValue *= -1

Use it to construct CoMOffset. Its a good idea to use Replace (%) in these cases

%CoMOffset = #0, $CoMValue$, 0

Finally, clean up the temporary variable

!CoMValue = DELETE

Could have used regex instead, but it gets hard to read ... it would look something like this:

@CoMOffset ^= /^(.*),\s*(.*),\s*(.*)$/$1, -$2, $3/

I think you'd agree its not really human-parsable for most people.

Now that CoM is in the right place, rebuild the node value, using 0.0 for the second part:

@node_attach = #$node_attach[0]$, 0.0, $node_attach[2]$, $node_attach[3]$, $node_attach[4]$, $node_attach[5]$

[Guest]

Any chance of a version (either MM-based or using a different texture) that would work with SXT? This looks good, but SXT adds a lot of parts at little memory cost. I just can't lose them. It'd be great if you could restore, say, gold foil on the lander can, or other such characteristic texture bits that SXT uses.

Edited September 23, 2014 by Guest

[RyanRising]

Thank you! This is brilliant.

[Ven]

Any chance of a version (either MM-based or using a different texture) that would work with SXT? This looks good, but SXT adds a lot of parts at little memory cost. I just can't lose them. It'd be great if you could restore, say, gold foil on the lander can, or other such characteristic texture bits that SXT uses.

Does it work with SXT? It uses stock textures, so any stock reskin will affect it, too. I'd like to know if it's for better or worse in this case.

SXT is at least partly compatible , because it seems that several models don't load, maybe because they use stock assets that technically no longer exist. The models that are entirely original still look right (are still using the stock textures).

I've been bashing my face trying to figure out what your mod was doing that was messing with TVPP, when I realized you replace the stock .cfgs instead of using MM.

Never do this.

I'll have a file that resolves that tomorrow

P.S. Some notes:

• radialLiquidEngine1-2
  
  • You changed the part origin and the node, and that's fine - but you didn't then set CoMOffset to set the part's CoM back where it was. Fixed cfg-side.
    
  • Changing the FxOffset is a bad idea - mods that change that engine to ModuleEnginesFX (like HotRockets!) will have FX that's in the wrong position (clipping the nozzle, I imagine). Move the thrust vector instead.
    
  • ModuleAnimateHeat was missing its closing bracket, Fixed.
    

Edit I lied ahaha: link

Thanks for posting about that, I've added The MM CFG's.

Javascript is disabled. View full album

OK, here's what I've added:

• A new Crew Cabin
  
• A 'new' Mk1 pod
  
• The small SRB got remodeled, and now has a fairing.
  
• The Long Antenna has been remodeled, and now collides with objects when extended. Antennas are now your early game landing gear.
  
• both the 1.25m and 2.5m decouplers were remodeled.
  
• Redid all the parachutes, added a few drouge chutes to even out the range.
  
• Changed the 1-2 pod's collider to make placement of parts easier and more precise.
  
• The sepatron was remodeled, and now uses the LES FX.
  
• .625m, 1.25m and inline docking ports have been redone.
  
• And some other things that I forgot.
  

[BudgetHedgehog]

Gib now pls

[Floppster]

I'm having some problems with this update, the game freezes on "Compiling Part Squad/.../radialLiquid..." and after htat line it says Exception: FormatException: Unknown char: #.

Guessing its from the MM cfg file, but why would this happen?

[Floppster]

It seems your folder for the radial engine is named Radial.. instead of radial..., this made the contents not write over the vanilla part and i ended up with two copies of the same part, probably screwing with ksp. Also, ven.cfg seems superflous as most of it is present in the part.cfg file.

[Robotengineer]

These are great Ven! Looking forward to a release.