[1.3 - 1.2.2] Collision FX v4.0 (2017-03-09) Now with biome coloured dust!

[pizzaoverhead]

  On 3/9/2017 at 10:54 PM, voicey99 said:

The latest release isn't on CF (is it still uploading?).

Also btw in the OP changelog it gives the V4 release date as 2016-03-09.

Expand  

Thanks, fixed.

  Quote

Collision FX v4.0    7.21 MB     1 hour ago     1.2.2 +2     0     Under Review

Expand  

Heh, sounds like someone at CurseForge is having the first bit of fun. It normally doesn't take long, probably within the hour.

 

Edit: GitHub release now available

Edited March 9, 2017 by pizzaoverhead

[Space Scumbag]

Oh yes! Thanks for the update. One of my favorite mods.

[Drew Kerman]

I'm guessing there won't be a conflict with Kerbal Foundries as that only handles ground effects for its own wheels and this one only affects stock?

[kerrigan778]

Will this mod work with mods that change the solar system and therefore have totally different biomes? ie Galileo's Planet Pack, RSS, Alternis Kerbol etc...

 

Thank you, love this mod, just hoping I can use it with my current modset.

[pizzaoverhead]

  On 3/14/2017 at 2:27 AM, kerrigan778 said:

Will this mod work with mods that change the solar system and therefore have totally different biomes? ie Galileo's Planet Pack, RSS, Alternis Kerbol etc...

 

Thank you, love this mod, just hoping I can use it with my current modset.

Expand  

Yes, it'll work fine. The dust trails will default to grey for bodies that don't have colours defined, but you can easily add the correct colours into the cfg file.

[Galileo]

  On 3/14/2017 at 2:16 PM, pizzaoverhead said:

Yes, it'll work fine. The dust trails will default to grey for bodies that don't have colours defined, but you can easily add the correct colours into the cfg file.

Expand  

I will have to add an mm cfg for this now as well  

i have a question though, if I wanted to create dust kicked up from rover wheels, is that possible? I assume you have the wheels disabled some how so that they aren't constantly "colliding" with the ground. Can I change that? If so can I use the available particles or would you reccomend a new particle effect?

Edited March 14, 2017 by Galileo

[voicey99]

  On 3/14/2017 at 2:16 PM, pizzaoverhead said:

Yes, it'll work fine. The dust trails will default to grey for bodies that don't have colours defined, but you can easily add the correct colours into the cfg file.

Expand  

How would you do that? I tried doing that for OPM bodies, but it didn't work (neither adding them into the main cfg or adding a separate cfg to the main OPM folder). Does it require a MM patch (and, if so, what would it look like)?

[pizzaoverhead]

  On 3/14/2017 at 2:53 PM, Galileo said:

I will have to add an mm cfg for this now as well  

i have a question though, if I wanted to create dust kicked up from rover wheels, is that possible? I assume you have the wheels disabled some how so that they aren't constantly "colliding" with the ground. Can I change that? If so can I use the available particles or would you reccomend a new particle effect?

Expand  

 

  On 3/14/2017 at 4:29 PM, voicey99 said:

How would you do that? I tried doing that for OPM bodies, but it didn't work (neither adding them into the main cfg or adding a separate cfg to the main OPM folder). Does it require a MM patch (and, if so, what would it look like)?

Expand  

At the moment, all new definitions have to go into settings.cfg. In future it could be made to load up any cfg in a set directory or similar. What has worked best for you with other mods?

Here's what the definitions would look like:

BodyDust
{
	name = Gael
	Biomes
	{
		EucriaShores = 0 0 0 0
		Highlands = 0 0 0 0
		IceCaps = 0 0 0 0
		Lowlands = 0 0 0 0
		Midlands = 0 0 0 0
		MinorShores = 0 0 0 0
		Mountains = 0 0 0 0
		PligiaShores = 0 0 0 0
		Reefs = 0 0 0 0
		Tundra = 0 0 0 0
		UakoraShores = 0 0 0 0
		Volcano = 0 0 0 0
		Midlands = 0 0 0 0
		EucriaShores = 0 0 0 0
		InlandWater = 0 0 0 0
		MinorShores = 0 0 0 0
		PligiaShores = 0 0 0 0
		Reefs = 0 0 0 0
		UakoraShores = 0 0 0 0
		Water = 0 0 0 0
	}
}

BodyDust
{
	name = Ceti
	Biomes
	{
		Highlands = 0 0 0 0
		Lowlands = 0 0 0 0
		Midlands = 0 0 0 0
		Plateaus = 0 0 0 0
		Poles = 0 0 0 0
	}
}
BodyDust
{
	name = Iota
	Biomes
	{
		Droops = 0 0 0 0
		Highlands = 0 0 0 0
		Lowlands = 0 0 0 0
		Midlands = 0 0 0 0
		Skids = 0 0 0 0
	}
}

