Jump to content

[1.3.x] CONTARES 1.8.9 closed


hraban

Recommended Posts

1 hour ago, hraban said:

jep, looks like ModuleManager ignore the NEEDS parameter. So please, remove the "CONTARES_extra_RT2.cfg" in "\Contares\Patches" when RemoteTech is not installed.

Thank you!

Took the liberty to ask about it in the ModuleManager thread, what little i know of Modulemanager scripting wasn't right.

EDIT: And hour later, your patches are fine, it's the patches of the Origami antennas that uses a FOR instead of a NEEDS. It created a condition where the Remotetech patches were applied. 

 

Edited by Mokmo
Link to comment
Share on other sites

3 hours ago, hraban said:

You mean the Toadicus mod AntennaRange?

Yes thats the mod i meant. I'll try to create a module manager script if i find the time. Can you give me some rough information about what range each antenna is designed for?

Link to comment
Share on other sites

10 minutes ago, Tantalus said:

Yes thats the mod i meant. I'll try to create a module manager script if i find the time. Can you give me some rough information about what range each antenna is designed for?

The maximum range you can find in the RT2 config. Take it as base for AntennaRange so both mods works with nearly identical parameters.

Link to comment
Share on other sites

littel wish ckan have a problem with overwrite existen file. I can not install or upgrade example: Contares CA-1 Canadian Arrow Suborbital Space-Tourist-Launcher 1.0 when other modul have install first this: CONTARES_TweakScale.cfg

have follow bug message: 

Spoiler


Oh no! We tried to overwrite a file owned by another mod!
Please try a `ckan update` and try again.

If this problem re-occurs, then it maybe a packaging bug.
Please report it at:

https://github.com/KSP-CKAN/CKAN-meta/issues/new

Please including the following information in your report:

File           : GameData/Contares/Patches/CONTARES_TweakScale.cfg
Installing Mod : ContaresCA1CanadianArrow 1.0
Owning Mod     : Contares-Antennas
CKAN Version   : v1.16.1-0-g2e91715 (beta)

Your GameData has been returned to its original state.
 

 

Link to comment
Share on other sites

5 minutes ago, Prismatech said:

littel wish ckan have a problem with overwrite existen file. I can not install or upgrade example: Contares CA-1 Canadian Arrow Suborbital Space-Tourist-Launcher 1.0 when other modul have install first this: CONTARES_TweakScale.cfg

have follow bug message: 

  Reveal hidden contents


Oh no! We tried to overwrite a file owned by another mod!
Please try a `ckan update` and try again.

If this problem re-occurs, then it maybe a packaging bug.
Please report it at:

https://github.com/KSP-CKAN/CKAN-meta/issues/new

Please including the following information in your report:

File           : GameData/Contares/Patches/CONTARES_TweakScale.cfg
Installing Mod : ContaresCA1CanadianArrow 1.0
Owning Mod     : Contares-Antennas
CKAN Version   : v1.16.1-0-g2e91715 (beta)

Your GameData has been returned to its original state.
 

 

Please, if you have problems with CKAN, diskuss that in the CKAN thread. If you want a clear functional installation then install manual.

Link to comment
Share on other sites

no you can help with littel work files that any modul from you use place example contares common modul and all only modulfiles in the modul that debind problem for overwrite that ckan not can. i have him ask to build in a overwrite function on demand or wish. he have say that he can that not do. sorry for bad english.

Edited by Prismatech
Link to comment
Share on other sites

11 minutes ago, Prismatech said:

no you can help with littel work files that any modul from you use place example contares common modul and all only modulfiles in the modul that debind problem for overwrite that ckan not can. i have him ask to build in a overwrite function on demand or wish. he have say that he can that not do. sorry for bad english.

There are two options:

1. CKAN learn to manage additional/incremental mods and handle overwrite by file-creation-date without additional work.
or
2. Contares stop using CKAN.

Link to comment
Share on other sites

16 hours ago, hraban said:

The maximum range you can find in the RT2 config. Take it as base for AntennaRange so both mods works with nearly identical parameters.

I've used your RT2-values, but RT2 seems to use a different reference frame for calculating the effective range than AR. I've made a quick-n-dirty module manager config, most values (MaxPowerFactor, MaxDataFactor) still need to be tweaked:

@PART[FFDM]:FOR[AntennaRange]
{
	@MODULE[ModuleDataTransmitter]
	{
		@name = ModuleLimitedDataTransmitter
		nominalRange = 55000000
		simpleRange = 55000000
		maxPowerFactor = 8
		maxDataFactor = 4
	}

	MODULE
	{
		name = ModuleScienceContainer

		dataIsCollectable = true
		dataIsStorable = false

		storageRange = 2
	}
}


@PART[HG_spiral]:FOR[AntennaRange]
{
	@MODULE[ModuleDataTransmitter]
	{
		@name = ModuleLimitedDataTransmitter
		nominalRange = 55000000
		simpleRange = 55000000
		maxPowerFactor = 8
		maxDataFactor = 4
	}

	MODULE
	{
		name = ModuleScienceContainer

		dataIsCollectable = true
		dataIsStorable = false

		storageRange = 2
	}
}

