PowerVR glitches - Motorola Droid 4

Hello to all!
I'm not sure is this is the right place but since our device have this GPU on board I think it's relevant.
This issue can be noticed in couple emulators (i.e. FPSe, PPSSPP) and it's causing transparent textures. Here you can find detailed description with screenshots:
http://forums.ppsspp.org/showthread.php?tid=12016&highlight=powervr
or:
http://forums.ppsspp.org/showthread.php?tid=3719&highlight=powervr
I'm wondering is there any solution for this glitches, maybe update drivers or gpu hack like Chainfire 3D. If you know anyone please let me know!
Thanks in advance!

Related

OpenGL ES on Kaiser (AT&T Tilt)

I am running a Kaiser, Windows Mobile 6.0 Professional. Does anyone know where I can get my hands on an implementation of OpenGL ES for this device? (I need the dll as well as the SDK; i.e. headers and libs).
Also, can someone confirm that such an implementation would be running on top of the software-rendered DirectDraw implementation that's native to this device?
Thanks,
Brian
http://forum.xda-developers.com/showthread.php?t=339745
Hi, Gonzo. I'm aware of that thread and have gone through most of its 104 (!) pages, but I didn't find the answer to my question.
Note I'm not asking for hardware accelerated OpenGL, and that thread is mostly about the issues with HTC and/or Qualcomm not supporting H/W acceleration.
Hello Bkramer,
To be honest your question is a little to technical for me. I knew of the previous thread and thought it might help you but it seems your asking about something a little different. I do not think i can help anymore on this issue because it is out of my realm. Sorry.

kaiser 3d drivers at last????

