Jump to content

Now-defunct-thread-that-should-not-appear-in-google-search.

Cilph

By Cilph
in KSP1 Mod Releases

 Share

Recommended Posts

Peppe

Peppe

Posted
Posted
I have noticed when targeting a planet with a dish, it won't connect to a dish in range around a moon. The same is true if I target a moon, the dish won't connect to sats in range around the planet. Are there any plans to fix this, or a way to make it work?

What is the cone angle on the dishes you are using with planet/moon targeting?

And what is the your distance to the target?

Link to comment
Share on other sites
Peppe

Peppe

Posted
Posted
Testing that hotfixed build. Please advise if it's safe to rename deployed satellite (after manned deployment craft was recovered), don't really want to risk editing my save :)

Bugs all had to do with ID getting unloaded or not unloading when they should renaming never did anything.

Link to comment
Share on other sites
Peppe

Peppe

Posted
Posted
I have noticed when targeting a planet with a dish, it won't connect to a dish in range around a moon. The same is true if I target a moon, the dish won't connect to sats in range around the planet. Are there any plans to fix this, or a way to make it work?

Here is a quick example of the affect of cone angle. Comparing one sat from each tier kerbin to minmus:

Javascript is disabled. View full album

If you are not using DTS-M1 or KR-7 for your moon to planet and back link you are probably have a very tiny window where sats can be to communicate. Minmus in the above shots is only 60Km. The 88-88 can see maybe half of minmus, but if you use the 88-88 to look back to kerbin it is 10x larger planet so the same sat will see an even smaller window/field of view of kerbin.

You have to size your dishes for the job they will do.

Link to comment
Share on other sites
TBryson2

TBryson2

Posted
Posted (edited)

Error in "Github / RemoteTech 2" , "Launch First Satellite" documentation?

at the bottom of the doc. It states:"The 'Comms DTS-M1' has the largest cone angle at 45°, as such, if you have three satellites, all targeting 'Kerbin', one over the Kerbin, the other two can sit on the other side of kerbin, still within the primary 'KSC geostationary' satallite's cone. These two will not talk directly to each each other, but they do not need to."

unless I'm missing something, there is NO way each satellite in (my) geostationary orbit can communicate with each other with a DTS-M1. Using 3 satellites, each with a DTS-M1 set to "Kirbin", I can see the (potential) angle of ambiguity (LOL) and they do NOT intersect with each other. They do not even come close. The only way to use this setting would be to use 4 satellites and your satellites had better be perfectly aligned with each other. 5 satellites are a better "fit". If the DTS-M1 had a 90 degree sweep, it would work with 3. Am I missing something?

also, i don't understand why it states "These two will not talk directly to each each other, but they do not need to."

and yes, I understand what a geostationary orbit is and have a true geostationary orbit

update, perhaps i do understand. The "back side" satellites do not have to be equally placed (say each satellite @ 120 degrees). That makes sense

Edited by TBryson2
Link to comment
Share on other sites
Peppe

Peppe

Posted
Posted
Error in "Github / RemoteTech 2" , "Launch First Satellite" documentation?

at the bottom of the doc. It states:"The 'Comms DTS-M1' has the largest cone angle at 45°, as such, if you have three satellites, all targeting 'Kerbin', one over the Kerbin, the other two can sit on the other side of kerbin, still within the primary 'KSC geostationary' satallite's cone. These two will not talk directly to each each other, but they do not need to."

unless I'm missing something, there is NO way each satellite in (my) geostationary orbit can communicate with each other with a DTS-M1. Using 3 satellites, each with a DTS-M1 set to "Kirbin", I can see the (potential) angle of ambiguity (LOL) and they do NOT intersect with each other. They do not even come close. The only way to use this setting would be to use 4 satellites and your satellites had better be perfectly aligned with each other. 5 satellites are a better "fit". If the DTS-M1 had a 90 degree sweep, it would work with 3. Am I missing something?

also, i don't understand why it states "These two will not talk directly to each each other, but they do not need to."

and yes, I understand what a geostationary orbit is and have a true geostationary orbit

update, perhaps i do understand. The "back side" satellites do not have to be equally placed (say each satellite @ 120 degrees). That makes sense

That whole section is new. Does not come off very clear. You are correct the far side satellites would not work with an eqalateral triangle, but there should be window where they can point at kerbin and see the sat over KSC.

At any rate I would prefer lower orbits and all Omni's to cover surface to orbit comms. Dish's should point out... To moons/planets.