The values are Red, Green Blue and Alpha (opacity), and can be specified in either decimals 0 - 1 or values from 0 to 255. For example, lime green would be "1  0.5  0  1" or "255  127  0  255", depending on whichever is easier for your workflow.

Edited March 14, 2017 by pizzaoverhead

[voicey99]

  On 3/14/2017 at 6:43 PM, pizzaoverhead said:

At the moment, all new definitions have to go into settings.cfg. In future it could be made to load up any cfg in a set directory or similar. What has worked best for you with other mods?

Here's what the definitions would look like:

<schnip>

The values are Red, Green Blue and Alpha (opacity), and can be specified in either decimals 0 - 1 or values from 0 to 255. For example, lime green would be "1  0.5  0  1" or "255  127  0  255", depending on whichever is easier for your workflow.

Expand  

I already have the cfg extension written out with all the values in decimal RGB-I'll test it out as soon as I get a gamebreaking planet-renaming bug fixed as last time I tried it it didn't work, though that was before it got updated.

[voicey99]

  On 3/14/2017 at 6:43 PM, pizzaoverhead said:

At the moment, all new definitions have to go into settings.cfg. In future it could be made to load up any cfg in a set directory or similar. What has worked best for you with other mods?

Here's what the definitions would look like:

<schnip>

The values are Red, Green Blue and Alpha (opacity), and can be specified in either decimals 0 - 1 or values from 0 to 255. For example, lime green would be "1  0.5  0  1" or "255  127  0  255", depending on whichever is easier for your workflow.

Expand  

Actually, I found why the dusts weren't working-they only show up on bodies with atmospheres (why non-atmospheric bodies have dust colours defined I don't know). As such, my extended config works perfectly-if anyone wants to use it, it's here.

Edited March 15, 2017 by voicey99

[GrapeInvaders]

1.2.2? WHAT?! 

[linuxgurugamer]

Two things:

First, does this support the new KSPWheel mod, which includes KerbalFounderies and Adjustable Landing Gear?

Second, would it be ok to add this to CKAN?

[TheRagingIrishman]

  On 4/19/2017 at 7:32 PM, linuxgurugamer said:

Two things:

First, does this support the new KSPWheel mod, which includes KerbalFounderies and Adjustable Landing Gear?

Second, would it be ok to add this to CKAN?

Expand  

Afaik KSPWheel does their own dust stuff without collision fx

[linuxgurugamer]

  On 4/19/2017 at 7:32 PM, linuxgurugamer said:

 

Second, would it be ok to add this to CKAN?

Expand  

@pizzaoverhead

Still waiting on an answer for this.  Apparently it used to be in CKAN, but got dropped when Kerbalstuff went away.  I'd just like confirmation that it's ok to add back.

Thanks

[StahnAileron]

  On 4/19/2017 at 7:32 PM, linuxgurugamer said:

[...] does this support the new KSPWheel mod, which includes KerbalFounderies and Adjustable Landing Gear?

Expand  

  On 4/19/2017 at 7:38 PM, TheRagingIrishman said:

Afaik KSPWheel does their own dust stuff without collision fx

Expand  

I've tried this with KF and I usually wind up with perpetual collision sounds and/or effects if anything happens to the wheels (the ALG ones specifically; haven't tried any others yet.) So I think there's some incompatibility between the two. I wound up removing this mod for the time being. (KF with ALG is far more useful.) I am considering making a personal patch to make it exclude anything using KSPWheel though to see if it helps. (This is just an effects module added to a part, no?)

 

 

[Nightside]

I had similar issues with this combo. I observed the ALG wheels would continue to glow after landing while Collision Effects was installed. I ended up abandoning that install for other reasons so I never unraveled that mystery.

[linuxgurugamer]

  On 4/20/2017 at 2:14 PM, StahnAileron said:

I've tried this with KF and I usually wind up with perpetual collision sounds and/or effects if anything happens to the wheels (the ALG ones specifically; haven't tried any others yet.) So I think there's some incompatibility between the two. I wound up removing this mod for the time being. (KF with ALG is far more useful.) I am considering making a personal patch to make it exclude anything using KSPWheel though to see if it helps. (This is just an effects module added to a part, no?)

 

 

Expand  

Could you post the patch when you have it done?

[linuxgurugamer]

  On 4/20/2017 at 2:14 PM, StahnAileron said:

I've tried this with KF and I usually wind up with perpetual collision sounds and/or effects if anything happens to the wheels (the ALG ones specifically; haven't tried any others yet.) So I think there's some incompatibility between the two. I wound up removing this mod for the time being. (KF with ALG is far more useful.) I am considering making a personal patch to make it exclude anything using KSPWheel though to see if it helps. (This is just an effects module added to a part, no?)

 

 

