Gigadrive 0.023

[fdave]

thanks!

ok, i first, as i always do, when a new version comes out, tested slimeworld and it has sound, but no graphics. weird, i always thought, it couldn't be emulated, but i can hear myself shoot, so the game runs, but there's nothing on the screen.

anyway, thanks for the update...

rings a bell actually - i think slimeworld does something unusual with colour, though i can't recall exactly what

i've definitely emulated it before though.

i'll download it and find out what's strange about it

 

[fdave]

I'm trying to decompress the FXE and hex-hack the clockspeed, but I figure Dave's got this one covered.

heh - yeah just search for 0x2c001 or 156000000 or something

 

[loki666]

Great!
Could you make a version colcked to 166mhz? :huh:

Damn I lost the e-mail with the settings in..

I know these two, anyone got 166 offhand?

// GpClockSpeedChange(132000000, 0x24001, 2); // speed = 133 Mhz
GpClockSpeedChange(156000000, 0x2c001, 2);


I'll have to go through and search for my e-mail from Ryleh....

http://www.gp32world.co.uk/html/overclocking_params.html

have to admit that table is just double-dutch to me


Anyway I stuck this in:
// GpClockSpeedChange(132000000,0x24001,2); timer=15;
// GpClockSpeedChange(156000000,0x2c001,2); timer=13;
GpClockSpeedChange(165000000,0x2f001,2); timer=12;

Does anyone else have the problem of the Timers going too fast when you overclock?

Let me know if 165mhz works because obviously I can't check here

Also, does anyone know what the third parameter should be? Is it 2 or 3 - what's the difference? 3 just seems to make the timers run too fast again

the third parameter set the clock dividers, there are 3 click in gp32
1 for arm920, 1 for sdram and lcd and 1 for the rest (usb,timers, uart)
i think it should be '3', 3 is for divider 1:2:4
read the s3c2400 ref manual (available on mr spiv web-page

 

[Dante]

awww man it's not fair, this is released and my batteries die what a bitch , thanks anyway dave your the man

 

[MaDsk8tard]

thanks fdave for your new version but :
landstalker and mr nuts , moonwalker not working yet...
if you can do works this games for your next release it could be great

 

[foft]

This is very very cool! Hadn't tried Gigadrive (or any GP32 MegaDrive emu). Exceeded all my expectations!

It doesn't sound that horrible...

Mark

 

[fdave]

Great!
Could you make a version colcked to 166mhz? :huh:

Damn I lost the e-mail with the settings in..

I know these two, anyone got 166 offhand?

// GpClockSpeedChange(132000000, 0x24001, 2); // speed = 133 Mhz
GpClockSpeedChange(156000000, 0x2c001, 2);


I'll have to go through and search for my e-mail from Ryleh....

http://www.gp32world.co.uk/html/overclocking_params.html

have to admit that table is just double-dutch to me


Anyway I stuck this in:
// GpClockSpeedChange(132000000,0x24001,2); timer=15;
// GpClockSpeedChange(156000000,0x2c001,2); timer=13;
GpClockSpeedChange(165000000,0x2f001,2); timer=12;

Does anyone else have the problem of the Timers going too fast when you overclock?

Let me know if 165mhz works because obviously I can't check here

Also, does anyone know what the third parameter should be? Is it 2 or 3 - what's the difference? 3 just seems to make the timers run too fast again

the third parameter set the clock dividers, there are 3 click in gp32
1 for arm920, 1 for sdram and lcd and 1 for the rest (usb,timers, uart)
i think it should be '3', 3 is for divider 1:2:4
read the s3c2400 ref manual (available on mr spiv web-page

Again, if I specify 3 for the 3rd parameter I have timing problems.... this time it's the PCM sound. Even though I specify 44.1khz stereo, it takes longer than 1 second to play 44100 samples. It's about 10% too slow.

If I specify 2 for the 3rd parameter it's fine...

Are you 100% certain it should be 3 not 2?

 

[PAUL103DOGS]

YOU DA MAN PDAVE

 

[pip]

Aye, great work. I actually forgot how good the sonic 1 music was

Dave, can your gp32 overclock to 160? I have a theory that most gp32s that people think can just clock to 156 can actually reach 164 (mine does) just not 166.

 

[Timpas]

Why can't my internet update :angry: arghhh!!

can't see any 0.023 version!!!! :angry:

can somebody send it to me?------> timthelad@hotmail.com
or maybe help me...

 

[maltloaf]

excellent work fdave. Only tried sonic 1 so far but its really really impressive sound you've made (sounds like a spectrum - yea right! not even nearly that bad !) Excellent !

If your gp doesnt do 166 dave, send it me and i'll oc mod it for free.

malty

 

[GPJosh]

Great, doesn't sound that bad...

 

[MaDsk8tard]

fdave <-- one game that sound working^^ : fantasia !

 

[fdave]

Aye, great work. I actually forgot how good the sonic 1 music was

Dave, can your gp32 overclock to 160? I have a theory that most gp32s that people think can just clock to 156 can actually reach 164 (mine does) just not 166.

If the option for 160mhz is in FGen32 then I tried it... if not, i'll try it at some point

by the way the real Sonic1 music is nothing like what GigaDrive is currently playing, it's much better i promise you!

 

[Compyfox]

May I ask what the differences are between GigaDriv, GigaDriv132 (133MHz) and GigaDriv165 (166MHz)? Well... just curious what is what because there isn't anything standing in the readme and the ZIP contains 3 fxe.

Thanks in advance.


PS: I'd love to see Comix Zone working on GigaDrive. Ristar works, but not with so many graphic layers and still a lot graphic glitches (for example no password, no shadings, planets are a graphic trash, the front layer isn't viewable). Just as info.

 

[fdave]

May I ask what the differences are between GigaDriv, GigaDriv132 (133MHz) and GigaDriv165 (166MHz)? Well... just curious what is what because there isn't anything standing in the readme and the ZIP contains 3 fxe.

Thanks in advance.


PS: I'd love to see Comix Zone working on GigaDrive. Ristar works, but not with so many graphic layers and still a lot graphic glitches (for example no password, no shadings, planets are a graphic trash, the front layer isn't viewable). Just as info.