@PART[IS18D]:FOR[AntennaRange]
{
	@MODULE[ModuleDataTransmitter]
	{
		@name = ModuleLimitedDataTransmitter
		nominalRange = 30000000
		simpleRange = 30000000
		maxPowerFactor = 8
		maxDataFactor = 4
	}

	MODULE
	{
		name = ModuleScienceContainer

		dataIsCollectable = true
		dataIsStorable = false

		storageRange = 2
	}
}


@PART[K-Sensor]:FOR[AntennaRange]
{
	@MODULE[ModuleDataTransmitter]
	{
		@name = ModuleLimitedDataTransmitter
		nominalRange = 30000000
		simpleRange = 30000000
		maxPowerFactor = 8
		maxDataFactor = 4
	}

	MODULE
	{
		name = ModuleScienceContainer

		dataIsCollectable = true
		dataIsStorable = false

		storageRange = 2
	}
}

@PART[MABA20m]:FOR[AntennaRange]
{
	@MODULE[ModuleDataTransmitter]
	{
		@name = ModuleLimitedDataTransmitter
		nominalRange = 30000000
		simpleRange = 30000000
		maxPowerFactor = 8
		maxDataFactor = 4
	}

	MODULE
	{
		name = ModuleScienceContainer

		dataIsCollectable = true
		dataIsStorable = false

		storageRange = 2
	}
}

@PART[PAFF1]:FOR[AntennaRange]
{
	@MODULE[ModuleDataTransmitter]
	{
		@name = ModuleLimitedDataTransmitter
		nominalRange = 10000000000
		simpleRange = 10000000000		
		maxPowerFactor = 8
		maxDataFactor = 4
	}

	MODULE
	{
		name = ModuleScienceContainer

		dataIsCollectable = true
		dataIsStorable = false

		storageRange = 2
	}
}

@PART[QuadDish]:FOR[AntennaRange]
{
	@MODULE[ModuleDataTransmitter]
	{
		@name = ModuleLimitedDataTransmitter
		nominalRange = 60000000000
		simpleRange = 60000000000
		maxPowerFactor = 20
		maxDataFactor = 4
	}

	MODULE
	{
		name = ModuleScienceContainer

		dataIsCollectable = true
		dataIsStorable = false

		storageRange = 2
	}
}

@PART[RadAlt]:FOR[AntennaRange]
{
	@MODULE[ModuleDataTransmitter]
	{
		@name = ModuleLimitedDataTransmitter
		nominalRange = 15000000
		simpleRange = 15000000
		maxPowerFactor = 8
		maxDataFactor = 4
	}

	MODULE
	{
		name = ModuleScienceContainer

		dataIsCollectable = true
		dataIsStorable = false

		storageRange = 2
	}
}




@PART[S_C_Dish]:FOR[AntennaRange]
{
	@MODULE[ModuleDataTransmitter]
	{
		@name = ModuleLimitedDataTransmitter
		nominalRange = 10000000000
		simpleRange = 10000000000
		maxPowerFactor = 8
		maxDataFactor = 4
	}

	MODULE
	{
		name = ModuleScienceContainer

		dataIsCollectable = true
		dataIsStorable = false

		storageRange = 2
	}
}

@PART[S_GPS_Dish]:FOR[AntennaRange]
{
	@MODULE[ModuleDataTransmitter]
	{
		@name = ModuleLimitedDataTransmitter
		nominalRange = 30000000
		simpleRange = 30000000
		maxPowerFactor = 8
		maxDataFactor = 4
	}

	MODULE
	{
		name = ModuleScienceContainer

		dataIsCollectable = true
		dataIsStorable = false

		storageRange = 2
	}
}

@PART[S_HAHM_P]:FOR[AntennaRange]
{
	@MODULE[ModuleDataTransmitter]
	{
		@name = ModuleLimitedDataTransmitter
		nominalRange = 60000000
		simpleRange = 60000000
		maxPowerFactor = 8
		maxDataFactor = 4
	}

	MODULE
	{
		name = ModuleScienceContainer

		dataIsCollectable = true
		dataIsStorable = false

		storageRange = 2
	}
}

@PART[S_YAGI_TV]:FOR[AntennaRange]
{
	@MODULE[ModuleDataTransmitter]
	{
		@name = ModuleLimitedDataTransmitter
		nominalRange = 15000000
		simpleRange = 15000000
		maxPowerFactor = 8
		maxDataFactor = 4
	}

	MODULE
	{
		name = ModuleScienceContainer

		dataIsCollectable = true
		dataIsStorable = false

		storageRange = 2
	}
}

@PART[SARL]:FOR[AntennaRange]
{
	@MODULE[ModuleDataTransmitter]
	{
		@name = ModuleLimitedDataTransmitter
		nominalRange = 20000000
		simpleRange = 20000000
		maxPowerFactor = 8
		maxDataFactor = 4
	}

	MODULE
	{
		name = ModuleScienceContainer

		dataIsCollectable = true
		dataIsStorable = false

		storageRange = 2
	}
}

