I see so NVIDIA seems out of it. I did read some posts about messed up files in the Steam version with people not even able to load the launcher. So its probably a Steam thing again.Mine gave me the time of 10-23-2019 13:47 yet my error happened at around 8 PM or so. I'm using an AMD, which I'll post my own status report when I get back home. I am using Steam though so I'm not sure if that's part of it, possibly relating to the new launcher? I'll try running it on the old one and see if it works out fine in DX11.
Really bad timing for XIV to be having these errors the moment this new content launches, especially for an EX.
ᛞᚨᚢᛃᛁᚦ ᚠᛖᚺᚢ
ᛞᚨᚢᛃᚨᚾ ᚠᚱᚨᚾᛞᛁᛊ : ᛞᚨᚢᛃᛁᚦ ᛊᛖᛚᛒᚨᛉ ᛊᚨᛗᛟ
ᛖᚲᚨ ᚹᚨᛁᛏ ᚨᚾᚨᛁᚾᛟ
ᚦᚨᛏᚨ ᚾᛖ ᚨᛚᛞᚱᚨᛁᚷᛁᚾ ᛞᚨᚢᛃᛁᚦ
ᛞᛟᛗᚨᛉ ᚢᛗᛒᛁ ᛞᚨᚢᛞᚨᚾᛟ ᚺᚹᚨᚱᛃᚨᚾᛟ
I looked through people's posted error reports to see if there was any similarities and it seems out of them the majority have been using Steam, and one was using Windows. So willing to bet it's due to the new launcher and some process it does, I'd say for now since we have the option try switching to the older launcher and see if it does anything different.
This really needs to be looked into for both sides so if anyone has these issues, please post your error reports so we can get this noticed/make a new thread just for your specific error report.
Mh, I have Retail version without Steam so it may not be that, unless I'm in a specific case, same error message though !
I'm getting the same error too. So far I've been booted 5 times between yesterday and today, and only on my work computer - at home it hasn't happened even once. I believe I've just been standing around at the Maelstrom HQ in Limsa each time it's happened.
I'm also on non-Steam version and get the same error message. It's happening to me in Eulmore and Kholusia in addition to Lakeland now, to the point where I can't really progress the main story quests.
Based on the wide range of locations where this is happening for people, I'm wondering if it's not about the locations, but maybe about some error trying to render one of the new pieces of equipment or some other new item.
Last edited by WrenElessedil; 11-01-2019 at 03:25 AM.
I believe it's multiple different errors tied into situations.I'm also on non-Steam version and get the same error message. It's happening to me in Eulmore and Kholusia in addition to Lakeland now, to the point where I can't really progress the main story quests.
Based on the wide range of locations where this is happening for people, I'm wondering if it's not about the locations, but maybe about some error trying to render one of the new pieces of equipment or some other new item.
I'm seeing some people just hanging around and not doing anything, while others are getting mixed into specific things like duties.
From the three errors I had yesterday all of mine happened in mid combat. I don't have the screenshot on my person but the error
s I received were different then the ones being posted however they shared the date of 10-23-19 and some specific time. I've had this happen in the new dungeon and the Nier raid at different points (1st and 3rd boss fights for me).
|
![]() |
![]() |
![]() |
|
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.