thehen, the issue is fixed in the latest beta (r137). Thanks again for your suggestion.

Ashley, fyi I was able to reproduce the problem on several computers. I also exported the project as an HTML 5 website and opened that on different computers as well and still had the problem. As noted above I do not see the issue with r137 beta, i.e. the pointy end of my collision poly now goes right up to the sprites (which is the desired and expected behavior).

Paul

thehen, I will try the beta. Thank you for the suggestion.

Ashley, did you watch the video I uploaded?

Paul

Ashley,

Thank you for taking a look at my report so promptly, however, your Jedi mind tricks won't work on me. I'm not confused about 8-dir behavior and just because someone hasn't found a particular bug doesn't mean it's not there.

In fact, I find your lack of faith disturbing. Seeing is believing so I made a video demonstrating what I am observing. I uploaded the video to Skydrive in the same location as the .capx file. Here's that link again for your convenience.

Examples uploaded to Skydrive

Right-click on the video to download it or left-click to play it in your browser.

Thanks!

Paul

p.s. In case it's not clear, the tone of this reply is intended to be humorous.

Link to .capx file (required!):

sdrv.ms/1aRSf6f

Steps to reproduce:

1. Create a player sprite (50 w, 25 h) with a custom collision polygon such that the nose of the player sprite falls inside the sprite's bounding box. Assign the behavior "8Direction" to the sprite.

2. Create a wall sprite (9 w, 147 h). Assign the behavior "Solid" to it.

3. Create another instance of the wall sprite. Set its Angle to 90.

Observed result:

The collision is correct when the player sprite collides with the non-rotated (Angle=0) wall sprite (i.e. the player sprite stops when its nose hits the wall sprite).

When the player sprite collides with the rotated (Angle=90) wall sprite, the player sprite stops when its bounding box hits the wall sprite and not when its nose hits the wall sprite.

Expected results:

1. Collisions with sprites work uniformly regardless of Angle.

2. Collisions use the collision polygon instead of the bounding box.

Browsers affected:

Chrome: Not tested

Firefox: yes (v 22)

Internet Explorer: yes (v 10)

Operating system & service pack:

Windows 8 Pro 64-bit

Construct 2 version:

Release 132 64-bit

Link to .capx file (required!):

This requires only C2 and the example projects.

Steps to reproduce:

1. Open C2

2. On the Start Page, click on Browse Examples

3. Double click on an example project

4. Notice that a new instance of C2 has launched with the selected example project.

5. The above steps may be repeated; a new C2 instance launches each time

Observed result:

Described above.

Expected result:

Selected project opens in the current instance of C2.

I understand now that "Browse Examples" just opens Windows Explorer to the examples directory but that was not obvious at first. The same icon is used for both "Open Project" and "Browse Examples", however, "Open Project" brings up the file open dialog while "Browse Examples" opens Windows Explorer.

Since a file may be selected in both a dialog and explorer by double-clicking I didn't realize at first that I wasn't getting a file open dialog via "Browse Examples".

It is perhaps not sufficient to rely on the user's understanding of the difference between "browse" and "open" when both commands are associated with the same icon. I suggest that the "browse examples" instead present the user with a file open dialog already set to the examples directory. This would allow a user to try out multiple examples without having to close an instance of C2 for each.

Browsers affected:

Chrome: no

Firefox: no

Internet Explorer: no

Operating system & service pack:

Win 8 Pro

Construct 2 version:

r132 (64-bit)