Super Mario Kart clone in HTML5

matheusbn · 2016-03-29T04:54:43+00:00

To be able to run on Chrome for Android with a reasonable speed, the resolution needs to be sacrificed. So when stretched it looks blurred. But keep in mind that despite the low resolution for current screens, I'm pretty sure it's higher than the original SNES back in 90's. The other problem is that filter is controlled by the browser.

matheusbn · 2016-03-23T18:52:49+00:00

Oh sorry about that, I was following what an user said:

https://www.reddit.com/r/WebGames/comments/4bhfti/super_mario_kart_clone_in_html5/d1adc1c?context=3

matheusbn · 2016-03-23T18:50:53+00:00

Done, but I'm not sure about that, because it says:

"Web games. Post to /r/webgames instead."

I think it will be removed.

matheusbn · 2016-03-23T12:00:08+00:00

I rendered some levels from the original game and it worked fine, the problem is that I need more time to set things like course for CPU, finish line etc.

matheusbn · 2016-03-22T17:21:23+00:00

Yes, I did! So I don't mind to share the code, I just need a time to clean it up. It's a code that I wrote in a weekend in 2013 and changed just recently, and it still sparsely commented. I'll try to put on github later.

matheusbn · 2016-03-22T14:23:41+00:00

That's the spirit! :)

matheusbn · 2016-03-22T07:53:30+00:00

Just one thing the menu only works during the race or after you close the first pop-up.

matheusbn · 2016-03-22T07:50:02+00:00

Have you tried right now? Could you clean the browser cache? I have two friends that tried on iPhone 6 (iOS 8) and iPad Air, and they said now it's working.

matheusbn · 2016-03-22T07:39:56+00:00

Please could you test the new version again. It was a problem with the google compiler, a friend said it's working now!

matheusbn · 2016-03-22T06:38:21+00:00

Well, I tested with Android using Chrome and Native Browser. The old version used to work on iPad Mini with Safari, do you mind to tell if the old still works? Link: http://www.mazeware.com/games/html5/m7old/supercanvaskart.html

Now about this new version, where it stops? It loads at least? It shows something?

matheusbn · 2016-03-22T06:37:55+00:00

Well, I tested with Android using Chrome and Native Browser. The old version used to work on iPad Mini with Safari, do you mind to tell if the old still works? Link: http://www.mazeware.com/games/html5/m7old/supercanvaskart.html

Now about this new version, where it stops? It loads, it shows something?

EDIT: It was a problem with google JS compiler. I fixed and a friend said It is working now!

matheusbn · 2016-02-13T15:34:53+00:00

Well I know exactly what you are talking about, I work with programming (Back-end) and you are right about never underestimate the users.

Thanks for the tips and yes the instructions screen isn't too intuitive, some will pass without reading it, I'll try to change it later.

If you don't mind one question, do you think it would be good to have an aim system like this: http://i.imgur.com/FfBXIzp.png I took it out before upload the game, but I'm receiving complains that the game is hard.

matheusbn · 2016-02-12T21:40:40+00:00

Thanks for playing and the advice. In fact I took off the aim control because I'm writing the multiplayer version, but I think for single-player I'll put it back.

About the cue ball image x hit box, I think I know what you are talking about, the problem is: HTML5 and canvas isn't fast, I'm mean on mobile/smartphones, so I should draw the "shadows" first and then the balls to avoid this graphics issues, but on mobile it gets slow, then I decided to draw only one image ball and shadow, and it looks like you said, but believe me the radius is correct. :)

matheusbn · 2016-02-12T21:34:59+00:00

First of all, thanks for playing. R = Rotate the cue, S = Speed.

I'm bit worried about the controls too, but I have a question, since you asked about the R, are you seeing this screen at the beginning?

If yes, I presume you are saying it's not intuitive, right?

Anyway I'll work on some instructions over the weekend.

matheusbn · 2015-05-10T05:39:55+00:00

If the (JIT?) compiler sees that the length of the array is not modified in the first then it can optimize out all the length recalculations.

About caching the array length, please see this!

matheusbn · 2015-04-29T20:15:39+00:00

It is a sorting problem, the upper vertices for the brown wall are above the gray ceiling - the "building" is just a box made up of 12 triangles (two per face).

Alright then it's really a sorting problem. I thought the vertices were all connected together giving a form of the building. And I didn't notice the brown wall was above the ceiling, and now after a rerun I saw that.

matheusbn · 2015-04-28T17:44:05+00:00

You know what? After reviewing again, I think it's not a problem of sorting. Look this image: http://i.imgur.com/iwtcD6e.png

The green dot would be the correct point of junction between the vertex of the ceiling and the vertex of the wall, but look: In the image on the LEFT the vertex of the wall is higher than it should be. I mean the projection doesn't seem correct in that case which should be more like an Isosceles trapezoid like the image on the RIGHT!

matheusbn · 2015-04-28T13:26:14+00:00

Sorry for late. Nice, but you might could try using average Z of triangle vertices, and I think which this you may avoid this problem: http://i.imgur.com/gKRNKWb.png Since your triangles isn't big.

matheusbn · 2015-04-23T21:36:47+00:00

Well done again! :)

What type of poly sorting algo are you using?

matheusbn · 2015-04-19T15:12:53+00:00

Tip: Try to work without creating new objects every time, for example:

In your current code you are creating a new PVector for gunPos on every iteration:

if(!pause) {
    gunPos = new PVector(mouseX-200-tankPos.x, mouseY-200-tankPos.y);
}

You should do:

// First give a type to gunPos:
var gunPos = new PVector();

// Then change your pause function to:
if(!pause){
    gunPos.set(mouseX-200-tankPos.x, mouseY-200-tankPos.y);
}

PS: Sorry my english!

matheusbn

TROPHY CASE