Am Mon, 17 Oct 2005 00:17:22 +0200 schrieb Fabian Bieler
[EMAIL PROTECTED]:
On Sunday 16 October 2005 23:34, Fabian Bieler wrote:
OK, here I go again:
This is a small C program which should get the videoRam using the
NV-CONTROL and ATIFGLEXTENSION extensions. As I only have a nVidia card,
Hello!
You can get the amount of videoRam from the x-server log (python script
attached). This is a little unsafe since the video driver is responsible for
logging this info and I don't know if my script works on the format of all
drivers. Also, certain drivers (fbdev) don't output this at all.
You can get the amount of videoRam from the x-server log (python script
attached). This is a little unsafe since the video driver is responsible
for logging this info and I don't know if my script works on the format of
all drivers. Also, certain drivers (fbdev) don't output this at all. Then
You can get the amount of videoRam from the x-server log (python script
attached). This is a little unsafe since the video driver is responsible
for logging this info and I don't know if my script works on the format of
all drivers. Also, certain drivers (fbdev) don't output this at all. Then
On Sunday 16 October 2005 13:06, Stefan Dösinger wrote:
Another update: The reason why the script is not working is the vendor
string - it's Gentoo (The X.Org Foundation 6.8.2, revision r4-0.1.10.2)
for me. Maybe a not so strict check against it would do it.
This should fix that problem.
Hello,
This should fix that problem.
Works nice
Another thing:
Would it be better to determine the amount of videoRam when installing wine
and storing it in the registry or checking at runtime when
GetAvailableTextureMem is called?
I'd suggest to determine it in IWineD3D::CreateDevice and
Another thing:
Would it be better to determine the amount of videoRam when installing
wine
and storing it in the registry or checking at runtime when
GetAvailableTextureMem is called?
I'd suggest to determine it in IWineD3D::CreateDevice and store it in the
IWineD3DDeviceImpl class.
For Nvidia systems at least, the script would probably be unnecessary,
as 'nvidia-settings -q VideoRam | grep 0.0 | tail --bytes=8' *should*
return the amount of videoram. Would it make more sense to check at
runtime if the 'nvidia' driver is loaded and then pass the output from
the line above
Now that I think about it there's some other issue which is partly related
to this that should be addressed too namely card detection. Right now
wined3d parses sets the card based on several opengl strings. First it
detects the vendor (Ati/Nvidia) and then there are two or three models of
each
As someone stuck with both nVidia and ATI cards, I'd vote against using
NV-CONTROL. Detecting the RAM for different manufacturers via different
methods sounds harder to maintain.
(--) fglrx(0): VideoRAM: 131072 kByte, Type: DDR SGRAM / SDRAM
Roderick Colenbrander wrote:
Parsing the X log
For Nvidia systems at least, the script would probably be unnecessary,
as 'nvidia-settings -q VideoRam | grep 0.0 | tail --bytes=8' *should*
return the amount of videoram. Would it make more sense to check at
runtime if the 'nvidia' driver is loaded and then pass the output from
the line
As someone stuck with both nVidia and ATI cards, I'd vote against using
NV-CONTROL. Detecting the RAM for different manufacturers via different
methods sounds harder to maintain.
(--) fglrx(0): VideoRAM: 131072 kByte, Type: DDR SGRAM / SDRAM
In my opinion parsing of the log file is very
Hi,
Another thing:
Would it be better to determine the amount of videoRam when installing
wine
and storing it in the registry or checking at runtime when
GetAvailableTextureMem is called?
I'd suggest to determine it in IWineD3D::CreateDevice and store it in the
On Sunday 16 October 2005 17:22, Oliver Stieber wrote:
ATI and NVidia both have extensions to X that return the total video memory
on the card, other options include using code from the DRI project, and
I've got some very old dos code for some Matrox cards. Since there is no
standard way to
OK, here I go again:
This is a small C program which should get the videoRam using the NV-CONTROL
and ATIFGLEXTENSION extensions. As I only have a nVidia card, could someone
with an ATI card (and the fglrx driver) please test this?
Fabian
getvram.tar.gz
Description: application/tgz
On Sunday 16 October 2005 23:34, Fabian Bieler wrote:
OK, here I go again:
This is a small C program which should get the videoRam using the
NV-CONTROL and ATIFGLEXTENSION extensions. As I only have a nVidia card,
could someone with an ATI card (and the fglrx driver) please test this?
Fabian
Le samedi 08 octobre 2005 à 10:47 +0900, Aric Cyr a écrit :
This is a simple patch to add a registry setting for a user's video
RAM which is used
by wined3d. Currently emulated_videoram is hardcoded at 64MB, which
is not enough for some games and having to recompile wine to change it
is a
On 10/8/05, Jonathan Ernst [EMAIL PROTECTED] wrote:
Le samedi 08 octobre 2005 à 10:47 +0900, Aric Cyr a écrit :
This is a simple patch to add a registry setting for a user's video
RAM which is used
by wined3d. Currently emulated_videoram is hardcoded at 64MB, which
is not enough for some
Hi,
I guess it is not possible to retrieve the real value from the system ?
Jonathan,
OpenGL does not have any standard features which allow querying of
total video memory. It does allow you to see if a texture allocation
would succeed or fail, but that would mean allocating a lot of
19 matches
Mail list logo
