[1.0.2] NovaPunch 2.09. - May 6th - 1.0 Compatibility Update

Tiberion · September 4, 2014

The first one: the missive texture is an emissive, which are used to make engines glow typically. That part is not an engine, and thus doesn't need it. I already removed the emssive shader here locally, so the error will be gone next time, but it shouldn't affect anything as-is.

The other errors are "stock" and all decouplers seem to cause them. They're harmless.

sarbian · September 5, 2014

There is an error in the gimbal config of the NP_lfe_125m_RMA3

gimbalTransformName = Engine_Nozzel

should be

gimbalTransformName = Engine_Nozzle

Here is a ModuleManager patch to fix it : https://www.sarbian.com/sarbian/NPFix.cfg


@PART[NP_lfe_125m_RMA3]:AFTER[NovaPunch2]
{    
    @MODULE[ModuleGimbal]
    {
        @gimbalTransformName = Engine_Nozzle
    }
}

Edited September 5, 2014 by sarbian

Tiberion · September 5, 2014

Are you basing the error on it being misspelled, or did you verify that some .mu files had an Engine_Nozzle gimbal transform?

Because quite a few of the engines do in fact have transforms named Engine_Nozzel (yep, misspelled, but not by me, I just haven't wanted to re-export to fix them) and that MM config will definitely break their gimbal function, so I don't recommend using it.

sarbian · September 5, 2014

Well, one of them does not gimball by default. I ll play with code and give you the list.

sarbian · September 5, 2014

I checked and it turn out only the NP_lfe_125m_RMA3 needs the fix.

Tiberion · September 6, 2014

Yep, for some reason that one had it spelled right. Tweaked the config for next time, thanks for the report.

Gristle · September 7, 2014

I'm having some trouble with the Odin custom fairings. They do not jettison. Can anyone else confirm this or is it just me?

DTraveler · September 8, 2014

Just wanted to say that this is an excellent mod, but I do have a question. When I attach the Yawmaster 2500 Service Module to a craft and put a kerbal into it, he doesn't show up on the bottom right corner of the screen with the other kerbals in the craft. I also can't switch to his IVA from inside the craft. Is this normal, or is something screwed up on my end?

wasmic · September 8, 2014

Just wanted to say that this is an excellent mod, but I do have a question. When I attach the Yawmaster 2500 Service Module to a craft and put a kerbal into it, he doesn't show up on the bottom right corner of the screen with the other kerbals in the craft. I also can't switch to his IVA from inside the craft. Is this normal, or is something screwed up on my end?

It's normal. The Yawmaster service module has no IVA, just like the stock Science Lab. To get the Kerbal out again, click on the hatch.

Tiberion · September 10, 2014

Finally uploaded to dropbox: https://dl.dropboxusercontent.com/u/46506740/NovaPunch2_06.zip

Mostly because Kerbalstuff is currently offline.

It's still just 2.06, same version that was released August 9th.

Sylandro · September 13, 2014

I should update it, but i'm not sure if the Surplus Liquid Fuel Boosters are still in

WackyMan157 · September 14, 2014

1mil views?!??! :0

biohazard15 · September 30, 2014

So, any news about NP development?

Tiberion · September 30, 2014

Nothing to report, really limited time lately, and haven't been motivated to spend free time on this yet. We'll see what needs to happen around the 0.25 release.

I do still need someone to work on the last two logos for the agencies.

biohazard15 · October 7, 2014

Tiberion, there is a problem with 0.25 and parts that use scaled models. To illustrate, your SAS and ASRBs:

From top to bottom: 1.25, 2.5, 3.75, 5

Left: 1.25m ASRB

Right: 0.625m mini-ASRB

Fairings, nosecones and small escape tower are also affected.

Edited October 7, 2014 by biohazard15

Tiberion · October 8, 2014

Yeah they fixed the rescalefactor bug it seems, so anything with model nodes and rescale will need a config edit to remove the weird division going on.

Anything else weird?

NathanKell · October 8, 2014

Assuming your entry costs are all "as desired" and you're not using MODEL on any Squad parts (paths changed) that should be it for partmods.

Ph34rb0t · October 10, 2014

Here's a workaround for the SAS modules. The changes need to be made to each partxm.cfg in NovaPunch2\Parts\SAS\NP_SAS_1_25m and are listed below.

Just open each partxm.cfgs and replace the two sections.

part1m.cfg:

// --- asset parameters ---
MODEL
{
model = NovaPunch2/Parts/SAS/NP_SAS_1_25m/model
scale = 0.8, 0.8, 0.8
}
scale = 1.0

// --- node definitions ---
// definition format is Position X, Position Y, Position Z, Up X, Up Y, Up Z
node_stack_bottom = 0.0, -0.063, 0.0, 0.0, 1.0, 0.0,1
node_stack_top = 0.0, 0.063, 0.0, 0.0, 1.0, 0.0,1

part2m.cfg:

// --- asset parameters ---
MODEL
{
model = NovaPunch2/Parts/SAS/NP_SAS_1_25m/model
scale = 1.64, 1.64, 1.64
}
scale = 1.64

// --- node definitions ---
// definition format is Position X, Position Y, Position Z, Up X, Up Y, Up Z
node_stack_bottom = 0.0, -0.063, 0.0, 0.0, 1.0, 0.0,2
node_stack_top = 0.0, 0.063, 0.0, 0.0, 1.0, 0.0,2

part3m.cfg:

// --- asset parameters ---
MODEL
{
model = NovaPunch2/Parts/SAS/NP_SAS_1_25m/model
scale = 2.512, 2.512, 2.512
}
scale = 2.512

// --- node definitions ---
// definition format is Position X, Position Y, Position Z, Up X, Up Y, Up Z
node_stack_bottom = 0.0, -0.063, 0.0, 0.0, 1.0, 0.0,3
node_stack_top = 0.0, 0.063, 0.0, 0.0, 1.0, 0.0,3

part5m.cfg:

// --- asset parameters ---
MODEL
{
model = NovaPunch2/Parts/SAS/NP_SAS_1_25m/model
scale = 3.4096,3.4096,3.4096
}
scale = 3.4096

// --- node definitions ---
// definition format is Position X, Position Y, Position Z, Up X, Up Y, Up Z
node_stack_bottom = 0.0, -0.063, 0.0, 0.0, 1.0, 0.0,4
node_stack_top = 0.0, 0.063, 0.0, 0.0, 1.0, 0.0,4

Other than that, I've only checked the engine, launch escape, misc and RCS models from NP 2.06c and they show up fine.

I've computed the x,y,z scale values for the parts like this:

1.25m: 0+0.8 = 0.8000

2.50m: 1+0.8^2 = 1.6400

3.75m: 2+0.8^3 = 2.5120

5.00m: 3+0.8^4 = 3.4096

So if you need to fix other parts, try the values above for a start.

Also make sure that you remove any "rescalefactor=" line from the part.cfg and that "scale=" has the same value as the part's scale (this scales the attach nodes).

biohazard15 · October 10, 2014

Be careful with SAS - as I found out several months ago, there is a weird bug with their attach nodes, which makes some craft unstable.

Also, many models in NP use TGA textures, which is not recommended now due to bug in 0.25. Although I must say that I NEVER encountered any bug with TGA, 0.25 or earlier - but I use OpenGL.

wasmic · October 10, 2014

Be careful with SAS - as I found out several months ago, there is a weird bug with their attach nodes, which makes some craft unstable.
Also, many models in NP use TGA textures, which is not recommended now due to bug in 0.25. Although I must say that I NEVER encountered any bug with TGA, 0.25 or earlier - but I use OpenGL.

Still, .tga files use more than twice as much memory as .png and .mbm, as it turns out. So maybe just convert to .png anyway?

NathanKell · October 10, 2014

That's due to a loader bug. Please read this as there's enough misinformation about KSP and textures floating around...

slumpie · October 12, 2014

So if you need to fix other parts, try the values above for a start.
Also make sure that you remove any "rescalefactor=" line from the part.cfg and that "scale=" has the same value as the part's scale (this scales the attach nodes).

I strongly recommend to use rescaleFactor = 1, at least for all parts than can be used as first part on a vessel.

Or it will look ugly if you reload the scene.

Ph34rb0t · October 12, 2014

I strongly recommend to use rescaleFactor = 1, at least for all parts than can be used as first part on a vessel.
Or it will look ugly if you reload the scene.

Is this the same bug that is addressed for the stock parts with this mod?

http://forum.kerbalspaceprogram.com/threads/96339-0-25-StockScalingBugFix-V2-MM-Update-fixed-some-mishaps

slumpie · October 12, 2014

Yes, if you use anything else than rF = 1 that can be first part on a vessel.

Read:

http://forum.kerbalspaceprogram.com/threads/96339-0-25-StockScalingBugFix-V2-MM-Update-fixed-some-mishaps?p=1472218&viewfull=1#post1472218

It's a relatively rare bug (depends on the player) and some people might never encounter it, but for those who do it's annoying. Especially if it affects existing crafts.

Edited October 12, 2014 by slumpie

biohazard15 · October 12, 2014

Yeah, I recognize that bug. KW Rocketry and its 1.25m Vesta engine. I've had (and still have) a nice little ship that uses it; that engine was a first part in its subassembly. Man, that was a PLAGUE.

That being said, modders should refrain from using that "scale-rescale" stuff. They should apply KISS principle in case of such things.

[1.0.2] NovaPunch 2.09. - May 6th - 1.0 Compatibility Update

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation