Scande.5908

Your comment made me curios so I replayed Descent now with a second chararacter in "windowed fullscreen". No glitches except for Kralkatorrik's heart always being rendered on the platform, where it would later be destroyed.

Weirdly enough I was able to finish the mission now. What I did was play the mission in windowed mode (all earlier attempts were in "windowed fullscreen" or fullscreen), but more importantly though I exchanged my GW2.dat with a backup from a year ago. I assume my GW2.dat at some point got corrupted and it was unable to be repaired by the client. This would also explain why I actually could see the cinematic the first time, when the game crashed loading into the epilogue (which I wrongly assumed to be the loading into the regular map).Again thanks for showing interest in my problems @"VAHNeunzehnsechundsiebzig.3618" , @DxCx.8653 , @"cyanidecapsule.3926" , aswell as everyone else who followed it and offering opinions on potential issues. If I had remembered about my GW2.dat backup I would have tried it earlier and it would have saved myself and especially you quite some headache. But as I mentioned earlier, my Internet just isn't that good to simply download ~50GB of files. Edit: I replayed the mission again with another character in "windowed fullscreen", so I confirm at least for me that my GW2.dat was corrupt and couldn't be repaired.

BIG update. I was able to finish "Descent" and the whole chapter. No crash and no major weirdness besides a couple missing sound clips at the "epilogue". 2 Things could be attributed to it. First of all, I played "Descent" in windowed for the first time; not "windowd fullscreen" or fullscreen. The bigger change was switching my gw2.dat with a one year old backup I remembered about today. My assumption is, that "our" gw2.dat files had a major bug in them, that couldn't or wouldn't be repaired by the client self repair function. Uploading the 50GB file is out of question for me though, it would take days with my internet upload rate.As for the wine setup, I used the non hotfix version. This all was a bit anti climatic now for those that tried to help, but I really appreciated the engagement especially by @"ArmoredVehicle.2849" . I won't retest the mission again with "windowed fullscreen" for now, as I am honestly a bit sick of the mission (especially the second boss that is invulnerable to conditions). That said, I probably will do it within the next few days again and if it crashes again I will post an update about it, otherwise just assume that it didn't matter if the game was windowed or "windowed fullscreen". Thanks again to everyone who followed the bug reports and tried to help.

I installed your hotfix package but sadly it did not work with it either. Same crash.

Similarly for me with /home/user/GuildWars2

I found a .xsession-errors file which isn't empty, it was however last modified in August 2018. As for the driver I simply use the default one that Ubuntu 18.04.02 LTS directly offers under "additional drivers" which is version 390.116. Current help with the debugging is continuing in this thread keeping this topic open in 2 separate threads is counterproductive I think.

I just retried the mission 2 times more with graphics settings changed to "best performance" and now get a crash report instead of just a freeze.Unfortunately I am unable to copy the crash report with Ctrl+C. I did a couple of screenshots, but I don't want to upload/crop each of them unless it would really help.