Link to comment
Share on other sites
Kaa253

Kaa253

Posted
Posted
Curious if anyone else was crashing on the DLL (1.3.3 fix) i put out:

Just got back and trying everywhere I can to crash/break things and get crash it on my system using my old test craft. So far i have not crashed with it.

edit:

Here is new build (madadam+JDMJ fixes) 1.3.3 fixpack 2:

RemoteTech2_2014.01.08.22.30.zip

I have been using this version and I have had not too many problems with it, I can recommend it. Importantly, there is no explosive duplication of ships going on. There is something buggy with the map's ship focus switcher icon (3rd one down on the right edge of the map screen) and when I renamed one ship it no longer appeared in the lists of target-able craft. Not sure if a game reload might have fixed that.

Link to comment
Share on other sites
lantay77

lantay77

Posted
Posted
What is the cone angle on the dishes you are using with planet/moon targeting?

And what is the your distance to the target?

I'm using the Alternis Kerbin plugin where Kerbin orbits Jool. I was using DTS-M1, which has a cone angle of 45 degrees. I was targeting a Kerbin from Mun and Bop (Kerbin's moon) was within the cone, but a connection only formed to satellites orbiting the Kerbin, and not Bop. I had the satelites around Kerbin and Bop pointing towards Mun, and all were within the dish's distance.

Link to comment
Share on other sites
Peppe

Peppe

Posted
Posted
I'm using the Alternis Kerbin plugin where Kerbin orbits Jool. I was using DTS-M1, which has a cone angle of 45 degrees. I was targeting a Kerbin from Mun and Bop (Kerbin's moon) was within the cone, but a connection only formed to satellites orbiting the Kerbin, and not Bop. I had the satelites around Kerbin and Bop pointing towards Mun, and all were within the dish's distance.

Sounds like issue 200:

https://github.com/Cilph/RemoteTech2/issues/200

Targeting a body will only talk to satellites in line of site and orbiting that body. So something can be in the cone, but if it is outside the SOI of the target body it will not be communicated with.

You might add your usage scenario to the issue and see if that might encourage a change in the code proposed by maxdreamland.

I personally think dishes should only use cone mode no matter what they target, but maybe that creates a performance issue.

Link to comment
Share on other sites
TBryson2

TBryson2

Posted
Posted
That whole section is new. Does not come off very clear. You are correct the far side satellites would not work with an eqalateral triangle, but there should be window where they can point at kerbin and see the sat over KSC.

At any rate I would prefer lower orbits and all Omni's to cover surface to orbit comms. Dish's should point out... To moons/planets.

Thanks for the reply. Makes sense about lower orbits, then your whole system isn't dependent on one sat hopefully staying stationary over KSC. Perhaps i'll revise my setup.

TB

Link to comment
Share on other sites
Sacred Aardvark

Sacred Aardvark

Posted
Posted
Sounds like issue 200:

https://github.com/Cilph/RemoteTech2/issues/200

Targeting a body will only talk to satellites in line of site and orbiting that body. So something can be in the cone, but if it is outside the SOI of the target body it will not be communicated with.

Holy crap. Someone actually made a bugreport about it. :) I made a few posts about the issue some fifty (might have been a hundred) pages back, but didn't really get anyone to have a go and confirm that it wasn't just my install, so never got around to doing a proper bugreport on it. :/

Link to comment
Share on other sites
BigD145

BigD145

Posted
Posted
I want antennas to eat more electricity

what i must change?

EnergyCost or PacketResourceCost

Both. Packets are your energy costs when sending science data. EnergyCost should be energy used while deployed/extended.

Link to comment
Share on other sites
Mystique

Mystique

Posted
Posted (edited)

Something's very wrong with flight computer (using hotfixed build). Tried using its functions for easier navigation to deploy satellite and it's doings following strage things:

1. Shakes/wobbles rocket like crazy (first tought it was FAR-related, but problem remains even in space).

2. When I give new command like point prograde it starts rotating rocket and does crazy turns instead of just picking closest way to prograde marker. Sometimes rotation gets so bad that I have to disable flight computer and turn on regular SAS to stop it.

3. Worst: when switching off all functions (like turn off follow prograde) rocket starts rotating on some side and doesn't respond to control. SAS tries to stop it, but can't. Helps switching computer on/off again. So it's definitely a problem that it doesn't actually switch off. Because of all those bugs I don't know if it's safe to use MJ on unmanned crafts, so it's kinda annoying.

4. Clicking "exec" starts countdown to node but doesn't make craft turn on node marker. Is that normal?

