Nvidia releases beta driver 304.48: FFXIV Sli profile updated

I wasn't sure where to really post this (sorry, virgin forum post, I mostly lurk >.>). Anywhos, Nvidia has a beta driver and says it has updated the sli profile for FFXIV. Hopefully it fixes the crashing for some of nvidia users. The link to it can be found here: http://www.geforce.com/whats-new/articles/nvidia-geforce-304-48-beta-drivers-released/ . Sorry again if i posted this in wrong place. Please Enjoy ^^;. Ta-ta.

thanks, I'm gonna install this right away when I get home tonight.

Re-Linked for the peoples.

So does this mean that sli will have more of an affect on the game now?

Coolies, many thanks

Quote:

---

Originally Posted by Jet

So does this mean that sli will have more of an affect on the game now?

---

Maybe. I'm sure we'll all find out when it's installed.

As someone who has been plagued by multiple FFXIV crashes per night I installed these drivers last night and have had no crash in game yet.

Keeping my fingers crossed...

I installed this last night. I haven't noticed a difference. The game still crashes a lot in cities.

Bear in mind, this is an updated SLI profile, which doesn't mean much unless you use SLI (2-4 graphics cards).

I should really log in and see if my average FPS increases. Running dual 470's never had many problems myself with the SLI being gimped maybe now it will just run a bit better.

Quote:

---

Originally Posted by Eekiki

Bear in mind, this is an updated SLI profile, which doesn't mean much unless you use SLI (2-4 graphics cards).

---

...and only in exclusive fullscreen mode (the one crashing on alt-tab), afaik.

Quote:

---

Originally Posted by Eekiki

I installed this last night. I haven't noticed a difference. The game still crashes a lot in cities.

Bear in mind, this is an updated SLI profile, which doesn't mean much unless you use SLI (2-4 graphics cards).

---

Darn then I must have just got lucky with no crashing last night.

Oh well, back to hoping 1.22c has a fix to the frequent random crashes some of us are experiencing.

Are all of you guys experiencing crashing useing SLI? because im not and my game crashes every now and again. What is SE doing about this in V 2.0? not one person asked that question.

Quote:

---

Originally Posted by DNO

Are all of you guys experiencing crashing useing SLI? because im not and my game crashes every now and again. What is SE doing about this in V 2.0? not one person asked that question.

---

I'm guessing that having a completely new client means that a lot of the current problems will go away. I'm sure we'll get a totally new set of problems to deal with, though. :p

I upgraded from two GTX580s in SLI to a single GTX670. The crashes are less frequent, but they still happen.

Quote:

---

Originally Posted by DNO

Are all of you guys experiencing crashing useing SLI? because im not and my game crashes every now and again. What is SE doing about this in V 2.0? not one person asked that question.

---

Writing a new graphics engine from scratch? There's no reason to think it will be a problem in 2.0 just because it's a problem now.

Quote:

---

Originally Posted by DNO

Are all of you guys experiencing crashing useing SLI? because im not and my game crashes every now and again. What is SE doing about this in V 2.0? not one person asked that question.

---

I am not and I crash 1-3 times per night playing FFXIV.

