Grand Theft Auto V For PC

Posted: October 11th, 2013 | Author: | Filed under: Software
Tags: , , , , , , , , ,

UPDATE 4:Officially coming this fall

UPDATE 3: It’s now missing from both the profiles .blb and the dx10+ .dlls in the 14.1 mantle beta. Not that it appeared to be needed in the first place as ‘HighPerfGPUAffinity’ doesn’t sound like it’s doing much.

UPDATE 2: It’s in the driver .dll files now. Hex edit atidxx32.dll from 13.11 beta 6 and go to 0x69ae34.

UPDATE: In the new 13.11 Beta 3 leak, hex edit the .blb file, go to 0x192a8, GTA5 is there again (was missing in beta 1).

Well I never looked very closely at the CAP file for 13.10 beta 2, but I just noticed some interesting things.

<application Title="Grand Theft Auto V" File="GTA5.exe">
	<use Area="PXDynamic">HighPerfGPUAffinity</use>
</application>

Want to prove it yourself? You don’t even need to convert the .blb to .xml, just hex edit the blb and go to 0x19130 and 0x19b88 locations.

And the usual games coming soon…

<application Title="Assassin's Creed 4" File="AC4BFSP.exe">
	<use Area="PXDynamic">HighPerfGPUAffinity</use>
</application>
<application Title="Assassin's Creed 4 MP" File="AC4BFMP.exe">
	<use Area="PXDynamic">HighPerfGPUAffinity</use>
</application>
<application Title="Batman: Arkham Origins" File="BatmanOrigins.exe">
	<use Area="PXDynamic">HighPerfGPUAffinity</use>
</application>
<application Title="Call of Duty: Ghosts" File="iw6sp64_ship.exe">
	<use Area="PXDynamic">HighPerfGPUAffinity</use>
</application>
<application Title="Planetary Annhilation (32bit)" File="PA.exe">
	<use Area="PXDynamic">HighPerfGPUAffinity</use>
</application>
<application Title="Planetary Annhilation (64bit)" File="PA32.exe">
	<use Area="PXDynamic">HighPerfGPUAffinity</use>
</application>
<application Title="Need for Speed sequel" File="Race.Main_Win64_Release.exe">
	<use Area="PXDynamic">HighPerfGPUAffinity</use>
</application>
<application Title="Watch Dogs Demo" File="DuniaDemoLaunch_PC_r64.exe">
	<use Area="PXDynamic">HighPerfGPUAffinity</use>
</application>
<application Title="Watch Dogs" File="Watch_Dogs.exe">
	<use Area="PXDynamic">HighPerfGPUAffinity</use>
</application>
<application Title="Wolfenstein: The New Order" File="WolfNewOrder_x64.exe">
	<use Area="PXDynamic">HighPerfGPUAffinity</use>
</application>

Looks like more 64-bit games are coming outside of Battlefield 4? Don’t think this suddenly means GTA5 magically comes out real soon, developers/porters also need working drivers for their games. I’m still expecting the usual +200 days after console launch.

(Guru3d backup post in case the site explodes, but it held up fine during Halo 3)

Last Modified: June 9th, 2014

5 Comments »

Halo 3 For PC

Posted: March 17th, 2013 | Author: | Filed under: Software
Tags: , , , , , , , ,

UPDATE: Want proof? Just look at the .blb file from the driver, or use the atiapfxx.exe tool to create the XML yourself. Try these locations of the .blb in a hex editor: 15a74 or 250b6.

Sup. From the CAP of the 13.3 Catalyst beta driver. Another point of interest after the steam app ID that showed up last month.

<profile Area="UDX" Usage="Halo3" Notes="Halo3">
	<value Property="Version">1</value>
	<value Property="MTShaderCompile">False</value>
</profile>
 
<application Title="Halo3" File="halo3*.exe">
	<use Area="UDX">Halo3</use>
</application>

Not that this can fully confirm anything, we still have ‘BF1943Game.exe’ that never came out. You heard it here first… probably.

(Here is my guru3d post in case something happens from all this site traffic, consider it a mirror.)

Last Modified: October 11th, 2013

18 Comments »

How To Restore The Missing AMD Pre-defined Crossfire Profiles In CCC

Posted: February 14th, 2013 | Author: | Filed under: Hardware, Tips/Tutorials
Tags: , , , , , ,

So a few months ago, maybe when 12.10 CAP 1 came out, you may have noticed some of the AMD pre-defined crossfire profiles do not appear anymore in CCC (and you know they used to be there). What seems to be happening is that CCC is falling back to the CAP that came with the currently installed driver, which is located in the system folders of Windows.

This is certainly a problem for legacy users stuck on a driver branch and default CAP made in April 2012. Hawken for example only appeared in later CAPs and you need to tell CCC to load the profile since it doesn’t match the game exe.

So what’s the solution? Might as well overwrite the driver CAP with the latest one since we know that’s what CCC is loading.

Let’s start with renaming atiapfxx.blb in your system folders of Windows: C:\Windows\SysWOW64 and C:\Windows\System32. Just put an -old at the end or something so that you can rename back if there is a problem.

Install the latest CAP then go to its folder, something like C:\Program Files (x86)\ATI Technologies\Application Profiles\. Copy atiapfxx.blb and paste it into the two system folders from earlier.

Restart your system and now your CCC will display the new profiles again.

There was a related bug posted on forums where ALL pre-defined profiles were missing for some users of newer cards. I’m not sure if this method can also fix that issue as I’ve never ran into it.

Last Modified: February 14th, 2013

No Comments »