search

LeonBlade / PaisleyPark

A waymark preset tool for FFXIV
MIT License
148 stars 60 forks source link

Game crashed on version 1.3.0 #3

Closed Leisterredux closed 5 years ago

Leisterredux commented 5 years ago

While updating Paisley Park from version 1.2.1 to 1.3.0, the application becomes unresponsive and can cause Final Fantasy XIV to crash.

Steps involved:

Open FFXIV Open Paisley Park (Version 1.2.1) Accept the update (to Version 1.3.0) An error will appear from ffxiv_dx11.exe and the client -may- crash. Screenshot of error is below along with error.log and output.log: error error.log output.log

EDIT: Did a fresh install, previous markers work but still not able to input new presets.

LeonBlade commented 5 years ago

Thanks for the report. I don't really have issues when I update, but I'll rethink the update process to prevent this from happening.

Leisterredux commented 5 years ago

Update:

Crashes only happen only when trying to use any of the presets.

Upon further testing, crashes do not happen when using the presets only in a certain maps and areas, including some dungeons and trials instances.

However attempting to teleport out of those safe areas after using presets will result in same crash.

Character deaths (screen blacked out) will not cause crash.

This is with the latest version 1.3.1

LeonBlade commented 5 years ago

This is a very strange error. This has never been a situation at all until this most recent patch. It will take me some time to investigate.

Leisterredux commented 5 years ago

Take your time, I'll also try to do more testings. For now it works as intended inside the instances which is great. I was doing ucob tonight and the game only crashed after we finished the lockout and need to exit the instance, which is a small setback. I suspect it's either due to my PC ( which is unlikely since I have everything up to date) or the new patch.

Trav877 commented 5 years ago

Want to say that i'm having the same issue as leister, and it only ever occurs when i leave UCoB but i haven't been using it anywhere else. it happened with 1.3 and 1.31 using presets that i made myself.

skyalteria commented 5 years ago

Also having same issue in both Ultima Weapon and UCOB. Have not tried other instances.

celphos commented 5 years ago

I had the same issues after I left doing o12s (no crashes during raid, just as soon as I left.) Here's the 2 logs, hopefully they'll help.

output.log error.log

EDIT: the error log seems to be something unrelated to the problem and happened a couple days ago when I was testing it.

LeonBlade commented 5 years ago

Thank you for your report. This is confirmed for being an issue for all users (myself included). I'll try to find some time here soon to fix the issue. I have put it off longer due to the program still functioning otherwise.

healrsadjust commented 5 years ago

I too crash and get same error when leaveing UCoB

MrSigy commented 5 years ago

Same issue no crash inside but upon exiting the area. Also Nancy Host keeps outputting this error

2019-04-28 23:33:43.7526 Could not start Nancy host. System.Net.HttpListenerException (0x80004005): De parameter is onjuist bij System.Net.HttpListener.AddAllPrefixes() bij System.Net.HttpListener.Start() bij Nancy.Hosting.Self.NancyHost.TryStartListener() bij Nancy.Hosting.Self.NancyHost.StartListener() bij Nancy.Hosting.Self.NancyHost.Start() bij PaisleyPark.ViewModels.MainWindowViewModel.OnStartServer() 2019-04-30 07:05:23.1525 Could not start Nancy host. System.Net.HttpListenerException (0x80004005): De parameter is onjuist bij System.Net.HttpListener.AddAllPrefixes() bij System.Net.HttpListener.Start() bij Nancy.Hosting.Self.NancyHost.TryStartListener() bij Nancy.Hosting.Self.NancyHost.StartListener() bij Nancy.Hosting.Self.NancyHost.Start() bij PaisleyPark.ViewModels.MainWindowViewModel.OnStartServer()

Icabbles commented 5 years ago

Getting also crashes. Some when leaving a certain area (just tested it inside T13) and in Mist paisleycrash

donneee commented 5 years ago

i'm getting the same type of errors. Can't wait for you to fix this and figure out how to implement json commands with this in Trig for memes

this was my test in goblet to a crash. http://bit.ly/2ZOrI6Z

keep up the work my dude!

Akava2005 commented 5 years ago

I'm getting this error as well. It only happens when trying to leave an instance after using way markers.

Steps to Reproduce:

  1. Enter an instance (UwU or The Minstrel's Ballad: Ultima's Bane)
  2. Open Paisley Park v1.3.1
  3. Select a preset and load it (Mine uses all Markers)
  4. Remove the markers
  5. Place all markers (manually or with a different preset)
  6. Attempt to exit the instance

FFXIV Error

celphos commented 5 years ago

So I did a little more messing around to see if I can create the crash in different ways, It still works amazing in duties, however I tested it in Shirogane to see if it would crash if I created a Profile there.

If I create a profile in Shirogane and attempt to load it, it immediately crashes. Here's the profile I used and also the error logs / output. House Shiro Outside.txt output.log

