brooklyn666

Members
  • Content Count

    302
  • Joined

  • Last visited

Posts posted by brooklyn666


  1. For anyone who is interested, here is cfg I made for RemoteTech2 to be used with RSS and RO. To use, simply put both cfgs in your Gamedata folder, and delete the AIES RT2 cfg if you have it.

    Make sure you have the following settings in your RemoteTech_Settings.cfg:

    ConsumptionMultiplier = 1

    RangeMultiplier = 1

    RangeModelType = Root

    MultipleAntennaMultiplier = somewhere between 0.25 and 1. Experiment to see what works best for you.

    I also suggest increasing your ground station omni range, but whether or not, and by how much is up to you.

    If you add this to an existing save, you may find that some of your probes/satellites are no longer in range, or don't have enough power, so I recommend only using it on a new save.

    Many thanks to NathanKell and RedAV8R for helping me put this together.


  2. For anyone who is interested, HERE is my Realism Overhaul for RemoteTech2. To use, simply put the cfg in your Gamedata folder, and delete the AIES RT2 cfg if you have it.

    Make sure you have the following settings in your RemoteTech_Settings.cfg:

    ConsumptionMultiplier = 1

    RangeMultiplier = 1

    RangeModelType = Root

    MultipleAntennaMultiplier = somewhere between 0.25 and 1. Experiment to see what works best for you.

    I also suggest increasing your ground station omni range, but whether or not, and by how much is up to you.

    If you add this to an existing save, you may find that some of your probes/satellites are no longer in range, or don't have enough power, so I recommend only using it on a new save.

    Many thanks to NathanKell and RedAV8R for helping me put this together.


  3. That's pretty much Greek to me, unfortunately. If changing the MODEL scale is an edit done to the model.mu file of the part, then I have no way of opening that. I'm dealing just with the config file. The only parameter dealing with scale there is simply 'scale' like this:

    // --- asset parameters ---

    mesh = model.mu

    scale = .5

    Which was originally set to 1. Changing it to .5 didn't have the desired effect, though I suspected it wouldn't be that simple.

    leave the scale alone. It's the rescaleFactor that you need to change. You can just add it in the cfg if it's not there.

    example:

    @PART[partname]
    {
    mass = x
    rescaleFactor = x
    }


  4. If the part uses a MODEL scale, you need to set that to the inverse of what you want, and then set the rescale factor for what you want. For example, if you want to double a part's size, set the MODEL scale to half of whatever it is, and set the rescaleFactor = 2.0. If it doesn't have a model scale, just use the rescale factor.


  5. I don't think there is such a thing as gimballed SRB's. I believe ICBM's use little thrusters, just like RCS to correct their path in flight. And it wouldn't make a lot of sence either because SRB's are made to get you going, not to steer. ICBM is one thing but if there's a man with a mission on top its a whole diffrent story. Besides, it would take an immense gimbal in order to direct the thrust that comes out of an SRB. SRB's are really... really... really powerfull. If you'd want the gimbal the SRB that's on the Space shuttle you'd need another one just to carry the gimbals.

    Incorrect. There were two hydraulic power units (HPUs) located in the aft skirt section of the SRBs. They provided pitch and yaw control to a pair of servo actuators that gimbaled the nozzle.


  6. Brooklyn666: I don't think the stock configs for the AIES antennas come with any RemoteTech modules. Your MM config uses the '@' symbol for all of it's changes, but that only modifies an existing entry in the part's vanilla config. If the module or entry doesn't exist, take off the @. Or you can use the '%' symbol, which will edit the line if it exists, or add if it doesn't.

    RT2 comes with a cfg for AIES antennas, so it should still be "@", no?


  7. Nathan, do you think I should wait for the .24 version to release my cfg? It seems like Cilph is planning some major changes that could cause compatibility issues. I've tried to get in touch with him on the RT2 thread and in PMs but I haven't heard back.

    Also, 2 more things.

    1) Revised table for the antennas for you and anyone else who wants to take a look. qjUv8B0.png

    and 2) My cgf editing is not going well (as usual). So far I've gone over all of the AIES antennas, but the only changes that show up in game are the masses. My guess is that either I'm doing something wrong (very likely), or there's another sneaky cfg somewhere. Anyone care to take a look?

    @PART[Antennacomtec1]
    {
    @mass = 0.045
    !MODULE[ModuleDataTransmitter] {}

    @MODULE
    {
    @name = ModuleRTAntenna
    @Mode0DishRange = 0
    @Mode1DishRange = 150000000000
    @EnergyCost = 0.15
    @DishAngle = 8.0

    @TRANSMITTER
    {
    @PacketInterval = 0.3
    @PacketSize = 1.5
    @PacketResourceCost = 10.0
    }
    }

    @MODULE
    {
    @name = ModuleSPUPassive
    }
    }

    @PART[Antennacomtec2]
    {
    @mass = 0.055
    !MODULE[ModuleDataTransmitter] {}

    @MODULE
    {
    @name = ModuleRTAntenna
    @Mode0DishRange = 0
    @Mode1DishRange = 500000000000
    @EnergyCost = 0.175
    @DishAngle = 2.0

    @TRANSMITTER
    {
    @PacketInterval = 1.1
    @PacketSize = 0.2
    @PacketResourceCost = 10.0
    }
    }

    @MODULE
    {
    @name = ModuleSPUPassive
    }
    }

    @PART[Antennaesc]
    {
    @mass = 0.012
    !MODULE[ModuleDataTransmitter] {}

    @MODULE
    {
    @name = ModuleRTAntenna
    @Mode0OmniRange = 500000
    @Mode1OmniRange = 15000000
    @EnergyCost = 0.018


    @TRANSMITTER
    {
    @PacketInterval = 0.2
    @PacketSize = 2
    @PacketResourceCost = 12.0
    }
    }

    @MODULE
    {
    @name = ModuleSPUPassive
    }
    }
    @PART[Antennaexpatvr2]
    {
    @mass = 0.025
    !MODULE[ModuleDataTransmitter] {}

    @MODULE
    {
    @name = ModuleRTAntenna
    @Mode0OmniRange = 1000000
    @Mode1OmniRange = 180000000
    @EnergyCost = 0.02

    @DeployFxModules = 0

    @TRANSMITTER
    {
    @PacketInterval = 0.1
    @PacketSize = 3
    @PacketResourceCost = 15.0
    }
    }

    @MODULE
    {
    @name = ModuleSPUPassive
    }
    }
    @PART[AntennaDF2]
    {
    @mass = 0.012
    !MODULE[ModuleDataTransmitter] {}

    @MODULE
    {
    @name = ModuleRTAntennaPassive
    @OmniRange = 500000
    @EnergyCost = 0.1

    @TRANSMITTER
    {
    @PacketInterval = 0.2
    @PacketSize = 3
    @PacketResourceCost = 8.0
    }
    }

    @MODULE
    {
    @name = ModuleSPUPassive
    }
    }
    @PART[Dishcl1]
    {
    @mass = 0.035
    !MODULE[ModuleDataTransmitter] {}

    @MODULE
    {
    @name = ModuleRTAntenna
    @Mode0DishRange = 0
    @Mode1DishRange = 400000000
    @EnergyCost = 0.025
    @DishAngle = 25.0

    @TRANSMITTER
    {
    @PacketInterval = 0.3
    @PacketSize = 1.8
    @PacketResourceCost = 20.0
    }
    }

    @MODULE
    {
    @name = ModuleSPUPassive
    }
    }

    @PART[Dishmccomu]
    {
    @mass = 0.007
    !MODULE[ModuleDataTransmitter] {}

    @MODULE
    {
    @name = ModuleRTAntenna
    @Mode0DishRange = 0
    @Mode1DishRange = 600000000000
    @EnergyCost = 0.175
    @DishAngle = 1.2

    @TRANSMITTER
    {
    @PacketInterval = 0.4
    @PacketSize = 0.6
    @PacketResourceCost = 15.0
    }
    }

    @MODULE
    {
    @name = ModuleSPUPassive
    }
    }
    @PART[dishcomlar1]
    {
    @mass = 0.105
    !MODULE[ModuleDataTransmitter] {}

    @MODULE
    {
    @name = ModuleRTAntenna
    @Mode0DishRange = 0
    @Mode1DishRange = 400000000000
    @EnergyCost = 0.2
    @DishAngle = 0.3

    @TRANSMITTER
    {
    @PacketInterval = 1.5
    @PacketSize = 0.1
    @PacketResourceCost = 20.0
    }
    }

    @MODULE
    {
    @name = ModuleSPUPassive
    }
    }
    @PART[Dishomega2g]
    {
    @mass = 0.075
    !MODULE[ModuleDataTransmitter] {}

    @MODULE
    {
    @name = ModuleRTAntenna
    @Mode0DishRange = 0
    @Mode1DishRange = 600000000000
    @EnergyCost = 0.18
    @DishAngle = 0.7

    @TRANSMITTER
    {
    @PacketInterval = 0.7
    @PacketSize = 0.4
    @PacketResourceCost = 12.0
    }
    }

    @MODULE
    {
    @name = ModuleSPUPassive
    }
    }
    @PART[Dishpcf]
    {
    @mass = 0.065
    !MODULE[ModuleDataTransmitter] {}

    @MODULE
    {
    @name = ModuleRTAntenna
    @Mode0DishRange = 0
    @Mode1DishRange = 450000000000
    @EnergyCost = 0.35
    @DishAngle = 0.4

    @TRANSMITTER
    {
    @PacketInterval = 0.8
    @PacketSize = 1
    @PacketResourceCost = 15.0
    }
    }

    @MODULE
    {
    @name = ModuleSPUPassive
    }
    }
    }


  8. OMG WHAT AN A-HOLE! lol

    I feel like the a-hole to be honest. Bit on more than I could chew and woopee! + funky IRL times. All is well, plus our wonderful friend Bronklyn666 has done an amazing job with an overhaul of range and power con. of antennas/dishes. Which just saved me loads of work. The pessimist in me would say within the month, we'd see a hopefully not too buggy MS19 peek it's ugly head out! boo!

    :)

    I'm building the mega desk for me, and my wife's PC today. And I'm finally getting my 3rd monitor on Monday, out of the 3 I ordered 2 of them had red pixels in the middle of the screen. Fuuuu!

    This is the last weekend where I had 'stuff to do', so I'll be firing all engines very shortly. Next stop, sun escape orbit!

    Take your time! that gives me some time to work on my RT2 edits, although as far as the tree goes, it only matters that the antennas unlock in the right nodes. If anyone is interested in what I'm working on, check out the Realism Overhaul thread.


  9. Impressive ship!

    Has anyone else had an issue with KW fairings only half-ejecting (one shell ejecting fine and the other only decoupling?) This is killing me, since they are the only decent payload fairings available initially.

    Are you using action groups? Make sure you don't click on the fairings after you assign the action group. If, say, you set the fairing ejection as action group 1, then take off the fairings for whatever reason, and put them back on, only the one you clicked on will keep its action group assignment.


  10. brooklyn666:

    1. Ah, ok. Sensible.

    2. You *definitely* want to change that to Root. Standard is the standard RT/RT2 range calculation, where the maximum range between two nodes is capped at the range of the shortest-ranged antenna. For example, consider a node with a 250km omni talking to KSC (with a 75,000km omni). No connection past 250km. The math I was giving you before was for Root. No wonder you had such high ranges for the small omnis!

    3. Open the part.cfg. File->save as (choose new name). Find, in file, the line name = (something). Change the (something) to whatever you want [as long as it's unique]. Presto, new part. Go ahead and change title so it has a different name in the GUI (the name line is the internal name of the part; title is what's shown in the GUI) and whatever other fields you want.

    4. Yes to both questions, calibrated for 100% sunlight at 1 AU.

    So do I just set the RangeModelType = Root in the cfg, or do I need to do something with this? https://github.com/Cilph/RemoteTech2/blob/master/src/RemoteTech2/RangeModel/RangeModelRoot.cs

    And based on the math you gave me, If I had a 10Mm omni, an 8Mm omni, and a 500km omni, it would be (10000000) + MultipleAntennaMultiplier * (8000000 + 500000).?

    So if the MultipleAntennaMultiplier is 1, the total range is 18.5Mm, and if the multiplier is 0.25, the total range is 12.125Mm, correct?

    and for dishes, a 300Gm dish and a 600Gm dish pointing at each other have an effective communication range of 724.26Gm?

    Assuming I did my math correctly, I'm going to reduce the ranges on most of these antennas at least a little bit. What do recommend for the KSP range?


  11. 1. I couldn't find any info on that, but I made some educated guesses. I took the dry mass of various spacecraft, and subtracted the mass of of the science payload and the dish. This left me with the mass of the bus + everything else. I figure the transceiver mass can't possibly be more than half of that.

    2. in my cfg, the RangeModelType = Standard. How is that different from root? 1 seems high, but I'm not putting that in this config, so I guess that's up to each user.

    3. That's not a bad idea. I might keep the GX-128 and maybe one other dish at their current size, but create duplicates with a 1.6 rescale. (I don't know how to make duplicate parts, so that's a problem :blush:)

    4. Those numbers seem right on. The crappiest solar panel give you 18.3 Watts (assuming direct sunlight, and that the output is calibrated for Earth's distance from the sun?) and the largest gives you a whopping 10.6kW. A few will have to be optimized for low power usage with RTGs, maybe at the cost of transmission rate.


  12. 1. Believe it or not, those masses are actually higher than in real life. The 5m TDRS dishes come in at only 20kg. I more than quadrupled that to get the mass of the whole comm assembly. I also figured a small percentage of the mass (wiring, controllers..etc) would be allocated to the bus, but I may change that. All of the masses are based on real life numbers (I did some serious digging for those).

    2. I did a little testing in game, and these are still a work in progress. I want two things to happen. 1: I want to reduce the range of omnis so that they are basically useless beyond MEO. and 2: group antennas into range categories more or less like this : LEO, anything up to GEO, anything up to the Moon, anywhere in the Earth-Moon SOI, all of the inner planets, and then finally, all of the solar system. What I can't do is make omni's in range NOT communicate with each other, so I think reducing their ranges and increasing KSP range makes sense. (I'm a little unclear about how MultipleAntennaMultiplier works, but it doesn't seem to make much sense to me).

    3. I don't really think any size rescaling is needed. Based on my research 3.5-4m is pretty much the largest size for interplanetary probes, (the exception being Galileo's 4.8m folding dish) and the TDRSS use the massive 5m dishes (the GX-128), which are really the largest that you'd need.

    4. They do as of now, but obviously I'm going to fix that. I'm going to do some in-game experiments to figure out how much power is reasonable for each class of antenna.


  13. Hey Medieval, take a look at this. Everything in black is what I've changed and and pretty much set with. Everything in red or blank has yet to be changed or decided. Let me know what you think. I just want to make sure the nodes are balanced so that when you unlock rockets capable of getting to the Mun, and Munar experiments, you have an antenna that can reach that far. Same goes for Duna/Eve...etc. I want to make sure you get the right antennas when you can use them, but not before they are useful. Wh0huDe.png


  14. Wow, ok!

    I was going to do an arbitrary pass on the ranges and make it gamey due to my lack of extensive knowledge of antennas/dish power usage/range. You tell me how many nodes you'd see for each Antenna and Dishes, and i'll make names for them for you. How far along are you in this epic quest of yours? If you are close to finishing it, I'll hold on my gamey pass and we'll go with your ranges/nodes, etc.

    Cheers!

    I'm almost done, I just need to figure out the correct power usage. I imagine them fitting into your existing node structure, so your first node (1950s?) would unlock the short range omnis, next node(early 1960s?) is better omnis and early dishes...etc. That's why I asked for what year ranges your nodes cover. Then you can just plop them in without having to change anything.


  15. They are, yes, but KSP has no easy of simulating varying bit rates. The reason Voyager can transmit at only 23W is that there's a honking huge very high gain dish pointed at it and even then the bit rate at this distance is atrocious. Voyager to Voyager at reasonable bit rate.... the max distance before path losses won would not be very long.

    Yea, but I can't simulate gain, so the best I can do is assume the dishes of that size have similar properties to their real life counterparts, and try and tweak the PacketSize, PacketInterval, and PacketResourceCost to simlulate bitrate, although it will be fixed at that rate for all distances. Obviously 23 watts is too low, but I can't make it so high that you need 500^2m of solar panels or 10 rtgs just to power the dish. I'm still working out the power consumption, but everything else has mostly been settled.


  16. brooklyn666: RO uses 1EC/sec = 1kW, so 1EC = 1kJ. The power consumption of an antenna is in EC/sec. The power consumption of an antenna transmitting data appears to be something like EC used = (data_size * (PacketResourceCost / PacketSize)).

    Since data transmission happens only in career, not sandbox, and since an active RT antenna represents the constant flow of status updates (perhaps including live video feed!) and command & control back-and-forth, I would recommend using at least a reasonable amount for these antennae even when not transmitting. IMO something reasonable would be maybe a watt for a Sputnik-class antenna (LEO), up to maybe 10 watts for GEO, and 100 for HEO/selenocentric.

    so just to make sure I have this right, the RT2 antenna with the highest energy consumption is the Reflektron GX-128, which uses 0.28 charges/second. This translates into 280 watts, correct? That seems way high, considering the Voyagers are transmitting on 23 watts...