The speed they run at...

 

[Timpas]

can't download the newest version(0,023), because my computer won't update the page <_<

can only see version 19,18,17 and 16

 

[GPJosh]

Try deleteing your browsers' cache.

 

[razzy]

great emu, one of the best yet! just one question though, I can only seem to get sound on sonic the hedgehog which is a bin file but none of the other roms seem to have sound (they are all smd files) is there an option screen for gigadrive so I can turn sound on? edit: sorry just me being dumb, sound works only in some games!

 

[Compyfox]

I found some time testing a couple of games with the latest build. To be honest Dave, v0.20 (was it in 166MHz?) was better and ran more smooth. Well that's at least my personal opinion.

I tested Ristar, Sonic 2 and Sonic 3. With the 132MHz version it was terrible slow but all frames were showed. With the 165MHz version it ran almost realtime if not faster, but it seemed to me that the emulator uses some kind of frame skip.

Don't want to be rude, I respect your work and the efforts you put into GigaDrive for us. But isn't it possible to optimise it back down to 100-133MHz? Afaik the Genesis only had a handful of MHz, so this should be theoretically possible. Perhaps a FPS view (possible to turn it on and off with let's say the shoulder L-button, don't know what the max fps of the Genesis was) would help especially while testing and finding bugs.


Then three other things I'd pesonally see in the next build:

- disabling the sound
Not only to see if the emulator runs faster then, but some games with the actually soundemulation really hurt the ears. *nothing personal of course *

- changing the A B C buttons
Personally I don't feel comfortable using the select button as A button - so far I'm changing that directly in the game. But if it's possible to map the buttons to: A=B, B=A, shoulder-R=C or an option to change this, I'd really apreciate that.

- saving
Some games use a battery for saving. For example Sonic 3. Everytime I start the emulator new, the "battery" is empty and there is no savestate. It's not so important in the first place, but would raise the fun on gaming.


Again thanks a lot for your work, but I guess I go back to v0.20 until a newer build is out.