videocard/wine

[Harm]

first of all, i don't know if the problem lies with wine, or with the ati driver. but when i run wine to play guild wars (a game if you're wondering) it says Unable to initialize 3D output. Please verify that you have installed DirectX 8 and an updated video driver. it doesn't say it anymore, but the first time the terminal client also said something about direct3d not found or something like that

[Adromeda]

I'm not certain, but I don't think wine can emulate DirectX, (Windows Properiaty 3d tools thingy...), I'm geussing your game then used OpenGL, which is, well, open source, and is why it's working...

[Dark_MaGe]

first of all, i don't know if the problem lies with wine, or with the ati driver. but when i run wine to play guild wars (a game if you're wondering) it says Unable to initialize 3D output. Please verify that you have installed DirectX 8 and an updated video driver. it doesn't say it anymore, but the first time the terminal client also said something about direct3d not found or something like that

I know there's a small bug on portage...you can fix it this way:

Code: Select all

layman -s sabayon && USE="opengl" emerge wine

[Harm]

first of all, i don't know if the problem lies with wine, or with the ati driver. but when i run wine to play guild wars (a game if you're wondering) it says Unable to initialize 3D output. Please verify that you have installed DirectX 8 and an updated video driver. it doesn't say it anymore, but the first time the terminal client also said something about direct3d not found or something like that

I know there's a small bug on portage...you can fix it this way:

Code: Select all

layman -s sabayon && USE="opengl" emerge wine

hmm yes, i'll try that, but there's somethign that doesn't work when compiling wine - at least i think something's wrong, it's possible that compiling things always looks like that

[Dark_MaGe]

log here the error you have so we can understand

[Harm]

the first error was gone too fast, but it had something to do with conflicts and 12
the first error was kicked out of the command log by a mass amount of
Missing glyph for char 0e56
Missing glyph for char 0e57
Missing glyph for char 0e58
Missing glyph for char 0e59
Missing glyph for char 0e5a
Missing glyph for char 0e5b
etc.
followed by
MS Sans Serif 10 pts 96x96 dpi
MS Sans Serif 12 pts 96x96 dpi

[Harm]

err.. i don't know why or how, but somehow my openGL renderer is mesa3d again.. and i'm sure it was the ati driver right after i installed sabayon :s

[Dark_MaGe]

the first error was gone too fast, but it had something to do with conflicts and 12
the first error was kicked out of the command log by a mass amount of
Missing glyph for char 0e56
Missing glyph for char 0e57
Missing glyph for char 0e58
Missing glyph for char 0e59
Missing glyph for char 0e5a
Missing glyph for char 0e5b
etc.
followed by
MS Sans Serif 10 pts 96x96 dpi
MS Sans Serif 12 pts 96x96 dpi

those are not errors if it doesn't stop there's no problem, you can often find warnings during compilation, just let it continue