Below is craft's screenshot. Not best build, but balanced enough not to cause such problems. And it's not signal related - I'm on Kerbin orbit with Jeb onboard.

vyau.png

Update: sudden turns could be caused by 90 degree inclination (polar orbit) when passing poles, but all other thing occur on regular prograde orbit also.

Edited by Mystique
Link to comment
Share on other sites
Mecripp

Mecripp

Posted
Posted (edited)
Something's very wrong with flight computer (using hotfixed build). Tried using its functions for easier navigation to deploy satellite and it's doings following strage things:

1. Shakes/wobbles rocket like crazy (first tought it was FAR-related, but problem remains even in space).

2. When I give new command like point prograde it starts rotating rocket and does crazy turns instead of just picking closest way to prograde marker. Sometimes rotation gets so bad that I have to disable flight computer and turn on regular SAS to stop it.

3. Worst: when switching off all functions (like turn off follow prograde) rocket starts rotating on some side and doesn't respond to control. SAS tries to stop it, but can't. Helps switching computer on/off again. So it's definitely a problem that it doesn't actually switch off. Because of all those bugs I don't know if it's safe to use MJ on unmanned crafts, so it's kinda annoying.

4. Clicking "exec" starts countdown to node but doesn't make craft turn on node marker. Is that normal?

Below is craft's screenshot. Not best build, but balanced enough not to cause such problems. And it's not signal related - I'm on Kerbin orbit with Jeb onboard.

http://imagizer.imageshack.us/v2/280x200q90/850/vyau.png

Try zipping up Kethane plugin or just move the .dll out and try again.

EDIT Don't think Kethane is all the problem but, I think it's choking on it and making it worse.

Edited by Mecripp2
Link to comment
Share on other sites
lucusloc

lucusloc

Posted
Posted

I got the 1.3.3 fix 2 DLL and am still having a problem. I have a cluster with antenna on each probe. When I decouple a probe and fly out of physics range, then use the map to switch back to the main craft (also a remote probe core) the background goes away, the navball goes blank and all values (altitude, speed etc.) are NaN. This is reproducible every time.

I have the save if necessary (I believe the only other mods on the vessel are KW rocketry, but may also have B9 batteries on board. I forget which part goes to which mod. kerbal alarm is also installed, as are other mods, but i dont think any of the others are active while this is happening).

here is the last part of the logs:

[LOG 17:08:25.847] 1/12/2014 5:08:25 PM,KerbalAlarmClock,Vessel Change from 'No Vessel' to 'antena cluster Probe'

[EXC 17:08:25.848] NullReferenceException

[LOG 17:08:26.135] RemoteTech: ModuleRTAntenna: OnDestroy

[LOG 17:08:26.136] RemoteTech: ModuleSPUPassive: OnDestroy

[LOG 17:08:26.137] RemoteTech: SatelliteManager: Unregister(ModuleSPUPassive(null, 00000000-0000-0000-0000-000000000000))

[LOG 17:08:26.141] RemoteTech: ModuleRTAntenna: OnDestroy

[LOG 17:08:26.142] RemoteTech: ModuleSPUPassive: OnDestroy

[LOG 17:08:26.143] RemoteTech: SatelliteManager: Unregister(ModuleSPUPassive(null, 00000000-0000-0000-0000-000000000000))

[LOG 17:08:26.144] RemoteTech: ModuleRTAntenna: OnDestroy

[LOG 17:08:26.145] RemoteTech: ModuleSPUPassive: OnDestroy

[LOG 17:08:26.146] RemoteTech: SatelliteManager: Unregister(ModuleSPUPassive(null, 00000000-0000-0000-0000-000000000000))

[LOG 17:08:26.153] RemoteTech: SatelliteManager: OnVesselDestroy(4e7bbe0f-df3c-45a2-9b7b-732ba95efe8d, antena cluster Probe)

[LOG 17:08:26.155] RemoteTech: SatelliteManager: UnregisterProto(4e7bbe0f-df3c-45a2-9b7b-732ba95efe8d)

[LOG 17:08:26.156] RemoteTech: SatelliteManager: OnUnregister(VesselSatellite(antena cluster Probe, 4e7bbe0f-df3c-45a2-9b7b-732ba95efe8d))

[LOG 17:08:26.157] RemoteTech: NetworkManager: SatelliteUnregister(VesselSatellite(antena cluster Probe, 4e7bbe0f-df3c-45a2-9b7b-732ba95efe8d))