Although my issue may be related to the new memory I recently installed... (can't install game without CRC errors, random blue screens, etc)

Quote:

---

Originally Posted by Soukyuu

...and only in exclusive fullscreen mode (the one crashing on alt-tab), afaik.

---

SLI works in windowed mode. I can see both GPU loading with EVGA overlay, on my 480s. No need to guess or spread wrong information.

Here's the SLI profile for the 301.42 WHQL drivers:

Profile "Final Fantasy XIV"
ShowOn GeForce
ProfileType Application
Executable "ffxivgame.exe"
Setting ID_0x0095def9 = 0x00010000
Setting ID_0x1033cec1 = 0x00000003
Setting ID_0x1033dcd2 = 0x00000004
Setting ID_0x1095def8 = 0x02c00005
Setting ID_0x10ecdb82 = 0x00000001
Setting ID_0x701eb457 = 0x2241ab21 InternalSettingFlag=V0
SettingString ID_0x7049c7ec = "웭ꑢ쫐₰" InternalSettingFlag=V0
SettingString ID_0x704d456e = "쪣⃅쀯���㓵僽婙簭鹼瀮딕ᤠ及���븄᱃뼍襢籜謬⑒贷㱃矺糓ꗼ熟胆㖩뫬뛝᯵쑖낡锛䭷乇솵᜶᢫୭謸壺嫣Ͱ嚉᚞誌㈡跽軧桧ⶇ䂚驐읒౦펴턖㛰눫" InternalSettingFlag=V0
SettingString ID_0x7051e5f5 = "籭鸙" InternalSettingFlag=V0
SettingString ID_0x705fafec = "웭ꑼ쫑₀쁰���㒨傢婋籨鸹灰땁᥿厈���븞ᰒ뽉襂" InternalSettingFlag=V0
Setting ID_0x708db8c5 = 0x5c04c2a2 InternalSettingFlag=V0
Setting ID_0x709a1ddf = 0x4b1cd968 InternalSettingFlag=V0
SettingString ID_0x70b5603f = "榻鳈⏹ꢗ" InternalSettingFlag=V0
Setting ID_0x70edb381 = 0x24208b6c InternalSettingFlag=V0
EndProfile

Profile "Final Fantasy XIV Benchmark"
ShowOn GeForce
ProfileType Application
Executable "ffxivwinbenchmark.exe"
Setting ID_0x0095def9 = 0x00010000
Setting ID_0x1033cec1 = 0x00000003
Setting ID_0x1033dcd2 = 0x00000004
Setting ID_0x1095def8 = 0x02c00005
Setting ID_0x10ecdb82 = 0x00000001
Setting ID_0x701eb457 = 0x2241ab21 InternalSettingFlag=V0
SettingString ID_0x7049c7ec = "웯ꑢ쫐₰" InternalSettingFlag=V0
SettingString ID_0x704d456e = "쪲⃕쀳���㓿僽娊籿鹫瀥딇ᤠ及���빁ᰂ뼊褶籊謽⑅贽㰆矽粝ꖸ熉胙㖰뫡뛝ᯕ쑚납锐䭫乿솵᜻ᢻ୻譪壻媦͸嚁ᚚ誊㈡跰軵桧⶛䃴" InternalSettingFlag=V0
SettingString ID_0x7051e5f5 = "籯鸙" InternalSettingFlag=V0
SettingString ID_0x705fafec = "웭ꑼ쫑₀쁰���㒢傢婉籮鸹灰땁᥿厈���븞ᰒ뽉襂" InternalSettingFlag=V0
Setting ID_0x708db8c5 = 0x5cf40380 InternalSettingFlag=V0
Setting ID_0x709a1ddf = 0x4b1cd968 InternalSettingFlag=V0
SettingString ID_0x70b5603f = "榻鳈⏹ꢗ" InternalSettingFlag=V0
Setting ID_0x70edb381 = 0x24208b6c InternalSettingFlag=V0
EndProfile


---------------------


Here's the profile for the beta 304.48 drivers:

Profile "Final Fantasy XIV"
ShowOn GeForce
ProfileType Application
Executable "ffxivgame.exe"
Setting ID_0x0095def9 = 0x00010000
Setting ID_0x1033cec1 = 0x00000003
Setting ID_0x1033dcd2 = 0x00000004
Setting ID_0x1095def8 = 0x02c00005
Setting ID_0x10ecdb82 = 0x00000001
Setting ID_0x701eb457 = 0x2241ab21 InternalSettingFlag=V0
SettingString ID_0x7049c7ec = "웭ꑢ쫐₰" InternalSettingFlag=V0
SettingString ID_0x704d456e = "쪣⃅쀯���㓵僽婙簭鹼瀮딕ᤠ及���븄᱃뼍襢籜謬⑒贷㱃矺糓ꗼ熟胆㖩뫬뛝᯵쑖낡锛䭷乇솵᜶᢫୭謸壺嫣Ͱ嚉᚞誌㈡跽軧桧ⶇ䂚驐읒౦펴턖㛰눫" InternalSettingFlag=V0
SettingString ID_0x7051e5f5 = "籭鸙" InternalSettingFlag=V0
SettingString ID_0x705fafec = "웭ꑼ쫑₀쁰���㒨傢婋籨鸹灰땁᥿厈���븞ᰒ뽉襂" InternalSettingFlag=V0
Setting ID_0x708db8c5 = 0x5c04c2a2 InternalSettingFlag=V0
Setting ID_0x709a1ddf = 0x4b1cd968 InternalSettingFlag=V0
SettingString ID_0x70b5603f = "榻鳈⏹ꢗ" InternalSettingFlag=V0
Setting ID_0x70edb381 = 0x24208b6c InternalSettingFlag=V0
EndProfile

Profile "Final Fantasy XIV Benchmark"
ShowOn GeForce
ProfileType Application
Executable "ffxivwinbenchmark.exe"
Setting ID_0x0095def9 = 0x00010002
Setting ID_0x1033cec1 = 0x00000003
Setting ID_0x1033dcd2 = 0x00000004
Setting ID_0x1095def8 = 0x02c08005
Setting ID_0x10ecdb82 = 0x00000001
Setting ID_0x701eb457 = 0x2241ab21 InternalSettingFlag=V0
SettingString ID_0x7049c7ec = "웯ꑢ쫐₰" InternalSettingFlag=V0
SettingString ID_0x704d456e = "쪲⃕쀳���㓿僽娊籿鹫瀥딇ᤠ及���빁ᰂ뼊褶籊謽⑅贽㰆矽粝ꖸ熉胙㖰뫡뛝ᯕ쑚납锐䭫乿솵᜻ᢻ୻譪壻媦͸嚁ᚚ誊㈡跰軵桧⶛䃴" InternalSettingFlag=V0
SettingString ID_0x7051e5f5 = "籯鸙" InternalSettingFlag=V0
SettingString ID_0x705fafec = "웭ꑼ쫑₀쁰���㒢傢婉籮鸹灰땁᥿厈���븞ᰒ뽉襂" InternalSettingFlag=V0
Setting ID_0x708db8c5 = 0x5cf40380 InternalSettingFlag=V0
Setting ID_0x709a1ddf = 0x4b1cd968 InternalSettingFlag=V0
SettingString ID_0x70b5603f = "榻鳈⏹ꢗ" InternalSettingFlag=V0
Setting ID_0x70edb381 = 0x24208b6c InternalSettingFlag=V0
EndProfile

That's what "afaik" at the end of my post was for, Zien.
I don't have SLI nor Crossfire, but one of them doesn't work unless the program is running windowed. I guess it must be Crossfire then.

After updating to the most recent true release, I found myself going down to like 10 fps. I updated to this beta build and am back up at 45+ fps. So if anything, it fixed whatever was buggy about the current release of my card's drivers.

I have noticed this 100% of the time.

1. Log out somewhere outside of Uldah, where there are likely little to no players
2. Restart your PC
3. Login to XIV
4. Return to Ul'dah
5. The moment you're able to have control of your character run directly forward

9/10 times the game will crash for me. What happens is it's pulling massive amounts of data, maybe trying to load various kinds of dats (because there are dozens of people in 1 spot, and the game becomes very choppy sometimes briefly for 2-seconds and that's enough to trigger the "This program is not responding" and it crashes.

Try the above steps, but when you're in uldah, hit the walk button and slowly move forward giving your computer enough time to handle all the stuff it has to pull and display. It's less likely you'll crash.

As far as Direct X, i have no idea why that happens to me personally. It'll happen at the most random times, not just when doing specific things or loading or anything. *shrug*

I have an i7 2.8 and GTX465

Quote:

---

Originally Posted by REDace0

Writing a new graphics engine from scratch? There's no reason to think it will be a problem in 2.0 just because it's a problem now.

---

Right... you keep on thinking that 2.0 will fix everything. im on the side of realism.

I would like to hear word from SE that they even know about the shut downs and that they plan to at least work on it.

Quote:

---

Originally Posted by RedAffinity

I have noticed this 100% of the time.

1. Log out somewhere outside of Uldah, where there are likely little to no players
2. Restart your PC
3. Login to XIV
4. Return to Ul'dah
5. The moment you're able to have control of your character run directly forward

9/10 times the game will crash for me. What happens is it's pulling massive amounts of data, maybe trying to load various kinds of dats (because there are dozens of people in 1 spot, and the game becomes very choppy sometimes briefly for 2-seconds and that's enough to trigger the "This program is not responding" and it crashes.

Try the above steps, but when you're in uldah, hit the walk button and slowly move forward giving your computer enough time to handle all the stuff it has to pull and display. It's less likely you'll crash.

As far as Direct X, i have no idea why that happens to me personally. It'll happen at the most random times, not just when doing specific things or loading or anything. *shrug*

I have an i7 2.8 and GTX465

---

Ive been in my mog house and its crash. logging on there and then logging crashing. I dont think this will work for me but i do think it is art of the reason.

Quote:

---

Originally Posted by DNO

Right... you keep on thinking that 2.0 will fix everything. im on the side of realism.

I would like to hear word from SE that they even know about the shut downs and that they plan to at least work on it.

---

My point was only that it's different code. 2.0 won't be running a 'patched' or 'fixed' version of this game engine, so there's no reason to expect this same fatal bug to remain, unless you don't think it's a bug in the current engine. For other parts of the system we don't know how much of it is going to be entirely from scratch, so who knows? Those bugs could well stick around.

I'm not exactly sure what you expect them to tell you. Do you really think they are going to say anything other than that they have completely rewritten the engine to perform correctly? If so, that isn't being a realist.

Yep, my crashes always occur in cities, usually when changing sections, and usually when entering adventurer's guilds (where there's the highest concentration of people.

I also quite often get the game to crash when in a heavily populated area and opening a menu window, and even sometimes from simply targeting someone.

The common thread is busy parts of cities. "Stay out of Ul'dah" isn't a viable workaround in this case, 'cause it happens just as often in Limsa and Gridania.

Quote:

---

Originally Posted by Zien

Here's the SLI profile for the 301.42 WHQL drivers:

...

Here's the profile for the beta 304.48 drivers:

...
Executable "ffxivwinbenchmark.exe"
Setting ID_0x0095def9 = 0x00010002
Setting ID_0x1033cec1 = 0x00000003
Setting ID_0x1033dcd2 = 0x00000004
Setting ID_0x1095def8 = 0x02c08005
Setting ID_0x10ecdb82 = 0x00000001
...

---

The interesting thing with these changes is that they only changed the SLi Profile for the benchmarking program. The ffxivgame.exe settings are still the same. I have no idea if this actually matters but I double checked by comparing my old driver (301.42) and this new one and there were indeed no changes.

Now to test if the ffxivwinbenchmark.exe settings work for ffxivgame.exe! ;)