great news that seems awesome
http://www.htcclassaction.org/driverprogress.php#update_20080717_1 (MOD EDIT: LINK CORRECTED)
""Now we have all that out of the way, here is the actual CAB file(http://www.htcclassaction.org/download/HTC-CA-Kaiser-Drivers.cab ) . Just install it on your device. Here is a RAR file (http://www.htcclassaction.org/download/Lights.rar) containing a sample D3D application - indeed the same as shown in the video - you can use to see if the drivers worked! Unrar it on your PC, copy the EXE files to your device, and run it on your device. It will show a few popups telling you if hardware is used or not.""
""These drivers require a Kaiser (TyTN II) and a ROM based on the official HTC WM 6.1 update!. Exactly which ROMs are compatible is not yet known. We have tested this on multiple Kaisers, but all of them were running Dutty's Diamond V1 ROM. It is extremely unlikely that these files will work out-of-the-box on any other MSM7x00 based device (at this time).""
i'm just flashing and check this out
They work on Garmin 1.2. Bigggg difference running the Lights program
Just thought i'd add the rest of the info:
"OK folks, here it is! A few hours later than projected, but still: OpenGL ES and D3D drivers (non-fullscreen) for the kaiser!"
"Before continuing, we would like to stress yet again, because there seems to be a little confusion here and there: these drivers are not finished, this is a work-in-progress. This is not a fix-all solution!. Currently the only things that are supported are hardware-accelerated D3D and OpenGL ES. These drivers are merely a release you can 'play' with, and prove it can be done. How many real-world applications will work with it remains to be seen, and we expect the users in the community will gather a list of these rather quickly."
"To elaborate further, these drivers do not accelerate video playback. These drivers do not accelerate normal Windows operation. Some of you have asked if we have abandoned accelerated 2D. We have not, it may still come. The simple fact is, that in this particular case, it was easier to work with the 3D drivers first"
yes but is a big big start
now we can keep hopping for better days with our kaisers
FINALLY!
I hope we get 2D acceleration as well. 3d is great, but 2D is better for me since I'm using office apps on my kaiser the majority of the time.
Ahh so it wasn't HTC who released these drivers like I originally thought. My original F**k you to HTC still stands.
Props to the person(s) who spent many hours getting this working.
Nice to see some actual progress, honestly I had pretty much given up hope. HTC isn't putting these out though, so don't thank their sorry asses.
Link in post 1 didnt work for me, the one below should lead to the page on the classaction site
http://www.htcclassaction.org/driverprogress.php#update_20080717_1
rcm_rx7 said:
Nice to see some actual progress, honestly I had pretty much given up hope. HTC isn't putting these out though, so don't thank their sorry asses.
Click to expand...
Click to collapse
Agreed !!! HTC had nothing to do with this driver project, it was all done by an indiviudual wiz , thanks should go there,HTC's behavior in this driver drama has been little but nothing more then talk with empty words. But indeed I got some hope again
sheptard said:
I hope we get 2D acceleration as well. 3d is great, but 2D is better for me since I'm using office apps on my kaiser the majority of the time.
I hope HTC continues with the development of these drivers and doesn't just say 'well, you complained about 3d accel long enough, here's something resembling a driver' and leave it at that.
If someone from HTC is reading this, Thank you very much for finally getting these out the door, and please don't stop I think 2D accel would be a great christmas present
Click to expand...
Click to collapse
As said in previous post HTC let us down totaly on the driver issue, vague promises, but no delivery, then againm why make the Kaiser better if that may have negative sale impact on the new Daimond..
I can tell HTC one thing: the Kaiser was my last HTC, not because of the Kaiser, I still love it; but due to their attitude in this driver struggle.. They shown they have no regards whatsoever to the customer after they bought their product,
Well.... for me... as long as i got a better camera in my device.... i am happy... as it is the only thing i am unhappy with my device..
----------------
Now playing: Hitomi Harada - Eternal Feather
via FoxyTunes
can someone upload the cab so we that are on our kaisers can download!
austinsnyc said:
can someone upload the cab so we that are on our kaisers can download!
Click to expand...
Click to collapse
There you go
Link to the cab file
we need a sticky thread that people post what there results are with the beta drivers with different ROM's right now i tried on my rom that is in my sig (april 29 dutty's), and i had no go, i dont know if before directdraw worked in video tests, but i benchmarked a video and it worked very slow though 39% vs 80-95% in raw and other setttings
also for those who can benchmark it would be nice to see which ROM gives the most performace and bug free?
also i would like to know if its possible to do reg hack/import of the paths that diamond based roms have, to those that were pre diamond based or even pre full 6.1 roms?
im not 100% sure but remember that those new roms didnt have drivers but did have paths/links to what could be drivers, with a simple cab older ROM's could work with the driver as well?
I'm sorry to interupt but this driver is not finished & doesnt make any change to kaiser graphic performance. i think there was an old thread similar with this that has been closed long time ago. dont get mad. i already say sorry
hang.tuah said:
I'm sorry to interupt but this driver is not finished & doesnt make any change to kaiser graphic performance. i think there was an old thread similar with this that has been closed long time ago. dont get mad. i already say sorry
Click to expand...
Click to collapse
That's not entirely true, it doesn't make any changes to the kaiser's 2D graphic performance, but that is because it's 3D graphics drivers. The video demonstrates that there is 3G acceleration being enabled by these drivers, though it still won't fix what ails the kaiser...but it's a step in the right direction.
skatdawg said:
That's not entirely true, it doesn't make any changes to the kaiser's 2D graphic performance, but that is because it's 3D graphics drivers. The video demonstrates that there is 3G acceleration being enabled by these drivers, though it still won't fix what ails the kaiser...but it's a step in the right direction.
Click to expand...
Click to collapse
OIC. thanks skat. so the conclusion we still have to wait or just buy Raphael
skatdawg said:
That's not entirely true, it doesn't make any changes to the kaiser's 2D graphic performance, but that is because it's 3D graphics drivers. The video demonstrates that there is 3G acceleration being enabled by these drivers, though it still won't fix what ails the kaiser...but it's a step in the right direction.
Click to expand...
Click to collapse
I agree, When I first tested the light.exe bench, It was laagy and hardware was not detected, now it rocks
Glbenchmark is still not working but I think there is hope for 3D games and may be touchflo 3D
confirmed
1. run lights.exe with no drivers
- driver provider: Microsoft
- hardware rasterization: false
- hardware T&L: false
- using system memory
- around 1 fps
2. installed drivers, soft reste
3. run lights.exe again
- driver provider: n/a
- hardware rasterization: true
- hardware T&L: true
- using video memory
- around 15 fps
one bug - could be driver could be lights.exe could be rom (L26_KDV9): leaving lights.exe runing until the screen turns off freezes your device. I didn't test w/o the driver.
dani31 said:
1. run lights.exe with no drivers
- driver provider: Microsoft
- hardware rasterization: false
- hardware T&L: false
- using system memory
- around 1 fps
2. installed drivers, soft reste
3. run lights.exe again
- driver provider: n/a
- hardware rasterization: true
- hardware T&L: true
- using video memory
- around 15 fps
one bug - could be driver could be lights.exe could be rom (L26_KDV9): leaving lights.exe runing until the screen turns off freezes your device. I didn't test w/o the driver.
Click to expand...
Click to collapse
u r right. just tried it. wonderful app by Omikr0n. but is there any benefit for other apps if we using this driver? just curious whether this driver better cooked in or just as seperate cab.

