Test

Mark Chisholm

Administrator
Administrator
Anyone wanna try an eye-hand test? Try this:
Test

I believe that it says that US fighter pilots will need to do 2 minutes of this? I can't break 21 seconds.
The rule is move the red box and don't touch the black or let the blue squares touch you.
 
Maybe using a joystick as the input device. I know this touchpad ain't the best tool for the job, at least not tuned the way I normally have it set. Just got 20.8.

I doubt, if it's true the pilots use that specific tool, that they use a computer mouse.

Other major factors in any comparisons here are browser, operating system, and CPU/RAM speed. Apples to apples may be unlikely.
 
To keep it from speeding up, fetch a copy of the page to your hard drive and edit it, then view it in your browser.

Search for the second occurrence of the word "speed". It's in a section that looks like this:
<font class="small">Code:</font><hr /><pre>function movenemies() {

gametime = gametime + 1

if (gametime &gt;= 0 &amp;&amp; gametime &lt; 100) speed = 80;
else if (gametime &gt;= 100 &amp;&amp; gametime &lt; 200) speed = 60;
else if (gametime &gt;= 200 &amp;&amp; gametime &lt; 300) speed = 40;
else if (gametime &gt;= 300 &amp;&amp; gametime &lt; 400) speed = 30;
else if (gametime &gt;= 400 &amp;&amp; gametime &lt; 500) speed = 20;
else speed = 10;</pre><hr />
Comment out the "if" lines by putting a pair of slashes (//) before the text and add one line with "speed = 80;". Or make it "speed = 90;" to slow it down some (or "100" to slow it even more). Don't forget to terminate the line with a semi-colon.

Like this:
<font class="small">Code:</font><hr /><pre>function movenemies() {

gametime = gametime + 1

speed = 80;
//if (gametime &gt;= 0 &amp;&amp; gametime &lt; 100) speed = 80;
//else if (gametime &gt;= 100 &amp;&amp; gametime &lt; 200) speed = 60;
//else if (gametime &gt;= 200 &amp;&amp; gametime &lt; 300) speed = 40;
//else if (gametime &gt;= 300 &amp;&amp; gametime &lt; 400) speed = 30;
//else if (gametime &gt;= 400 &amp;&amp; gametime &lt; 500) speed = 20;
//else speed = 10;
</pre><hr />

Alternatively, you could leave the speed increases uncommented-out but just increment each speed value by 10 or something. Every time the code passes through that routine it increments the "gametime" counter and that's what ramps up the speed.

I didn't look through the whole page so don't know if it's there or not, but it would be good for something like this game to time how long it takes to do some little thing, and use the result to tune the speed of the page accordingly so it would run the same everywhere.

A few years ago a friend ran a test of some relatively simple javascript, comparing the speed between the Linux and Windows versions of Netscape, and between the Windows version of Netscape and Internet Explorer. All on the same hardware, the order from fastest to slowest was the same as just mentioned. That was a few versions of everything ago, though. I don't know how they'd stack up now.
 
I would do it this way.

<font class="small">Code:</font><hr /><pre>
function movenemies() {

gametime = gametime + 1

if (gametime &gt;= 0 &amp;&amp; gametime &lt; 100) speed = 80;
else if (gametime &gt;= 100 &amp;&amp; gametime &lt; 200) speed = 60;
else if (gametime &gt;= 200 &amp;&amp; gametime &lt; 300) speed = 40;
else if (gametime &gt;= 300 &amp;&amp; gametime &lt; 400) speed = 30;
else if (gametime &gt;= 400 &amp;&amp; gametime &lt; 500) speed = 20;
else speed = 10;
speed = 80;
</pre><hr />
It burns a few extra cycles processing the if/else clauses, but that's kind of the point anyway /forum/images/graemlins/grin.gif.
 
5 y=1
10 x=1
20 print "you guys are cheaters"
30 x=x+1
40 if x&lt;5000 goto 20
50 print "the end"
60 print "basic rocks"
70 y=y+1
80 if y&lt;10 goto 10


hahaha. boy that is old school. anyone here know fortran? cobol? C++? not me. just some old school Basic. Hahaha
 
[ QUOTE ]
I would do it this way.

It burns a few extra cycles processing the if/else clauses, but that's kind of the point anyway /forum/images/graemlins/grin.gif.

[/ QUOTE ]
"tomato"

Wouldn't that method would tend to progressively slow play (even if imperceptibly) as the counter engulfs more and more of the tests? :)
 
[ QUOTE ]
[ QUOTE ]
I would do it this way.

It burns a few extra cycles processing the if/else clauses, but that's kind of the point anyway /forum/images/graemlins/grin.gif.

[/ QUOTE ]
"tomato"

Wouldn't that method would tend to progressively slow play (even if imperceptibly) as the counter engulfs more and more of the tests? :)

[/ QUOTE ]

I was wondering that too.
 
[ QUOTE ]

"tomato"


[/ QUOTE ]
Most definitely, but ...

[ QUOTE ]
Wouldn't that method would tend to progressively slow play (even if imperceptibly) as the counter engulfs more and more of the tests? :)

[/ QUOTE ]
That slight change compensates for user fatigue /forum/images/graemlins/grin.gif. You know you have to design things to work this way!

Jimmy,

Yes, no, yes and yes to at least a dozen more.

Cary
 
[ QUOTE ]
To keep it from speeding up, fetch a copy of the page to your hard drive and edit it, then view it in your browser.
(snip)

[/ QUOTE ]
I assumed it was meant to speed up, and if I can't handle it I admit my flaw and move on. I'm not really motivated to try and rig the game so it looks like I win even if I lose (with all due respect to Capt. Kirk).

k
 
I wasn't thinking so much in terms of "cheating" in order to "win" or anything. More along the lines of pointing out a way to make it a little more enjoyable. I have not ventured beyond about 40 seconds. I find the exercise interesting but not compelling.
 

New threads New posts

Back
Top Bottom