Quote:

---

Originally Posted by PetriW

The interesting thing with these changes is that they only changed the SLi Profile for the benchmarking program.

---

http://i0.kym-cdn.com/entries/icons/...4/facepalm.jpg

Quote:

---

Originally Posted by PetriW

The interesting thing with these changes is that they only changed the SLi Profile for the benchmarking program. The ffxivgame.exe settings are still the same. I have no idea if this actually matters but I double checked by comparing my old driver (301.42) and this new one and there were indeed no changes.

Now to test if the ffxivwinbenchmark.exe settings work for ffxivgame.exe! ;)

---

Yes that's all that was changed under the SLI profile settings. I ran the benchmark and it's about 50pts more which is within margin of error. If they improved SLI as noted on patch notes, hopefully it's for stability and on driver side that we can't see.

Quote:

---

Originally Posted by REDace0

My point was only that it's different code. 2.0 won't be running a 'patched' or 'fixed' version of this game engine, so there's no reason to expect this same fatal bug to remain, unless you don't think it's a bug in the current engine. For other parts of the system we don't know how much of it is going to be entirely from scratch, so who knows? Those bugs could well stick around.

---

right thats my point "who knows" i would like to know and i would like to know soon. theres no reason to believe anything will be fixed besides the things they have already talked about. this is not one of them. SE has said zero about shutdowns

