![nerdcubed just cause 2 mods nerdcubed just cause 2 mods](https://i.ytimg.com/vi/rDhAFwjQrZA/maxresdefault.jpg)
I suppose I could kickstart my brain if I could just see some code that lets me extract the data that my navball needs. but as they say, "If you don't use it, you lose it!" which is very true. It means I can no longer keep up with the current systems.
Nerdcubed just cause 2 mods plus#
Plus the fact that I learned too many languages means I keep getting them mixed up.īasically I need help on the KRPC to Arduino coding side!Īs a programmer its tough asking for help. But I have realised that because I haven't really coded anything for several years I am vastly out of practice. Well, another year and I'm starting my prototyping again. and actually the pitch and yaw motors are INSIDE the ball. Oh and here is how the ball is actually two hemispheres connected through a central disk of metal. If I stress test it and it stays working I won't even need to switch to metal. The reason for this is that I'm using 10mm acrylic to make the cage and outer chassis so you can see the thing working inside. I will probably shift to weaker motors when I build a production model design (if I do that is) but I want to see how fast I can drive he changes without it falling apart. To say I jumped when the thing just disintegrated in front of me was an understatement. I had used 2 point support made out of crappy acrylic sheet layered together and the thing just shattered when I switched instantly from prograde to retrograde in a tiny craft. Because my old version wasn't balance right it was like something had hit the prototype with a metal bar. My motors can change the orientation really quickly but I think I will include a ramping system to stop any sudden jolts (I think I broke prototype 4 that way.
![nerdcubed just cause 2 mods nerdcubed just cause 2 mods](https://www.giantbomb.com/a/uploads/scale_medium/8/87790/1897530-box_jcause2.png)
I'm also going to have to select the guidance mode from surface to orbital a target which should affect the FDAI 8-ball like the KSP navball.Ĭhanging the guidance mode is easy (joystick button) but I don't know (yet) how it affects the data coming out to the nav ball. pretty much like how the Apollo Astronauts did.
![nerdcubed just cause 2 mods nerdcubed just cause 2 mods](https://i.ytimg.com/vi/9JPgXaFhBgU/maxresdefault.jpg)
The way I will set up the navball will be to have a Cage option where the switch disconnects the FDAI from the input and returns to 0, 0, 0 position (or where it thinks the 0 position is) and then I just offset the ball using rotary encoders to align the ball. and without memory I end up spending more time looking something up than coding these days. but living on morphine really defocuses the memory. I've programmed in all sorts of stuff over the years, from huge mainframes to tiny embedded stuff. then that pesky target you get on the nav ball when you set a burn too will be translated to the error needles on the FDAI (that's the error or how far out of alignment you are to the burn target in the X, Y and Z axis). Heading, pitch and roll (or properly said, X, Y and Z axis) are the basics but then I want the rates of change for all three too.