ATI 690G/x1250 problems (41 Viewers)

[rtv]

But to be honest I think this is not an ATI problem but a Mediaportal problem. I have other games running just fine with the new drivers

It's ONLY mediaportal that f***s up using direct X 3D (checked error log and is the same all the time as posted before on this thread.. ONLY DirectX.Direct3D causes errors, nothing else!) When running DXdiag diagnostic, direct X cannot find any issues, the X cube spins nice and smooth in all modes, which learns me the ATI can hande directx just fine.. it is Mediaportal that needs fixing handling directX.direct3D correctly.

Muhahahhaw - you made my day

My Mazda wagon perfectly drives on streets, sand and rubble. So if it fails on snow the car must be fixed since I've learned from a Toyota Hilux that driving on snow works fine. F** Mazda!


Sorry but comments like yours are absolutely superfluous here...

 

[Paranoid Delusion]

It's ONLY mediaportal that f***s up using direct X 3D (checked error log and is the same all the time as posted before on this thread.. ONLY DirectX.Direct3D causes errors, nothing else!) When running DXdiag diagnostic, direct X cannot find any issues, the X cube spins nice and smooth in all modes, which learns me the ATI can hande directx just fine.. it is Mediaportal that needs fixing handling directX.direct3D correctly.

And it was not broken in Feb 2007 and earlier drivers, only subsequent releases.

Good cars Toyota's, i've got a Celica, love it to bits.

 

[Lotsofjazz]

But to be honest I think this is not an ATI problem but a Mediaportal problem. I have other games running just fine with the new drivers

It's ONLY mediaportal that f***s up using direct X 3D (checked error log and is the same all the time as posted before on this thread.. ONLY DirectX.Direct3D causes errors, nothing else!) When running DXdiag diagnostic, direct X cannot find any issues, the X cube spins nice and smooth in all modes, which learns me the ATI can hande directx just fine.. it is Mediaportal that needs fixing handling directX.direct3D correctly.

Muhahahhaw - you made my day

My Mazda wagon perfectly drives on streets, sand and rubble. So if it fails on snow the car must be fixed since I've learned from a Toyota Hilux that driving on snow works fine. F** Mazda!


Sorry but comments like yours are absolutely superfluous here...

Ok point taken.. hihi.. But still strange the direct3d test in dxdiag doesnt show any flaws, so how do you explain that? That it does work with one software and not with the other? I was just thinking straight..

Probably a combination of both MP and ATI have flaws that collide and give us these freezing problems.

BTW, I got arround the problem by not using the filmstripview in the Monochrome skin. I also got a tip that the Project Mayhem III skin works fine.

Lots

It's ONLY mediaportal that f***s up using direct X 3D (checked error log and is the same all the time as posted before on this thread.. ONLY DirectX.Direct3D causes errors, nothing else!) When running DXdiag diagnostic, direct X cannot find any issues, the X cube spins nice and smooth in all modes, which learns me the ATI can hande directx just fine.. it is Mediaportal that needs fixing handling directX.direct3D correctly.

And it was not broken in Feb 2007 and earlier drivers, only subsequent releases.

Good cars Toyota's, i've got a Celica, love it to bits.

It was not broken, because it did not have the feature that gives us problems, reflections are not shown using 7.2.. with later versions it tries to show a reflection and then freezes.

lots

 

[NewUser]

Ok so let me get this straight. I am planning to get this mobo (Asus M2A-VM HDMI) which of course has the 690G chipset. The work arounds so far

1.) Use 7.2 drivers but no reflection (Since it was not supported) in XP
2.) Use latest drivers but no relfection (by removing flipY) in XP
3.) Use vista and everything is supported.
4.) Update to latest BIOS, everything is supported in XP

 

[Spragleknas]

I believe all is correct EXCEPT 4.

 

[OgdenP]

But to be honest I think this is not an ATI problem but a Mediaportal problem. I have other games running just fine with the new drivers

It's ONLY mediaportal that f***s up using direct X 3D (checked error log and is the same all the time as posted before on this thread.. ONLY DirectX.Direct3D causes errors, nothing else!) When running DXdiag diagnostic, direct X cannot find any issues, the X cube spins nice and smooth in all modes, which learns me the ATI can hande directx just fine.. it is Mediaportal that needs fixing handling directX.direct3D correctly.

Muhahahhaw - you made my day

My Mazda wagon perfectly drives on streets, sand and rubble. So if it fails on snow the car must be fixed since I've learned from a Toyota Hilux that driving on snow works fine. F** Mazda!


Sorry but comments like yours are absolutely superfluous here...

Personally, I think it is quite naive to think that MP's code is perfect and everything else is wrong. I'm not saying it IS wrong, but that the developers should always keep an open mind and at least investigate the code that is triggering this problem. Possibly there is an alternate way of doing the reflections without triggering this issue?

Please don't offer the standard response - "if you don't like it, then fix it yourself" - I'm not a C programmer. Though I have programmed (many, many years ago) in Assembler, Fortran, Basic, Pascal and later Delphi, so I know the sort of things that are possible, just not how to fix it myself.

 

[NewUser]

Either way someone please find a work around that has reflections

 

[charli181]

All,
I have just submitted my logs to ATI based on a request from them, asking me to run thier trouble report generating tool. Lets see what kind of action we get from this....

 

[Paranoid Delusion]

Personally, I think it is quite naive to think that MP's code is perfect and everything else is wrong. I'm not saying it IS wrong, but that the developers should always keep an open mind and at least investigate the code that is triggering this problem

They do keep a open mind.

This specifically affects one GPU (i'm ignoring olodin's FX5200 as he has not got back since changing drivers) and i have gone back and reread the whole of this thread, just to make sure i have my facts right.

Either ATI are not following Directx guidelines (unlikely), or there GPU's do not support a particular function (may be corrected by driver, who knows), no one with a higher specification GPU has a problem, whether ATI or Nvidia.

As stated by rtv, everything is written using the .net framework, so is compatible with Directx (unless M$ have screwed up, has been known )

For me this equates to a ATI problem, not MediaPortals.

This may not stop the Dev's from trying to find away around this, but may not be possible before MP2.

Regards

 

[charli181]

I am not in to the blaming of one group here, I personally believe it is ATI's prob but >>>