• Competiton - Star Wars Pod Racer
    244 replies, posted
Could someone make a tutorial on how to make it hover using E2?
Lol, i made those engines in like half an hour, what have you guys been doing all this time?
[QUOTE=Hunta;15371579]Lol, the correct line was interval(20) applyForce( - entity():vel() * 2) this means the chip will apply a force in the opposite direction the the velocity, slowing it down, In mine I removed the Z velocity from the vector, so the pods wouldn't nose dive if they do a jump, you can do this in a few ways, the easiest probably being something like: @persist V:vector F:vector interval(20) V = entity():vel() F = -V * vec(2,2,0) applyForce( F )[/QUOTE] damn i was gonna say that you guys have no clue what your doing. applforce entity pos ? that wont do anything ... you can use :setZ(0) (i think that is the line), but does the same thing.
I just can't understand all this wire talk. So I can't actually get anything I make airborne :(
I wasn't sure what he was trying to do with the code thats all. When i get my chip working, I'll give you all an annotated chip that you can put on your podracer. all you gotta do is wire it up.
Hopefully that will be soon. I'm going to start building my racer right now.
[QUOTE=Maximash;15382826]I wasn't sure what he was trying to do with the code thats all. When i get my chip working, I'll give you all an annotated chip that you can put on your podracer. all you gotta do is wire it up.[/QUOTE] Oh damn, i'm glad to hear that.
Hopefully it'll give the competition a bit more momentum. When do we find out who wins?
[QUOTE=Maximash;15384846]Hopefully it'll give the competition a bit more momentum. When do we find out who wins?[/QUOTE] The first of July. Check page two
im a judge, hunta old me i was :D
A sweet, well I'm working on the chip now, I've made the pods all float a variable distance from eachother. I'll write a mini tutorial on how to use it when i post it.
[QUOTE=Maximash;15386834]A sweet, well I'm working on the chip now, I've made the pods all float a variable distance from eachother. I'll write a mini tutorial on how to use it when i post it.[/QUOTE] for engines [CODE]@name apply force @inputs Button Entity:entity @outputs Z @persist Z Range:ranger A B runOnTick(1) rangerFilter(Entity) Range=rangerOffset(500,Entity:pos(),vec(0,0,-90)) Z=Range:distance() if((Button)&(Z<150)) { A=(150-Z) Entity:applyForce(vec(0,0,10*A+40*$A)*8) Entity:applyForce(Entity:vel() * -1) } if(Button) { B=Entity:angles():pitch()*-1 Entity:applyAngForce(ang(15*B+40*$B,0,0)*5) }[/CODE] for seat [CODE] @name apply force seat @inputs Button Entity:entity @outputs Z @persist Z Range:ranger A B C runOnTick(1) rangerFilter(Entity) Range=rangerOffset(500,Entity:pos(),vec(0,0,-90)) Z=Range:distance() if((Button)&(Z<60)) { A=(60-Z) Entity:applyForce(vec(0,0,5*A+20*$A)*8) Entity:applyForce(Entity:vel() * -0.1) } if(Button) { B=Entity:angles():pitch()*-1 C=Entity:angles():roll()*-1 Entity:applyAngForce(ang(15*B+40*$B,0,15*C+40*$C)*5) }[/CODE] i should still give a dupe of what i had a video of soon maybah but if u want code noaw spawn 4 engine chips spawn 4 entity markers spawn 4 1x1 plates right click each entity marker with a plate wire entity of each chip to the entity marker spawn a numpad input wire button of each chip to the numpad input do same thing for seat but only 1 of chip,marker, and plate
I'm doing a full system. The engines floating has been done already, and its all in one chip instead of two like yours. I think my floating is different to yours... atleast, the Keep upright I used is.
Will the chip be used for just floating? Or will it be used for everything, including movement?
everything, but with alot of variables to play with, like distance of engines from pod, accelleration, speed, etc etc.
Well, i finally got my pod working :D without using any codes from this page besides interval(20) applyForce( - entity():vel() * 2)
Wow Maximash yours looks brand new, my old thing is going to have a hard time keeping up with that. Unless its starts first and has pieces dropping off it so slow you down :P
Lol thanks :), you could always try and throw a piece of metal on yours inside the front of mine. (That makes it shutdown and theres a 50% for it to blow up. Yeah, it's epic.) Mmk guys, mine's pretty much done, just working on making everything smooth and without annoying bugs.
i'm working on this: [IMG]http://img.photobucket.com/albums/v331/DarkEagle/Gmod/gm_modernbuild0022.jpg[/IMG] [IMG]http://img.photobucket.com/albums/v331/DarkEagle/Gmod/gm_modernbuild0023.jpg[/IMG] [IMG]http://img.photobucket.com/albums/v331/DarkEagle/Gmod/gm_modernbuild0024.jpg[/IMG]
Bah you lier, you said it wasn't for the competition >.>. Looks nice though dude, I'll talk you through the chip soon if you want.
I will make one.
[QUOTE=Karbine;15492790]i'm working on this:[/QUOTE] that is tight
I'm gonna make one too, once I'm done studying my Dutch exam. :v:
Yeah me too, as soon as I finish everythi- haha good one. :(
[QUOTE=Hunta;15158949]Ok- seeing as I have been naged, here is my basic pod set up, excluding the cockpit, because I don't like how I did mine, so I'd prefer if you guys figured out your own way. [IMG]http://i208.photobucket.com/albums/bb270/yamclam999/podint.jpg[/IMG] Edit: I've changed a significant amount for things since I made this, but it gives you the basic idea[/QUOTE] if you want a much, much quicker and simpler way for air resistance, just place a speedometer on top of a wire thruster and wire the thruster to the speedo's Z. They are know as "Speedobrakes".
Wow this turned out pretty good of a competition
[QUOTE=Karbine;15510820]if you want a much, much quicker and simpler way for air resistance, just place a speedometer on top of a wire thruster and wire the thruster to the speedo's Z. They are know as "Speedobrakes".[/QUOTE] lol applyforce is MUCH better at being a speedbrake plus, its quicker. one expression line, instead of spawning a thruster, and spawning a speedo and wiring it. also, you can slow down any specific x y z instead of all of it. if you want to slow it down with thrusters, you need one for each x y and z
Just to clear things up, you can use WIRED hoverballs, not the ones controlled by the numpad, is this right? Because, I'm thinking of joining the competition (not that my podracer is going to be any good), and I might use the wired ones.
[QUOTE=Abstrakt;15511369]lol applyforce is MUCH better at being a speedbrake plus, its quicker. one expression line, instead of spawning a thruster, and spawning a speedo and wiring it. also, you can slow down any specific x y z instead of all of it. if you want to slow it down with thrusters, you need one for each x y and z[/QUOTE] tru [editline]03:51PM[/editline] [QUOTE=Ultraken;15515724]Just to clear things up, you can use WIRED hoverballs, not the ones controlled by the numpad, is this right? Because, I'm thinking of joining the competition (not that my podracer is going to be any good), and I might use the wired ones.[/QUOTE] thanks for reminding me, I've forgotten about wired hoverballs. If used right, they could allow for a cheap way to a working racer- wireballs that conform to terrain. That'd be awesome.
It seems much easier than the other options and, judging from previous posts, wired hoverballs are allowed (I suck at Wiremod, so this is great for me). Also, I've seen quite a few posts about applyForce, what the heck is that?
Sorry, you need to Log In to post a reply to this thread.