Quote:

---

Originally Posted by AlexNiculaie

I'm not exactly sure what you expect them to tell you. Do you really think they are going to say anything other than that they have completely rewritten the engine to perform correctly? If so, that isn't being a realist.

---

not sure this is for me but ill answer. If not then my bad.

I expect them to say "The game you purcahsed for 70 bucks. waited 2 years to get good while paying a monthly fee for a year of that time... Will work as good as every other game on the market. We are aware of these problems and 2.0 will fix them"

If that is not being a realist then what is?

Just upgraded from a GTX560Ti to a GTX670. I've crashed running through cities twice now, with the "Unable to detect DirectX device" error that i only ever saw while trying to tab out of full screen. I play in windowed mode. Never crashed with this error using the 560Ti or my old 460.

I've had that problem only twice, and it was while playing after CTRL/ALT/DEL to get to task manager (seriously SE, another game where DirectX crashes your game? Fucking terrible)

I rebooted and haven't had it since.

Just crashed 4 times in Hamlet with the same DirectX error. Bloody hell. Trying beta drivers and then older drivers and if it still doesn't work i guess i'll have to go back to my 560Ti.

i been using SLI from day 1 and i see no difference in preformance, its always ran smooth with v-sync & tripple buffering.
its probably better on the older cards maybe it fixed bugs.