Jump to content

[0.90] TweakScale - Rescale Everything! (v1.50 - 2014-12-24 10:40 UTC)

Biotronic

By Biotronic
in KSP1 Mod Releases

 Share

Recommended Posts

Remi

Remi

Posted
Posted

Hi. I wonder if someone can help.

I am trying to get tweakscale working with Karbonite fuels tanks. For some reason the tweak settings never show up. I have the latest Karbonite and tweakscale release.

Other fueltanks work, just not Karbonite tanks. Can anyone think of what I am doing wrong?

Link to comment
Share on other sites
Apollo13

Apollo13

Posted
Posted (edited)
Hi. I wonder if someone can help.

I am trying to get tweakscale working with Karbonite fuels tanks. For some reason the tweak settings never show up. I have the latest Karbonite and tweakscale release.

Other fueltanks work, just not Karbonite tanks. Can anyone think of what I am doing wrong?

Most part names in the TweakScale file are incorrect. For instance, the Karbonite Detection Array in the part.cfg is named "KA_DetectionArray_01". In the Karbonite_TweakScale.cfg file, it is "Karbonite_Antenna"

Secondly, only one tank, the KA-200 Karbonite Tank, is in the Karbonite_TweakScale.cfg file.

Edited by Apollo13
Link to comment
Share on other sites
Remi

Remi

Posted
Posted (edited)
Fails for me as well.

All the part names in the TweakScale file are wrong. For instance, the Karbonite Detection Array in the part.cfg is named "KA_DetectionArray_01". In the Karbonite_TweakScale.cfg file, it is "Karbonite_Antenna"

Secondly, there only the KA-200 Karbonite Tank in the Karbonite_TweakScale.cfg file.

yeah I just noticed this too. Looks like the tweakscale cfg for Karbonite is based on a previous release. I am having a look at how much work it is to convert it now.

Edit:

It doesn't look too hard to bring it up to date. I might go ahead and do that, unless someone on the karbonite thread already has a new one.

Edited by Remi
Link to comment
Share on other sites
AccidentalDisassembly

AccidentalDisassembly

Posted
Posted
yeah I just noticed this too. Looks like the tweakscale cfg for Karbonite is based on a previous release. I am having a look at how much work it is to convert it now.

Edit:

It doesn't look too hard to bring it up to date. I might go ahead and do that, unless someone on the karbonite thread already has a new one.

I put one out in the Dev forum. Or here: https://dl.dropboxusercontent.com/u/59567837/Karbonite_TweakScale.cfg

Requires this: https://dl.dropboxusercontent.com/u/59567837/ExtendedScaletypes.cfg

Link to comment
Share on other sites
SorensonPA

SorensonPA

Posted
Posted (edited)

I've been trying to get SCANSat to work with TweakScale, and since search isn't being helpful as to whether it's something in SCANSat itself or me hosing something up file-side figured I may as well ask here. Added the function to ScaleExponents:

TWEAKSCALEEXPONENTS
{
    name = SCANsat
    max_alt = 3;
    best_alt = 3;
    power = 3;
}

and duped and formatted a part configuration file:

@PART[SCANSat_Scanner] // SCAN RADAR Altimetry Sensor
{
	MODULE
	{
		name = TweakScale
		type = surface
	}
}

@PART[SCANSat_Scanner2] // SCAN SAR Altimetry Sensor
{
	MODULE
	{
		name = TweakScale
		type = surface
	}
}

@PART[SCANSat_Scanner24] // SCAN Multispectral Sensor
{
	MODULE
	{
		name = TweakScale
		type = surface
	}
}

@PART[SCANSat_Scanner32] // SCAN Been There Done That®
{
	MODULE
	{
		name = TweakScale
		type = surface
	}
}

but no dice.

EDIT: Of all the stupid crap to get caught on, it's letter case. :facepalm: Well, thanks for spotting that.

Edited by SorensonPA
Link to comment
Share on other sites
Biotronic

Biotronic

Posted
  • Author
Posted (edited)
I've been trying to get SCANSat to work with TweakScale, and since search isn't being helpful as to whether it's something in SCANSat itself or me hosing something up file-side figured I may as well ask here. Added the function to ScaleExponents:

TWEAKSCALEEXPONENTS
{
    name = SCANsat
    max_alt = 3;
    best_alt = 3;
    power = 3;
}

and duped and formatted a part configuration file:

@PART[SCANSat_Scanner] // SCAN RADAR Altimetry Sensor
{
	MODULE
	{
		name = TweakScale
		type = surface
	}
}

@PART[SCANSat_Scanner2] // SCAN SAR Altimetry Sensor
{
	MODULE
	{
		name = TweakScale
		type = surface
	}
}

@PART[SCANSat_Scanner24] // SCAN Multispectral Sensor
{
	MODULE
	{
		name = TweakScale
		type = surface
	}
}

@PART[SCANSat_Scanner32] // SCAN Been There Done That®
{
	MODULE
	{
		name = TweakScale
		type = surface
	}
}

but no dice.

Two things. The part names are wrong (SCANSat should be SCANsat), and the exponents should not have a semicolon. In addition, I really think you should add min_alt to the exponents. Fixed:

TWEAKSCALEEXPONENTS
{
    name = SCANsat
    max_alt = 3
    min_alt = 3
    best_alt = 3
    power = 3
}

