tomek.piotrowski

[1.9] RemoteTech v1.9.6 [2020-02-15]

Recommended Posts

@C04L Just a quick heads up. This was the last thing preventing me from upgrading to 1.1.3, so I actually tested it. And it seems that the newest Remote Tech dev build 554 works perfectly fine with Contract Configurator v1.13.0. I thus conclude that your issue was indeed that you didn't have nightingale's RemoteTech contract pack installed. As the others pointed out, RT doesn't ship with contracts of its own.

Share this post


Link to post
Share on other sites

Facing a rather peculiar bug.  I launched a single rocket to Duna with two ships on it, a comm satellite and a lander.  Comm satellite was the top portion and separated by a stack separator.  Working as intended.  Beneath it was the lander which was to use the drive section to de-orbit and land.  However when the lander gets ~11km or so away from the comm satellite, connection is lost.  I have an extended Communotron 32, a Comms DTS-M1 targeted at the satellite (which targets it back with the same and also has extended Comm. 32) as well as a Reflectron DP-10.  I suspect that it has something to do with the part of the lander that was attached to the separator is a monoprop tank and not a probe core, so it might be the root part which has lead to issues in the past.  Is this the likely issue and is there a fix?  Is there something else I should check or do to fix this?  It kind of sucks wasting all that time and effort on the lander to lose it like this, and I don't really want to temporarily disable RT for this.

Share this post


Link to post
Share on other sites

Is there any way to stop the remotetech debug window coming up whenever I hit F12? F12 already does two other things, so that means I keep having to close it when I am, for example, toggling the aerodynamic forces display.

Share this post


Link to post
Share on other sites

@eberkain      Vessel's controlled by RT will not respond to any action or respond in any fashion. I only noticed this issue recently when I deployed a mission to Mun to set up a  ComSat network an realized after decoupling and burning for a return orbit to Kerbin that none of the satellites would respond to controls or commands. The satellites in question have a clear link to the network around Kerbin.

Edited by Sanfonic1

Share this post


Link to post
Share on other sites
1 hour ago, Sanfonic1 said:

@eberkain      Vessel's controlled by RT will not respond to any action or respond in any fashion. I only noticed this issue recently when I deployed a mission to Mun to set up a  ComSat network an realized after decoupling and burning for a return orbit to Kerbin that none of the satellites would respond to controls or commands. The satellites in question have a clear link to the network around Kerbin.

Can you show a pic of your sats that are not working and what version of the mod, and what game version are you running?

Share this post


Link to post
Share on other sites

I had the same problem.  Commands would just queue up and not process.  I noticed the RT version I had installed wasn't 'compatible' with KSP 1.1.3 so I updated to the latest Dev build 554 and now everything seems to be working good.  So it looks like whatever it was is fixed in the latest build.

Share this post


Link to post
Share on other sites
1 hour ago, Shaman said:

I had the same problem.  Commands would just queue up and not process.  I noticed the RT version I had installed wasn't 'compatible' with KSP 1.1.3 so I updated to the latest Dev build 554 and now everything seems to be working good.  So it looks like whatever it was is fixed in the latest build.

I'll try the dev build and see if things have changed

Share this post


Link to post
Share on other sites

1.7.1 is available!

This is mostly an update of 1.7 to make it work with KSP 1.1.3.

- Updated to work with KSP 1.1.3
- Updated ModuleManager
- Fixed tracking station dish button
- Support for Procedural Probe Cores
- Wording/typo fixes

Can be downloaded through usual channels.

Couple of quick remarks:

1. I've noticed that a lot of you guys talk about bugs here. Please report them on our bug tracker: https://github.com/RemoteTechnologiesGroup/RemoteTech/issues. We're not always following this thread and they might easily be overlooked.

2. We do not have a lot of manpower here and sadly RT development is now limited mostly to KSP compatibility releases and only the most urgent bug fixes. If you'd like to see a new feature implemented or a bug fixed then you'll probably have to write the necessary code yourself and submit a pull request here: https://github.com/RemoteTechnologiesGroup/RemoteTech/pulls. If you'd like to help to develop RT in any way feel free to PM me. I can add you to our Slack channel.

Edited by tomek.piotrowski

Share this post


Link to post
Share on other sites

Hi,

Trying to de-bug my frequent crashing in VAB. Happening a lot when I move/delete a part.

Not suggesting that it is remote tech bug, I just need some clarification as to what this is in my KSP log and is it any of concern before moving on to other mods.

I am on v1.1.2 using remote tech v1.7.0

[LOG 12:04:26.850] Voxelization Time (ms): 383
[LOG 12:04:33.411] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:04:33.419] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:04:33.421] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:04:33.422] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:04:33.424] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:04:33.425] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:04:33.435] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:04:33.449] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:04:33.457] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:04:33.458] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:04:33.460] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:04:33.461] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:04:33.463] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:04:33.472] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:04:33.485] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:04:33.492] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:04:33.494] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:04:33.495] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:04:33.497] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:04:33.498] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:04:33.508] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:04:34.338] Updating 3 Sat Launcher
[LOG 12:04:34.435] Updating 3 Sat Launcher
[LOG 12:04:34.804] Voxelization Time (ms): 367
[LOG 12:04:34.815] Std dev for smoothing: 3 voxel total vol: 2090.41407103334 filled vol: 279.171360727706

