'MK1-2 Pod' IVA Replacement by ASET[v0.3]

[Mogoloko 3]

Hi,

Have you tried to modify the name of model to use, as alexustas said?

 

@Mogoloko

You should also add all this stuff to the config of the Pod, but not only change the name of the INTERNAL

  Reveal hidden contents

or you can take the config from this post and replace "mk1-3pod " to "mk1pod_v2"

[EvanR 3]

Hi

Was looking to try this mod on KSP 1.7, but I get the impression that command pod mk1-2 is an old pod that was removed from the game? I see mk1pod_v2 files in the GameData/Squad folder, but not sure whether this is it. I tried putting @category = Pods into the config, but no new pod appears in the VAB. 

 

[Emilius73 2]

Is there any way to install this to the new Mk1-3 pod from 1.4?

[Emilius73 2]

Also is there a proper Mk1-3 version coming?

[RW-1 73]

I'd also like to know if a new version is coming, in 1.7.1 and .2, my side window is half covered by "something" ...

[Jobin 0]

@alexustas I've been playing KSP since v0.11 and this is the coolest mod I've seen. I never cared for the UI of KSP and always wondered what the point of the IVA was given its limitations. The developers of  KSP should pay you to implement something like this in an expansion pack. Well done!

[Hannil 1]

On 6/15/2019 at 5:11 PM, RW-1 said:

I'd also like to know if a new version is coming, in 1.7.1 and .2, my side window is half covered by "something" ...

How do you do to play with this mod in 1.7.1 and .2 ? I try but it's always the stock IVA. Of course I also downloaded dependencies.

Thank you

 

EDIT : Finally it works!! I only patched the mod with the config file in page 10. But I didn't it before because when I downloaded the config file my firewall blocked it. So this time I tried in manual : creating a file and put the text in. And that works very well. I can see the lateral window. But I only have an artefact in the frontal window, then it's not too bad.

Edited June 24 by Hannil

[RW-1 73]

On 6/23/2019 at 6:56 PM, Hannil said:

How do you do to play with this mod in 1.7.1 and .2 ? I try but it's always the stock IVA. Of course I also downloaded dependencies.

Thank you

 

EDIT : Finally it works!! I only patched the mod with the config file in page 10. But I didn't it before because when I downloaded the config file my firewall blocked it. So this time I tried in manual : creating a file and put the text in. And that works very well. I can see the lateral window. But I only have an artefact in the frontal window, then it's not too bad.

 

Hannil,

Thanks for posting!

 

I had to go back and look at my setup, I must have forgotten to rename the patch cfg's when I went to breaking ground and the latest version of KSP, I had just copied the patch file to the proper location and left it.

 

I have my window back as well, feels so good!

[jeancallisti 17]

On 6/26/2019 at 12:59 PM, RW-1 said:

 

Hannil,

Thanks for posting!

 

I had to go back and look at my setup, I must have forgotten to rename the patch cfg's when I went to breaking ground and the latest version of KSP, I had just copied the patch file to the proper location and left it.

 

I have my window back as well, feels so good!

Can you guys be more descriptive about what you did?

What I did :

- I have KSP 1.7.2

- Download MK1-2_IVA_Replacement_by_ASET-0.3.zip and Install the mod's files into GameData

- Go to GameData\ASET\MK1-2_IVA_Replacement_by_ASET

- Create a new .cfg file with a name of my own choice (alongside MK1-2_ASETinternal-patch.cfg), and paste the entirety of the file suggested on page 10 of this thread. Save the file.

- Go to GameData\Squad\Parts\Command\mk1pod_v2 and edit mk1Pod_v2.cfg to replace the line

name = mk1pod_IVA

with the line

// name = mk1pod_IVA

name = MK1-2_ASETInternals

- Start the game

Despite this, I still see the stock cockpit...

 

[Hannil 1]

After puting the mod in the GameData folder, I just followed it :
 

Quote

 

make a config named: mk1-3IVA.cfg

