This is BreakApp in view mode; [Up]
Date: Sun 05-Aug-1989 21:22:06 From: Unknown Subject: BreakApp Wasn't there some discussion regarding the BreakApp game a few months ago? I'm just wondering if there's a fix for when the ball goes to "hyper-velocity" and goes *through* the tiles rather than bouncing them out. In addtion, has anyone made it to level 100? beyond? It's hard to overcome boredom after 50 or so. -Myron PS. Level 76, 12930. Still wired too. >From: ali@polya.Stanford.EDU (Ali T. Ozer)
Date: Sun 05-Aug-1989 23:31:51 From: Unknown Subject: Re: BreakApp In article <13244@polyslo.CalPoly.EDU> Myron Deale writes: > Wasn't there some discussion regarding the BreakApp game a few >months ago? I'm just wondering if there's a fix for when the ball >goes to "hyper-velocity" and goes *through* the tiles rather than >bouncing them out. The fix would be to change the maximum y velocity in the BreakView.m file. The sources to BreakApp are in /NextDeveloper/Examples/BreakApp. I believe it'll be enough if you reduce the maximum velocity by two... >It's hard to overcome boredom after 50 or so. The 1.0 BreakApp has some improvements... 8-) Ali Ozer, NeXT Developer Support aozer@NeXT.com >From: mdeale@cosmos.acs.calpoly.edu (Myron Deale)
Date: Sun 07-Aug-1989 01:31:38 From: Unknown Subject: Re: BreakApp In article <11148@polya.Stanford.EDU> aozer@NeXT.com (Ali Ozer) writes: >In article <13244@polyslo.CalPoly.EDU> Myron Deale writes: >> I'm just wondering if there's a fix for when the ball >>goes to "hyper-velocity" and goes *through* the tiles rather than >>bouncing them out. > >The fix would be to change the maximum y velocity in the BreakView.m >file. The sources to BreakApp are in /NextDeveloper/Examples/BreakApp. >I believe it'll be enough if you reduce the maximum velocity by two... > >Ali Ozer, NeXT Developer Support The velocity I don't mind. Gives ya' a little something to worry about. But when you have "hyper-velocity" it is possible to aim for a tile and have the ball go *through* it. Repeatedly. If the ball can at least hit the tile there's the possibility of things slowing down and the chance of completing the round. Otherwise you just have to let the ball go by. Hopefully there are some remaining. ... sure is hard with the small paddle :) -Myron // disclaimer: i_speak_for_me_and_not_for_them >From: ali@polya.Stanford.EDU (Ali T. Ozer)
Date: Sun 07-Aug-1989 14:44:43 From: Unknown Subject: Re: BreakApp In article <13261@polyslo.CalPoly.EDU> Myron Deale writes: >In article <11148@polya.Stanford.EDU> aozer@NeXT.com (Ali Ozer) writes: >>The fix would be to change the maximum y velocity in the BreakView.m >>file. > > The velocity I don't mind. Gives ya' a little something to worry >about. But when you have "hyper-velocity" it is possible to aim for >a tile and have the ball go *through* it. The reason the ball goes through the tile is because the super cheap implementation allows the ball to skip over the tile when its y-velocity is at the maximum. If you set the maximum y velocity a little lower, it won't go through the tiles. Ali >From: jpd00964@uxa.cso.uiuc.edu
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Marcel Waldvogel and Netfuture.ch.