Expand  

This would probably do it, replace line 29 in the ModuleManager_CollisionFX.cfg with this:

@PART[*]:HAS[!MODULE[ModuleWheelBase],!MODULE[KerbalEVA],!MODULE[CollisionFX],!MODULE[FSwheel],!MODULE[FSwheelAlignment],!MODULE[BDAdjustableLandingGear],!MODULE[TTModularWheel],!MODULE[Repulsor],!MODULE[ModuleTrack],!MODULE[TrackWheel],!MODULE[KFModuleWheel],!MODULE[KFWheel],!MODULE[KFTrackSurface],!MODULE[KSPWheelBase],!MODULE[KSPWheelAdjustableGear],!MODULE[KSPWheelSteering],!MODULE[KSPWheelMotor],!MODULE[KSPWheelBrakes],!MODULE[KSPWheelDamage],!MODULE[KSPWheelDustEffects],!MODULE[KSPWheelSounds],!MODULE[KSPWheelConstraints]]

 

[linuxgurugamer]

  On 4/21/2017 at 1:06 AM, linuxgurugamer said:

This would probably do it, replace line 29 in the ModuleManager_CollisionFX.cfg with this:

@PART[*]:HAS[!MODULE[ModuleWheelBase],!MODULE[KerbalEVA],!MODULE[CollisionFX],!MODULE[FSwheel],!MODULE[FSwheelAlignment],!MODULE[BDAdjustableLandingGear],!MODULE[TTModularWheel],!MODULE[Repulsor],!MODULE[ModuleTrack],!MODULE[TrackWheel],!MODULE[KFModuleWheel],!MODULE[KFWheel],!MODULE[KFTrackSurface],!MODULE[KSPWheelBase],!MODULE[KSPWheelAdjustableGear],!MODULE[KSPWheelSteering],!MODULE[KSPWheelMotor],!MODULE[KSPWheelBrakes],!MODULE[KSPWheelDamage],!MODULE[KSPWheelDustEffects],!MODULE[KSPWheelSounds],!MODULE[KSPWheelConstraints]]

 

Expand  

@pizzaoverhead

Two things.

First, the patch have here will prevent this from being attached to anything with KSPWheel, apparently it already does this and there is some sort of incompatibility there.

Second, is it ok to add this back to CKAN?

Thanks

[Matchlight]

It didn't work, I may have installed it incorrectly but it is just as simple as dragging the collision fx folder into GameData right? No dependencies or other folders that need dragging in? 

 

It just didn't work for me, is it possible its incompatible with OS X?

[hieywiey]

  On 4/26/2017 at 2:28 PM, Matchlight said:

It didn't work, I may have installed it incorrectly but it is just as simple as dragging the collision fx folder into GameData right? No dependencies or other folders that need dragging in? 

 

It just didn't work for me, is it possible its incompatible with OS X?

Expand  

It is fully compatible with macOS Sierra, as that is what I am using right now. Very few mods are incompatible with certain OSes, and the ones that are usually require an external application, require certain hardware and/or graphics capabilities, like Scatterer, or make significant changes to how the game runs, like Principia, which completely replaces KSP's physics. So, yes, you likely installed it incorrectly. Double click on "CollisionFXv4.0.zip", and open the extracted folder. Open the GameData folder inside and select the "CollisionFX" folder, and copy it (press ⌘C). Then go to your KSP folder, open the GameData folder inside, and paste (press ⌘V). Now boot up KSP!

[Matchlight]

  On 4/26/2017 at 11:22 PM, hieywiey said:

It is fully compatible with macOS Sierra, as that is what I am using right now. Very few mods are incompatible with certain OSes, and the ones that are usually require an external application, require certain hardware and/or graphics capabilities, like Scatterer, or make significant changes to how the game runs, like Principia, which completely replaces KSP's physics. So, yes, you likely installed it incorrectly. Double click on "CollisionFXv4.0.zip", and open the extracted folder. Open the GameData folder inside and select the "CollisionFX" folder, and copy it (press ⌘C). Then go to your KSP folder, open the GameData folder inside, and paste (press ⌘V). Now boot up KSP!

Expand  

 

Thats exactly what I did!

[Smarti]

Hi. What about part Mods like Near Future? Do these parts also produce dust and all? Or what is for example with added landing gears?

Thank you.

Edited April 29, 2017 by Smarti

[Iamsodarncool]

are there plans to update this to 1.3?

[pizzaoverhead]

  On 5/29/2017 at 10:33 PM, Iamsodarncool said:

are there plans to update this to 1.3?

Expand  

Yes, any mod that's broken will be updated. Are you having issues with this mod under 1.3?