• Content count

  • Joined

  • Last visited

Community Reputation

290 Excellent

About VaPaL

  • Rank
    Sr. Spacecraft Engineer

Recent Profile Visitors

2,783 profile views
  1. I uploaded the first batch of contracts. The Navigational and the Move/Investigate/decomission contracts are not ready yet Download the PRE-RELEASE folder and put it insed the contract pack folder (...\Kerbal Space Program\GameData\ContractPacks) as it was a contract pack
  2. Upper and lower size limits are "allways" a debatable topic in astronomy apparently, from wikipedia: Save with planets and dwarf planets for instance.
  3. VaPaL

    Duvidas em Kolonization

    materialkits é um recurso que você precisa ter pra inflar os módulos, mande um container com materialkits junto. Você pode configurar o que cada container carrega durante a montagem no menu do botão direito do mouse. electriccharge e eletricidade mesmo, se não me engano ela ó vai ser necessária se primeiro você tiver materialkits. Alguns módulos só podem ser inflados por mecânicos pelo lado de fora.
  4. Nothing exactly new, but some payload details
  5. "Researchers have proposed naming the "oddball" Valetudo, after the Roman goddess of health and hygiene." The funny thing is, Valetudo in Portuguese (vale tudo) means - Everything Goes or Free for All depending on the context. Which I think both are suitable
  6. From the 12 new moons, 9 have retrograde orbit (which is common between Jupiter's moons, 33 out of 67 (already known) are retrograde) The oddity comes from a small moon (1km in diameter - samllest of all), it's prograde orbit is among a retrogade group of moons.
  7. Tutorials wiki page: My communication skill is not the best, so can you guys tell me if it's understandable? Of course the contracts may help it's understandig, they will be playable shortly. I plan to release the Comm, Weather and Spy until the end of the week (if everything goes well).
  8. @Mark Kerbin can you add a poll asking: What Navigation System you would like to be in this pack? GPS: 6 circular, 55° inclined, semi-synchronous and equally spaced orbits, 3-4 sats per orbit GLONASS: 3 circular, 63,4° inclined, a bit lower than semi-synchonous and equally spaced orbits, 5 sats per orbit Galileo: 3 circular, 56° inclined, a bit higher than semi-synchronous and equally spaced orbits, 5 sats per obrit QZSS: 3 tundra (63,4° inclined, synchronous, high elliptic) equally space orbits, 1 sat per orbit IRNSS (NAVIC): 1 stationay orbit with 2 sats with 50° of separation and 2 synchronous 30° inclined 180° of separation orbits with 1 sat each (scale down of this) How hard/realistic you want this pack to be? Hard, asking for sats in precise orbits and locations (where the sat should be above or should be at a specific time) Normal, standard orbit precision and general locations (where the sat should be above or should be at a specific time) Easy, don't ask for locations, only orbits BDS (BeiDou-2) would also be o good Navigation System to add, since in a global one with different types of orbits, but I haven't found much about it yet (may look more if people are interested) Exemples for the second question would be (for a comm/weather): HARD: precise stationary orbit with a waypoint that the sat must be in (above a certain region) with 1° of precision (very hard to do) NORMAL: stationary orbit with a waypoint that the sat must be in (above a certain region) with 10° of precision (takes some time but it's doable) EASY: stationary orbit (could not be simplier) I created this wiki page explaining why I made some decision in the contracts, would be good to know what you guys think, I need some feedback as my play style might not match the majority of players:
  9. VaPaL

    Dawn at Ceres Thread
  10. VaPaL

    JWST: it's done!

    I heard that, even servicing not being planned, JWST has a docking ring So it's not completely discarted by NASA the idea of maintenance. A robot could use RCS to dock "under" the sunshield and move around JWST using some sort of arms. That (maybe) would prevent RCS damaging the mirror or the instruments EDIT: From the article
  11. I'm working on a contract for a satellite constallation. The initial idea, to avoid multiple contract types (one for each orbital plane), is to do the longitude of ascending node dependent on something. Is the following possible? [...] maxCompletions = 3 [...] BEHAVIOUR{ name = OrbitGenerator type = OrbitGenerator FIXED_ORBIT{ SMA = 2431280 ECC = 0.0 INC = 56 LAN = ActualCompletions() == 0 ? 0 : ActualCompletions() == 1 ? 120 : 240 REF = 1 } } [...] Or should I use the persistent store and increase it's value after each completion? if so, there's an event that triggers at completion that I could use to increase the counter? Thanks
  12. Excellent work @Katten will check when I got home. Is it known if this conflicts if Konstruction? It seems unlikely though. If it's unkown, I can check for it tomorrow (I think) EDIT: EDIT2: spelling
  13. I haven't checked, I still playing 1.2.2, but I'll upgrade soon. But if you find any, just let me know and I'll fix it
  14. Steam Workshop connection? Maybe even version bought brom the Squead Store tries to connect to it in some way
  15. VaPaL

    Dawn at Ceres Thread

    Dawn reached its final orbit with perigee of 35km