thiagohdf

January 9, 2017

Ok, I understand, but I guess I was not clear on my explanation.
Is my CFG correct? The example I posted it changed exactly what I wanted, as you said. But it is not working as it should. I only have the sound effect, but not the RCS thrusters ...
Is there something missing? Could you tell me?

Thanks for your time.

January 9, 2017

Hello everyone!
I created a cfg to apply the ModuleRCSFX to my old parts.

@PART[*]:HAS[@MODULE[ModuleRCS],!MODULE[ModuleRCSFX]]:Final
{
	@MODULE[ModuleRCS]
	{
		@name = ModuleRCSFX
                runningEffectName = running
	}
	EFFECTS
	{
        	running
	        {
               		AUDIO
                	{
                   		channel = Ship
                 		clip = sound_rocket_mini
                 		volume = 0.0 0.0
                 		volume = 0.1 0.0
                 		volume = 0.5 0.025
                 		volume = 1.0 0.1
                 		pitch = 0.0 0.75
                 		pitch = 1.0 1.5
                 		loop = true
                	}
			MODEL_MULTI_PARTICLE
			{
				modelName = Squad/FX/Monoprop_small
				transformName = RCSthruster
				emission = 0.0 0.0
				emission = 0.1 0.0
				emission = 1.0 1.0
				speed = 0.0 0.8
				speed = 1.0 1.0
				localRotation = -90, 0, 0
			}
            	}
    	}
}

But it only ran on parts that are RCS blocks, but it did not work primarily on capsules and cokpits with rcs.
Directly from ModuleManager.ConfigCache, an example of a part where it did not work:

Spoiler