[LOG 17:08:26.173] RemoteTech: ModuleSPU: OnDestroy

[LOG 17:08:26.174] RemoteTech: SatelliteManager: Unregister(ModuleSPU(null, 00000000-0000-0000-0000-000000000000))

[LOG 17:08:26.183] RemoteTech: SatelliteManager: OnVesselDestroy(0ae55d20-24df-4714-bfd4-e001f7bc8cde, antena cluster Probe)

[LOG 17:08:26.185] RemoteTech: SatelliteManager: UnregisterProto(0ae55d20-24df-4714-bfd4-e001f7bc8cde)

[LOG 17:08:26.186] RemoteTech: SatelliteManager: OnUnregister(VesselSatellite(antena cluster Probe, 0ae55d20-24df-4714-bfd4-e001f7bc8cde))

[LOG 17:08:26.188] RemoteTech: NetworkManager: SatelliteUnregister(VesselSatellite(antena cluster Probe, 0ae55d20-24df-4714-bfd4-e001f7bc8cde))

[LOG 17:08:26.190] RemoteTech: SatelliteManager: OnVesselDestroy(49c680c3-e56c-4b3d-8b52-68a7178b2ba4, antena cluster Debris)

[LOG 17:08:26.191] RemoteTech: SatelliteManager: UnregisterProto(49c680c3-e56c-4b3d-8b52-68a7178b2ba4)

[LOG 17:08:26.196] RemoteTech: SatelliteManager: OnVesselDestroy(12d5a78b-8351-409c-a8d1-8bef584549be, Comsat Mk3 Debris)

[LOG 17:08:26.198] RemoteTech: SatelliteManager: UnregisterProto(12d5a78b-8351-409c-a8d1-8bef584549be)

[LOG 17:08:26.206] RemoteTech: SatelliteManager: OnVesselDestroy(1b507fce-538f-41eb-aa15-640c31e43be9, antena cluster Debris)

[LOG 17:08:26.207] RemoteTech: SatelliteManager: UnregisterProto(1b507fce-538f-41eb-aa15-640c31e43be9)

[LOG 17:08:26.218] 1/12/2014 5:08:26 PM,KerbalAlarmClock,Destroying the KerbalAlarmClock-KACFlight

[LOG 17:08:26.233] RemoteTech: ModuleRTAntenna: OnDestroy

[LOG 17:08:26.233] RemoteTech: ModuleSPUPassive: OnDestroy

[LOG 17:08:26.234] RemoteTech: SatelliteManager: Unregister(ModuleSPUPassive(null, 00000000-0000-0000-0000-000000000000))

[LOG 17:08:26.240] RemoteTech: ModuleSPU: OnDestroy

[LOG 17:08:26.241] RemoteTech: SatelliteManager: Unregister(ModuleSPU(null, 00000000-0000-0000-0000-000000000000))

[LOG 17:08:26.242] RemoteTech: ModuleRTAntennaPassive: OnDestroy

[LOG 17:08:26.246] RemoteTech: SatelliteManager: OnVesselDestroy(993e4e5f-34fe-45b2-a78e-a5bdfa1e70bb, antena cluster Probe)

[LOG 17:08:26.247] RemoteTech: SatelliteManager: UnregisterProto(993e4e5f-34fe-45b2-a78e-a5bdfa1e70bb)

[LOG 17:08:26.248] RemoteTech: SatelliteManager: OnUnregister(VesselSatellite(antena cluster Probe, 993e4e5f-34fe-45b2-a78e-a5bdfa1e70bb))

[LOG 17:08:26.249] RemoteTech: NetworkManager: SatelliteUnregister(VesselSatellite(antena cluster Probe, 993e4e5f-34fe-45b2-a78e-a5bdfa1e70bb))

[EXC 17:08:26.252] NullReferenceException

[LOG 17:08:26.253] RemoteTech: SatelliteManager: OnVesselDestroy(aaf1d0ee-db90-4fa1-85a0-a2462f3ff453, Mid moons Comsat Mk2)

[LOG 17:08:26.254] RemoteTech: SatelliteManager: UnregisterProto(aaf1d0ee-db90-4fa1-85a0-a2462f3ff453)

[LOG 17:08:26.255] RemoteTech: SatelliteManager: OnUnregister(VesselSatellite(Mid moons Comsat Mk2, aaf1d0ee-db90-4fa1-85a0-a2462f3ff453))

[LOG 17:08:26.256] RemoteTech: NetworkManager: SatelliteUnregister(VesselSatellite(Mid moons Comsat Mk2, aaf1d0ee-db90-4fa1-85a0-a2462f3ff453))

