Walking, Flying, Custom Replica T-Rex Mech[.23.5]

[m1sz]

nop, they are just opposed medium size landing legs. They work as charm, but often break..!

[Tidus Klein]

HA I dont even know how you do it!

[m1sz]

It's stock + B9 + infernal robotics only

[m1sz]

Enjoy the little GIF teaser!!

http://gfycat.com/ChubbyRipeHoatzin#?speed=2

[Red Iron Crown]

Awesome!

Needs vestigial arms, too. Maybe swing them as part of the balancing act.

[m1sz]

sure, moving them will be cool =)

[VR_Dev]

Super good find with this thread m1. http://forum.kerbalspaceprogram.com/threads/68089-0-23-kOS-Scriptable-Autopilot-System-v0-11-2-13

I probably should have looked harder for people scripting ksp already. That could be huge for our mechs

[m1sz]

yes!, a script would be a lot better doing the walking than ourselves, and also, anyone would be able to do it by activating the script =) which seems easy to do!

[rillz]

Have not had a good look at this yet, but this may be what we need for a script handler.

http://forum.kerbalspaceprogram.com/threads/69313-WIP-kRPC-A-language-agnostic-Remote-Procedure-Call-server-for-KSP

Edited March 28, 2014 by rillz
1st post was unclear

[VR_Dev]

Yeah, so now we have two different scripting options. I'm working on figuring them out right now. It would be nice to be able to change from a "walk" to a "run" setup as the velocity changes too

[Parallax]

this is the utility im using http://www.autohotkey.com/

I assigned hotkeys to activate the different servo groups. Then I wrote a simple script that presses the hotkeys in the order and duration that is needed, which keeps looping while I hold down a specified key. instead of trying to press 7,6,2,0+9,8,4,1,0+9 over and over, I just hold down /, and focus on balance and navigation.

works pretty well:

some sample code

$/::

While GetKeyState("/","P"){

Send {1 down}

Sleep 600

Send {1 up}

Sleep 25

Send {3 down}

Sleep 600

Send {3 up}

Sleep 25

}

return

servo group 1 is activated with "1" and "2", servo group 2 is activated with "3" and "4". to walk I need to press "1" and "3" intermittently. the script holds down "1" for 600ms, lets go of "1" and waits 25ms, then holds down "3" for 600ms, lets go of "3" and waits 25ms, then loops around as long as I hold down "/".

Edited March 30, 2014 by Parallax

[VR_Dev]

I saw this on reddit. Super impressive. Especially how it looks like it turns. The leg structure on it is much more similar to what we are attempting. Between you and M1 I'm super confident we can make it walk. We're just waiting on MassDivide to finish designing the thing then we can work on getting it to walk/fly. Thanks for the interest and the post, you guys blown my mind with your robotics skills

Edited March 30, 2014 by clown_baby

[m1sz]

Parallax is on the team??, this can't go wrong. AWESOME robotics man!

[VR_Dev]

I'm pretty sure I did something awesome. I still am working out the bugs but this could be huge for our walking mechs. I combined the code from a hinge with the code from the B9 VTOL engine which allows you to toggle limits. This could allow us to use a hotkey to toggle through the limits of a part. THis could make turning and transitioning from run/walk much easier.

[VR_Dev]

So I'm really close to being able to set toggle-able limits for the IR parts.

I just need help with some of the code, it's basic stuff but I haven't coded in a long time. If you think you can help, check out my post.

http://forum.kerbalspaceprogram.com/threads/74410-Trying-to-put-toggle-able-limits-on-IR-parts-Just-need-help-with-last-bit-of-code

[VR_Dev]

Updated the main post

[VR_Dev]

So I'm breaking the whole model into parts. I'll be able to figure out attachment points, animations, and .cfgs. But I really, really need help with the textures.

[Naten]

That's a lot of polygons. Sorry, but I suck more at textures than anyone, and that I'm sure. Great, absolutely GREAT job modelling there, and you need more attention.

[VR_Dev]

Thanks, like I said. A guy named DGMM at deviantArt modeled it. I just begged him to send it to me promissing I could make it work realisticaly in Kerbal. Here's his website. Hopefully if I get this to work he'll send me more

http://dgmm.deviantart.com/gallery/

[m1sz]

It's awesome clown_baby, nice work getting everyone to work on this project!

I dont know anything about textures or modelling, so I think my only use is to make it walk!

[MassDivide]

Mass is sad. His model is now useless...

[VR_Dev]

So I've figured out how to do the textures. As you can see here I've isolated the head, however, I'm having trouble loading it into the game. Using the same exact steps as I did to load the whole model into the game doesn't work.

The part loads into the game but doesn't show up under the command tab. When I reload the parts from the debug menu(f-12) I can see briefly in the scroll that the part has problems. However I can't get back to that debug screen. When I look at the log under f-2 is doesn't say anything about the part.

Does anyone know how to view the "reload all" debug scroll in f-12?

[VR_Dev]

Detailed post about the problem I'm having

http://forum.kerbalspaceprogram.com/threads/75803-Only-a-fraction-of-my-custom-t-rex-mech-part-loads-into-KSP

[blackheart612]

So I've figured out how to do the textures. As you can see here I've isolated the head, however, I'm having trouble loading it into the game. Using the same exact steps as I did to load the whole model into the game doesn't work.

The part loads into the game but doesn't show up under the command tab. When I reload the parts from the debug menu(f-12) I can see briefly in the scroll that the part has problems. However I can't get back to that debug screen. When I look at the log under f-2 is doesn't say anything about the part.

Does anyone know how to view the "reload all" debug scroll in f-12?

http://i.imgur.com/GCgcnaH.png

It's in KSP_Data/output_log.txt afaik. Find it there.

Also, it's category = Pods in the cfg, just to be sure you put it like that.

[VR_Dev]

So I'm getting really close. Still a lot of things to figure out. Nodes, attachment points, and attachment rules should be pretty easy.

However the mesh collider is now only surrounding one aspect of the part. Which means that you can only connect things to one aspect of the part. This is a problem

And I've gone back to square one with textures