Jump to content

c4ooo

Members
  • Posts

    133
  • Joined

  • Last visited

Everything posted by c4ooo

  1. I would ask, but apparently to post onto the Discord, you need verify with a reddit account >_>
  2. Anyone have KSP benchmarks for Ryzen yet?
  3. Huh, you're right, camera mode doesn't affect how RCS works. (It is *always* relative to the craft). What's confusing though, is that sometimes I/K move the target_prograde vector up/down (respectively) and othertimes down/up (respectively) (when facing target vecotr).
  4. So, i have finally learned how to dock, with the power of locked screen mode. Since i am currently away from my hardware and cant test, could someone tell me how RCS behaves with the plugin? Is it relative to the orientation of the craft (like locked screen mode) or is it relative to the surface of kerbin? (Like all other screen modes). I think having a switch to toggle between absolute and relative RCS mode would be useful, could i accomplish relative RCS mode with something like: rcs_x' = rcs_x*cos roll - rcs_y*sin(roll) rcs_y' = rcs_x*sin roll + rcs_y*cos(roll) or am i misunderstanding how this works?
  5. @Snark I don't quite understand, how do KSP reaction wheels break real world physics? And what is the difference between rotation and angular position? @NFunky The sun does indeed produce heat radiation and can blow up your craft if you get too close. Therefore you should only approached the sun at night.
  6. The problem is - the 1 axis joystick seems to be somewhat inaccurate. It's fine for roll(rockets)/yaw(aeroplanes) (where its either center, left r right), but quite frankly i would want something more accurate for throttle control. Plus i already have a linear potentiometer that is well suited for throttle control. I do have to agree on the sturdiness of hot glue though - i think i could make a platform from wood that fits snugly around the knob of the 1-axis and that could have the 2-axis screwed onto it. Although i may disagree, I appreciate all tips
  7. I found a one axis joystick (pulled it from an rc helicopter controller) However instead of using it directly, I think some hot glue will do nice in combining this 1 axis and this 2 axis joysticks into a single 3 axis joystick.
  8. I think Computerphile did an interview with the creator of the game
  9. Nice! I have considered trying to hack KSPSIO to allow multiple arduinos (I need 2 as my second one will act as a guidance computer), but havnt had the time. Anyways, I hope the win10 issue will be solved for both KSPSIO and this. Good luck on the project
  10. Hmm, I too am wondering how to make labels for switches. One option is to go to a decal printer. I have free access to 3D printer at school though, so I was thinking it might be possible to 3D print text and symbols a few layers thick. Not sure if feasible though. (Alternatively I could print the text / symbols on paper, cut out the parts with ink, and use the remaining paper as a paint mask - although this will be hard for thin symbols) For the actual casing I will just go with wood spray painted black - don't have the tools to work with metal.
  11. Well if your going to build this thing, you are going to need a few things: 1) Some knowledge about electricity/circuits 2) An arduino to link the game with the buttons and other things on your panel. (You will need the KSPSerialIO plugin to make the game talk to the arduino) 3) some basic programming knowledge. You will need to program the arduino to receive data from the game, update the control panal, and send data from the control panel back to the game. This may sound difficult, but it really doesn't require to much programming knowledge. You can seek programming help at the KSPSerialIO thread. 4) A GPIO expander. Even the arduino mega only has so many pins, meaning there is a limited amount of LEDs/switches you can hook up to it. A GPIO expander will allow you to access more buttons/LEDs. I will be able to help you build one when you cross this bridge - running out of pins. (My GPIO expander is pictured in one of the posts above) 5) Parts to actually make your panel out of. These include switches, buttons, LEDs, voltmeters and 7 segment displays and joysticks. By these from China as otherwise they may be expensive!, but be prepared to wait a month for shipping. :3 But, before starting to build or really design anything, make sure to figure out what you want on the control panel - what do you want to be able to do from the control panel? Hope this helps Link to KSPSerialIO thread: First post in that thread lists what data the plugin allows you to send and receive.
  12. A month ago i had bought a bunch of parts from china; unfortunately my ebay shipping address was outdated and they where not sent to me. Therefore, last week i reordered the parts. I was surprised however, when i revived one of my original packages yesterday. All in all, this means i may have twice as many parts as I need. I guess i will sell the extras or something, since i likely wont need the extra joysticks, voltmeters, 7 seg displays and adruinos for future projects. Meanwhile, i have still been designing the actual panel layout in cad, now that some of the parts are shipped, i have a better idea of what should go where. Just my monthly progress report, bye for now
  13. @Gaarst sorry for the the necropost It said 'january' so i thought it was recent. (stumbled on this thread through google search)
  14. Planning to build a PC soon. Would paying the extra to get a 7700 instead of an 7600 (or something lower) be worth it? It seems like no one is doing KSP cpu benchmarks.
  15. Just a shot in the dark, but have you made sure that windows is set to "high performance", not "balanced" power saving mode? Sidenote: we have matching avatars lol.
  16. Alright, i see. I still haven't gotten the hang of docking, (my current computer is a bit to slow for KSP to be enjoyable, so i haven't been playing it much ), so cant really comment on docking. One thing that would be cool though is if your DSKY could run programs, like circularize, suicide burns, and maybe even docking (Not currently possible with KSPSIO though)
  17. Looks nice, wish i had a working navball I dont understand however, what exactly are you going to be using the LEDs for?
  18. While waiting for parts to arrive I have built the IO expansions: Those resistors are kinda close to touching each other though x.x
  19. With all the people who are sending keystrokes to the computer via an arduino emulating a keyboard, perhaps a control byte could be added that would designate a single key that the plugin would then press. I am sure .net has an equivalent of the Java robot class.
  20. I have been experimenting with crashing missiles from orbit into the VAB / SPH. Sometimes with a heavy rocket at high speed doesn't do anything, while sometimes the KSC explodes from a very small rocket at slow(er) speeds
  21. Hahaha thats dirt cheap compared to what i found. In the description it lists these pins: VCC, GND, DIN, CS, CLK The first two are self explanatory, but what exactly do the last 3 do? Also is there a built in resistor for the LEDs? Thanks
  22. I have considered the following layout: Pe Alt [8 7-segment displays] time to Pe [6 7-segment displays] Ap Alt [8 7-segment displays] time to Ap [6 7-segment displays] Vessel altitude (Alt / Radar Alt) [8 7-segment displays] time to node [6 7-segment displays] speed (orbit, target, surface, or delta-v left to complete maneuver) [5 7-segment displays] However this adds up to a total of 47 7-segment displays, and doesn't look as clean IMHO Edit: so it will end up being a big price tag
×
×
  • Create New...