@PART[U_DRR_F1]:FOR[AntennaRange]
{
	@MODULE[ModuleDataTransmitter]
	{
		@name = ModuleLimitedDataTransmitter
		nominalRange = 15000000
		simpleRange = 15000000
		maxPowerFactor = 8
		maxDataFactor = 4
	}

	MODULE
	{
		name = ModuleScienceContainer

		dataIsCollectable = true
		dataIsStorable = false

		storageRange = 2
	}
}

 

Link to comment
Share on other sites

2 minutes ago, Tantalus said:

I've used your RT2-values, but RT2 seems to use a different reference frame for calculating the effective range than AR. I've made a quick-n-dirty module manager config, most values (MaxPowerFactor, MaxDataFactor) still need to be tweaked:

Looks good, but i have no clue about this mod, so go on and test. Please insert PAFF2, there is missing :wink:

Link to comment
Share on other sites

The work on the ALV-Extension for Tantares goes on. The Kerbalized Briz (Breez) named ZIRP is nearly ready.

Inner 1.25 Engine (ZIRP-S) was used also on Tarockot (Eurockot). With radial thorodoid tank the part is named (ZIRP-L) the 4th stage for ALV-M.

 

Link to comment
Share on other sites

Just now, VenomousRequiem said:

Put the GameData in the GameData

hahaha ok! I am an idiot. I am just so used to the gamedata folder not being the right folder. Usually when you install the folder named gamedata its usually wrong lol.

Link to comment
Share on other sites

Head shaking and :D tröööööööööööööööt

My mistake. in GameData, the Contares Folder is missing.

Create a Folder Contares in GameData. Then copy all subdirectories (Agenics, Parts ...) in Contares.

Thanks!

Updated on SpaceDock!

 

 

Edited by hraban
Link to comment
Share on other sites

Alright, I've made an FE filter for Tantares, TantaresLV, and Contares, and also updated my tweakscale patch to include Contares. If you've downloaded my previous patch, you should delete it, though leaving it probably won't do anything. https://www.dropbox.com/s/lqb6r1yo1dckiqw/Fox%20Tantares%20Contares%20Patches.7z?dl=0

Link to comment
Share on other sites

12 hours ago, lagcity613 said:

Alright, I've made an FE filter for Tantares, TantaresLV, and Contares, and also updated my tweakscale patch to include Contares. If you've downloaded my previous patch, you should delete it, though leaving it probably won't do anything. https://www.dropbox.com/s/lqb6r1yo1dckiqw/Fox%20Tantares%20Contares%20Patches.7z?dl=0

Thanks, the Filter is usefull but i preffer my own tweakscale settings.

Link to comment
Share on other sites

 Warning:

The following bug has already been reported in the prerelease and rejected without comment, or ignored.


There is a serious bug in KSP 1.1 of obviously is only used when the object, controlled by the player first enters the area of influence*  of the target object.

The attempt to dock the object controlled by the player to the target object (via any docking port) ends with 50% probability in a sudden drift off the camera and KSP crash when both objects have one docking port.

Has one of the objects more than one docking port equipped increases the crash rate to 90%. More than 16 docking ports = 100% error probability.

If the docking operation (Contrary to the probability) was successful can be made in 50% of cases no separation/decouple/undock of the object/s.

Should To prevent the bug, go back to "Space Center" after the two objects are in the area of influence* , save the game and select/fly the object again on the "Tracking Station".

After reloading the scene, now with two objects, the docking process can be completed without any problems.

* Space around; Radius 2.5km

Try it out, it saves you a lot of frustration.

Link to comment
Share on other sites

On ‎27‎/‎04‎/‎2016 at 9:29 AM, hraban said:

 Warning:

The following bug has already been reported in the prerelease and rejected without comment, or ignored.


There is a serious bug in KSP 1.1 of obviously is only used when the object, controlled by the player first enters the area of influence*  of the target object.

The attempt to dock the object controlled by the player to the target object (via any docking port) ends with 50% probability in a sudden drift off the camera and KSP crash when both objects have one docking port.

Has one of the objects more than one docking port equipped increases the crash rate to 90%. More than 16 docking ports = 100% error probability.

If the docking operation (Contrary to the probability) was successful can be made in 50% of cases no separation/decouple/undock of the object/s.

Should To prevent the bug, go back to "Space Center" after the two objects are in the area of influence* , save the game and select/fly the object again on the "Tracking Station".

After reloading the scene, now with two objects, the docking process can be completed without any problems.

* Space around; Radius 2.5km

Try it out, it saves you a lot of frustration.

Thanks! I have this problem and i will try again with this advise!

Link to comment
Share on other sites

Hello guys

Now I am probably just being an idiot, but I see the title of this page is Contares 1.7.0 and but the link on the front goes to 1.6.4.  Am I missing something?

Link to comment
Share on other sites

Take a little more time to read the first Post and type "Contares" to Spacedock :)

The new complete Pack of Contares is in work but not released.

There are 5 "split of" sub-mods to download on first Page or via SpaceDock.

Edited by hraban
Link to comment
Share on other sites

This thread is quite old. Please consider starting a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...