and put then following lines in,and put the mk1-3IVA.cfg into GameData/ASET/MK1-2_IVA_Replacement_by_ASET

 

I putted all of the "Reveal hidden content" of the Burning Kan's post from page 10, in the mk1-3IVA.cfg file.

 

Quote

 

- Create a new .cfg file with a name of my own choice (alongside MK1-2_ASETinternal-patch.cfg), and paste the entirety of the file suggested on page 10 of this thread. Save the file.

- Go to GameData\Squad\Parts\Command\mk1pod_v2 and edit mk1Pod_v2.cfg to replace the line

 

I guess it doesn't work for you as you just changed few lines and not all of the content of the config file. The MK1-2_ASETinternal-patch.cfg must be copy and puted into GameData/ASET/MK1-2_IVA_Replacement_by_ASET. I suggest to keep this name mk1-3IVA.cfg (not personnalize it).

 

PS: excuse me if I'm not totally clear, because English isn't my mother tongue.

Edited July 11 by Hannil

[jeancallisti 17]

18 hours ago, Hannil said:

After puting the mod in the GameData folder, I just followed it :
 

I putted all of the "Reveal hidden content" of the Burning Kan's post from page 10, in the mk1-3IVA.cfg file.

 

I guess it doesn't work for you as you just changed few lines and not all of the content of the config file. The MK1-2_ASETinternal-patch.cfg must be copy and puted into GameData/ASET/MK1-2_IVA_Replacement_by_ASET. I suggest to keep this name mk1-3IVA.cfg (not personnalize it).

 

PS: excuse me if I'm not totally clear, because English isn't my mother tongue.

Apart from not choosing a custom file name, I think you're describing the exact same steps as I described :

- Put the entire file "MK1-2_ASETinternal-patch.cfg" (and the entire mod, actually) from the mod into folder GameData/ASET/MK1-2_IVA_Replacement_by_ASET

- Creating an additional config file that you also put into GameData/ASET/MK1-2_IVA_Replacement_by_ASET, and copy all the lines from the "hidden" section of the comment on page 10 into that file. (I've tried naming the file "mk1-3IVA.cfg" instead of giving it a custom name but it didn't help. )

- In GameData\Squad\Parts\Command\mk1pod_v2\mk1Pod_v2.cfg , change the one line about "INTERNAL" (as I described in my previous post) as recommended in this forum

I still see the stock IVA when I build a rocket that only contains the Mk1-3 or the Mk1-

 

Are there any implicit steps that I'm overlooking? Something that looks obvious to you brainiacs but not to a regular human being?

Examples :

- I'm trying it in sandbox -- "Duh, it only works in career!"

- In the VAB, the part is named like in the mod's config file: "Mk1-3 Command Pod (M)" -- "Duh, it proves that the mod is properly loaded but the issue is with something else!"

- I'm using that part on my rocket -- "Duh! You should use the other new part, not that stock part! Didn't you notice there was a new command pod in the list somewhere else?"

- I don't know how to troubleshoot further -- "Duh! Don't you know that there's a log file somewhere that will tell you if the mod didn't get fully loaded?"

 

Edited Friday at 10:04 AM by jeancallisti

[RW-1 73]

On 7/11/2019 at 10:47 AM, jeancallisti said:

Can you guys be more descriptive about what you did?

 

 

Grab the patch file MK1-3_ASETinternal-patch.cfg

 

RENAME it to "MK1-2IVA.cfg

 

Place that into      ASET \ MK1-2_IVA_Replacement_by_ASET   location.

 

That's it.

 

In my last thanks post, I was saying I had copied the patch over, but had not renamed it to MK1-2IVA.cfg

If you dont rename it the program will ignore it.

[Hannil 1]

On 7/12/2019 at 11:17 AM, jeancallisti said:

- In GameData\Squad\Parts\Command\mk1pod_v2\mk1Pod_v2.cfg , change the one line about "INTERNAL" (as I described in my previous post) as recommended in this forum

I didn't do this step. Maybe that's a reason to doesn't work.