[LOG 17:08:26.257] RemoteTech: SatelliteManager: OnVesselDestroy(56b7de50-1edd-433c-97eb-80bb939b953c, Comsat Mk2)

[LOG 17:08:26.258] RemoteTech: SatelliteManager: UnregisterProto(56b7de50-1edd-433c-97eb-80bb939b953c)

[LOG 17:08:26.259] RemoteTech: SatelliteManager: OnUnregister(VesselSatellite(Comsat Mk2, 56b7de50-1edd-433c-97eb-80bb939b953c))

[LOG 17:08:26.260] RemoteTech: NetworkManager: SatelliteUnregister(VesselSatellite(Comsat Mk2, 56b7de50-1edd-433c-97eb-80bb939b953c))

[LOG 17:08:26.263] RemoteTech: SatelliteManager: OnVesselDestroy(c1fd9e30-0940-4314-94a6-738160bf3207, polar 1 comm sat)

[LOG 17:08:26.264] RemoteTech: SatelliteManager: UnregisterProto(c1fd9e30-0940-4314-94a6-738160bf3207)

[LOG 17:08:26.265] RemoteTech: SatelliteManager: OnUnregister(VesselSatellite(polar 1 comm sat, c1fd9e30-0940-4314-94a6-738160bf3207))

[LOG 17:08:26.266] RemoteTech: NetworkManager: SatelliteUnregister(VesselSatellite(polar 1 comm sat, c1fd9e30-0940-4314-94a6-738160bf3207))

[LOG 17:08:26.270] RemoteTech: SatelliteManager: OnVesselDestroy(0001c454-8a81-4f8d-819d-052b2c73e343, comm sat)

[LOG 17:08:26.271] RemoteTech: SatelliteManager: UnregisterProto(0001c454-8a81-4f8d-819d-052b2c73e343)

[LOG 17:08:26.272] RemoteTech: SatelliteManager: OnUnregister(VesselSatellite(comm sat, 0001c454-8a81-4f8d-819d-052b2c73e343))

[LOG 17:08:26.273] RemoteTech: NetworkManager: SatelliteUnregister(VesselSatellite(comm sat, 0001c454-8a81-4f8d-819d-052b2c73e343))

[LOG 17:08:26.274] RemoteTech: SatelliteManager: OnVesselDestroy(0001c454-8a81-4f8d-819d-052b2c73e343, comm sat)

[LOG 17:08:26.275] RemoteTech: SatelliteManager: UnregisterProto(0001c454-8a81-4f8d-819d-052b2c73e343)

[LOG 17:08:26.278] RemoteTech: SatelliteManager: OnVesselDestroy(1f963605-4837-4563-8433-7dd14c6ceb74, Comsat Mk3)

[LOG 17:08:26.279] RemoteTech: SatelliteManager: UnregisterProto(1f963605-4837-4563-8433-7dd14c6ceb74)

[LOG 17:08:26.280] RemoteTech: SatelliteManager: OnUnregister(VesselSatellite(Comsat Mk3, 1f963605-4837-4563-8433-7dd14c6ceb74))

[LOG 17:08:26.280] RemoteTech: NetworkManager: SatelliteUnregister(VesselSatellite(Comsat Mk3, 1f963605-4837-4563-8433-7dd14c6ceb74))

[LOG 17:08:26.282] RemoteTech: ModuleSPU: OnDestroy

[LOG 17:08:26.283] RemoteTech: SatelliteManager: Unregister(ModuleSPU(null, 00000000-0000-0000-0000-000000000000))

[LOG 17:08:26.283] RemoteTech: ModuleRTAntennaPassive: OnDestroy

[LOG 17:08:26.285] RemoteTech: ModuleRTAntenna: OnDestroy

[LOG 17:08:26.286] RemoteTech: ModuleSPUPassive: OnDestroy

[LOG 17:08:26.286] RemoteTech: SatelliteManager: Unregister(ModuleSPUPassive(null, 00000000-0000-0000-0000-000000000000))

[LOG 17:08:26.288] RemoteTech: ModuleRTAntenna: OnDestroy

[LOG 17:08:26.288] RemoteTech: ModuleSPUPassive: OnDestroy

[LOG 17:08:26.289] RemoteTech: SatelliteManager: Unregister(ModuleSPUPassive(null, 00000000-0000-0000-0000-000000000000))

