Am 06.06.2009 um 08:18 schrieb Roderick Colenbrander:
We don't use GL extensions when they aren't around. Perhaps there is a
small check which fails for FBOs. Backbuffer should work fine but a
lot more changes have been made in .23 and those are which cause the
zbuffer error.
A long time ago th
2009/6/6 Stefan Dösinger :
> Hmm. Does fglrx support this extension at all?
http://bugs.winehq.org/attachment.cgi?id=21581
That's attached to bug 18794.
That's probably the same issue as http://bugs.winehq.org/show_bug.cgi?id=18794
I'm afraid the conclusion there is simply going to be that fglrx's FBO
support sucks. We could probably justify not checking depth stencil
formats, but it's perfecly reasonable to try
GL_COMPRESSED_RED_GREEN_RGTC2_EXT.
2009/6/6 Jerome Leclanche :
> Would it be a good/stupid idea to check for fglrx during wineboot, and
> set OSRM to a different value than fbo?
>
That's essentially what blacklisting EXT_framebuffer_object would do,
although during wined3d initialization, not wineboot. We want to avoid
that for the
Sure that is possible but it is something we should avoid. In the
longterm having this enabled by default is better as it would get ATI
and others to fix their drivers. If we would restore the old value
(the old method is also not great for modern games and causes a lot of
issues, FBOs are needed f
Would it be a good/stupid idea to check for fglrx during wineboot, and
set OSRM to a different value than fbo?
2009/6/6 Henri Verbeet :
> 2009/6/6 Kovács András :
>> wine: Unhandled page fault on read access to 0x0018 at address
>> 0x7c71fb02 (thread 0009), starting debugger...
>> Unhandled ex
"chris ahrendt" wrote:
Using this attached Reg File Is still a no go... same...
(I forgot the Direct3D tag but added it and no change)
Have you heard of a regression testing? Also wine-devel is not
an appropriate place to report bugs.
--
Dmitry.
Using this attached Reg File Is still a no go... same...
(I forgot the Direct3D tag but added it and no change)
Chris
rendering3.Reg
Description: Binary data
2009/6/6 Kovács András :
> wine: Unhandled page fault on read access to 0x0018 at address
> 0x7c71fb02 (thread 0009), starting debugger...
> Unhandled exception: page fault on read access to 0x0018 in 32-bit
> code (0x7c71fb02).
> Register dump:
> CS:0073 SS:007b DS:007b ES:007b FS:0033 GS
On 06/05/2009 09:16 PM, Austin English wrote:
> On Fri, Jun 5, 2009 at 8:03 PM, chris ahrendt wrote:
>
>> On 06/05/2009 08:15 PM, Austin English wrote:
>>
>>> On Fri, Jun 5, 2009 at 7:11 PM, chris ahrendt
>>> wrote:
>>>
>>>
Tried it several times.. and different iterati
On Fri, Jun 5, 2009 at 8:03 PM, chris ahrendt wrote:
>
> On 06/05/2009 08:15 PM, Austin English wrote:
>> On Fri, Jun 5, 2009 at 7:11 PM, chris ahrendt wrote:
>>
>>> Tried it several times.. and different iterations of the registry keys
>>> (you will find them attached) and both cases it fails the
Hi!
With new wine (1.1.23+ git) I'm getting wide range of failures of
different games.
System:
Ubuntu Jaunty x86
ATI Radeon HD4870 512 MB
fglrx 9.5
- The most significant crash (with several games):
wine: Unhandled page fault on read access to 0x0018 at address
0x7c71fb02 (thread 0009), star
On 06/05/2009 08:15 PM, Austin English wrote:
> On Fri, Jun 5, 2009 at 7:11 PM, chris ahrendt wrote:
>
>> Tried it several times.. and different iterations of the registry keys
>> (you will find them attached) and both cases it fails the same way any
>> of the d3d tests will fail or the machi
On Fri, Jun 5, 2009 at 7:11 PM, chris ahrendt wrote:
> Tried it several times.. and different iterations of the registry keys
> (you will find them attached) and both cases it fails the same way any
> of the d3d tests will fail or the machine locks up.
--
-Austin
REGEDIT4
[HKEY_CURRENT_USER\Soft
Tried it several times.. and different iterations of the registry keys
(you will find them attached) and both cases it fails the same way any
of the d3d tests will fail or the machine locks up.
rendering.Reg
Description: Binary data
rendering2.Reg
Description: Binary data
On 06/05/2009 05:10 PM, Roderick Colenbrander wrote:
> Check the useful registry keys page at wiki.winehq.org (it is
> Direct3D/OffscreenRenderingMethod)
>
> Roderick
>
> On Fri, Jun 5, 2009 at 10:41 PM, chris ahrendt wrote:
>
>> On 06/05/2009 04:32 PM, Roderick Colenbrander wrote:
>>
>
Check the useful registry keys page at wiki.winehq.org (it is
Direct3D/OffscreenRenderingMethod)
Roderick
On Fri, Jun 5, 2009 at 10:41 PM, chris ahrendt wrote:
>
> On 06/05/2009 04:32 PM, Roderick Colenbrander wrote:
>> As of Wine 1.1.23 wined3d made FBOs the default offscreen rendering
>> method
On 06/05/2009 04:32 PM, Roderick Colenbrander wrote:
> As of Wine 1.1.23 wined3d made FBOs the default offscreen rendering
> method. If you are using a non-nvidia card (those in general have
> buggier drivers) that could explain all the failures. Setting
> OffscreenRenderingMethod to backbuffer re
As of Wine 1.1.23 wined3d made FBOs the default offscreen rendering
method. If you are using a non-nvidia card (those in general have
buggier drivers) that could explain all the failures. Setting
OffscreenRenderingMethod to backbuffer restores the old behavior.
Roderick
On Fri, Jun 5, 2009 at 10:
Something majorly changed and is wrong with the latest GIT tree.
Between the comits yesterday and today 90% of the tests get exceptions
or fail.
All of the d3d tests get a process exception and fail with a dialog box.
Ideas?
Chris
20 matches
Mail list logo
