Talk:Bullet Shadow - Revision history

Nat: /* Size of the Shadow */ bullet collision...

2011-09-03T13:26:14Z

Size of the Shadow: bullet collision...

Chase-san: /* Size of the Shadow */

2011-09-02T17:22:42Z

Size of the Shadow

Voidious: /* Size of the Shadow */ clarification

2011-09-02T16:31:11Z

Size of the Shadow: clarification

Voidious: /* Size of the Shadow */ typo

2011-09-02T16:27:14Z

Size of the Shadow: typo

Voidious: /* Size of the Shadow */ reply

2011-09-02T16:26:52Z

Size of the Shadow: reply

Skotty: Add question on calculating size of shadow

2011-09-02T16:17:43Z

Add question on calculating size of shadow

GrubbmGait: 'New' inventions still possible.

2011-08-26T19:03:08Z

'New' inventions still possible.

Voidious at 15:07, 23 August 2011

2011-08-23T15:07:40Z

Voidious: comment

2011-08-23T14:04:26Z

comment

Skilgannon: not bad, but needs to be taken into account =)

2011-08-23T13:56:50Z

not bad, but needs to be taken into account =)

← Older revision		Revision as of 13:26, 3 September 2011
Line 54:		Line 54:

	:: I handle it exactly like I do precise intersection cover area, but with just a single line instead. — <span style="font-family: monospace">[[User:Chase-san\|Chase]]-[[User_talk:Chase-san\|san]]</span> 17:22, 2 September 2011 (UTC)		:: I handle it exactly like I do precise intersection cover area, but with just a single line instead. — <span style="font-family: monospace">[[User:Chase-san\|Chase]]-[[User_talk:Chase-san\|san]]</span> 17:22, 2 September 2011 (UTC)
		+
		+	Bullet collision is handled the same way with bullet/robot collision. If bullets' line segments intersect each other, the bullet colloid. The only problem with this method is that if the bullets are in exactly same angle, they won'y colloid... (I believe Robocode use Line2D.intersect, so using that would be safe) --[[User:Nat\|<span style="color:#099;">Nat</span>]] [[User talk:Nat\|<span style="color:#0a5;">Pavasant</span>]] 13:26, 3 September 2011 (UTC)

← Older revision		Revision as of 17:22, 2 September 2011
Line 52:		Line 52:

	: Er, obviously that page doesn't talk about bullet collisions, but talks about the bullet line segment stuff, and precise intersection of wave/bullet is similar to wave/bot. --[[User:Voidious\|Voidious]] 16:31, 2 September 2011 (UTC)		: Er, obviously that page doesn't talk about bullet collisions, but talks about the bullet line segment stuff, and precise intersection of wave/bullet is similar to wave/bot. --[[User:Voidious\|Voidious]] 16:31, 2 September 2011 (UTC)
		+
		+	:: I handle it exactly like I do precise intersection cover area, but with just a single line instead. — <span style="font-family: monospace">[[User:Chase-san\|Chase]]-[[User_talk:Chase-san\|san]]</span> 17:22, 2 September 2011 (UTC)

← Older revision		Revision as of 16:31, 2 September 2011
Line 50:		Line 50:

	I expected to find it on [[Robocode/Game Physics]], but [[Waves/Precise Intersection]] seems to have the best description of it. On each tick, bullets move forward by their speed and a line segment is formed between the two locations. Any two bullets whose line segments intersect will collide. So yeah, I simulate wave and bullet movements tick by tick and make shadows for the angles that would cause a bullet collision - where ever a bullet line segment falls between the corresponding pair of wave circles for that tick. --[[User:Voidious\|Voidious]] 16:26, 2 September 2011 (UTC)		I expected to find it on [[Robocode/Game Physics]], but [[Waves/Precise Intersection]] seems to have the best description of it. On each tick, bullets move forward by their speed and a line segment is formed between the two locations. Any two bullets whose line segments intersect will collide. So yeah, I simulate wave and bullet movements tick by tick and make shadows for the angles that would cause a bullet collision - where ever a bullet line segment falls between the corresponding pair of wave circles for that tick. --[[User:Voidious\|Voidious]] 16:26, 2 September 2011 (UTC)
		+
		+	: Er, obviously that page doesn't talk about bullet collisions, but talks about the bullet line segment stuff, and precise intersection of wave/bullet is similar to wave/bot. --[[User:Voidious\|Voidious]] 16:31, 2 September 2011 (UTC)