[LOG 17:08:26.290] RemoteTech: SatelliteManager: OnVesselDestroy(0001c454-8a81-4f8d-819d-052b2c73e343, comm sat)

[LOG 17:08:26.290] RemoteTech: SatelliteManager: UnregisterProto(0001c454-8a81-4f8d-819d-052b2c73e343)

[LOG 17:08:26.292] RemoteTech: ModuleRTAntennaPassive: OnDestroy

[LOG 17:08:26.295] RemoteTech: ModuleRTAntenna: OnDestroy

[LOG 17:08:26.295] RemoteTech: ModuleSPUPassive: OnDestroy

[LOG 17:08:26.296] RemoteTech: SatelliteManager: Unregister(ModuleSPUPassive(null, 00000000-0000-0000-0000-000000000000))

[LOG 17:08:26.300] RemoteTech: SatelliteManager: OnVesselDestroy(b5d0b3ed-b606-4b90-bb73-7b1cdabddfd0, comm sat)

[LOG 17:08:26.301] RemoteTech: SatelliteManager: UnregisterProto(b5d0b3ed-b606-4b90-bb73-7b1cdabddfd0)

[LOG 17:08:26.302] RemoteTech: SatelliteManager: OnUnregister(VesselSatellite(comm sat, b5d0b3ed-b606-4b90-bb73-7b1cdabddfd0))

[LOG 17:08:26.303] RemoteTech: NetworkManager: SatelliteUnregister(VesselSatellite(comm sat, b5d0b3ed-b606-4b90-bb73-7b1cdabddfd0))

[LOG 17:08:26.308] RemoteTech: ModuleRTAntenna: OnDestroy

[LOG 17:08:26.309] RemoteTech: ModuleSPUPassive: OnDestroy

[LOG 17:08:26.310] RemoteTech: SatelliteManager: Unregister(ModuleSPUPassive(null, 00000000-0000-0000-0000-000000000000))

[LOG 17:08:26.314] RemoteTech: ModuleSPU: OnDestroy

[LOG 17:08:26.314] RemoteTech: SatelliteManager: Unregister(ModuleSPU(null, 00000000-0000-0000-0000-000000000000))

[LOG 17:08:26.315] RemoteTech: ModuleRTAntennaPassive: OnDestroy

[LOG 17:08:26.317] RemoteTech: ModuleRTAntenna: OnDestroy

[LOG 17:08:26.318] RemoteTech: ModuleSPUPassive: OnDestroy

[LOG 17:08:26.319] RemoteTech: SatelliteManager: Unregister(ModuleSPUPassive(null, 00000000-0000-0000-0000-000000000000))

[LOG 17:08:26.324] RemoteTech: SatelliteManager: OnVesselDestroy(154c4d8a-8434-4978-9de8-160105ae2395, hIGH comm sat 1)

[LOG 17:08:26.325] RemoteTech: SatelliteManager: UnregisterProto(154c4d8a-8434-4978-9de8-160105ae2395)

[LOG 17:08:26.325] RemoteTech: SatelliteManager: OnUnregister(VesselSatellite(hIGH comm sat 1, 154c4d8a-8434-4978-9de8-160105ae2395))

[LOG 17:08:26.326] RemoteTech: NetworkManager: SatelliteUnregister(VesselSatellite(hIGH comm sat 1, 154c4d8a-8434-4978-9de8-160105ae2395))

[LOG 17:08:26.329] RemoteTech: SatelliteManager: OnVesselDestroy(12d013cd-0f31-4269-87d8-4fd4ff61ce2b, antena cluster Debris)

[LOG 17:08:26.330] RemoteTech: SatelliteManager: UnregisterProto(12d013cd-0f31-4269-87d8-4fd4ff61ce2b)

[LOG 17:08:26.331] RemoteTech: ModuleRTAntenna: OnDestroy

[LOG 17:08:26.332] RemoteTech: ModuleSPUPassive: OnDestroy

[LOG 17:08:26.332] RemoteTech: SatelliteManager: Unregister(ModuleSPUPassive(null, 00000000-0000-0000-0000-000000000000))

[LOG 17:08:26.334] RemoteTech: SatelliteManager: OnVesselDestroy(0001c454-8a81-4f8d-819d-052b2c73e343, comm sat)

[LOG 17:08:26.335] RemoteTech: SatelliteManager: UnregisterProto(0001c454-8a81-4f8d-819d-052b2c73e343)

[LOG 17:08:26.336] RemoteTech: SatelliteManager: OnVesselDestroy(8c0a1c63-0e31-492e-baa8-fc40ca3e4a5f, Comsat Mk3 Debris)