@PART[SCANsat_Tracker] // SCAN MapTraq®
{
	MODULE
	{
		name = TweakScale
		type = surface
	}
}
@PART[SCANsat_Scanner] // SCAN RADAR Altimetry Sensor
{
	MODULE
	{
		name = TweakScale
		type = surface
	}
}
@PART[SCANsat_Scanner2] // SCAN SAR Altimetry Sensor
{
	MODULE
	{
		name = TweakScale
		type = surface
	}
}
@PART[SCANsat_Scanner24] // SCAN Multispectral Sensor
{
	MODULE
	{
		name = TweakScale
		type = surface
	}
}
@PART[SCANsat_Scanner32] // SCAN Been There Done That®
{
	MODULE
	{
		name = TweakScale
		type = surface
	}
}

Edited by Biotronic
Link to comment
Share on other sites
Biotronic

Biotronic

Posted
  • Author
Posted
Biotronic, can you change current intercation with RealFuels? Try to get maxThrust values dynamically to avoid situation with resetting to defaults after relaunch or changing techlevel.

RealFuels support is limited to tank volume at the moment. It seems NathanKell will assume ownership of TweakScale_RealFuels in the future, and I hope he will add support for engines.

Link to comment
Share on other sites
mecki

mecki

Posted
Posted
mecki,

Can you test that with just KSP-AVC and TweakScale? If that still causes the freeze, take a look at your output log to see what's causing the problem.

hm… Sometimes it works, sometimes it doesn't… Will keep you updated!

Sorry, didn't want to cause any stir.

Link to comment
Share on other sites
Sokar408

Sokar408

Posted
Posted (edited)

This messes up KW engines badly by making the attachment nodes sit a good bit above the model itself. Anyway to quick fix this?

(I have deleted the Tweakscale for KW, as a temperarily fix)

Edited by Sokar408
Link to comment
Share on other sites
Master Tao

Master Tao

Posted
Posted

mecki,

Thanks for posting the correct log. It says KSP is running out of memory – that's the error related to "malloc" at the end of the log. I think it's just a coincidence that the crash happens while loading TweakScale. Try removing EVE (EnvironmentalVisualEnhancements + BoulderCo). If that solves the problem, you might be able to cram the clouds back in by changing to ActiveTextureManagement - Aggressive. You could also halve the size of the cloud textures in KSP/GameData/BoulderCo/Clouds/Textures/. You want to make anything over 10 MB smaller – scaling them so the height is 2048 px is a good idea.

Link to comment
Share on other sites
mecki

mecki

Posted
Posted
mecki,

Thanks for posting the correct log. It says KSP is running out of memory – that's the error related to "malloc" at the end of the log. I think it's just a coincidence that the crash happens while loading TweakScale. Try removing EVE (EnvironmentalVisualEnhancements + BoulderCo). If that solves the problem, you might be able to cram the clouds back in by changing to ActiveTextureManagement - Aggressive. You could also halve the size of the cloud textures in KSP/GameData/BoulderCo/Clouds/Textures/. You want to make anything over 10 MB smaller – scaling them so the height is 2048 px is a good idea.

Damn! I'm already using ATM–Aggressive. Maybe I'll make the textures smaller then.

Didn't think that I had that many parts mods…

Thank you for pointing me in the right direction, I never really know which line of the logs are relevant!

Link to comment
Share on other sites
Master Tao

Master Tao

Posted
Posted

That's definitely a case where programming experience helps. I've used the malloc function, so I know it stands for (memory+allocate).

And the clouds are just huge, so it doesn't much matter how many parts you're using.

Link to comment
Share on other sites
aphenine

aphenine

Posted
Posted

I have a question regarding TweakScale and compatibility with the B9 Aerospace parts mod. I've had a look at the TweakScale config for B9 and it looks complete and professionally done. However, the scale tweaking stops at any of the chassis types. I'm thinking this is deliberate and I was wondering, is there any reason for this? Did someone try letting TweakScale work on them and did it work?

Link to comment
Share on other sites
AccidentalDisassembly

AccidentalDisassembly

Posted
Posted
I have a question regarding TweakScale and compatibility with the B9 Aerospace parts mod. I've had a look at the TweakScale config for B9 and it looks complete and professionally done. However, the scale tweaking stops at any of the chassis types. I'm thinking this is deliberate and I was wondering, is there any reason for this? Did someone try letting TweakScale work on them and did it work?

Works fine for basically all parts, so far as I can tell. I created my own custom config for it that produces abominations such as 6x scaled cargo bays. Seems not to break anything! May or may not look good when you try to mate these to other parts without additional adapters with ratios that don't exist in B9.

Link to comment
Share on other sites
Biotronic

Biotronic

Posted
  • Author
Posted
I have a question regarding TweakScale and compatibility with the B9 Aerospace parts mod. I've had a look at the TweakScale config for B9 and it looks complete and professionally done. However, the scale tweaking stops at any of the chassis types. I'm thinking this is deliberate and I was wondering, is there any reason for this? Did someone try letting TweakScale work on them and did it work?

I see no reason for it not to work, I just feel it doesn't make as much sense - there are so windows and other doodads that look weird to me when they're twice the size of the people who use them. Also, IVAs are not scaled, which saddens me (but would of course make no sense whatsoever).

Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...