[1.1] RemoteTech v1.6.10 [2016-04-12]

[Sigma88]

hi there, quick question

Since I play with the signal delay off and every time I update the mod it goes back on (with devastating results )

Is there a way to make a cfg file using module manager to automatically switch off the signal delay?

so I can keep it into my personal folder of changes that never gets deleted

thanks for the help

- - - Updated - - -

An omni can communicate with a dish that is within the omni's range and pointed in the right direction. One omni can communicate with as many other antennas as are in range; the only advantage of multiple omnis is extended range in Root range mode.

If you have satellites that are connected when active, but don't relay when you switch to another ship, the most likely cause is a dish targeting "active vessel" that's no longer pointing in a useful direction for the intended relay.

I'll add something to this since it was a problem I had a while ago and it me took a very long time to figure out why my setup didn't work.

If you point an antenna to a planet you get a "cone" which covers the planet and if you have multiple satellites in the range you can talk with each one.

BUT

if you point an antenna to a specific satellite OR to the active vessel, that's the only satellite that will get the connection, even if you have other satellites in the cone.

IDK if this can be of help, but I lost a lot of time on this, so I hope this post will save time to someone else

[*Aqua*]

Is there a way to make a cfg file using module manager to automatically switch off the signal delay?

I don't know if it'll work but you can try:

@RemoteTechSettings[*]:NEEDS[RemoteTech]:FINAL
{
@EnableSignalDelay = False
}

Copy that to a file and put it somewhere in your GameData directory.

[NikoKun]

I'm a little confused by this:

RemoteTech is not yet compatible with either of the two full-featured autopilot mods, MechJeb and kOS. Mix at your own risk.

But, on the Instruction Manual page, where it talks about changes to Third-Party mods, it say:

The MechJeb AR202 can act as a signal processor.

So which is it? Is this mod incompatible with MechJeb, or do they play ok together? Cause I'd much rather have both, for my DMP server.

[undercoveryankee]

I'll add something to this since it was a problem I had a while ago and it me took a very long time to figure out why my setup didn't work.

If you point an antenna to a planet you get a "cone" which covers the planet and if you have multiple satellites in the range you can talk with each one.

BUT

if you point an antenna to a specific satellite OR to the active vessel, that's the only satellite that will get the connection, even if you have other satellites in the cone.

IDK if this can be of help, but I lost a lot of time on this, so I hope this post will save time to someone else

I know that was the behavior in 1.4 and 1.5. Didn't it change in 1.6?

- - - Updated - - -

I'm a little confused by this:

But, on the Instruction Manual page, where it talks about changes to Third-Party mods, it say:

So which is it? Is this mod incompatible with MechJeb, or do they play ok together? Cause I'd much rather have both, for my DMP server.

The current behavior is that MechJeb can control your spacecraft whenever you could manually control it. It's "incompatible" in that you can't arrange for MechJeb to do things while a probe is out of contact. The AR202, which acts as a probe core, gets ModuleSPU added so it doesn't provide local control to ships that are supposed to be unmanned. So you can use both RT and MechJeb in one game; you just don't get as much from the combination as you might imagine should be possible.

[Sigma88]

I don't know if it'll work but you can try:

@RemoteTechSettings
[*]:NEEDS[RemoteTech]:FINAL
{
@EnableSignalDelay = False
}

Copy that to a file and put it somewhere in your GameData directory.

Thank you!

I know that was the behavior in 1.4 and 1.5. Didn't it change in 1.6?

Idk, if they did that's awesome!

--

1 more question, I have installed the mod "cacteye" which adds a probe core. I noticed that when I use that one I can move the probes without a connection, I guess that's because it's not configured for RT.

I looked at the cfg files in the remote tech directory but under "probe cores squad" I see only this:

@PART[probeCoreOcto]:FOR[RemoteTech]{

%MODULE[ModuleSPU] {

}

%MODULE[ModuleRTAntennaPassive] {

%TechRequired = unmannedTech

%OmniRange = 3000

%TRANSMITTER {

%PacketInterval = 0.3

%PacketSize = 2

%PacketResourceCost = 15.0

}

}

}

which doesn't seem to add anything special other than the 3km antenna inside the probe.

how can I fix the probe core to use RT?

-EDIT-

I checked the cfg of the cacteye core compared to the stock OKTO core, they are mostly the same, no difference in the command parts (just SAS, reactionwheel and stuff like that)

-EDIT2-

nevermind, I'm blind -.-

Edited February 1, 2015 by Sigma88

[RocketBlam]

