I Have succeded in porting PocketQuake to CASIOS

[CARPEDIEM]

Yep Moose, you are at 180, and it looks even better @ 200, i was @ 180 up until yesterday.<br>Now if i remove the sky i get 2.6 fps<br>My goal is 3fps, then im a happy man )<br><br>Btw Dan, ¿do you know where i can remove the fire form torches and stuff?

[Dr. Phat]

How would you do that... Remove the sky<br>BTW, is it necessary to have that anti-static stuff when overclocking? I wanna look into it.  

[Moose or Chuck]

Remove the sky, or just make it uni-layered. I never look at the sky anyway. Or better yet, add a console command. That's easy enough.<br><br>Here's my new timerefresh rate after I reached 200MHz:<br>2.431824 FPS<br>And the sound doesn't stutter as much when it's looking towards the portals.<br><br>Seems like every 10MHz adds .1 FPS. Too bad I can't go above 200MHz. But now I've got a smooth SNES Emulator <br><br>Argh, it's not that the screw is to tight. There's a cord in the way. Now I have to go back into the thing AGAIN. If you OC your Casio, watch for cords getting into the way. It's a nuisance.Last modification: Moose Master - 02/24/01 at 12:45:02

[Moose or Chuck]

No, it's not NECESSARY. But I do advise you to get some kind of anti-static method. What I did was opened my computer case until I could get a good fingure hold on a piece of the metal case. Then, every minute or so, I would touch it. I also put the RAM chip ontop of the metal case so that it would be constantly destaticisified (err. you know what I mean). I had no problems, except that cord getting in the way of my stylus holder.<br>Ahh junk. It froze. Oh well, maybe I'll bump it back down to 180 and use it for a few days to burn it in.Last modification: Moose Master - 02/24/01 at 12:56:59

[Dr. Phat]

that' one of those unforseen problems;) Ha!

[CARPEDIEM]

Lol i removed all monsters and stuff and i get now 3.1 fps!<br>if we can get it up to 3 it's gonna be very very playable.<br>

[Moose or Chuck]

Wow, it's good to know that a measily 3 is playable . Boy, Doom is REALLY fast on a 200MHz Casio

[Dr. Phat]

Moose, try landscape, its crashed me three times!  Maybe your overclocked one will do better.

[Dr. Phat]

I had to do a hard reset!  Those suck.  Howvever, I crashed my PalmIII sll the time when I would play the action games for it.  Those were CRAP compared to Doom and Quake!

[CARPEDIEM]

What landscape mode are you guys talking about?<br>Did you compile for mips the latest source of dan or what?

[Moose or Chuck]

Will do. I brought mine back to 180 MHz because it was stalling at 200. I'll bring it back up in a few days though, after it gets used to the speed.<br>Landscrape (ya) mode freezes on me too.<br>Argh. Not only that, but I think it caused a problem with my RAM, when I press reset it told me that inside a fullscreen warning message. Good thing I just made a backup for my speed tests. Or maybe it was because I OC it. Whatever the reason, oh well.<br><br>Ok, how can I add command line params to the PocketQuake shortcut? It doesn't like working for me.Last modification: Moose Master - 02/24/01 at 13:52:07

[Moose or Chuck]

Uhm.. I went into the video options menu, pressed right, then action. I guess it's not implemented yet =)

[CARPEDIEM]

Wow im running at 2.81 now at no apreciable graphics quality decrease!!!!<br>How far can we get??

[cookie319]

carpe, 2.81?? did you make a new build? how'd you get that high?

[CARPEDIEM]

Here Dan, see if you like it, it's an optimization "A la argentina"<br><br>void D_PolysetCalcGradients (int skinwidth)<br>{<br><br>      int xstepdenominv, ystepdenominv;<br>      int p01_minus_p21, p11_minus_p21, p00_minus_p20, p10_minus_p20, t0, t1;;<br>      p00_minus_p20 = (r_p0[0] - r_p2[0]);<br>      p01_minus_p21 = (r_p0[1] - r_p2[1]);<br>      p10_minus_p20 = (r_p1[0] - r_p2[0]);<br>      p11_minus_p21 = (r_p1[1] - r_p2[1]);<br>      xstepdenominv = (1000 / d_xdenom);<br>      ystepdenominv = -xstepdenominv;<br>      t0 = (r_p0[4] - r_p2[4]);<br>      t1 = (r_p1[4] - r_p2[4]);<br>      r_lstepx = ((t1 * p01_minus_p21 - t0 * p11_minus_p21) * xstepdenominv) / 1000;<br>      r_lstepy = ((t1 * p00_minus_p20 - t0 * p10_minus_p20) * ystepdenominv) / 1000;<br>      t0 = (r_p0[2] - r_p2[2]);<br>      t1 = (r_p1[2] - r_p2[2]);<br>      r_sstepx = ((t1 * p01_minus_p21 - t0 * p11_minus_p21) * xstepdenominv) / 1000;<br>      r_sstepy = ((t1 * p00_minus_p20 - t0* p10_minus_p20) * ystepdenominv) / 1000;<br>      t0 = (r_p0[3] - r_p2[3]);<br>      t1 = (r_p1[3] - r_p2[3]);<br>      r_tstepx = ((t1 * p01_minus_p21 - t0 * p11_minus_p21) * xstepdenominv) / 1000;<br>      r_tstepy = ((t1 * p00_minus_p20 - t0 * p10_minus_p20) * ystepdenominv) / 1000;<br>      t0 = (r_p0[5] - r_p2[5]);<br>      t1 = (r_p1[5] - r_p2[5]);<br>      r_zistepx = ((t1 * p01_minus_p21 - t0 * p11_minus_p21) * xstepdenominv) / 1000;<br>      r_zistepy = ((t1 * p00_minus_p20 - t0 * p10_minus_p20) * ystepdenominv) / 1000;<br>      a_sstepxfrac = r_sstepx & 0xFFFF;<br>      a_tstepxfrac = r_tstepx & 0xFFFF;<br>      a_ststepxwhole = skinwidth * (r_tstepx >> 16) + (r_sstepx >> 16);<br><br>}<br><br>that funcion is found in d_polyse.c Try it and you'll notice a neat increase in performance.<br>about 0.13 fps faster on the timerefresh test and the graphics glitches are not very big, the gun isn't as good as it should when you are shooting but hey. 0.13 is 0.13 right?<br><br>