[LOG 12:04:35.139] deleting part launchClamp1
[LOG 12:04:35.197] RemoteTech: ModuleRTAntennaPassive: OnDestroy
[LOG 12:04:39.605] QuickStart(QPersistent)[2.00]: autoSaveShip: save
[LOG 12:04:58.210] deleting part smallRadialDecoupler
[LOG 12:05:09.552] radialDecoupler added to ship - part count: 204
[LOG 12:05:09.554] radialDecoupler added to ship - part count: 205
[LOG 12:05:09.601] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:09.608] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:09.610] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:09.611] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:09.613] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:09.614] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:09.624] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:09.636] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:09.644] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:09.645] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:09.647] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:09.648] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:09.649] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:09.662] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:09.674] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:09.682] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:09.684] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:09.685] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:09.686] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:09.687] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:09.697] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:10.567] Updating 3 Sat Launcher
[LOG 12:05:10.669] Updating 3 Sat Launcher
[LOG 12:05:11.065] Voxelization Time (ms): 394
[LOG 12:05:11.075] Std dev for smoothing: 3 voxel total vol: 2172.24802782713 filled vol: 276.183745308517

[LOG 12:05:11.965] QuickStart(QPersistent)[2.00]: autoSaveShip: save
[LOG 12:05:14.346] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:14.354] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:14.356] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:14.357] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:14.359] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:14.360] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:14.370] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:14.382] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:15.074] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:15.076] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:15.078] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:15.080] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:15.081] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:15.094] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:15.107] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:15.115] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:15.120] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:15.121] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:15.123] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:15.124] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:15.134] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:15.295] Updating 3 Sat Launcher
[LOG 12:05:15.383] Updating 3 Sat Launcher
[LOG 12:05:15.786] Voxelization Time (ms): 401
[LOG 12:05:15.808] Std dev for smoothing: 3 voxel total vol: 1421.16569029799 filled vol: 261.64274219458

[LOG 12:05:16.194] deleting part launchClamp1
[LOG 12:05:16.253] RemoteTech: ModuleRTAntennaPassive: OnDestroy
[LOG 12:05:18.823] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:18.831] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:18.833] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:18.834] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:18.836] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:18.837] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:18.847] RemoteTech: ModuleRTDataTransmitter::OnSave
[LOG 12:05:18.860] RemoteTech: ModuleRTDataTransmitter::OnSave

From above you can see everytime I manipulate a part the log is spammed with RemoteTech: ModuleRTDataTransmitter::OnSave

Above is just a snippet.

I hope someone can clear this up for me.

Cheers,

Edited by FizzerUK

Share this post


Link to post
Share on other sites

So i updated remote tech to the latest version for 1.1.3, im still having issues with it. I have 2 satellites in orbit I cannot make any pitch/yaw/roll adjustments, they automatically roll back. and SAS turns off within less then a second every time I try to turn it on.

Share this post


Link to post
Share on other sites

I have RT installed through CKAN. As of a few days ago, CKAN shows it as 1.1.3 compatible but doesn't offer 1.7.1 as an upgrade. I'm sure that could cause some confusion.

Share this post


Link to post
Share on other sites
17 hours ago, Tylerd said:

So i updated remote tech to the latest version for 1.1.3, im still having issues with it. I have 2 satellites in orbit I cannot make any pitch/yaw/roll adjustments, they automatically roll back. and SAS turns off within less then a second every time I try to turn it on.

Do you have Mechjeb Installed? Sounds like you have another autopilot at work. Eitherway, the SAS issue is due to some auto pilot currently being in effect, and it's overriding it and probably conflicting with RT as well.

If you don't have MJ, check that you have a clear RT queue. Click the ">>>" button and if there is stuff in line up, "x" out of it. It might be holding a previously issued command for you still.

On 7/3/2016 at 6:26 AM, FizzerUK said:

Hi,

Trying to de-bug my frequent crashing in VAB. Happening a lot when I move/delete a part.

Not suggesting that it is remote tech bug, I just need some clarification as to what this is in my KSP log and is it any of concern before moving on to other mods.

I am on v1.1.2 using remote tech v1.7.0

From above you can see everytime I manipulate a part the log is spammed with RemoteTech: ModuleRTDataTransmitter::OnSave

Above is just a snippet.

I hope someone can clear this up for me.

Cheers,

Is this with the official version? There was an unofficial version (but I think that was 1.1.3) that was a debug version. Either way, is there a reason you're tied to 1.1.2? 1.1.3 is so much nicer and will likely clear up (almost) all your VAB crashes. I just checked now and RT doesn't do that under 1.1.3. I checked the most recent patch notes and a few back and haven't seen any thing relevant. Dunno. A ...remote...possibility is you have a DTS-M1 with *Blink Lights* flashing that's triggering updates, but that's unlikely.