← Older revision		Revision as of 16:27, 2 September 2011
Line 49:		Line 49:
	Is there somewhere that describes how Robocode decides if two bullets collide? Details on this would seem to be required in order to calculate the angles for the shadow. Unless all of you are just treating the shadow as a estimated single point (or small fixed width) that does not grow as the bullet wave expands outward. -- [[User:Skotty\|Skotty]] 16:17, 2 September 2011 (UTC)		Is there somewhere that describes how Robocode decides if two bullets collide? Details on this would seem to be required in order to calculate the angles for the shadow. Unless all of you are just treating the shadow as a estimated single point (or small fixed width) that does not grow as the bullet wave expands outward. -- [[User:Skotty\|Skotty]] 16:17, 2 September 2011 (UTC)

−	I expected to find it on [[Robocode/Game Physics]], but [[Waves/Precise Intersection]] seems to have the best description of it. On each tick, bullets move forward by their speed and a line segment is formed between the two locations. Any two bullets whose line segments intersect on will collide. So yeah, I simulate wave and bullet movements tick by tick and make shadows for the angles that would cause a bullet collision - where ever a bullet line segment falls between the corresponding pair of wave circles for that tick. --[[User:Voidious\|Voidious]] 16:26, 2 September 2011 (UTC)	+	I expected to find it on [[Robocode/Game Physics]], but [[Waves/Precise Intersection]] seems to have the best description of it. On each tick, bullets move forward by their speed and a line segment is formed between the two locations. Any two bullets whose line segments intersect will collide. So yeah, I simulate wave and bullet movements tick by tick and make shadows for the angles that would cause a bullet collision - where ever a bullet line segment falls between the corresponding pair of wave circles for that tick. --[[User:Voidious\|Voidious]] 16:26, 2 September 2011 (UTC)

← Older revision		Revision as of 16:26, 2 September 2011
Line 48:		Line 48:

	Is there somewhere that describes how Robocode decides if two bullets collide? Details on this would seem to be required in order to calculate the angles for the shadow. Unless all of you are just treating the shadow as a estimated single point (or small fixed width) that does not grow as the bullet wave expands outward. -- [[User:Skotty\|Skotty]] 16:17, 2 September 2011 (UTC)		Is there somewhere that describes how Robocode decides if two bullets collide? Details on this would seem to be required in order to calculate the angles for the shadow. Unless all of you are just treating the shadow as a estimated single point (or small fixed width) that does not grow as the bullet wave expands outward. -- [[User:Skotty\|Skotty]] 16:17, 2 September 2011 (UTC)
		+
		+	I expected to find it on [[Robocode/Game Physics]], but [[Waves/Precise Intersection]] seems to have the best description of it. On each tick, bullets move forward by their speed and a line segment is formed between the two locations. Any two bullets whose line segments intersect on will collide. So yeah, I simulate wave and bullet movements tick by tick and make shadows for the angles that would cause a bullet collision - where ever a bullet line segment falls between the corresponding pair of wave circles for that tick. --[[User:Voidious\|Voidious]] 16:26, 2 September 2011 (UTC)

← Older revision		Revision as of 16:17, 2 September 2011
Line 45:		Line 45:

	Aaargh, you did it! During my holidays before I could implement it myself! I know I should have kept my mouth shut about this idea I had since Moxiebot came around. Although my idea was much more rudimentary and the original idea is probably almost as old as Robocode itself. Oh well, the implementation still has to be done in my case. --[[User:GrubbmGait\|GrubbmGait]] 19:03, 26 August 2011 (UTC)		Aaargh, you did it! During my holidays before I could implement it myself! I know I should have kept my mouth shut about this idea I had since Moxiebot came around. Although my idea was much more rudimentary and the original idea is probably almost as old as Robocode itself. Oh well, the implementation still has to be done in my case. --[[User:GrubbmGait\|GrubbmGait]] 19:03, 26 August 2011 (UTC)
		+	== Size of the Shadow ==
		+
		+	Is there somewhere that describes how Robocode decides if two bullets collide? Details on this would seem to be required in order to calculate the angles for the shadow. Unless all of you are just treating the shadow as a estimated single point (or small fixed width) that does not grow as the bullet wave expands outward. -- [[User:Skotty\|Skotty]] 16:17, 2 September 2011 (UTC)

