Jump to content

Handwich

Members
  • Posts

    3
  • Joined

  • Last visited

Everything posted by Handwich

  1. Toadicus said here that bug will be fixed in the next release, but until then, you can remedy it by entering either assembly building then exiting it. The info boxes will then display correctly in R&D.
  2. Hi toadicus. I have couple of small suggestions, but because it feels a bit weird doing so while having not contributed anything, I drew a cat. http://imgur.com/xYYwtzo I hope you like cats. First, in the R&D/construction info boxes, could you move the "nominal" and maximum ranges from the "Requires:" section to the one above, on the line below Bandwidth? I think they'd look better there. Also, there's a stock bug where the bandwidth is displayed incorrectly. It's meant to be packetSize divided by packetInterval (values from the config file), but it's multiplying them instead, giving a tiny and completely wrong result. It works fine in action, it's just the info box which is wrong. Could you fix that in this mod? Secondly, something which would make those suggestions sort of pointless. Considering how this mod works, I'm not sure the single bandwidth display is all that useful. I think it would be better to have sections which show the values at specific distances: optimum - where the packet size is at maximum, standard - where the packet size matches stock (currently "nominal", but I don't think that's the right word), and the maximum distance. Something like this for the Communotron with a level 1 tracking station. The values here are probably wrong, but you get the idea. Optimum Range Range: 21.2 km Packet size: 8.0 Mits Bandwidth: 13.33 Mits/sec Requires: - ElectricCharge: 12.0/packet Standard Range Range: 42.4 km Packet size: 2.0 Mits Bandwidth: 3.33 Mits/sec Requires: - ElectricCharge: 12.0/packet Maximum Range Range: 120 km Packet size: 2.0 Mit Bandwidth: 3.33 Mits/sec Requires: - ElectricCharge: 96.0/packet Would this be feasible? It would also have to take into account the option for fixedPowerCost, which I (and maybe others) have enabled. As for the new Asteroid Day dish, I'd be happy with a range between the DTS and the 88-88. I don't know if you're planning to change the tech tree placement like you mentioned, but consider that its original placement doesn't make any less sense than the rest of the stock tree. And to Yemo: Since AntennaRange seems to be balanced around only the 3 stock antennae, it makes sense that adding new ones will cause some overlap in terms of ranges covered. I don't use SETI or RemoteTech, but if you're adding more antennae, it may be reasonable to change the ranges AntennaRange gives to stock ones so yours fit where you want them in terms of balance.
×
×
  • Create New...