[LOG 17:08:26.336] RemoteTech: SatelliteManager: UnregisterProto(8c0a1c63-0e31-492e-baa8-fc40ca3e4a5f)

[LOG 17:08:26.337] RemoteTech: SatelliteManager: OnVesselDestroy(4403660f-14c5-495b-a3a5-f04f537ea997, Polar 2 Comsat Mk3)

[LOG 17:08:26.338] RemoteTech: SatelliteManager: UnregisterProto(4403660f-14c5-495b-a3a5-f04f537ea997)

[LOG 17:08:26.339] RemoteTech: SatelliteManager: OnUnregister(VesselSatellite(Polar 2 Comsat Mk3, 4403660f-14c5-495b-a3a5-f04f537ea997))

[LOG 17:08:26.340] RemoteTech: NetworkManager: SatelliteUnregister(VesselSatellite(Polar 2 Comsat Mk3, 4403660f-14c5-495b-a3a5-f04f537ea997))

[LOG 17:08:26.343] RemoteTech: SatelliteManager: OnVesselDestroy(a9e2b420-f700-455a-8fc8-c8eeee0cd28c, antena cluster Debris)

[LOG 17:08:26.344] RemoteTech: SatelliteManager: UnregisterProto(a9e2b420-f700-455a-8fc8-c8eeee0cd28c)

[LOG 17:08:26.346] RemoteTech: SatelliteManager: OnVesselDestroy(1d02fc9d-8b02-440c-9f41-8c1b240f8ba3, comm sat)

[LOG 17:08:26.347] RemoteTech: SatelliteManager: UnregisterProto(1d02fc9d-8b02-440c-9f41-8c1b240f8ba3)

[LOG 17:08:26.348] RemoteTech: SatelliteManager: OnUnregister(VesselSatellite(comm sat, 1d02fc9d-8b02-440c-9f41-8c1b240f8ba3))

[LOG 17:08:26.349] RemoteTech: NetworkManager: SatelliteUnregister(VesselSatellite(comm sat, 1d02fc9d-8b02-440c-9f41-8c1b240f8ba3))

[LOG 17:08:26.354] RemoteTech: SatelliteManager: OnVesselDestroy(00de03b1-1394-4d10-bbb1-617fe894f432, antena cluster Probe)

[LOG 17:08:26.355] RemoteTech: SatelliteManager: UnregisterProto(00de03b1-1394-4d10-bbb1-617fe894f432)

[LOG 17:08:26.356] RemoteTech: SatelliteManager: OnUnregister(VesselSatellite(antena cluster Probe, 00de03b1-1394-4d10-bbb1-617fe894f432))

[LOG 17:08:26.357] RemoteTech: NetworkManager: SatelliteUnregister(VesselSatellite(antena cluster Probe, 00de03b1-1394-4d10-bbb1-617fe894f432))

[LOG 17:08:26.358] RemoteTech: SatelliteManager: OnVesselDestroy(2972adab-e53f-482e-8e97-e684b4db4c6b, antena cluster Debris)

[LOG 17:08:26.359] RemoteTech: SatelliteManager: UnregisterProto(2972adab-e53f-482e-8e97-e684b4db4c6b)

[LOG 17:08:26.360] RemoteTech: SatelliteManager: OnVesselDestroy(5fad5aff-fc63-4c7d-af23-d7b7b38a6bcc, antena cluster Debris)

[LOG 17:08:26.361] RemoteTech: SatelliteManager: UnregisterProto(5fad5aff-fc63-4c7d-af23-d7b7b38a6bcc)

[LOG 17:08:26.368] RemoteTech: SatelliteManager: OnVesselDestroy(229adfa7-1197-4a30-b56d-341ebd710f57, antena cluster Debris)

[LOG 17:08:26.369] RemoteTech: SatelliteManager: UnregisterProto(229adfa7-1197-4a30-b56d-341ebd710f57)

[LOG 17:08:26.370] RemoteTech: SatelliteManager: OnVesselDestroy(c2cb1d6d-0294-4045-a0f8-336294095632, Comsat Mk3)

[LOG 17:08:26.371] RemoteTech: SatelliteManager: UnregisterProto(c2cb1d6d-0294-4045-a0f8-336294095632)

[LOG 17:08:26.372] RemoteTech: SatelliteManager: OnUnregister(VesselSatellite(Comsat Mk3, c2cb1d6d-0294-4045-a0f8-336294095632))

