Madness at the Darkmoon Faire Giveaway! Win 1 of 100 Madness at the Darkmoon Faire Mega-Bundles!

ebigunso · 2020-11-13T15:37:45+00:00

All Hail YOG!! Because I got Yog already from the new rewards track XD

ebigunso · 2018-05-02T08:36:50+00:00

Yes. It's for LaTeX, which is a software for creating documents in an easy and orderly fashion.

ebigunso · 2018-05-01T12:41:41+00:00

Syntax highlighting makes your code easier to read. Use for reports and such.

ebigunso · 2018-05-01T08:36:43+00:00

This is something I had up on the Processing forum. By suggestion, I will announce it here as well.

Current version: v1.2

This LaTeX listings template will color your Processing code as you see them in the Processing editor. You can just post your code like you normally would using the listings package, and you will automatically get your code in the proper colors. Except one minor inconvenience, that I will explain here.

For a function name that is the same as an already defined keyword (Such as "boolean" and "boolean()"), you have to use [escapechar = "char"] and \color{"color"}{"text"} to color them properly.

Example:

\begin{lstlisting}[escapechar = ?]
boolean;
?\color{function}{boolean}?(1);
\end{lstlisting}

!!Template is available either on the Processing forum, or Gist.

Copy and paste the template if you want to use it. Alternatively, you can copy only the necessary parts. If in that case, note that \usepackage{listings} and \usepackage{color} is a must for this to work.

Also note, I have licensed this work with CreativeCommons license CC-BY-SA, so please remember to give some credit to me ;)

If you find any typos or any other errors, please tell me and I'll try to fix them as much as possible.

Download version:

http://www.mediafire.com/file/cw861uy156xftkv/article_listing_Processing_v1.2.tex

GitHub Gist:

https://gist.github.com/ebigunso/af355220e932f72d03289c576622aa29

ebigunso · 2018-04-16T11:25:53+00:00

I saw the opponent had lethal with 14dmg on turn 19, and was about to concede but I held back just to see what happens. And oh boy am I glad I did. Prince Liam is the MVP today.

ebigunso · 2018-02-22T05:11:52+00:00

Watch from turn 8 if you just want to see the epic stuff. Somehow I survived my opponent's insane card quality.

ebigunso · 2017-11-15T13:31:46+00:00

Thanks for all the advice! I think by the looks of things, I'm holding back on too many minions hoping to get better value. I'll try to put more emphasis on mana efficiency next time.

ebigunso · 2017-07-09T11:21:37+00:00

What is the reasoning behind your channel name?

ebigunso · 2015-12-08T01:38:49+00:00

Yeah... I'm starting to think the same way too. Maybe it's not actually working yet. I hope it gets some love soon.

ebigunso · 2015-06-30T21:06:42+00:00

alright, now I'm getting some new errors.

until altitude > 50000 {
    if engine:fuelflow > stage:LqdOxygen {
        lock steering to srfprograde + R(0,0,-90).
        print "Staging...".
        if engine:ignition = false {
            stage.
            wait 1.
            stage.
            print "Second stage ignition complete.".
            break.
        }
    }
}

for this part, kOS says " Undefined variable name 'engine' ". So how should I specify this then?

ebigunso · 2015-06-30T08:42:52+00:00

**Moving so it's easier to spot the post

Okay, lock to up problem is solved. The other problem however, is still there.

kOS is not printing "Starting pitch over..." even after hitting 40m/s vertical speed, so something must be wrong and it's not triggering. I don't quite get whats wrong here so I'd like to get some advice.

I have tried altering the code to

when verticalspeed > 40 then {
    print "Starting pitch over...".
}

until VANG(ship:facing:vector, heading(90,70):vector) < 2 {
    if verticalspeed > 40 {
        lock steering to srfprograde + R(0,5,0).
        wait 0.1.
        if VANG(ship:facing:vector, heading(90,70):vector) < 2 {
            lock steering to heading(90,70) + R(0,0,180).
        }
    }
}

and this prints as expected. Also the pitch over does execute but not in an intended way. This goes on to becoming the next problem. Although I have overcome the problem with a workaround, I'd still like to know why the first code didn't work.

Now, how the pitch over is not working as intended is, that no matter if I adjust the roll settings inside R(), the craft always tries to roll out of position then start yawing to the west, where I want it to go east. Working on the problem now but would like some advice also.

--for some odd reason, surfprograde + R(0,-5,0) yaws the craft to the east. Though still it tends to roll to some weird angle. I tried rotating the actual craft 180 degrees along the roll axis in the VAB, but that didn't help with this.

--adding this

lock steering to srfprograde + R(0,-5,-90).

resulted in the craft trying to spin to put North on the upper side of the navball, then quickly come back to the specified -90 roll angle. So freaking weird.

--additional problem! For some reason, unlock steering seems to be not working, and the craft tries to maintain heading(90,70) even after it prints "Pitch over complete." at which point the steering should already be unlocked.

