The Sims™ 3
Lils 14 FEB 2024 a las 23:24
Texture memory being detected incorrectly
Hi! I was using this guide (https://steamcommunity.com/sharedfiles/filedetails/?id=1131162350) to get the game to register the graphics card that it links in the beginning. I use Linux, and it was simpler doing it the manual way the guide links to than trying to use the program it linked. I am 100% sure I did it the way it described, because I've lost count for how many times I've double-checked and verified things with it and everything comes back correctly every time.

However, the DeviceConfig.log file states that my card's texture memory is 184MB, which is strange. I didn't have the usual problem of it being set to 32MB, it was only ever detected as 184. Setting texture memory to 1024 in the GraphicsRules.sgr file did not change the result of 184 it keeps getting in the log after starting the game. This also ends up with the GPU in the Rating Info being registered as 5 while GPU Memory is only 2. Does anyone have a solution to this?



For reference, here are my specs that might be relevant (if you need more info just ask):
OS: Linux (Fedora 39)
(Installed through Lutris using the EA App)
Graphics Card: AMD Radeon RX 6800 XT

Also, here are the relevant part of the GraphicsRules files and DeviceConfig logs.
GraphicsRules.sgr:
setb textureMemorySizeOK true if ($textureMemory == 0) seti textureMemory 1024
# setb textureMemorySizeOK false
endif

And here is the DeviceConfig.log:
=== Application info === Name: Sims3 Version: Build: Release === Rating info === GPU: 5 GPU Memory: 2 CPU: 4 RAM: 4 CPU Speed: 3500 Threading: 3 Adjusted CPU: 4267 RAM: 31986 Adjusted RAM: 31474 Cores: 12 === Machine info === OS version: Windows 8 6.2.9200 OS prod type: 0 OS major ver: 6 OS minor ver: 2 OS SP major ver: 0 OS SP minor ver: 0 OS is 64Bit: 1 CPU: AuthenticAMD Brand: AMD Ryzen 5 5600 6-Core Processor Family: 15 Model: 1 Cores: 12 HT: 0 x64: 0 Memory: 31986MB Free memory: 22344MB User: XXX Computer: FEDORA === Graphics device info === Number: 0 Name (driver): AMD Radeon RX 6800 XT (RADV NAVI21) Name (database): AMD Radeon RX 6800 XT (RADV NAVI21) [Found: 1, Matched: 1] Vendor: ATI Chipset: Vendor: 1002, Device: 73bf, Board: 00000000, Chipset: 0000 Driver: aticfx32.dll, Version: 32767.65535.65535.65535, GUID: 00000000-000C-0000-0000-000000000000 Driver version: 65535 Monitor: \\.\DISPLAY1 Texture memory: 184MB Vertex program: 3.0 Pixel program: 3.0 Hardware TnL: 1
Última edición por Lils; 14 FEB 2024 a las 23:29
< >
Mostrando 1-6 de 6 comentarios
BlunderingFool 15 FEB 2024 a las 6:47 
Probably a dumb question but have you tried to manually enter your texture memory settings and then set the file as read-only so the game can't mess with it?

Also just a quick sanity check, have you tried setting GPU memory to either 4gb or the physical amount your GPU has?
Inconsistent 15 FEB 2024 a las 7:43 
Unrelated reply, but may I ask where you locate the DeviceConfig File?
Lils 15 FEB 2024 a las 20:10 
Publicado originalmente por BlunderingFool:
Probably a dumb question but have you tried to manually enter your texture memory settings and then set the file as read-only so the game can't mess with it?

Also just a quick sanity check, have you tried setting GPU memory to either 4gb or the physical amount your GPU has?
I tried the permissions for GraphicsRules and that didn't change anything; the log still reported as 184MB. I don't really know if editing the log file and changing permissions would do anything, because the log just reports what the game is registering.

I also tried setting it to 4GB and the amount my GPU has, and that didn't fix it either sadly.
Lils 15 FEB 2024 a las 20:16 
Publicado originalmente por Consistent:
Unrelated reply, but may I ask where you locate the DeviceConfig File?
It depends on the operating system and which way you installed it (whether through EA App, Steam, Origin, CD, or if you had a custom install path you set. I just kind of poked around through my filesystem til I found it. The folder is also in a different location from 2 other Sims 3 folders that I guess are used for different things, so you might find a Sims 3 folder but not the right one.

Usually, this is how it most often is:
32-bit Windows
EA App: C:\Program Files\Origin Games\The Sims 3\
DVD: C:\Program Files\Electronic Arts\The Sims 3\
Origin: C:\Program Files\Origin Games\The Sims 3\

64-bit Windows
EA App: C:\Program Files\Origin Games\The Sims 3\
Origin: C:\Program Files (x86)\Origin Games\The Sims 3\
DVD: C:\Program Files (x86)\Electronic Arts\The Sims 3\

^If these don't work, you could check your Documents folder.
For me, I since I'm using Linux and installed it through Lutris using the EA App, I had it in
/home/[My User}/Games/EA_App/drive_c/users/Yuk/Documents/Electronic Arts/The Sims 3/
Última edición por Lils; 15 FEB 2024 a las 20:18
emanueru_95 5 NOV 2024 a las 5:45 
Wondering if you ever found out how to fix it. I'm also using Fedora 41 with integrated graphics UHD 620, and I got a little creative with the GraphicsRules.sgr

setb textureMemorySizeOK true if ($textureMemory == 192) seti textureMemory 1024 # setb textureMemorySizeOK false endif

in my case, DeviceConfig.log was stating I have 192MB so I changed the 0 from
"if ($textureMemory == 0)" to 192. This fixed the problem.

Just leaving this comment here in case someone else needs it, since I didn't find an answer searching the Internet.
Última edición por emanueru_95; 5 NOV 2024 a las 5:46
Lils 9 NOV 2024 a las 11:55 
Publicado originalmente por emanueru_95:
Wondering if you ever found out how to fix it. I'm also using Fedora 41 with integrated graphics UHD 620, and I got a little creative with the GraphicsRules.sgr

setb textureMemorySizeOK true if ($textureMemory == 192) seti textureMemory 1024 # setb textureMemorySizeOK false endif

in my case, DeviceConfig.log was stating I have 192MB so I changed the 0 from
"if ($textureMemory == 0)" to 192. This fixed the problem.

Just leaving this comment here in case someone else needs it, since I didn't find an answer searching the Internet.
Oh, awesome! I never found a solution to it. Thanks for the fix!
< >
Mostrando 1-6 de 6 comentarios
Por página: 1530 50

Publicado el: 14 FEB 2024 a las 23:24
Mensajes: 6