Would like to report Direct3D driver bug.

Hello I'm a beginner D3D Developer and I notice a possible bug with remade Direct3D Drivers.
After using SetStreamSource with a vertex buffer I can no longer draw any other mesh. I thought it was my fault but my example app worked well on a Himalaya and Universal.
Should any details be needed, contact me in this thread
Greetings
Have you double-checked the behavior with the recent Samsung/XSCALE D3D drivers?
Do you have some sample code to help demonstrate the problem?
NuShrike said:
Have you double-checked the behavior with the recent Samsung/XSCALE D3D drivers?
Do you have some sample code to help demonstrate the problem?
Click to expand...
Click to collapse
Yes I have tested it on a WM6.1 Himalaya (Xscale) and worked flawlessly, and on a WM6.1 Universal (also Xscale) also flawlessly. Also worked on Reference Drivers. Don't have a Samsung or Omap device so can't tell.
I have a code but currently can't access it. I'll get back when I'll be able to get it, but basically it would look SOMETHING like this:
void Render() {
...
device.SetStreamSource(0,vbuffer,0);
device.SetTexture(0,texture);
... some code ...
mesh.DrawSubset(0)
}
If i removed call to SetStreamSource before, the mesh would draw (but the background would not, it was a rectangle made of 2 TransformedTextured triangles)
Also, could you tell me one thing? Are there any updated Samsung drivers? The ones I've always had were horrible, no sample with texture would even run because driver didn't support texture mapping.

[SKIN][MORPHGEAR][UPDATED] Multi-touch - works on resistive

1st thing: I need a graphics designer badly for this. I am really bad with computer graphics editing, so if somebody wants to help me reskin this, it would be awesome.
I had orginally planned to keep this to myself, but I decided to give it to you guys, it's my modded multi touch version of Dredd67s skin that he released. It's still a work in progress so please give feedback. Just drop the 2 files into the morphgear skin directory and then select it under the emulator settings menu and bam, you got fake multi touch. I orginally modified it because I couldn't catch that rat in chrono trigger.
For those that don't know what Morphgear is; it's a emulator. It emulates SNES, nes,gba,gb etc. I recommend you download the version on here for the hd2. It won't let me post links or otherwise i'd link to it.
Please give feedback.
Update: version 2.0
How it works
It's very simple how it works. When you press 2 points on the screen at the same time, the exact middle of those 2 points is what the screen senses. So thats why the buttons placed the way they are. There are invisible buttons in the middle, and thats how it works.
Bump for version 1.6
Bump for 2.0. Hopefully final version.
Because is was a bid bored and liked your program I made this skin...
Ciss