AS I already mentioned here and in the other thread; my game also freezes before the cutscene.uLimit -Hn = 1048576uLimit -Sn = 1048576 System= [WineD3D setup by @"ArmoredVehicle.2849" version 1.6.2_nvidia](https://en-forum.guildwars2.com/discussion/31192/playing-guild-wars-2-on-linux-performance-optimizations-and-more/p1 "WineD3D setup by @"ArmoredVehicle.2849" version 1.6.2_nvidia")Ubuntu 18.04.2 LTSIntel I5 6500, 3GB KFA2 GeForce GTX 1060 (Driver 390.116), 8 GB DDR4-2133Played mission ~10 times. First time playing crashed onto a blackscreen AFTER the cutscene, afterwards always froze BEFORE the cutscene.

I haven't tested D9VK and I also did not post anything related to that. I mentioned my "old" playonlinux setup, because it was different to what @"ArmoredVehicle.2849" has created and it was quite easy for me to test with that too. This specific "old" setup I have is not from the normal playonlinux script available and has several big problems like crashing in fullscreen and memory leaks.But that is all really not that important to me currently. My real problem is that I can't finish the current LW4 chapter and therefor also can't unlock the new skyscale mount. Furthermore, I did manage to complete LW3 just recently, aswell as do several LW2 missions without issues. It really is only just the current chapter that is causing me troubles and I don't seem to be alone with that, although those people also do play on linux too.

Even the last couple of lines are nothing that shows "weirdness"? The top lines always repeat that's why I didn't copy everything.I did play the mission now around 10 times. I let the game "repair" itself 2 times, tried it with an alt, tried it with the lowest possible graphics settings and even used my "old" playonlinux setup (I moved my .dat for that). The game always froze right after Kralkatorik shouts "mother". What still confuses me greatly is, that I was able to see the full cutscene the very first time, but after that it never got loaded again (and sadly it didn't count the story step as finished either). I really would like to avoid having to download a full new .dat file as my internet speed is quite awful, but I really don't know what else I could try. Any suggestions?

I currently can't finish the story step "Descent" of the new LW4 story. First time it crashed was, after what I think was an end cutscene for the instance, on a blackscreen. 3 More attempts did make the game freeze before loading even the cutscene (no blackscreen that time). These were the last couple of lines from the debug of the 4th attempt. 0086:fixme:d3d:wined3d_debug_callback 0x82cecb0: "Program undefined behavior warning: Sampler object 12 has depth compare enabled. It is being used with depth texture 86, by a program that samples it with a regular sampler. This is undefined beahvior.". 0086:fixme:d3d:wined3d_debug_callback 0x82cecb0: "Program undefined behavior warning: Sampler object 12 has depth compare enabled. It is being used with depth texture 86, by a program that samples it with a regular sampler. This is undefined beahvior.". 0086:fixme:d3d:wined3d_debug_callback 0x82cecb0: "Program undefined behavior warning: Sampler object 12 has depth compare enabled. It is being used with depth texture 86, by a program that samples it with a regular sampler. This is undefined beahvior.". 0086:fixme:d3d:wined3d_debug_callback 0x82cecb0: "Program undefined behavior warning: Sampler object 12 has depth compare enabled. It is being used with depth texture 86, by a program that samples it with a regular sampler. This is undefined beahvior.". 0043:fixme:heap:RtlSetHeapInformation 0x31000000 0 0x265ee80 4 stub 0043:fixme:thread:SetThreadIdealProcessor (0x16f4): stub 0043:fixme:thread:SetThreadIdealProcessor (0x14fc): stub 0043:fixme:thread:SetThreadIdealProcessor (0x182c): stub 010a:fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0x78cfd78): stub My desktop PC runs Ubuntu 18.04 LTS that had been upgraded from 16.04 LTS. It has an i5-6500 CPU, a NVidia GTX1060 3GB and 8GB ram. Because the last line mentions "audio" I want to add that I use a PCI-e soundcard and cheapish 5.1 boxes. I used the "wine_gw2_1.6.2_nvidia" setup.

I too am playing on Linux, so not sure if it's the setup I use or game specific. First time playing the instance I got to see a cut scene, but it ended on a blackscreen and a crash. The next 3 times the game froze before the cutscene was supposed to happen.To play GW2 on Ubuntu I used the installer setup from I too am playing on Linux, so not sure if it's the setup I use or game specific. First time playing the instance I got to see a cut scene, but it ended on a blackscreen and a crash. The next 3 times it crashed before the cutscene was supposed to happen. Before the third redo I did let the client "repair" my game after having skipped that step the first 2 times (It asked me each time). To play GW2 on Ubuntu I used the installer setup from this thread this thread which runs quite well except for an occasional crash before, but never after entering a story instance (e.g. when loading a regular map). More details in this post.

I thought that I may have to add the lines, was just a bit unsure, because the pre-written lines were in such a neat table format. Am I right to think that this is just done by spamming the appropriate amounts of space bar to help readability while programs just ignore the added characters? As for the game, so far it runs better than what I used previously and I haven't encountered the "memory leak" issue that I had with my former setup either. Max and medium shaders settings are a bit wonky in that it causes the grass sprites to move as if there was a constant wind storm, but I haven't encountered any other abnormalities. Load times are good again and I also love the little status window it shows while loading. Many thanks @ArmoredVehicle.2849 ! PS: I sent you a carrion pidgeon ingame.

Sorry for interrupting your discussion but I have several problems with the instruction and how the game runs with the provided tools. First of all. My desktop PC runs Ubuntu 18.04 LTS that had been upgraded from 16.04 LTS. It has an i5-6500 CPU, a NVidia GTX1060 3GB and 8GB ram. Furthermore I ran GW2 for over a year now with a "custom" setup for which I can't remember all the settings.This setup works rather good except for one glaring and annoying problem; memory leak causing heavy stutter after the system decided that the 8GB physical ram is full and starts writing into my virtual ram. This "only" happens when playing for around 2 hours non stop although events with huge player participation does decrease the time limit significantly.My hope was that @"ArmoredVehicle.2849" setup has no memory leak and thus significantly increases the playability of GW2. Now to my problems specifically with the instructions on the first page. The contents of my "limits.conf" are different and I worry about editing the wrong things. Also I already tested playing the game without increasing the limit. Once it crashed while loading into a zone, another time it was a black screen with only some buttons and other player characters visible. This probably had to do with me not having increased the limit yet, what worried me however were load times. It took 3+minutes to load into a zone. Is this going to change with increased limit or is this to be expected with your "Nvidia Package"?