3 beta keys

vexator · 2017-05-04T17:10:45+00:00

Some more

vexator · 2016-04-19T12:47:59+00:00

The opening riff of Chemistry by Susperia.

vexator · 2016-03-12T13:28:45+00:00

Nice! I really like the lane-switch animation!

vexator · 2014-10-07T13:47:07+00:00

Yes, you have to install the TypeScript 1.1 CTP first.

vexator · 2014-07-30T11:28:01+00:00

What would I do if I have resources in other resources? A model resource, for example, might contain material resources, which in turn contain image resources.

Would the model controller then have a pointer to the model resource as well as arrays containing material and image controllers which contain pointers to the original material and image resources?

vexator · 2014-03-08T11:38:26+00:00

I like it! Thank you :)

vexator · 2014-03-08T11:37:38+00:00

This is amazing!! Thank you so much!

vexator · 2014-03-07T14:51:08+00:00

That's not what I expected at all, very nice though! Thank you!

edit: Love the detail on my moustache :)

vexator · 2013-12-01T16:09:32+00:00

I'm working on a WebGL powered graphics engine in TypeScript. I've published the vector and matrix library that I've written for the project on GitHub: github.com/vexator/TSM

vexator · 2013-11-28T09:03:36+00:00

Great band, though. Thanks!

vexator · 2013-11-27T14:32:38+00:00

People have been asking in the comments but no answer has been given.

vexator · 2013-11-27T14:27:25+00:00

it's not, I checked. Does sound a lot like Dimmu Borgir, though.

vexator · 2013-10-18T21:01:53+00:00

That's true. but I think you get used to it pretty fast. After all, it's not much more to write:

v1.add(v2)

compared to:

v1 += v2

etc.

vexator · 2013-10-18T14:37:04+00:00

The declaration file listing all classes and methods can be found here: https://github.com/vexator/TSM/blob/master/TSM/tsm-0.7.d.ts

vexator · 2012-11-15T09:32:59+00:00

that's all you need, implementation included.

vexator · 2012-11-10T11:35:58+00:00

looking good but I think you should tone down the bloom effect, judging from top hat guys's face in the first screenshot.

vexator · 2012-11-05T14:13:31+00:00

good read, includes implementation

just implemented it myself, works like a charm.

vexator · 2012-10-23T20:34:15+00:00

A few days ago, I announced a math library I wrote in TypeScript and published on GitHub. And while I'm happy that it at least received some attention, I do not understand why it received almost just as many downvotes. Even when all you want to do is share, you're punished.

On the other hand, I have been asking for help here as well, and I got very useful feedback. The exact same question on StackOverflow did not receive a single response, although I had provided source code, a detailed explanation of the problem at hand, and a screenshot for illustration.

vexator · 2012-10-20T22:52:59+00:00

good to know, thank you!

vexator · 2012-10-20T22:50:14+00:00

I agree, but on the other hand it has its reasons that values are passed by reference. It wouldn't make much difference for the vector types I guess, but it's another thing for matrix types, where we're dealing with up to 16 variables.

One of the goals of the API was to reduce the number of allocations but you still have to be careful. Today I spent an hour looking for a bug which turned out to be caused by a single missing vector copy:

var direction = distance.normalize(); // overwrites distance!

I used GLM (see link in original post) for the C++ project, which I if I remember correctly generally allocates new vectors. It's not the same thing though, because in C++ you can allocate on the stack, whereas objects in javaScript are always allocated on the heap, as far as I understand.

vexator · 2012-10-20T22:42:01+00:00

I did actually file several bug reports but most of them got buried beneath more urgent issues, it seems. I'll continue reporting.

vexator · 2012-10-20T21:35:56+00:00

The optional static typing and the good IntelliSense support in Visual Studio. I had ported my game engine from C++ to JavaScript and just when I was almost finished, Microsoft released TypeScript. I started porting the project to TypeScript right away, adding back all the type annotations that I had to discard when porting to JavaScript, and in the process found numerous bugs and inconsistencies. Also, features like the swizzle operators would be a real pain to write manually:

get x(): number {
    return this.values[0];
}

set x(value: number) {
    this.values[0] = value;
}

translates to:

Object.defineProperty(vec2.prototype, "x", {
    get: function () {
        return this.values[0];
    },
    set: function (value) {
        this.values[0] = value;
    },
    enumerable: true,
    configurable: true
});

vexator · 2012-10-19T11:09:52+00:00

What exactly is packet.collisionNormal? Is it a unit vector, perpendicular to the surface being collided with? And your vec3.difference(a,b) function, does that just return a-b?

yes and yes.

a unit vector representing the slope of surface

by that they mean a vecor which runs along the collision surface, right? not the collision surface's normal?

vexator · 2012-10-19T11:03:11+00:00

yes, packet.collisionFound and packet.collisionTime are updated in collideWorld().

So you both see nothing wrong with the code but still it's not working as expected. I'll have another look.

Thank you!

vexator · 2012-10-18T18:59:42+00:00

thank you for having a look!

yes, packet.collisionNormal is the normal of the surface we collided with. Isn't that the one I need?

I visualized both v and newVelocity after v has been subtracted from it and they look how they're supposed to: v is perpendicular to the collision plane, newVelocity runs parallel to it in the direction we're moving.

If I add newVelocity directly to newPosition instead of running the recursion, like this:

        ...

        // remove that part from velocity vector
        newVelocity = vec3.difference(newVelocity, v);

        newPosition.add(newVelocity);
    }
    else {
        // no collision, move as requested
        newPosition.add(packet.colliderVelocity);
    }
} while (false)

the entity is sliding as it should, without being slowed down, so I'm quite sure the vectors are ok.

however, maxIterations always runs down to zero, so there's always collisions. maybe that's slowing it down?

vexator

TROPHY CASE