What you have to do now is figure out your own command lines and if you do it right, your problem will most likely disappear.
The screenshot below represents how my game looked for the first half a second after I turned away for a moment. Then all the textures slowly loaded to high quality. For a brief time a number of objects was missing, too.
All of R* Toronto responses to this thread are quoted below. Some of them may be out of context so please be careful. Please remember that what you really have to do is find command lines specific to your hardware configuration.
|QUOTE (Rockstar Toronto @ Apr 22 2010, 15:15)|
|Basically -memrestrict is telling the game how much video memory your system has available. At startup we query the OS for this value but as some of you may have noticed the number can vary even though you are obviously not changing your video card everytime you play the game.|
Once the game exceeds the amount of video memory available, the Os finds it from somewhere else (system memory) and eventually this causes fragmentation and the game throws up an RESC10 error because the OS can't find anymore free memory. The tricky part is that every OS behaves differently, and thats before you factor in other .dll's and drivers that also make requests from this memory pool which will be different from user to user.
Using -memrestrict explicitly tells the game how much video memory to use. The math is to take the desired meg number and multiply it by 1024 twice. So if we wanted to declare 600 megs of VRAM:
600 x 1024 x 1024 = 629145600
you would enter the commandline "-memrestrict -629145600"
Lowering this number increases stability of the game by capping the video memory, but there will come a point where there isn't enough memory to draw everything required by the game which is when you see "popping".
|QUOTE (Rockstar Toronto @ Apr 21 2010, 21:07)|
|OutOfTimer, if you use the following commandline the memory settings will be the same as they were in Patch 126.96.36.199 (these are specific to your hardware):|
-reservedApp 0 -memrestrict 943718400
I'm not sure if this will cause an RESC10 error with your current video driver, but on some machines the OS manages the memory better than others.
|QUOTE (Rockstar Toronto @ Apr 21 2010, 17:26)|
|- Load Times Cut in Half|
I'm not seeing this at all, what are you using as a test? Loading from the Start Menu to the First Mission?
- Draw Distance Higher than before
This is mainly because our new shadow solution requires less VRAM then the old one
-Auto Configure chooses Medium Textures instead of High Textures
On Vista 32 and Windows 7 32 the video card drivers use up the memory in our application space. This scenario is unique to these OS'. On a 32 Bit OS this defaults to 2GB, on 64 Bit OS this is 4GB. We have no control over Video Card drivers (among other .dll's that end up in our address space due to mods and whatnot) that can change the amount of address space used with every release.
In our latest profiles, with High Textures we saw that the application memory was exceeding the 2GB limit in some cases so we now auto configure to Medium Textures. Now it is entirely possible that you can run High Textures on these 32 Bit Os and never see the problem due to the unpredictibility of the game (ie. if you skip a cutscene or do a mission differently) but I think even you can see the logic in our auto configure choice in this instance.
|QUOTE (Rockstar Toronto @ Apr 22 2010, 00:25)|
|I don't see why you couldn't run High Shadows on your rig and have same performance as 188.8.131.52 with Very High Shadows.|
We have a Win 7 64 bit i7 rig here running an Nvidia 480 and we get a rock solid 35-45 with Very High Shadows and sliders set at 50/50/50.
You can try the higher mem restrict number as well, but it won't make as big a difference as I expect it to make on OutOfTimers rig.
-reservedApp 0 -memrestrict 943718400
Again, make sure clip capture is ON to avoid the water slowdown bug.
|QUOTE (Rockstar Toronto @ Apr 22 2010, 14:56)|
|With the latest drivers I would expect this setting to cause gameplay stuttering but as I've said before in this thread sometimes the OS' memory management works better on some machines vs others.|
|QUOTE (Rockstar Toronto @ Apr 22 2010, 16:49)|
|We have no set "cap" on how much the game will render or how fast it can run.|
On this same rig we can configure the game to run a sustained 185 fps. We allow the user to tailor their experience based on what they personally want out of the game within the limits of the hardware they have. This is what we beleive the PC gamer wants.
The game looks and plays amazing with the settings we have dialed in on the i7 machine that is hitting 35-45 fps. If we wanted it to run at 55fps we can change the settings to achieve this but we have to lower some settings due to the constraints of the current hardware.
We've tried to convey this by telling the user how each setting influences the CPU and GPU.
|QUOTE (Rockstar Toronto @ Apr 16 2010, 18:48)|
|Do not do this unless you know exactly what is going on. Do not do this if you have less than 4 Gigs of system RAM.|
This does not work in XP32 and the game will crash within minutes if you try the /3GB switch.
Open a command prompt and type the following:
bcdedit /set increaseuserva 3072
Reboot. To disable, open a command prompt and type the following:
bcdedit /deletevalue increaseuserva
Win 7 32:
Same as above, but you must open the command prompt as the administrator or you will be denied access.
Again, DO NOT TRY THIS IF YOU ARE NOT COMFORTABLE WITH THE TERMINOLOGY OR NEED MORE DETAILED INSTRUCTIONS. You could put your system into a bad state.
|QUOTE (Rockstar Toronto @ Apr 16 2010, 19:47)|
|Thats only if you have a 32 Bit OS and insist on using High Textures. Medium textures are recommended for Vista 32 / Win 7. On those Operating systems the video card drivers are in the same application space as GTA IV so we have alot less to work with.|
|QUOTE (Rockstar Toronto @ Apr 16 2010, 22:11)|
|Do not try to run GTA IV or EFLC with a 3GB address space with XP 32 as it will make the game unstable.|
Vista 32 / Win 7 32 are unique in that the video drivers share the same memory space as the game which is why we don't recommend High Textures for this OS.
Since XP 32 has more of the 2GB maximum memory space to work with then Vista 32/ Win 7 32, you may be able to use High Textures depending on other hardware.
|QUOTE (Rockstar Toronto @ Apr 16 2010, 17:31)|
|If your setup was stable with Patch 5 and you are seeing excessive popping on high end rigs, try the following commandline:|
Do not use any of your old commandlines in conjunction with this when first attempting it; try it on it's own first and let the in game memory management handle the rest. This should NOT be used on Vista/Win 7 32 bit*. Same goes for High Textures in general, there simply isn't enough memory available on 32 bit Vista/Win 7.
GTA IV and EFLC are Large Address Aware, on 32 Bit Vista/Win 7 you can use the bcdedit command to enable 3GB memory address space which will allow the games memory management to behave as if it was on a 64 Bit Os. Do not attempt this if you've never heard of this before, it can cause your system to become unstable when using other software.
|QUOTE (Rockstar Toronto @ Apr 21 2010, 21:14)|
|There is a bug right now with Clip Capture OFF so leave it ON until we can distribute a fix.|
|QUOTE (Rockstar Toronto @ Apr 21 2010, 21:19)|
|The disc check is something that was mandated. If you don't want disc check get the Steam version.|