← Older revision		Revision as of 19:03, 26 August 2011
Line 43:		Line 43:

	: Funny you should say that about endless tweaking. This struck me as a super straightforward feature that you'd implement, collect your 0.8 APS, and move on. :-) Well, before considering more strategic applications where you modify when/where you fire. I may try doing the integral thing to subtract the exact danger in the shadowed region, but I don't expect much gain from that, if any. And it seems non-debatable that that's the most accurate way of modeling the impact on surfing dangers, right? The approximation of 171 bins can't be too far off. --[[User:Voidious\|Voidious]] 18:07, 22 August 2011 (UTC)		: Funny you should say that about endless tweaking. This struck me as a super straightforward feature that you'd implement, collect your 0.8 APS, and move on. :-) Well, before considering more strategic applications where you modify when/where you fire. I may try doing the integral thing to subtract the exact danger in the shadowed region, but I don't expect much gain from that, if any. And it seems non-debatable that that's the most accurate way of modeling the impact on surfing dangers, right? The approximation of 171 bins can't be too far off. --[[User:Voidious\|Voidious]] 18:07, 22 August 2011 (UTC)
		+
		+	Aaargh, you did it! During my holidays before I could implement it myself! I know I should have kept my mouth shut about this idea I had since Moxiebot came around. Although my idea was much more rudimentary and the original idea is probably almost as old as Robocode itself. Oh well, the implementation still has to be done in my case. --[[User:GrubbmGait\|GrubbmGait]] 19:03, 26 August 2011 (UTC)

← Older revision		Revision as of 15:07, 23 August 2011
Line 42:		Line 42:
	s		s

−	: Funny you should say that about endless tweaking. This struck me as a super straightforward feature that you'd implement, collect your 0.8 APS, and move on. :-) Well, before considering more strategic applications where you modify when/where you fire. I may try doing the integral thing to subtract the exact danger in the shadowed region, but I don't expect much gain from that, if any. And it seems non-debatable that that's the most accurate way of modeling the impact on surfing dangers, right? The approximation of 171 bins can't be too far off. ~~(Btw, we should prolly cut/paste all this to [[Talk:Bullet Shadow]] sometime...)~~ --[[User:Voidious\|Voidious]] 18:07, 22 August 2011 (UTC)	+	: Funny you should say that about endless tweaking. This struck me as a super straightforward feature that you'd implement, collect your 0.8 APS, and move on. :-) Well, before considering more strategic applications where you modify when/where you fire. I may try doing the integral thing to subtract the exact danger in the shadowed region, but I don't expect much gain from that, if any. And it seems non-debatable that that's the most accurate way of modeling the impact on surfing dangers, right? The approximation of 171 bins can't be too far off. --[[User:Voidious\|Voidious]] 18:07, 22 August 2011 (UTC)

@@ Line 12: / Line 12: @@
 ::: Oh yeah - duh. I'm sure eating my words about this not being kinda complicated... ;) --[[User:Voidious|Voidious]] 12:07, 23 August 2011 (UTC)
 :::: It doesn't have to be that bad - the nice thing about precise prediction is that you can exactly reverse what you've done before. Just redo the calculation on waves that haven't hit yet and subtract what you added. --[[User:Skilgannon|Skilgannon]] 13:56, 23 August 2011 (UTC)
 Lol @ "death blow". =) Yes, I calculate as soon as a bullet or wave is added. And as of 1.6.1 (which sadly seems to be exploding somehow on Darkcanuck's client) I recalculate all bullet shadows from onBulletHitBullet. It's not really that nasty. I have my lists of active bullets and active enemy waves - when I add one, I loop through the other, and onBulletHitBullet I loop through both, clearing the old shadows first. --[[User:Voidious|Voidious]] 09:26, 22 August 2011 (UTC)