[LOG 17:08:26.373] RemoteTech: NetworkManager: SatelliteUnregister(VesselSatellite(Comsat Mk3, c2cb1d6d-0294-4045-a0f8-336294095632))

[LOG 17:08:26.375] RemoteTech: ModuleRTAntenna: OnDestroy

[LOG 17:08:26.376] RemoteTech: ModuleSPUPassive: OnDestroy

[LOG 17:08:26.377] RemoteTech: ModuleRTAntenna: OnDestroy

[LOG 17:08:26.377] RemoteTech: ModuleSPUPassive: OnDestroy

[LOG 17:08:26.378] RemoteTech: ModuleSPU: OnDestroy

[LOG 17:08:26.378] RemoteTech: ModuleRTAntennaPassive: OnDestroy

[LOG 17:08:26.378] RemoteTech: ModuleSPU: OnDestroy

[LOG 17:08:26.379] RemoteTech: ModuleRTAntennaPassive: OnDestroy

[LOG 17:08:26.379] RemoteTech: ModuleSPU: OnDestroy

[LOG 17:08:26.380] RemoteTech: ModuleRTAntennaPassive: OnDestroy

[LOG 17:08:26.381] RemoteTech: ModuleSPU: OnDestroy

[LOG 17:08:26.381] RemoteTech: ModuleRTAntennaPassive: OnDestroy

Link to comment
Share on other sites
inferno4200

inferno4200

Posted
Posted

Having a bit of an issue. I sent a two part probe to duna. On arrival, I undocked the two pieces. The orbiter has the long range dish, a 500km omni and a 5MM omni. The lander has a 500km omni and a 5MM omni. The 500km omnis on the probe and the orbiter are activated but I get no connection. I tried toggling the omni's on the orbiter but no luck. Any ideas why this is? Both ships have electric charge and of course probe cores.

Link to comment
Share on other sites
Mecripp

Mecripp

Posted
Posted
Having a bit of an issue. I sent a two part probe to duna. On arrival, I undocked the two pieces. The orbiter has the long range dish, a 500km omni and a 5MM omni. The lander has a 500km omni and a 5MM omni. The 500km omnis on the probe and the orbiter are activated but I get no connection. I tried toggling the omni's on the orbiter but no luck. Any ideas why this is? Both ships have electric charge and of course probe cores.

Did u have a connection to KSC or 6 kerbals in a pod as command ?

Link to comment
Share on other sites
NoMrBond

NoMrBond

Posted
Posted
Having a bit of an issue. I sent a two part probe to duna. On arrival, I undocked the two pieces. The orbiter has the long range dish, a 500km omni and a 5MM omni. The lander has a 500km omni and a 5MM omni. The 500km omnis on the probe and the orbiter are activated but I get no connection. I tried toggling the omni's on the orbiter but no luck. Any ideas why this is? Both ships have electric charge and of course probe cores.

Did you turn on the lander antenna's before decoupling it from the orbiter (or within the 3km built in antenna range)?

Link to comment
Share on other sites
Mecripp

Mecripp

Posted
Posted (edited)
Did you turn on the lander antenna's before decoupling it from the orbiter (or within the 3km built in antenna range)?

He is showing he as the 500km omnis which is on all the time or should be.

EDIT I think , I ran into that as a pod of 1 to 3 can't send commands so he would have to have a connection to ksc and the delay might be getting him.

Edited by Mecripp2
Link to comment
Share on other sites
inferno4200

inferno4200

Posted
Posted
Did you turn on the lander antenna's before decoupling it from the orbiter (or within the 3km built in antenna range)?

The orbiter has connection to KSC. Both ships have their omnis enabled, I double checked. I also tried toggling the omnis on the orbiter but no luck. They're about 50 meters away from each other.

Link to comment
Share on other sites
NoMrBond

NoMrBond

Posted
Posted (edited)
He is showing he as the 500km omnis which is on all the time or should be.

They default to on when you select the part from the list in the VAB, but that doesn't mean they are both switched on at any point after then

If my job has taught me anything, it's that you always check the simple things first

The orbiter has connection to KSC. Both ships have their omnis enabled, I double checked. I also tried toggling the omnis on the orbiter but no luck. They're about 50 meters away from each other.

Dang, hopefully not a bug with RT2 itself although I remember seeing stuff about decoupling in the previous pages

Are you using straight RT2 v1.3.3 or the 'hotfix patch 2' that, I think it was Peppe posted?

Edited by NoMrBond
Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...