Any hope for 2700G optimized morphgear?

08-31-05, 03:58 PM

I might be getting a tad too hopeful but will we be seeing a 2700g optimized version of morphgear anytime soon? Or maybe those new GBA modules that accurately reproduce sounds so it wouldnt be beep beep click sfx.

Or are you guys waiting for WM5 with the DirectX equivant things to be released for less work? (I assume its less because ATI and Intel chips will both use the direct 3d so just program in direct 3d...)

Im sure its difficult to work with the 2700 but I can hope.

da1writer · 09-01-05, 02:47 AM

"Or are you guys waiting for WM5 with the DirectX equivant things to be released for less work?"
You know adwark... I might get in trouble for saying this but...
the above is what we are fiddling with... right now.
If I say anymore, I'm going to get killed...

darkdestroyer · 09-01-05, 08:04 AM

lol, good good, eagerly awating more information...

09-01-05, 08:07 AM

Originally Posted by da1writer

"Or are you guys waiting for WM5 with the DirectX equivant things to be released for less work?"
You know adwark... I might get in trouble for saying this but...
the above is what we are fiddling with... right now.
If I say anymore, I'm going to get killed...

Come on, we can keep a secret ;)

blutrane · 09-01-05, 02:06 PM

Originally Posted by awdark

I might be getting a tad too hopeful but will we be seeing a 2700g optimized version of morphgear anytime soon? Or maybe those new GBA modules that accurately reproduce sounds so it wouldnt be beep beep click sfx.

Or are you guys waiting for WM5 with the DirectX equivant things to be released for less work? (I assume its less because ATI and Intel chips will both use the direct 3d so just program in direct 3d...)

Im sure its difficult to work with the 2700 but I can hope.

don't worry Da1 no killing today :P

i wasn’t going to post anything but frankly the more people i can get to help out the better off i will be. My time is limited but i am trying to get MG optimized for the new windows mobile. Any one with relevant skills in eVC++ please PM or email me.

I am not trying to generate hype, i can actually use help

so here is a screen shot of where i am at. i managed to confirm that MG will run in windows mobile 5.0

dev plans include

- fix GUI to display nicely in VGA (tool bar and virtual pad)
- incorporate desktop directx driver in to pocket pc version to
use direct 3D mobile ( will use 2700g in x50v by default )
- possibly port an older version (faster) version of snes9x like
version 1.42

because the application barely runs in the device emulator it will be hard to test it before i get a real copy of windows mobile 5.0

i have no idea how much faster it will go but it wont be any faster then pocket snes openGL most likely slower but better then using GAPI

hopefully I will have something ready to test in October but that really depends on how much trouble I have (expecting enough) with the code. I was hoping someone more experienced then myself would have undertaken the project but no one has stepped up

its not to late to jump on and help out :) more help = faster/ better release

--------------------------------------------------------------------------------------------------

as for GBA. i am not involved in that aspect at all and i am less then hopeful that we will see an update. that’s not stopping anyone from porting visual boy advance into a morphmodule ... i fear that this task is beyond my skill

EDIT: here is a link to full sized version of the screen shot the one i posted dosent look too hot
http://www.centralstamp.com/Untitled-4.jpg

09-01-05, 02:28 PM

If only porting meant changing one name to another name to make it work with it... I can do that... but I know it means more than just one thing to another.
>_< why cant we use GP32 stuff... they seem to have working emulators... Not saying we dont but I guess I just assuem the work better. O_O GBA uses arm.. GP32 uses arm.. PPC.. Xscale arm... pity they just dont work with each other like that.

Oh and your screen shot. Get a gamepad skin, resize the 240x240 to 480x480. Use that skin instead. Works on my x50v.

blutrane · 09-01-05, 02:37 PM

Originally Posted by awdark

If only porting meant changing one name to another name to make it work with it... I can do that... but I know it means more than just one thing to another.
>_< why cant we use GP32 stuff... they seem to have working emulators... Not saying we dont but I guess I just assuem the work better. O_O GBA uses arm.. GP32 uses arm.. PPC.. Xscale arm... pity they just dont work with each other like that.

Oh and your screen shot. Get a gamepad skin, resize the 240x240 to 480x480. Use that skin instead. Works on my x50v.

gba uses arm but dosent have the overhead of a windows mobile OS

as for the vpad yes a vga one will be used by default and the icons for the tool bar will beincreased to 32x32 instead of 16x16 this isnt the kinda stuff that has me woried as it is easy to do

im more concerend with creating a direct3d mobile video driver that will actualy work