brooklyn666

Members
  • Content Count

    302
  • Joined

  • Last visited

Everything 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. Nathan, maybe just keep it in the second post for now, let people use it and see what they think. I want it to be optional if people prefer the stock RT2 cfg better.
  3. 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.
  4. Nathan, can you put my RT2 cfg in the 2nd post? I'm going to post the link here shortly
  5. This is a known issue. You'll have more luck if you post this in the RT2 thread.
  6. Glad to see you back! And also glad things at your job have calmed down a bit. No apologies are needed, take your time! Also, check your PMs, I sent you a link to my RT2 cfg if you want to check it out/test it and make sure it'll work with your tree.
  7. 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 }
  8. 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.
  9. It's the same as in real life. RSS uses all real-world figures.
  10. 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.
  11. RT2 comes with a cfg for AIES antennas, so it should still be "@", no?
  12. 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. 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 } } }
  13. 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.
  14. 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.
  15. 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?
  16. 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 ) 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.
  17. 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.
  18. Last I heard Ledenko was busy with rl stuff. Anyone seen him around lately?
  19. Hey Nathan, when you get a chance, take a look at this and let me know what you think. Everything in black is what I've already changed and I'm pretty happy with. Everything blank or in red is still up in the air. The nodes are for integration into Medieval's MS19 tech tree.
  20. 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.
  21. Any chance you could make the tanks compatible with RealFuels?
  22. 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.
  23. 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.
  24. 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...