PART
{
// --- general parameters ---
	name = NoseCone
	module = Part
	author = Pete (Pak)
	
// --- asset parameters ---
	MODEL
	{
	model = Cormorant Aeronology/Assets/NoseCone
	}
	rescaleFactor = 1
// --- definition format is Position X, Position Y, Position Z, Up X, Up Y, Up Z	
	node_stack_bottom = 0.0, -0.07, 0.11, 0.0, -1.0, 0.0, 1
	
// --- node definitions ---
	TechRequired = experimentalAerodynamics
	entryCost = 25000
	cost = 3800
	category = Aero
	subcategory = 0
	title = CA - Forward Reaction Control System
	manufacturer = Cormorant Aeronology
	description = Full Nose Cone for the Shuttle Lifting Body comes equipped with 14 RCS thrusters and an ample amount of MonoPropellent

// attachment rules: stack, srfAttach, allowStack, allowSrfAttach, allowCollision
	attachRules = 1,0,1,1,0
	
// --- standard part parameters ---
	mass = 0.6
	dragModelType = default
	maximum_drag = 0.01
	minimum_drag = 0.01
	angularDrag = 0.1
	crashTolerance = 50
	maxTemp = 2800
	vesselType = Ship
	bulkheadProfiles = size2
	breakingForce = 50
	breakingTorque = 50

	RESOURCE
	{
		name = MonoPropellant
		amount = 300
		maxAmount = 300
	}
	
	MODULE
{
	name = ModuleRCSFX
	thrusterTransformName = RCSthruster
	thrusterPower = 2
	resourceName = MonoPropellant
	resourceFlowMode = STAGE_PRIORITY_FLOW
runningEffectName = running
	atmosphereCurve
 	{
   	 key = 0 275
  	 key = 1 125
         key = 4 0.001
 	}
}
EFFECTS
	{
        	running
	        {
               		AUDIO
                	{
                   		channel = Ship
                 		clip = sound_rocket_mini
                 		volume = 0.0 0.0
                 		volume = 0.1 0.0
                 		volume = 0.5 0.025
                 		volume = 1.0 0.1
                 		pitch = 0.0 0.75
                 		pitch = 1.0 1.5
                 		loop = true
                	}
			MODEL_MULTI_PARTICLE
			{
				modelName = Squad/FX/Monoprop_small
				transformName = RCSthruster
				emission = 0.0 0.0
				emission = 0.1 0.0
				emission = 1.0 1.0
				speed = 0.0 0.8
				speed = 1.0 1.0
				localRotation = -90, 0, 0
			}
            	}
    	}

	MODULE
	{
		name = ModuleReactionWheel
		PitchTorque = 45
		YawTorque = 20
		
		RESOURCE
		{
			name = ElectricCharge
			rate = 0.06
		}
}

What should I do?

Thanks.

January 6, 2017

Ok thanks, in some parts worked, but in others only the audio effect is working. Cfg looks like this:

@PART[*]:HAS[@MODULE[ModuleRCS],!MODULE[ModuleRCSFX]]:Final
{
	@MODULE[ModuleRCS]
	{
		@name = ModuleRCSFX
                runningEffectName = running
	}
	EFFECTS
	{
        	running
	        {
               		AUDIO
                	{
                   		channel = Ship
                 		clip = sound_rocket_mini
                 		volume = 0.0 0.0
                 		volume = 0.1 0.0
                 		volume = 0.5 0.025
                 		volume = 1.0 0.1
                 		pitch = 0.0 0.75
                 		pitch = 1.0 1.5
                 		loop = true
                	}
			MODEL_MULTI_PARTICLE
			{
				modelName = Squad/FX/Monoprop_small
				transformName = RCSthruster
				emission = 0.0 0.0
				emission = 0.1 0.0
				emission = 1.0 1.0
				speed = 0.0 0.8
				speed = 1.0 1.0
				localRotation = -90, 0, 0
			}
            	}
    	}
}

It only ran on parts that are RCS blocks, but it did not works primarily on capsules and cokpits with rcs.
Directly from ModuleManager.ConfigCache, an example of a part where it did not work:

Spoiler


PART
{
// --- general parameters ---
	name = NoseCone
	module = Part
	author = Pete (Pak)
	
// --- asset parameters ---
	MODEL
	{
	model = Cormorant Aeronology/Assets/NoseCone
	}
	rescaleFactor = 1
// --- definition format is Position X, Position Y, Position Z, Up X, Up Y, Up Z	
	node_stack_bottom = 0.0, -0.07, 0.11, 0.0, -1.0, 0.0, 1
	
// --- node definitions ---
	TechRequired = experimentalAerodynamics
	entryCost = 25000
	cost = 3800
	category = Aero
	subcategory = 0
	title = CA - Forward Reaction Control System
	manufacturer = Cormorant Aeronology
	description = Full Nose Cone for the Shuttle Lifting Body comes equipped with 14 RCS thrusters and an ample amount of MonoPropellent

// attachment rules: stack, srfAttach, allowStack, allowSrfAttach, allowCollision
	attachRules = 1,0,1,1,0
	
// --- standard part parameters ---
	mass = 0.6
	dragModelType = default
	maximum_drag = 0.01
	minimum_drag = 0.01
	angularDrag = 0.1
	crashTolerance = 50
	maxTemp = 2800
	vesselType = Ship
	bulkheadProfiles = size2
	breakingForce = 50
	breakingTorque = 50

	RESOURCE
	{
		name = MonoPropellant
		amount = 300
		maxAmount = 300
	}
	
	MODULE
{
	name = ModuleRCSFX
	thrusterTransformName = RCSthruster
	thrusterPower = 2
	resourceName = MonoPropellant
	resourceFlowMode = STAGE_PRIORITY_FLOW
runningEffectName = running
	atmosphereCurve
 	{
   	 key = 0 275
  	 key = 1 125
         key = 4 0.001
 	}
}
EFFECTS
	{
        	running
	        {
               		AUDIO
                	{
                   		channel = Ship
                 		clip = sound_rocket_mini
                 		volume = 0.0 0.0
                 		volume = 0.1 0.0
                 		volume = 0.5 0.025
                 		volume = 1.0 0.1
                 		pitch = 0.0 0.75
                 		pitch = 1.0 1.5
                 		loop = true
                	}
			MODEL_MULTI_PARTICLE
			{
				modelName = Squad/FX/Monoprop_small
				transformName = RCSthruster
				emission = 0.0 0.0
				emission = 0.1 0.0
				emission = 1.0 1.0
				speed = 0.0 0.8
				speed = 1.0 1.0
				localRotation = -90, 0, 0
			}
            	}
    	}

	MODULE
	{
		name = ModuleReactionWheel
		PitchTorque = 45
		YawTorque = 20
		
		RESOURCE
		{
			name = ElectricCharge
			rate = 0.06
		}
}

What do you think?
Thanks.

January 6, 2017

I was wanting to add the new RCS sound effects of KSP 1.2 to how my old parts and command modules, how would it be?

@PART[*]:HAS[@MODULE[ModuleRCS]]:FINAL
{
MODULE
   {
      runningEffectName = running
   }
EFFECTS
   {
       running
           {
               AUDIO
               {
               channel = Ship
               clip = sound_rocket_mini
               volume = 0.0 0.0
               volume = 0.1 0.0
               volume = 0.5 0.025
               volume = 1.0 0.1
               pitch = 0.0 0.75
               pitch = 1.0 1.5
               loop = true
               }
           }
   }
}

What is wrong?

April 26, 2016

On 22/01/2015 at 8:12 AM, Divico said:

Temporary location of the two new LP's:

Divico has any chance you provide the KSC in the above format? I wanted very much to play with several pads at KSC like NASA KSC 39A and 39B.
PS .: I am using Kosmodrome here at KSP 1.1 x64 Win without any problem! Excellent job!

December 11, 2015

23 hours ago, milbournosphere said:

I'm having issues with SDHI in 1.0.5, probably due to issues with the decoupler dependency. The primary faring does not fire when toggled, and when triggered on the pad, the faring fell down to the ground through the ship and exploded.

Exactly the same problem here. If someone wants to analyze my logs would be happy to send.

May 19, 2015

I have not tested the 1.0 version, updated by the steam directly from version 0.90 to 1.0.2 and i have problems with the launch clamps appearing in mid air following rocket.

I tested and it occurs with or without mods installed. Also tested it with a clean install and the same bug occurs.

My problem is exactly the same as the description here: http://bugs.kerbalspaceprogram.com/issues/4874

"I first noticed it when trying to fly a huge ship (almost 2000 parts, see attached image including clamps), then I reduced it to around 500 parts of initial setup. The issue is deterministically reproducible on my PC but might depend on how powerful the PC is.
In the described case, launch clamps appear at 6000, 12000, 18000, and 24000 meters, then if I keep switching between ship and them they spawn near the ship and follow it. They are material and can destroy the ship if it rotates in a way that makes them spawn over ship's parts.
The scenario is harder to reproduce or fails to reproduce with less parts - suggests it's some kind of race condition where cleanup of physics frame does not finish before it is used or something like that." - Description Bug # 4874

Javascript is disabled. View full album

This problem already have some solution?

The "Stock Bug Fix Modules (v1.0.2d.3 Release - 18 May 15)" fixes this bug?

Thanks!

July 18, 2014

AIES Aerospace v1.5.1 is not working in 0.24 ksp x64 Win!

June 24, 2014

I believe I have found a way to make KSP.exe access up to 4.0 GB using PAE. Just when the KSP came to 3.3GB of RAM in use just after the game crashed! Until the Unity Player for Windows 64Bit be stable and Squad staff of the KSP release 64 for Windows, as follow the next tip:

A brief explanation: In 32 bit systems each process and the operating system itself is able to address up to 4GB of RAM, due to bad hardware reserves that limit falls between 3.2 to 3.8 depending on the configuration. This applies to any OS be it Windows, Linux or Mac Using PAE process can use up to 4gb 8gb depending on how the program is done even though it is 32 bits. Just run the Patch in 2 files. Mono.dll and KSP.exe

modo.dll on: "<Your installation folder KSP>\KSP_Data\Mono\mono.dll"

KSP.exe on: "<Your installation folder KSP>\KSP.exe"

Do not forget to make a backup first in case something goes wrong!

Doing this my KSP began using maximum 4Gb, and has not yet crash ... (yet! )

Earn 500mb-700mb or more is too much!

If you want to know more about the limits of memory addressing on 32-bit systems and PAE search on Google.

Download the program to the pach: http://www.ntcore.com/4gb_patch.php

Here is still running smooth with: Active Texture Management, Visual Astronomer's Pack V3 and many many many many other mods. :sticktongue:

Sign In

thiagohdf

Posts

Joined

Last visited

Content Type

Profiles

Forums

Developer Articles

KSP2 Release Notes

Bug Reports

Posts posted by thiagohdf

[1.8.x-1.12.x] Module Manager 4.2.3 (July 03th 2023) - Fireworks season

[1.8.x-1.12.x] Module Manager 4.2.3 (July 03th 2023) - Fireworks season

Module manager exampels

Module manager exampels

[1.0.5] Kosmodrome - Space Centre v1.0 Career Edition (24.02.2016)

[1.10.x] SDHI Service Module System (V4.0.4 / 11 October 2020)

Launch clamps Bug

0.24 Mod Compatibility Testing

[0.90] Kerbin Shuttle Orbiter System v4.13

Forum

Activity

Community

Mods

Social Media