Smartgear works great on Touch Pro 2! NES! Genesis!

[THE-COPS]

Smooth scaling would be a nice addition. But doesn't that stretch the image? Also, woud it be possible to add an adjustable sound buffer, for latency? I am noticing that some have lag or static issues while others do not. Perhaps having a slider to adjust it would even it out for all. I kinda miss this option as most PPC/Smartphone emulators don't have such an option. Not all devices are universal, so the emulator I think should have some sort of compensation for each. Does that make any sence to you?

And as far as the differences in why there are gfx glitches in some roms while other users such as yourself aren't experiencing them.. I'm thinking, could it be the gx.dl file? Is that the correct file I'm thinking of? The driver for gfx . I forget the file name. But in any case, could it be that since the T-mobile TP2 came out wel before the VZ & Sprint versions, that there coud have been some minor code changes done to it after the TMO unit came out? If this is the file, then perhaps I could send you a copy of said file and you could somehow compare them? I noticed it's a very small file at 6.83KB. That can't be the gfx driver? Confused here.

[bitbank]

Originally Posted by THE-COPS

Smooth scaling would be a nice addition. But doesn't that stretch the image? Also, woud it be possible to add an adjustable sound buffer, for latency? I am noticing that some have lag or static issues while others do not. Perhaps having a slider to adjust it would even it out for all. I kinda miss this option as most PPC/Smartphone emulators don't have such an option. Not all devices are universal, so the emulator I think should have some sort of compensation for each. Does that make any sence to you?

And as far as the differences in why there are gfx glitches in some roms while other users such as yourself aren't experiencing them.. I'm thinking, could it be the gx.dl file? Is that the correct file I'm thinking of? The driver for gfx . I forget the file name. But in any case, could it be that since the T-mobile TP2 came out wel before the VZ & Sprint versions, that there coud have been some minor code changes done to it after the TMO unit came out? If this is the file, then perhaps I could send you a copy of said file and you could somehow compare them? I noticed it's a very small file at 6.83KB. That can't be the gfx driver? Confused here.

I'm already stretching the images to fill the display. GBC = 160x144 and Genesis = 320x224, so in order to fill a 800x480 display, the image needs to be stretched.. The idea would be to make the stretched image look less blocky.

I'm not sure about some of the sound differences you're seeing, but I do see the Genesis graphics problems and will eventually have a fix for them. GX.dll is not used by SmartGear and there is no real "driver" involved. SmartGear asks the system for the address of the display VRAM and then writes directly to that memory. I don't think a variable sound buffer scheme is necessary; all WinCE devices work pretty much the same, so once I get things working well it will work well on all devices.
L.B.

[Cobaltikus]

Originally Posted by bitbank

I would be very grateful if you could provide any help in making things work with the Widcomm stack! I found a good source of BGP100's is dealextreme; they sell it for $24.28 including shipping.

I currently use the Microsoft bluetooth stack in a very simple way to communicate with both the BGP100 and Zeemote:

1) Discover BT devices in range and look at their 6-byte BT address.
2) Compare the first 3 bytes of the BT address (manufacturer code) to the known addresses for BGP100's and Zeemotes. If there's a match, create a socket and connect to the device.
3) Have a thread waiting on recv() from the socket and parse the data.

For both devices, there's no special initialization necessary; they just start spewing data when you connect to them.

Any help you can provide with the Widcomm SDK would be very welcome.

Thanks,
L.B.

Just a little note here to say that I am actively working on getting the PS3 Sixaxis/DS3 working with Windows Mobile 6.5 with the Widcomm stack. Once I finish that I'll do the M$ stack. Once I finish that I plan on doing the Wiimote. All this combined with your awesome emu should make a lot of people happy. I know I will be.

[aldamon]

......

[aldamon]

Originally Posted by Cobaltikus

Just a little note here to say that I am actively working on getting the PS3 Sixaxis/DS3 working with Windows Mobile 6.5 with the Widcomm stack. Once I finish that I'll do the M$ stack. Once I finish that I plan on doing the Wiimote. All this combined with your awesome emu should make a lot of people happy. I know I will be.

Holy crap. This would be great. I've got two original SIXAXIS collecting dust.

[Cobaltikus]

hard part is over
the sixaxis connects and sends data
now I just need to map out what to do when each button is pressed
currently works on windows mobile devices with a widcomm bt stack
I plan to make it work for the M$ stack as well but I'll have to borrow a phone with it from work cuz I don't have one any more
working on Touch Pro2 and HTC HD2 at the moment

I was so frickin happy when I finally got it to connect and sending data

so bitbank - in your opinion - what would the best way be to tie this in with your program - should I have registry settings that map out control codes for each button like HKCU\Software\Cobaltikus\Sixaxis\Circle = "W" etc? and then just send those keydown and keyup events to the active foreground window?

[Cobaltikus]

[App] CobaltContoller - Sixaxis/DS3 for Windows Mobile
http://forum.xda-developers.com/showthread.php?t=689984

[newkidd]

Smart gear works great with me, except i do get alot of screen garble whenever i use fit2win option. usually its ghosting on the sides of the screen where the game isnt. noticable in all versions of smart gear i have played.

[bitbank]

Originally Posted by newkidd

Smart gear works great with me, except i do get alot of screen garble whenever i use fit2win option. usually its ghosting on the sides of the screen where the game isnt. noticable in all versions of smart gear i have played.

I have not seen this occur. Can you please let me know what game you're playing, what system, what orientation and settings?

Thanks,
L.B.

[bitbank]

so bitbank - in your opinion - what would the best way be to tie this in with your program - should I have registry settings that map out control codes for each button like HKCU\Software\Cobaltikus\Sixaxis\Circle = "W" etc? and then just send those keydown and keyup events to the active foreground window?

Congratulations on getting this to work. Since your code will not be running inside SmartGear, the thing to do is use keybd_event() to create simulated key events. Pick any keys and everyone can do the key definition setup once. Or... we can integrate your code into mine to directly control SmartGear. I would be happy to publish the source code to my Microsoft BT routines in exchange for some widcomm code which can connect and read data from a BT device.
L.B.