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.
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.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
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.
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.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
...
Now to test if the ffxivwinbenchmark.exe settings work for ffxivgame.exe!![]()
Last edited by PetriW; 06-20-2012 at 08:40 AM. Reason: Added changes.
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.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!
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
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?
Player
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.