Drmd V5 Beta 4 - Squidge-injected Version

[washo]

OMFG...
you're a god among humans...

Thank you very much

see you :lol:

 

[Nickmon]

I managed to crash it:

Was playing squideSnes with MMU hack (playing Mario World), exited it
Loaded DrMd 5.4 and it crashed straight away before the nice gp2x.com logo

After a reboot it ran fine...

Some sort of memory issue?

 

[Racer445]

Awesome. Awesome. Awesome.

Did I mention it is awesome? EVERYTHING I throw at it runs around 60 FPS.

A few bugs though. While playing the Game Gear game Sonic & Tails, the rings are inside an orange square, and when playing Sonic Drift, the score area where positions are displayed is blinking really fast... It hurts my eyes to look at it.

PSyMastR, I get the same thing with the pausing in Sonic 3, 3 and Knuckles, Sonic 3D, and also while paused and during the SEGA intro in Sonic and Knuckles.

 

[PSyMastR]

My question is, if the screen doesn't display at 60FPS, then how can the emu's display at 60fps?

Get a high-speed camera and prove that to me .

Interesting, I will have to download that emu and read the new readme when I get home.

So this hack works because the Blitter is using the high memory? I don't know why this should work is what I mean.

I thought this was already proven with a video encoded at 60 FPS, on my PC there were details that were there that were missing on the GP2x, that were in every other frame (showing its slower then 60fps). I dunno lol.

 

[sam fisher]

My question is, if the screen doesn't display at 60FPS, then how can the emu's display at 60fps?

Get a high-speed camera and prove that to me .

Interesting, I will have to download that emu and read the new readme when I get home.

So this hack works because the Blitter is using the high memory? I don't know why this should work is what I mean.

I thought this was already proven with a video encoded at 60 FPS, on my PC there were details that were there that were missing on the GP2x, that were in every other frame (showing its slower then 60fps). I dunno lol.

Or it could just be that your eyes are better suited to your pc

for the last bloody time!!!

IT MAY NOT BE ABLE TO DECODE VIDEO AT 60FPS BUT THE FUCKING TFT CAN DO THAT. Do you understand....

 

[PSyMastR]

Sam... relax k? I understand.

 

[sam fisher]

Well you don't seem to.

 

[paulobecker]

Yeah, that was easily fixed, but some roms are completely freaking out on me, and only the directional controls seem to work so I can't seem to confirm anything which is strange. And yes I have tried re-configuring the controls.

Same here. I only tried Sonic 3 real quick. Framerate was amazing, but buttons were all screwy.

Yup, me too. Tried playing Sonic 3 and the only button that was working was Directional Up. Can't do much other than watch the demo in amazement at the speed

 

[naples39]

Have you guys having control problems tried remapping the controls in the menu? I did and everything works fine for me (including sonic 3).

 

[paulobecker]

Have you guys having control problems tried remapping the controls in the menu? I did and everything works fine for me (including sonic 3).

To tell you the truth, nope, heheh. Didn't even cross my mind. I'll try again and report back afterwards.

 

[Rivroner]

Impressive, thanks Reesy ( and Squidge )
Before with Vectorman 1 y 2 with 260-270 mhz OverClock it runs at 40 frames more or less.Now, it runs at 40 frames with 200 mhz.So, if you overclock these games now will run at fullpeed and constant frames
Thank you very muck guys

 

[paulobecker]

Ok now I feel embarassed. Adjusted the controls via the game options and all works fine now
*Hides until his face unblushes*

 

[nubie]

Sam... relax k? I understand.

They underclocked the mplayer, I think.

The mplayer has nothing to do with the homebrew or any LCD/Clock/refresh settings anywhere else in any application or game or even the menu, it is a seperate program with unknown settings right now. Agreed?

Not to mention I don't think it is supporting 3 Bframes yet, at least that was the problem I was having with my encoded Xvids.

On Topic (Enough thread hijacking for now.)

I love the great work being done on this emulator by the dedicated Reesy .

Quick Question for Reesy: Did you ever get the pixels being written to the screen the way you wanted to? (I.E. not the GP32 way anymore and optimized for the GP2X)

I checked the readme and couldn't find it.

 

[williamc]

I'm currently using version 4.3. I'm anxious to update to 5.4b but have a concern about the save state problem mentioned in the readme. Will my 4.3 save states be unusable in the new version or is this only if you upgrade from beta 2? Thanks.

William

From the readme:

Re-wrote save state code which has broken backward compatiblity with beta 2. I'm not going to fix this
because basically I have no idea what has changed. The re-write means that save states should never be
broken again though.

 

[shinneri]

I'm currently using version 4.3. I'm anxious to update to 5.4b but have a concern about the save state problem mentioned in the readme. Will my 4.3 save states be unusable in the new version or is this only if you upgrade from beta 2? Thanks.

William

From the readme:

Re-wrote save state code which has broken backward compatiblity with beta 2. I'm not going to fix this
because basically I have no idea what has changed. The re-write means that save states should never be
broken again though.

Could you just have both versions and only open the games you have saves for in your old version?

 

[Reesy]

Quick Question for Reesy: Did you ever get the pixels being written to the screen the way you wanted to? (I.E. not the GP32 way anymore and optimized for the GP2X)

Nope, that is next. I'm going to re-write all of the MD rendering routines, not much point in worring about SMS/GG as they run fast enough please the fact you can always use AlexKidd2x.

I'm currently using version 4.3. I'm anxious to update to 5.4b but have a concern about the save state problem mentioned in the readme. Will my 4.3 save states be unusable in the new version or is this only if you upgrade from beta 2? Thanks.

William

From the readme:

Re-wrote save state code which has broken backward compatiblity with beta 2. I'm not going to fix this
because basically I have no idea what has changed. The re-write means that save states should never be
broken again though.

No save states from any older versions of DrMD will load in v5b4.

 

[DaveC]

MD:

I noticed that there are 1 cm black lines that appear randomly on both sides of the screen on many games.

Also in Altered beast your character "spazzes out" while walking.

GG: some games have rectangles around the sprites.

I noticed in Megadrive that solid colors have a subtle dithered "screen door" type texture. I never noticed that before, is that new? Is it supposed to do that?

Other than those bugs (and old ones like the windowing bug in Zombies') The speed is incredible, it really DOES run 60 fps, no joke. Thanks for the update.

 

[DARKGATE]

I have found a bug with DRMD b4 and 5
MORTAL KOMBAT 1 don't work the comands =°| sigh

 

[CeNTauR2]

Incredibly release, Reesy, and what a find, Sqidge!

I can confirm that ROMs occasionally work or not, just as the want to.
I too have the little black lines around the edge of the screen.
And the buttons just won't work sometimes.

Keep up the great work!

 

[Reesy]

Yes I think the black lines are being created as I clear the whole frame buffer ready for the next frame. This could be effecting the DMA that drives the LCD, without caching on the frame buffer I can do this but it looks like I can only clear 1 line at a time with caching on. I'll play around and see if I can clear this up.

I'm also have the occasional lockup when loading a rom that has loaded correctly before, not sure whats causing this I'll try to work it out.

EDIT

Nope just tried only clearing 1 line at a time and it didn't make a difference..oh well.