Direct3D acceleration WORKING!!

See Here http://forum.xda-developers.com/showthread.php?t=416474
the story of how i came here is i was looking for a phone with direct3D support and the msm7225 processor as the native support on the touch 3g sucked.
i looked at the datasheet page here http://pdadb.net/index.php?m=cpu&id=...alcomm_msm7225
Clicked the browse all devices that use the MSM7225 looked through the list until i come across one that had windows mobile as the os, first one i come across was the omnaPro, checked if it supported direct3d knowing the gpu would be the same as its embedded in the msm7225 and google lead me here.
i thought what the hell , its not a omniaPro, but theres always hard resetting lol (done it once tonight lol)
tried the direct3d examples first, without driver , sucked , less than 1fps would be my guess, installed the drivers expecting a crash and nothing , it booted , run the examples an BANG PERFECT!!! AWESOME!! WELL HAPPY!!!
off to post in the touch 3g forum am a happy bunny, hope it will solve the 2d issues as looking at the cab its local hooked and not remote hooked so it must be the only gpu driver running.
AWESOME!
does it run on jade!! does this means that we can run tf3d on jade!!
oooh wow, thnx for the find !
Maybe some of the cooks will create a rom with this one and Touch Flow 3D
this was my first thought too lol . not gonna happen tho, because tf3d uses opengl ES, and thats totally diffrent to direct3d.
not imposible because there is a opengl ES compatibility layer for the omnia 2 i8000 (dont bother iv tried it already for fun and what i expected happend nothing at all lol).
tf3d would be nice tho, so if iv missed somthing and we can run tf3d on just pere direct3d someone let me know how please would be nice to have a mini hd mini lol
hehe yeah our own htc hd mini
so wait, what exactly is this useful for then ? gaming ?
I confirm that D3D driver from Omnia works perfectly.
Now we just need to get a working Opengl ES driver ("lib_GLES_cm.dll" I believe).
there is just one game that stil wont run after this driver instal ( xtrakt ). other games like cod can now run on full speed on max settings. and without the driver it was stil playabel at lowest settings but stil laggy a bit. sow there is a big diffrends whit this driver !
i confirm too that the 3d tests run very well , but didn't try any game. Exept some 3d games does it play a role for some other 2d games or apps , or even the menus slide ?
soms apps are faster whit this even scrolling feels difrend and smoother like my navigon ( gps navigator) is running faster and loading faster but on manila i dont see that much difrend
ritchietos said:
there is just one game that stil wont run after this driver instal ( xtrakt ). other games like cod can now run on full speed on max settings. and without the driver it was stil playabel at lowest settings but stil laggy a bit. sow there is a big diffrends whit this driver !
Click to expand...
Click to collapse
that game requires OpenglES thats why it doesnt run. il say it again , its DIRECT3d not opengles , hence tf3d will not run yet.
it does seem to help manilia , the bottom scroll is smoother. and yeah it prob will help games no end judging by the jumpp on the 3d tests.
again , no tf3d yet but well worth it
thatguy1982 said:
that game requires OpenglES thats why it doesnt run. il say it again , its DIRECT3d not opengles , hence tf3d will not run yet.
it does seem to help manilia , the bottom scroll is smoother. and yeah it prob will help games no end judging by the jumpp on the 3d tests.
again , no tf3d yet but well worth it
Click to expand...
Click to collapse
iam using a opengl software driver from vincent works well for touchflo 3d
if u use throttle launcher runs on opengl if u set it so. i now its still emulate on the cpu but its faster than the normal settings
ritchietos said:
iam using a opengl software driver from vincent works well for touchflo 3d
if u use throttle launcher runs on opengl if u set it so. i now its still emulate on the cpu but its faster than the normal settings
Click to expand...
Click to collapse
Can you please give us some more explanation and eventually some link for the files?
Thanks
P.S. This thread and Android thread I am following and reading with interest.
dreamdreamt said:
Can you please give us some more explanation and eventually some link for the files?
Thanks
P.S. This thread and Android thread I am following and reading with interest.
Click to expand...
Click to collapse
here is the page for the opengl.
http://www.vincent3d.com/
and here is the tool its like manila whit skins. and there is a android skin phone 7 skin an touchflo 3 the hero skin the sense skin.... (soms skins need difrend thorttle bulds so read it good )
http://www.throttlelauncher.com/portal/
u need the opengl from vincent to make the animation work.
and net framework 3.5.
hope this helps .
ritchietos said:
here is the page for the opengl.
http://www.vincent3d.com/
and here is the tool its like manila whit skins. and there is a android skin phone 7 skin an touchflo 3 the hero skin the sense skin.... (soms skins need difrend thorttle bulds so read it good )
http://www.throttlelauncher.com/portal/
u need the opengl from vincent to make the animation work.
and net framework 3.5.
hope this helps .
Click to expand...
Click to collapse
Thanks a lot
Hi ritchietos,
I downloaded Vincent ES 1.x but don't know how to install it??
ok so u se a folder whit the name ogles-bin-1.0.0 .then open bin .than open arm and then u se 2 maps debug and release open the release map and copy al te files in the windows directory on u phone. dont forget to turn on opengl on the throttleconfig.
and u ready to go
awesome now we have software emulated ogles too !!
i cant get it working with tf3d. i used the tf3d_qvga.cab from htcclassaction.com and the same thing happened.
what cab are you using that works ?
if i can get it working il make a cab for the jade when i get some spare time
thatguy1982 said:
awesome now we have software emulated ogles too !!
i cant get it working with tf3d. i used the tf3d_qvga.cab from htcclassaction.com and the same thing happened.
what cab are you using that works ?
if i can get it working il make a cab for the jade when i get some spare time
Click to expand...
Click to collapse
the real touchflo3d works but there are som white textures because its for a ati chipsets. there are som ports for this to get it work but didnt have the thime jet to search for it . the throttlelauncher touchflo 3d or android skin works whit opengl
throttlelauncher seems about the same speed with and without acceleration, but that cud b because im tired lol.
i never knew the textures were not displayed because of the lack of the ati chip are you sure about this as the vincent dll emulates it all in software id think it was because this dll lacks certain fetures.
anyone ever hear of the old glide wrappers that converted 3dfx calls to directx ? sounds similar to early glide wrappers to me lol
EDIT: Its slower with 3d acceleration enabled because of the wrapper i think, am just going to verify everythings installed right
EDIT2: yes its all installed right the d3d samples still fly too, shame throttlelauncher does not support direct3d acceleration. with the hero theme it averages 4fps just sitting there on the homescreen with acceleration on, and about 19-20fps without acceleration.
thatguy1982 said:
throttlelauncher seems about the same speed with and without acceleration, but that cud b because im tired lol.
i never knew the textures were not displayed because of the lack of the ati chip are you sure about this as the vincent dll emulates it all in software id think it was because this dll lacks certain fetures.
anyone ever hear of the old glide wrappers that converted 3dfx calls to directx ? sounds similar to early glide wrappers to me lol
EDIT: Its slower with 3d acceleration enabled because of the wrapper i think, am just going to verify everythings installed right
EDIT2: yes its all installed right the d3d samples still fly too, shame throttlelauncher does not support direct3d acceleration. with the hero theme it averages 4fps just sitting there on the homescreen with acceleration on, and about 19-20fps without acceleration.
Click to expand...
Click to collapse
White squares: Images appearing as white squares is due to non support of ATC textures - this can be caused by a non ATI graphics driver - either an nvidia one (intel used ati i beleive) or software based ones. This is an IP issue more than anything else, and not something that we as developers can easily fix. (from xda)
they are som devices whit this fix so iam looking for it to ghet it working.

Categories

Resources