Jump to content

[1.2.1] Spacetux - Contract Pack: Unmanned Contracts, Rover Contracts, Grand Tours and Sprite Missions


linuxgurugamer

Recommended Posts

23 hours ago, eberkain said:

I'm assuming these contracts are body specific, IE. wont work with a planet mod like GPP that removes the stock planets?

EDIT:  turns out there are not many errors from Rover Missions or Unmanned Contracts, so I created a github issue on one of them. 

Ok, thanks, I'll take a look.  I recently updated the Grand Tours, it shouldn't be that difficult to find.

Will be sometime next week, I think, before I get to it

Link to comment
Share on other sites

  • 1 month later...
4 hours ago, RaendyLeBeau said:

hi linuxgamer,  can you give me a hint or links about "how to building own contract and mission"

many thanks in advance !

cheers

It's been a while, but:

First, decide what you want to do

Then, head over to the CC thread for help.  I would suggest downloading some of the existing contract packs and looking at them for inspiration.

It's been a while since I did these, so I'm a bit foggy on the details

Link to comment
Share on other sites

4 hours ago, linuxgurugamer said:

It's been a while, but:

First, decide what you want to do

Then, head over to the CC thread for help.  I would suggest downloading some of the existing contract packs and looking at them for inspiration.

It's been a while since I did these, so I'm a bit foggy on the details

hi, i follow your advice. Many thanks again ! cheers

Link to comment
Share on other sites

1 hour ago, Rebelgamer said:

Not sure if this is just my install that's doing this, but there is an issue in the Grand Tour contracts that involve landing on the outer planets.  Specifically, they want you  "landed" on Jool. 

First, I assume you are fully updated?

Then, please send a log file, and your save as well, I'll be able to look at it on Wednesday

Link to comment
Share on other sites

Running 0.1.11

Looked into the cfg for landing on planets and moons:

PARAMETER
			{
				name = ReachState
				type = ReachState
				targetBody = Jool
				disableOnStateChange = true
			}

	PARAMETER
	{
		name = ReachState
		type = ReachState
		targetBody = Jool
		situation = LANDED
		disableOnStateChange = true

 

Edited by Rebelgamer
Link to comment
Share on other sites

  • 1 month later...

With rover mods such as Bon Voyage that really help doing long distances with rovers, is there a possibility of tweaking the contract pack to get longer distance waypoints?

Edit: talking about the Rover Missions pack of course.

Edit2: found this bit in the code:

distanceFactor = @distanceFactorTemp / 2

Edited by ioresult
precision, found it
Link to comment
Share on other sites

11 hours ago, ioresult said:

With rover mods such as Bon Voyage that really help doing long distances with rovers, is there a possibility of tweaking the contract pack to get longer distance waypoints?

Edit: talking about the Rover Missions pack of course.

Edit2: found this bit in the code:

distanceFactor = @distanceFactorTemp / 2

Quite possible.  Could you add it to the Github issue tracker please

Link to comment
Share on other sites

  • 2 weeks later...

Just noted a few minor inconsistency issues with cfg files for each of the contract packs in the KSP log file. 

Grand Tour

  • missing a CONTRACT_GROUP node / group.cfg file for this pack.
  • all point to an group = SpaceTuxGroup that doesn't exist (Maybe: GrandTourMissionsGroup once it's created)
  • each mission has an Agent node that probably not required - already declared via CONTRACT_GROUP node (when it exists)

Unmanned Contracts

  • each mission has an Agent node that probably not required - already declared via CONTRACT_GROUP node

Shared Assets - Agents

With the various contact packs they differ between
 - GrandTour comes with agencies in this location:  GameData/spacetux/Agencies
 - Unmanned & Rover Missions comes with agencies in this location: GameData/ContractPacks/Spacetux/SharedAssets/Agencies

Having two agent files causes a duplicate Agent attempted to be created on game load with an ERR message generated. Having all these contact pack have the same centralized agent file location would fix this.

 

Edited by wile1411
Errors about agent were fixed by mentioned changes - no need to comment out.
Link to comment
Share on other sites