Share this post


Link to post
Share on other sites

-----

This really isn't a bug, but it took me by surprise and might be of interest to anyone trying to get RT to process queued Maneuver Nodes across SOI changes (as in queue up a node for Circularizing the Mun while still in the SOI of Kerbin). Everything would seem golden till RT got to then end of the burn...and it just kept on burning. And burning. This was with a full connection and with a Spark engine (not exactly a powerhouse) on a ~400 dV burn maybe. After going around and around with the issue, thinking the SOI change was the culprit, it turned out the real culprit was...too much thrust. Apparently RT doesn't like throttling down engines and just goes hog wild (or so it would seem), but a Spark engine at 30% thrust was enough to do the trick.

Share this post


Link to post
Share on other sites

@Deimos Rast thanks for reply back, I tried 1.1.3 (Game) but my saves all break. Still trying to figure out a way to upgrade without it breaking the progress I made.

OR... Do you mean v1.1.3 remote tech  :)   If so I am going to try that.

Still have many other issue to deal with like game stutter. Thanks for the suggestion.

Edited by FizzerUK

Share this post


Link to post
Share on other sites

Hi there what lines i need to add to cfg in command pod to get integrated omni im using RSS/RO ??

 

Share this post


Link to post
Share on other sites
6 hours ago, FizzerUK said:

@Deimos Rast thanks for reply back, I tried 1.1.3 (Game) but my saves all break. Still trying to figure out a way to upgrade without it breaking the progress I made.

OR... Do you mean v1.1.3 remote tech  :)   If so I am going to try that.

Still have many other issue to deal with like game stutter. Thanks for the suggestion.

I meant the game, yeah. Unlikely that 1.1.3 Remote Tech will help any with 1.1.2.

 

1 hour ago, tees said:

Hi there what lines i need to add to cfg in command pod to get integrated omni im using RSS/RO ??

 

Something like this would work for you. I use it myself. Adjust to taste. Note: it's written as a patch, but you could simply rip the modules out if you wanted.

//-----------------REMOTETECH-------------------------------//
@PART[INSERT_POD_NAME_HERE]:NEEDS[RemoteTech]
{
MODULE
	{
		name = ModuleSPUPassive
	}

MODULE
	{
		name = ModuleRTAntennaPassive
		OmniRange = 50000 //---50Km
		TRANSMITTER
		{
			PacketInterval = 0.3
			PacketSize = 2
			PacketResourceCost = 15.0
		}
	}
}

 

Share this post


Link to post
Share on other sites

guys im still at loss with the "science not being transmitted"-problem.

any fixes or ideas where it come from?

it seems few people do have this problem?

Share this post


Link to post
Share on other sites
2 hours ago, angrybold said:

guys im still at loss with the "science not being transmitted"-problem.

any fixes or ideas where it come from?

it seems few people do have this problem?

You need 2 way connection between Kerbin and probe. If it is distant probe, you need to have one comm relay in orbit around Kerbin with connection to ground base and with dish connection pointing to distant probe. That distrant probe need to have dish pointed to comm relay probe near Kerbin.

Of course, you also need enough battery power and solar panels to recharge them.

Share this post


Link to post
Share on other sites
5 hours ago, kcs123 said:

You need 2 way connection between Kerbin and probe. If it is distant probe, you need to have one comm relay in orbit around Kerbin with connection to ground base and with dish connection pointing to distant probe. That distrant probe need to have dish pointed to comm relay probe near Kerbin.

Of course, you also need enough battery power and solar panels to recharge them.

Its not about not having a connection. It is about that i cannot get the science of certain experiments back to ksc. It transmits as intended, then i get the messag "done", however the next message where it says "x science added" doesnt pop up. Happened mostly with scansat reports, but with an eva report aswell. Might be related to the kind of dish used, im going to try that out now.

EDIT: To whom it might concern: What works for me is reloading the vessel end sending the report once or twice. Got 4 reports through like that that kinda bugged out before.

thanks for the answers tho, lads :)

Edited by angrybold

Share this post


Link to post
Share on other sites
1 hour ago, angrybold said:

Its not about not having a connection. It is about that i cannot get the science of certain experiments back to ksc. It transmits as intended, then i get the messag "done", however the next message where it says "x science added" doesnt pop up. Happened mostly with scansat reports, but with an eva report aswell. Might be related to the kind of dish used, im going to try that out now.

No, I didn't have such issue, although, my latest career was on 1.1.2. , didn't have a chance to try that on 1.1.3. Although I didn't notice any issue with SCANsat, using those as primaray science resource.

Share this post


Link to post
Share on other sites

I have a hail button on my antennas, is this remote tech or other (mod problems) and if so what does it do?

Share this post


Link to post
Share on other sites
26 minutes ago, Kertech said:

I have a hail button on my antennas, is this remote tech or other (mod problems) and if so what does it do?

That's from ESLD Jump Beacons, nothing to do with RemoteTech.

Share this post


Link to post
Share on other sites

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.