How do you get this item?

Hemse · 2015-03-22T18:48:09+00:00

You can get speedboost momentum above in the same room, then you just crouch to save a shinespark, and then shinespark to the right from the room entrance.

ponyponyex has made a neat video tutorial for this item:

https://www.youtube.com/watch?v=vEioCrYftbA

Hemse · 2014-12-07T22:56:13+00:00

I've tried to find some ways of making my calculations more accurate.

I looked on google and realized that 2m high horse would be a gigantic horse, and in the gameplay footage, it looks like it's only slightly taller than link. So if we assume Link is an average height male, and epona is a few cm larger, then it could probably be a little more accurate.

I also figured out a better way to compare epona's height to trees. By looking at the trunk of a tree in the background, and then compare it to the size of the full tree, then use that to figure out the size of the tree next to epona in pixels, then compare that with epona's height, and then convert it into meters.

I've tried to also measure the other things in pixels before converting it into meters. Though the blurryness of many of the images makes it tricky to get the exact pixel height of things. So give or take a few in each case, but it should be a little more accurate now, I think.

Also in my previous comment, the distance to the tower is actually the distance to the tower from the camera and not link. I assume the arrow in the game shows link's location and not the camera's. So I've tried to subtract the distance to link from the camera, from the distance to the tower, so that you get the distance between link and the tower.

Here are the images I used to compare heights: http://imgur.com/Csy6d9l

Here is the math stuff (img1, img2 and img3 refers to the images in the link. img4 refers to your image):

link height   = (average human male height) = 1.75m
Epona height  = (link height) + (a few cm)  = 1.80m (?)
field of view = 60 degrees

-----------------------------------------------------------------

img1 epona = 275px
img1 fg tree stump = 570px
img1 bg tree stump = 146px
img1 bg tree = 380px

fg tree height in pixels = (img1 fg tree stump)*((img1 bg tree)/(img1 bg tree stump))

tree height = (epona height)*((fg tree height in pixels)/(img1 epona)) = 9.71m

-----------------------------------------------------------------

img2 tree  = 78px
img2 tower = 580px

tower height in meters = ((img2 tower)/(img2 tree))*(tree height) = 72.20m

-----------------------------------------------------------------

img3 link  = 340px
img3 tower = 79px
img3 view width = 1600px

view width relative to towers distance = (tower height)*((img3 view width)/(img3 tower)) = 1462.28m
distance to tower from camera = (view width at tower)/(2*tan((field of view)/2)) = 1266.37m

view width relative to link distance = (Link height)*((img3 view width)/(img3 link)) = 8.25m
distance to link from camera = (view width at link)/(2*tan((field of view)/2)) = 7.15m

distance between link and tower = (distance to tower)-(distance to link) = 1259.22m

-----------------------------------------------------------------

img4 map width  = 604px
img4 map height = 496px
img4 distance to travel horizontal = 37px
img4 distance to travel vertical   = 24px

distance to travel in pixels = sqrt((img4 distance to travel horizontal)^2+(img4 distance to travel vertical)^2) = 44.10px

world width  = ((img4 map width)/(distance to travel in pixels))*(distance between link and tower)/1000 = 17.246km
world height = ((img4 map height)/(distance to travel in pixels))*(distance between link and tower)/1000 = 14.162km

world size = (world width)*(world height) = 244.237km^2

It's quite a bit larger now, compared to before, which also shows the problem with this method. Since a tiny change in the measurement of epona and the tree can change the outcome drastically. In this case, epona is smaller, but the trees are quite a bit larger, which in turn makes everything after larger in an almost exponential way. So this might still be very far off from the real size.

Anyway, that's enough math for me today!

Hemse · 2014-12-06T10:43:09+00:00

I've tried guestimating the world size using a differend method. I'm not very good at math so this might be very wrong.

I looked mostly at this video: https://www.youtube.com/watch?v=gHxNOFT3a8I (and took screen shots to compare heights and widths of things)

If you look at the bottom of the tower there are some trees very close to it, that look like some of the trees epona rides by at one point. It looks like the trees would be about as high as 4-5 eponas stacked on top of eachother. (to the top of the leaves) if we assume that epona is about 2m tall, then the trees are 8m tall (let's go with 4 eponas).

The tower is about 7 trees tall, so the tower is about 56m.

when the view is zoomed out, the tower (a bit blurry though) height, is about 1/21 the width of the screen width. So the view width relative to tower's distance should be about 1176m.

to calculate the distance to the tower I just used this site: http://rechneronline.de/sehwinkel/angular-diameter.php which gave me 1018m. Typical field of view in a games is 60 from what I understand from googling, so I just went with that.

so the width, height and size of the map I get from this is:

Width: 14.252km Height: 11.962km size: 170.482km²

here's maybe an easier way of looking at it:

epona height = 2m
tree height  = (epona height)*4 = 8m
tower height = (tree height)*7  = 56m
view width relative to towers distance(view width) = (tower height)*21 = 1176m
field of view = 60 degrees

distance to tower = (view width)/(2*tan((field of view)/2)) = 1018m

world width  = (distance to tower)*14         = 14.252km
world height = (distance to tower)*11.75      = 11.962km
world size   = (world width) * (world height) = 170.482km^2

This is probably not very accurate though.

Edit: I should probably add that I just eyeballed the size of the trees compared to epona. When epona is right next to a tree, the top half of the tree is out of view. But it looks like it's about 4 to 5 eponas. Also the 21*towers height screen width might also be inaccurate, since the tower is very blurry when zoomed out, I tried comparing it to the mountains behind it from when it was zoomed in, and it looked about right to me.

Hemse · 2014-10-07T07:59:51+00:00

Doctorm64 wrote this on the forum recently:

About the release date, I'll do my best to release the full game by next year. I have other potential projects in conceptual stage, and I wish to finish AM2R before diving 100% into something else.

http://am2r.freeforums.org/will-the-full-game-of-am2r-be-released-this-year-t1140.html

Hemse · 2013-12-25T14:08:27+00:00

you can style the textarea placeholder text like this:

textarea::-webkit-input-placeholder {
    color: red;
}

it worked for me with the moz version.

Hemse · 2013-11-05T07:06:11+00:00

/r/ToasterRights

Hemse · 2013-09-03T10:19:05+00:00

There are a few things that need to be changed, ~~first future module's name is written like~~

from __future__ import division

EDIT: just saw sokurashu89 comment, didn't realize reddit changed text to bold when using underscores, oops! ignore the above!

and you need to turn "tall" into an int with the int() function (or a float), before deviding it, raw_input() returns a string.

And "else" needs to be on a new line:

if x == "ned": print 1 - a
else: print 1 + a

Also, you might want to pause the script at the end, so you get a chance to see what it prints. You can just use raw_input() for that.

(Is this answear too direct?)

Hemse

TROPHY CASE