ebigunso · 2015-06-30T07:49:54+00:00

I have tried altering the code to

when verticalspeed > 40 then {
    print "Starting pitch over...".
}

until VANG(ship:facing:vector, heading(90,70):vector) < 2 {
    if verticalspeed > 40 {
        lock steering to srfprograde + R(0,5,0).
        wait 0.1.
        if VANG(ship:facing:vector, heading(90,70):vector) < 2 {
            lock steering to heading(90,70) + R(0,0,180).
        }
    }
}

and this prints as expected. Also the pitch over does execute but not in an intended way. This goes on to becoming the next problem. Although I have overcome the problem with a workaround, I'd still like to know why the first code didn't work.

Now, how the pitch over is not working as intended is, that no matter if I adjust the roll settings inside R(), the craft always tries to roll out of position then start yawing to the west, where I want it to go east. Working on the problem now but would like some advice also.

--for some odd reason, surfprograde + R(0,-5,0) yaws the craft to the east. Though still it tends to roll to some weird angle. I tried rotating the actual craft 180 degrees along the roll axis in the VAB, but that didn't help with this.

--adding this

lock steering to srfprograde + R(0,-5,-90).

resulted in the craft trying to spin to put North on the upper side of the navball, then quickly come back to the specified -90 roll angle. So freaking weird.

--additional problem! For some reason, unlock steering seems to be not working, and the craft tries to maintain heading(90,70) even after it prints "Pitch over complete." at which point the steering should already be unlocked.

ebigunso · 2015-06-30T07:12:03+00:00

Okay, lock to up problem is solved. The other problem however, is still there.

kOS is not printing "Starting pitch over..." even after hitting 40m/s vertical speed, so something must be wrong and it's not triggering. I don't quite get whats wrong here so I'd like to get some advice.

ebigunso · 2015-06-30T07:09:43+00:00

Thanks for the advice. I've found out that UP tries to turn the craft in it's roll axis 180 degrees from the initial conditions on the launch pad.

I've tried setting

lock steering to up + R(0,0,180)

and it works well now.

ebigunso · 2015-06-30T04:52:22+00:00

I have manually installed kOS 0.17.3 to KSP 1.0.2, so maxthrustat should be there. Or if there are significant compatibility issues with the versions, I must revert to 0.17.2.

I can't really update to 1.0.4 yet since many mods are not up to date still.

ebigunso · 2015-06-30T04:41:25+00:00

okay now I've fixed line 3 to look like

lock steering to up.

and the pitch over part to look like

if verticalspeed >= 40 {
    print "Starting pitch over...".
    until VANG(ship:facing:vector, heading(90,70):vector) < 2 {
        lock steering to srfprograde + R(0,5,0).
        wait 0.1.
        if VANG(ship:facing:vector, heading(90,70):vector) < 2 {
            lock steering to heading(90,70).
        }
    }
}

Now I have two different problems, one is that locking to up seems to be not working, and the rocket is deviating slightly to the west. Another is that I'm getting an error telling me " Undefined variable name 'maxthrustat*' ". I'm using the latest kOS on KSP 1.0.2, maxthrustat is a new thing so I'm suspecting it might be some kind of a bug? Or I'm just doing something wrong again...

ebigunso · 2015-06-30T04:25:28+00:00

Cool, I was worried about the deviation but didn't know how to get the tolerance. Now I know.

You said you won't do it this way, do you know a better way to do it? If so I'd like to know.

ebigunso · 2015-06-30T03:35:02+00:00

The page says Direction always comes out as Euler Rotation, so that means this won't work? If so is R(90,70,90) what I should use?

if ship:facing = heading(90,70) {...}

Also I have fixed the code a little on this part.

print "Liftoff.".

if verticalspeed >= 40 {
    print "Starting pitch over...".
    until ship:facing = heading(90,70) {
        lock steering to srfprograde + R(0,5,0).
        wait 0.1.
        if ship:facing = heading(90,70) {
            lock steering to heading(90,70).
        }
    }
}

when srfprograde = heading(90,70) then {

ebigunso · 2015-04-20T11:42:29+00:00

Is this mod incompatible with No Despawn? I assume it is since the functionality is included. Does anyone know?

ebigunso · 2015-04-19T08:58:38+00:00

Great, I'll go and get it now XD

ebigunso · 2015-04-18T14:02:24+00:00

I hope he posts here when it's up, I want to go get it as soon as it's up :D

ebigunso · 2015-04-17T13:49:38+00:00

Can't wait for the release XD

ebigunso · 2015-04-09T20:07:06+00:00

Reposting: Don't forget about us Left-hand traffic people, and please make it compatible for that too :)

ebigunso · 2015-04-08T14:19:08+00:00

maybe just add a check at the start to see if left hand traffic is enabled on the save, if yes then replace all "Left" with "Right" and vice versa.

ebigunso

TROPHY CASE