I'm trying to use this... but I have a problem. I read the FAQ and it didn't address it. I'm trying to send a crew report back to the KSP with a Communotron 16. No matter where I am, in orbit even on the pad, it doesn't work. It says I have no comms device.

[undercoveryankee]

I'm trying to use this... but I have a problem. I read the FAQ and it didn't address it. I'm trying to send a crew report back to the KSP with a Communotron 16. No matter where I am, in orbit even on the pad, it doesn't work. It says I have no comms device.

Unlike stock, where the antenna will automatically deploy when you try to transmit something, RT requires you to manually activate the antenna before you can transmit. Is your antenna activated?

[RocketBlam]

Unlike stock, where the antenna will automatically deploy when you try to transmit something, RT requires you to manually activate the antenna before you can transmit. Is your antenna activated?

Yes, I deployed it manually in both scenarios.

[PH-G]

Problem solved! I had a faulty download of RT don't know how I got it. Thanks for all the help guys!

[RocketBlam]

I think I figured out the problem. I checked in CKAN, and there was an entry for Remote Tech 2 and also Remote Tech 2 RSS configuration (I have RSS installed, and it's what installed RT2). So I uninstalled RT2 and reinstalled with the RSS Config option, and it works now.

So apparently RSS doesn't properly install RT2.

[PetWolverine]

It used to be that have a mobile command center required a vessel with 6 kerbals. Now this doesn't seem to be sufficient, and I see in the instructions page,

Command Stations require a special probe part and a minimum number of kerbals on the same ship. Consult your VAB technicians for more information.

Also from the release notes for 1.5.0,

The number of crew needed to both operate a command station and fly a ship can now be configured on a part-by-part basis.

But I don't see anything in the VAB to give more details. What am I missing? How do I tell how many kerbals is enough? Have I just not unlocked the necessary "special probe part" yet?

[Deadpan110]

It used to be that have a mobile command center required a vessel with 6 kerbals. Now this doesn't seem to be sufficient, and I see in the instructions page,

Also from the release notes for 1.5.0,

But I don't see anything in the VAB to give more details. What am I missing? How do I tell how many kerbals is enough? Have I just not unlocked the necessary "special probe part" yet?

The RC-L01 Remote Guidance Unit is possibly what you are looking for.

The info on the part in the VAB has:

Signal Processor

Remote Command capable (6 + crew)

I am unsure where it unlocks in career mode though.

[Kobymaru]

Hi! With the recent version 1.6.2, I can steer my vessel instantanously without the signal delay (WASD + Throttle controls).

Is that on purpose? I'm pretty sure that was not possible in older (1.5?) versions.

[PetWolverine]

The RC-L01 Remote Guidance Unit is possibly what you are looking for.

The info on the part in the VAB has:

Signal Processor

Remote Command capable (6 + crew)

I am unsure where it unlocks in career mode though.

Thanks - I guess I haven't unlocked it yet. I'll have to keep my eyes peeled for it as I get more science.

[Armarnis]

Hi there people,

today i finally managed to setup my first three comsats, but it looks like i am missing something, because my sats dont connect from one to the other?! i have 3 comms dts-m1 on each, 1 i point at mission control and another one i point to my keosynchronous main satellite, but it keeps saying no connection beneath the time warp panel -.- do i have to put up a connection on both sides, so each is radio'ing to its opposite? kinda confuses me and jeb is already going to crash his lifter down to kerbin because he is so frustrated :< (and, because i forgot to load the vessel up with snacks)

[bdito]

Hi there people,

today i finally managed to setup my first three comsats, but it looks like i am missing something, because my sats dont connect from one to the other?! i have 3 comms dts-m1 on each, 1 i point at mission control and another one i point to my keosynchronous main satellite, but it keeps saying no connection beneath the time warp panel -.- do i have to put up a connection on both sides, so each is radio'ing to its opposite? kinda confuses me and jeb is already going to crash his lifter down to kerbin because he is so frustrated :< (and, because i forgot to load the vessel up with snacks)

Are these 3 sats all orbiting kerbin? If so you should connect them using omni antennas. I always go with the Communitron 32 due to it's greater range. Omni's are necessary because they can connect to anything within their range without needing to point them at anything. You should only use dishes when pointing towards other moons & planets or vessels outside of kerbin's SOI.

[Armarnis]

yep i have one right above mission control, another one in polar orbit and one in an equatorial orbit but both are dead while not in view of mission control :S will give it a new shot with omnis!

how do you manage to keep in contact with sats around other planets? i mean, if i use that round dish antennae that is very early available (dont have it's name around), it has only a 45 degree angle, wouldn't i leave its field of view possibly, loosing all connection? well, i guess i will find out sooner or later, really enjoying this

[bdito]

If you want to connect to the mun, you would make your kerbin comm sats with both omni's and a dish. The omnis would be used to connect to each other and mission control, and you'd point the dish towards the mun. Then anything around the mun will connect to it as long as it has a dish pointing towards kerbin. If you point a dish towards a planet it will always track the planet's position so you don't have to worry about it leaving the field of view.

[PetWolverine]

@Armarnis, you do indeed have to make the connection both ways, so if your main satellite doesn't have a dish pointed at each of the others (or a single dish that catches them both in its cone) then you'll find they aren't connected.

Also, the cone angle is only for allowing you to make multiple connections with one dish - you select a target and anything near enough to it in your field of view is also connected (assuming, again, it has an antenna to make the return connection). You don't have to physically rotate the satellite so that the dish is pointed in the right direction, if that's what you're worried about. "Only" a 45-degree angle is a very wide cone, and handy for getting area coverage in medium-range networks; the narrower cones have longer ranges and are suited for long-range point-to-point.

[bdito]

For example, I have 4 sats around kerbin in an equitorial orbit. They all have 1 communitron 32, 2 DTS M1's (one pointing to the mun and one to minimus). I also have 2 in a polar orbit and they are my long-range comm sats. They have 1 communitron 32, 1 DTS M1, 2 Commtech 1's, and 2 communotron 88-88's.

[freshpatrick]

Hi,

this mod is really cool and makes the game a lot more challenging ;-) especially the Sandbox Mode.

Right now I am trying to find out how the remote control center works.

I have a plane with 8 Kerbals, antenna, dish and of course with the RC-L01Remote Guidance Unit :-)