9 minutes ago, wile1411 said:

Just noted a few minor inconsistency issues with cfg files for each of the contract packs in the KSP log file. 

Grand Tour

  • missing a CONTRACT_GROUP node / group.cfg file for this pack.
  • all point to an group = SpaceTuxGroup that doesn't exist (Maybe: GrandTourMissionsGroup once it's created)
  • each mission has an Agent node that probably not required - already declared via CONTRACT_GROUP node (when it exists)

Unmanned Contracts

  • each mission has an Agent node that probably not required - already declared via CONTRACT_GROUP node

Shared Assets - Agents

With the various contact packs they differ between
 - GrandTour comes with agencies in this location:  GameData/spacetux/Agencies
 - Unmanned & Rover Missions comes with agencies in this location: GameData/ContractPacks/Spacetux/SharedAssets/Agencies

Having two agent files causes a duplicate Agent attempted to be created on game load with an ERR message generated. Having all these contact pack have the same centralized agent file location would fix this.

 

That will be a problem if you install some by hand and some with CKAN.

Can you say how they were all installed?

Link to comment
Share on other sites

3 minutes ago, linuxgurugamer said:

That will be a problem if you install some by hand and some with CKAN.

Can you say how they were all installed?

I did all mine by hand and just unzipping all files via the gamedata directory.
EDIT: Just downloaded all zips from spacedock again - Zip paths for agencies is different in the grand tour files compared to the others

 

Edited by wile1411
Link to comment
Share on other sites

1 hour ago, linuxgurugamer said:

Ok, I'll take a look at them over the weekend

I fixed all mine with the below edits and removed all ERR instances:

1: Created new group.cfg file in the GameData\ContractPacks\Spacetux\Grandtours

CONTRACT_GROUP
{
//trace = true
	agent = Space Penguins, Inc
	minVersion = 1.15.0
	// Name of the contract group
	name = GrandTourMissionsGroup
	displayName = Grand Tour Missions
}

2: Changed all 12 x Grand Tour missions cfg files to point to the new group node:

group = GrandTourMissionsGroup

3: Deleted folder - GameData/spacetux/Agencies
This would be fixed with redone zip file

4: Add a title field to the AGENT node (most people seem to just copy the name field value)

(Ignore previous post about commenting out Agent property - seems the above changes fixes those errors as well.)

Edited by wile1411
Link to comment
Share on other sites

  • 3 weeks later...
  • 2 months later...

I'm confused by the manual install for unmanned, there's a contractpacks folder at the same level with a spacetux folder. Inside the contractpacks folder is another spacetux folder with different contents. Is it really intended to install a spacetux folder with Agencies and Flags subfolders at the main GameData\ level?

Link to comment
Share on other sites

  • 2 months later...
On 16/6/2017 at 9:23 AM, wile1411 said:

I fixed all mine with the below edits and removed all ERR instances:

1: Created new group.cfg file in the GameData\ContractPacks\Spacetux\Grandtours


CONTRACT_GROUP
{
//trace = true
	agent = Space Penguins, Inc
	minVersion = 1.15.0
	// Name of the contract group
	name = GrandTourMissionsGroup
	displayName = Grand Tour Missions
}

2: Changed all 12 x Grand Tour missions cfg files to point to the new group node:


group = GrandTourMissionsGroup

3: Deleted folder - GameData/spacetux/Agencies
This would be fixed with redone zip file

4: Add a title field to the AGENT node (most people seem to just copy the name field value)

(Ignore previous post about commenting out Agent property - seems the above changes fixes those errors as well.)

Can you upload your files?
I don't understand the number 4 item.

Add a title field to the agent node? what does that mean?

Edited by Agustin
Link to comment
Share on other sites

Out of curiosity, why is Coherent Cntracts a dependency? Reading the description of it, it looks like all it does is make the language of contracts make more sense... and I -like- the nonsense contracts. :D

(also crap, just noticed this hasn't been updated for 1.3 yet. My question still stands. :D)

Edited by etmoonshade
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...