|
|
|
#1
Hello, I just bought a GTX 460 and I wanna max out DOW but it is being mean and not letting me. How do I circumvent this ruthless block so I can max out my game? Is there a way? I remember there being one a long time ago but I thought they patched it out.
The true mind can weather all the lies and illusions without being lost. The true heart can touch the poison of hatred without being harmed. Since beginning-less time, darkness thrives in the void but always yields to purifying light.
only way is to force it via config but it will kill you game balance believe me
u dont need the ultra graphic i didn't use it too.
or you install an 64bit system^^
My Games--->Dawn of War 2--->Settings--->Config*
and then a 3 instead of a 1 or 2
LSA|Eternal
There used to be a way, but it no longer exists.
gfwl= Blatant Silence
Man is certainly stark mad. He cannot make a worm, and yet he will be making gods by the dozens. -Montaigne
#4
Why do I need a 64 bit OS if I have a GTX 460, a Quad core, and 4 GB of ram? Does the 64 bit os make that much of a difference? I'm pretty bad when it comes to computers so I really don't know any of this stuff so thanks for answering.
#5
There still is a way; I've done it. I remember that it involves changing something in the WindowsautoexecBoot.ini file.
Last edited by Dux; 26th Aug 10 at 3:41 PM. Reason: I remembered how to do it. See next post.
In-Game: Dux
Steam Account: DucusSumus
#6
setting = "use64bitrt",
value = 0,
},
I see that the use64 bit is set to 0 in my config folder. If I set it to 1 will it trick it into thinking I have a 64 bit OS or will my game explode?
nonono not modify the system pls.
just the config ok?
its the best way really and if its not working with your balance and stuff...
u can set ur settings in game to high and your config has the normal settings again (urs) before u forced ur game^^
Every 2 weeks there's a thread like this, let me dig up my old post. In the mean time: yes, 64 bit OS makes a difference.
There is a workaround for 32bit systems, but it's not recommeded since it can lead to system instability and bluescreens. That's surely a risk you don't want to take just to have pimp gfx?
#9
In the event this doesn't work out if I just delete the file will it go back to defaults? Because I just went through everything set at 2 and put it to 3.
u just need to modify:
dynamiclighting
effectsfidelity
reflections
effectsdensity
terraindetail
yeah i think thoose are the ones...try it out 1 after another
u have the ultra setting then but its still black/grey
but u will see it ^^
I don't think the changes stick anymore, since relic changed their policy on the 32/64bit issue.
To know what the problem actually is, and the problems that circumventing it can cause read my posts in this thread http://forums.relicnews.com/showthre...00#post3842600
Also, your 4gb of ram will be quite useless in a 32 bit OS, as a maximum of 3gb of this can be used.
Basically ultra is disabled because the game will crash when you force it on (since memory requirements rose with CR). You have to edit windows files in order to make it work, but that can lead to system instability.
Like if your going to spend the money on a pc with that kind of horse power why the hell would you use a 32bit OS?
#13
In order to get ultra settings to work on a 32-bit system, you need to allow your OS to allocate 3 GB of virtual address space for applications. By default, 32-bit versions of Windows will only allocate 2 GB of virtual address space for applications, preserving the other 2 GB for the OS. You can change this using the 3GB switch in the Windows Boot.ini file. Instructions on how to do this can be found here:
http://dwf.blogs.com/beyond_the_pape...ows-vista.html
Do this at your own risk, as some people have reported instability issues as a result. Personally, I have had no such issues, and I've been using this for several months now. Your system sounds like it has more than enough power to run DoW II at ultra settings, so I wouldn't worry about in-game performance hits.
Also, I am moving this thread over to tech support.
#14
We never changed our policy. Ultra on a 32-bit OS was never officially supported. There was a command-line parameter to disable the check (basically, use at your own risk), but we found that caused too many crashes, so we took it out.
Also, "use64bitrt" has nothing to do with ultra settings - the "rt" stands for "render target".
Lastly, this is not "relic blocking", this is a system requirements issue. You may have a beefy PC, but your OS is important. The fact is 32-bit Windows operating systems cannot provide enough memory address space for DOW2 in ultra settings mode.
#15
Cool, so DOW was crashing when I maxed out the settings. I will be getting Windows 7 64-bit soon so I guess I'll have to wait till then to max out DOW. I just got impatient when my new GPU and PSU arrived. I am so eager to see what this thing can do.
@Dux, is there any risk to doing that? Like can I damage my computer or something or do you get slow downs when you aren't in games?
When you do that, effects can range from nothing changes, to occasional bluescreens to system not booting anymore
Edit: Excerp from anandtech (linked in the other thread)
Changing Windows on the other hand to allocate more of the virtual address space to applications is in practice just as dangerous as we theorized earlier. We initially set our copy of Windows Vista to adjust the split to 1GB kernel mode, 3GB user mode, only for Vista to encounter a BSOD while booting. We had to settle for a 1.4GB/2.6GB split before Vista would boot, and even then Vista still periodically encounters a BSOD upon booting at that allocation or any other allocation other than 2GB/2GB. While what problems may occur and with what values is highly variable from system to system, this is why trying to move the barrier at all can be dangerous.
#17
Apparently, there are some risks. Like I said, I've never encountered a single issue myself, and I've been using the 3GB switch for a long time now. Then again, I have Windows XP, not Vista.Originally Posted by Vintage
If you follow the instructions on the link I provided, you should easily be able to boot up into 2GB (standard) mode in the event that 3GB gives you trouble. While it may cause crashes, I do not believe that the 3GB switch can cause any irreparable damage to your PC; I doubt that Microsoft would have made it an option if it was that dangerous.
That being said, go through with this procedure at your own risk. I'm not liable for any damage you cause as a result of this procedure; I am merely sharing my personal experience with it.
Hmm my old XP(32bit) computer was able to access 3.5gb of R.A.M. and i've read other threads where people's computers have been able to use 3.5 so I don't think it's limited to 3gb only.
#19
This is not a debatable issue. Just because your OS lists that it "detects 3.5GB" does not mean a single application can access all that memory. Microsoft has numerous pages explaining the technical reasons for all of this. This is a technical fact.
a 32 bit OS has 4gb of adress space. You can theorhetically adress 4 gb of ram, but your vidcard memory gets substracted. So I assume you simply had a 512 MB card.
#21
#22
This is true -- it is not possible to address more than 3 GB of virtual space for a single application in a 32-bit architecture -- but as long as you have less than 1 GB of video memory, Windows should be able to recognize (and use) over 3 GB of physical system memory in address translation.
#23
The thing is it doesn't always work like that. I've had experiences where, after plugging in four 1GB RAM sticks, my computer stopped recognising my video card. It was only a 320 MB card as well so I don't think it matters what size your video card is - Windows will allocate a set amount of space for it even if that space isn't being used.
(and the problem resolved itself when I removed the fourth RAM stick)
I am an Iron Warrior! Iron Within, Iron Without!
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