But unfortunately my Satellite dont want to be controlled by the other vessel.

Here are some screenshots: http://imgur.com/a/fpGnr

Am I doing something wrong or is this feature buggy?

[light_odin5]

heyy,

i have a problem with RT namely it doesn't do anything, i only get the parts but the rest of the mod doesn't work which is shame.

i run on a completely clean install so other mods are not a problem.

could anyone please help?

[Mecripp]

are you missing the plugin ?

EDIT- Make sure your path is KSP/GAMEDATA/RemoteTech

Edited February 2, 2015 by Mecripp2

[Deadpan110]

Hi,

this mod is really cool and makes the game a lot more challenging ;-) especially the Sandbox Mode.

Right now I am trying to find out how the remote control center works.

I have a plane with 8 Kerbals, antenna, dish and of course with the RC-L01Remote Guidance Unit :-)

But unfortunately my Satellite dont want to be controlled by the other vessel.

Here are some screenshots: http://imgur.com/a/fpGnr

Am I doing something wrong or is this feature buggy?

Not sure of the ins and outs of how it should work currently as I have yet to set up a remote command for my 0.90 career game.

But your satellite will contact the closest control point in the system (the KSC looks closer to the satellite than your mobile command unit is) unless you are pointing dishes.

*the communotron 32 is omni directional and will use the shortest path for the signal within its range.

The first pic, I would expect the KSC and your remote command to have red dots - I am unsure but could it be anything to do with being landed on Kerbin (my past remote command control crafts are usually designed as stations to sit in orbit of some planetary body)?

To test this, you could try launching a 6 man crewed remote command in Kerbin orbit and test while your satellite and remote command are in line of sight of each other and are not in view of the KSC.

As for the delay being different - maybe someone else could explain this (bug/feature?) as you shouldn't be getting a 12min delay from Kerbin orbit (unless you set the signal to occur after 12 mins).

Hope that helps?!

Edit: Personally, i would have put some kind of dish on the remote command and set its target to 'Active Vessel' with another dish on the other craft set to point back to the remote command.

Edited February 3, 2015 by Deadpan110

[Armarnis]

i have a new problem with RT, i placed a satellite with 2 comms DTS-M1 antennaes and a radar altimetry scanner from the scansat mod in orbit, the satellite is connected to mission control and now i wanted to transmit my scandata to earn some science, but it tells me i have no transmission system aboard.. i tried again with a communotron 16 and it worked, but i cant see a difference in the statistics beside that the comms DTS-M1 has a greater range, is there any way how i can see which antennaes can transmit scientific data and which not?

sorry if that is a really dumb question but wernher von kerman keeps buggin me that he wants to have these data :S