Jump to content

Capt Snuggler

Members
  • Posts

    812
  • Joined

  • Last visited

Reputation

720 Excellent

1 Follower

Profile Information

  • About me
    #1 Porkjet Fan

Recent Profile Visitors

3,739 profile views
  1. I left 3 Kerbals strapped in their seats for 7 years transferring to Jool. The smell when that capsule door opened could strip paint off a battle ship.
  2. On 2/25/2018 at 12:53 PM, klgraham1013 said:

    One of the first things every creator should learn is to "kill your darlings."  No matter how much you love something you've created, no matter how much you think it's a great idea, if it's not working, throw it away.  Preferably in a garbage fire.

    It's been clear for a very long time that these original concepts, which can be seen to have a certain merit hypothetically, just don't actually work in this type of game.  That Squad holds on to certain ideas so tightly (the above, career mode) when core parts of them clearly aren't working, is just baffling to me.

     

    I'm a musician.  This is one of the first rules of writing I learned.

    I don't need to post anything on this forum any more, when I can just upvote your posts.

    this is spot on!

  3. I wish they would add programmable flight script automation to the 2.5m probe core. *not an auto pilot as the player must assemble the command list. for example, a basic launch script would look like: set throttle: 100% set SAS mode: rotation hold set rotation hold: pitch: 90° yaw: 90° roll: 0° Stage! wait for: alt = 7000m set rotation hold: pitch: 45° yaw: 90° roll: 0° wait for: stage fuel = 0.0L Stage! wait for: alt = 20000m set SAS mode: prograde hold wait for: apoapsis = 100000m set throttle: 0% wait for: altitude = 71000m Stage! wait for: altitude = 100000m set throttle: 100% wait for: periapsis = 99000m set throttle: 0% print msg: (free text) You are now in orbit. have a nice day! end It would make the high end probe cores worth striving for.
  4. They could totally do this with the new texture switch feature coming.
  5. I used masking tape and a sharpy but also came up with my own standard keys for common AGs: primary engine toggle secondary engine toggle engine mode toggle chutes coms toggle panels toggle cargo bay toggle cargo release docking release retract/close all
  6. yes them too and WOW that comparison is so jarring!!! need to post that every where repeatedly and stir up an old fashioned community frenzy. that's the only way to get things changed around here.
  7. the longer they leave this the more resistance there will be from corners of the community. they need to be replaced now before too many more people ( @Majorjim!) get emotionally attached to the ugly parts.
  8. Don't forget adequate tools/budget calculators/mission planners to help the player figure it all out. without the supporting tools it will just get shouted down by all the dummies. or worse diluted down to a boring mass depleting "fuel" resource.
  9. I mean that average players (my self included) cannot be expected to learn a programming language in order to stop their probes from bricking when outside comms range. You could crate the script and initiate it when in coms range. just make the first event a "wait for: X" or similar. so you could initiate the script just as you enter the SOI of Duna, then it waits until the X condition (ie. altitude) is met before continuing with the script. so for example, just as you enter the SOI of Duna you run the script. set SAS mode: retrograde hold set throttle 50% wait for: periapsis = 100000m set throttle 0% wait for: altitude = 100000m set throttle 100% wait for: apoapsis = 110000m set throttle 0% end
  10. ALSO The functions and script length should be defined by the probe core. the better the probe core, the more "memory" and the more advanced functions. such as: set throttle: maintain acceleration = 2.0 G set rotation hold: match target orientation (for docking) or a bunch of specific rover driving or plane piloting functions. The player still needs to define all the values.
  11. instead of "programming", which I agree is far too complicated for the average player, what about a simple event script? pick "events" from a drop down list and put them in the correct order. set the functions, targets and required values (time delays, altitudes etc, resource values). load to launch pad and click "run script". eg: set throttle: 100% set SAS mode: rotation hold set rotation hold: pitch: 90° yaw: 90° roll: 0° Stage wait for: alt = 7000m set rotation hold: pitch: 45° yaw: 90° roll: 0° wait for: stage fuel = 0.0L Stage wait for: alt = 20000m set SAS mode: prograde hold wait for: apoapsis = 100000m set throttle: 0% wait for: altitude = 71000m Stage wait for: altitude = 100000m set throttle: 100% wait for: periapsis = 99000m set throttle: 0% print msg: (free text) You are now in orbit. have a nice day! end This is a crude launch to orbit script. obviously it depends on the craft and could be improved and made infinitely more precise. (*also im not sure about the pitch, yaw and roll values. I think 0,0,0 points you at the eastern horizon.) The scripts would be as important as the craft files and shared by the community. by having predefined options you avoid having to learn syntax. instead you just keep adding events to the script. by selecting options from a drop down and inputting values where needed.
  12. I'll Keep this short a sweet. the proposed dragon fly probe will be a quadcopter. https://en.wikipedia.org/wiki/Dragonfly_(spacecraft) can we have stock electric propellers now... PLEASE.
×
×
  • Create New...