I also did a test with the program inside the house and it doesn't crash if I make a profile in there. Inside Shiro Mansion.txt

In fact, every profile I had that normally crashes if I'm outside in Shirogane and attempt to load it did not crash while I was in the home. I'm guessing the waymarks don't appear cause it's on a different map or too far out.

I'm not sure if it ever worked in housing areas in previous patches but hopefully this helps solve the mystery a little.

LeonBlade commented 5 years ago

Thank you @celphos for your testing. Unfortunately, the logs don't help because of the nature of the crash. If I could get information from the game it would be better, but the most we can get is a stack trace.

It's very interesting that inside a house it doesn't crash if that's what you're saying? When you load waymarks in the house and leave it doesn't crash? Unfortunately, I don't have time to look into this more at the moment.

It will take a long time to figure out what's wrong. I'm sorry for the long wait to fix this error, but it's a lot more obscure than you might think.

celphos commented 5 years ago

Sorry I mean that I can load any waymark setting inside the house and it wont crash, if I leave the house after doing so, I will crash. I even made a waymark setting with the outside areas that crash immediately and load those same waymarks inside the house and they wont crash.

I'm basically just alt gearing up omega and stuff with nothing else to do so I'll keep looking around in areas to see what crashes and what doesn't if that helps?

There's no need to apologize for the delays, as Leis said, take your time.

LeonBlade commented 5 years ago

It doesn't really matter what you load in, it matters if you crash or not when you transfer areas.

On Sun, May 5, 2019 at 12:25 AM celphos notifications@github.com wrote:

Sorry I mean that I can load any waymark setting inside the house and it wont crash, if I leave the house I will crash. I even made a waymark setting with the outside areas that crash and load them inside the house and they wont crash.

I'm not sure on how I can get in game information for you but if it's something I can do, feel free to msg me on Discord at Celphos#5498

I'm basically just alt gearing up omega and stuff with nothing else to do so I'll keep looking around in areas to see what crashes and what doesn't if that helps?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/LeonBlade/PaisleyPark/issues/3#issuecomment-489388779, or mute the thread https://github.com/notifications/unsubscribe-auth/AAE3BJQM7OVAHP5THO6QNBDPTZOTFANCNFSM4HH7QDYQ .

Kurtty5878 commented 5 years ago

I am having the same issue as celphos stated. Anytime I teleport or enter any housing ward it crashes. Tried it in Ul'dah and it worked fine, teleported to my house and it crashed as soon as the load screen started,

LeonBlade commented 5 years ago

@Kurtty5878 Thanks! I just confirmed this today myself and thought it was a new issue. I'm currently looking into a new method of placing waymarks to avoid this issue.

Thank you everyone for submitting your experiences with this issue.

Surged28 commented 5 years ago

I have the issue as well but the odd part is I still crash even if I close the program before leaving the duty.

Jyntax commented 5 years ago

I have the issue as well but the odd part is I still crash even if I close the program before leaving the duty.

That's because the Injection of Data is still in the game. It's not the programm that crashed the game but the injected Code which the game can't handle for some reason. Correct me if I'm wrong.

LeonBlade commented 5 years ago

I have the issue as well but the odd part is I still crash even if I close the program before leaving the duty.

That's because the Injection of Data is still in the game. It's not the programm that crashed the game but the injected Code which the game can't handle for some reason. Correct me if I'm wrong.

The game will crash regardless of if you close it or not. Once you place a waymark with Paisley Park, no matter what you do, it will crash the game when you leave the zone.

Kurtty5878 commented 5 years ago

I get this error when trying to update.

2019-05-15 (2)

Jyntax commented 5 years ago

Since the Update to 1.3.3 it doesn't crash on teleportation/leaven the area anymore. It crashes like 2-3 seconds after I press load to load a preset.

LeonBlade commented 5 years ago

Does anything pop up? @Jyntax

@Kurtty5878 That sounds unrelated to this issue. Try downloading a new release. Make sure you're running in admin mode as well. You can upload your error log as well.

Kurtty5878 commented 5 years ago

It's the most recent release. 1.3.1 works but when I go to update it it gives me that error. It runs in admin by default. The files are all located in the same folder.

LeonBlade commented 5 years ago

It's the most recent release. 1.3.1 works but when I go to update it it gives me that error. It runs in admin by default. The files are all located in the same folder.

Your antivirus could be triggering it. Just download the new release manually here: https://github.com/LeonBlade/PaisleyPark/releases/download/v1.3.3/PaisleyPark.zip

Kurtty5878 commented 5 years ago

Looks like it was the antivirus. Idk how this stuff works, but why did a previous version work fine and this one had issue?

LeonBlade commented 5 years ago

Looks like it was the antivirus. Idk how this stuff works, but why did a previous version work fine and this one had issue?

Not sure. I'm glad it works for you though!

LeonBlade commented 5 years ago

Thank you everyone for submitting feedback on this bug. It's now fixed in 1.3.4!