Djentleman.1650

:expressionless: Yea, I figured... I play for a month now and wanted to stay in denial for a day or so longer. Thx, mate. Now life really sucks right now already. :wink: I will try your downclocking fix. If anything, I hope my last post at least yields a good, hearty laugh in their front office. :tongue:

Evidently it is not. I was an exclusive nVidia customer since Riva, just after 3DFx, and always went with mid-budget nVidia boards. Computer graphics research, tweaking, overclocking, water-cooling, the whole shabang ever since the release of the original Unreal: In all of these roughly 10 years of nVidia I had ridiculous frame drops as soon as there was fog, mist, translucent smoke or alike... So my current and probably last beast (i7 @ 4GHz) got an AMD/ATI for Elite Dangerous for a change and I have to say that I had the best, constantly pleasant and performance-wise predictable 3D graphics experience ever since Unreal with my first Monster 3D. Two thumbs up for AMD, also regarding CrossFire technology. If anyone has doubts, read a decent tech article comparing SLI and CF. I'm afraid, nVidia has a too aggressive obsolescence planning department ever since the GeForce era, when they were seriously on top of ATI. Back to topic: Software version with regular major crashes MUST not be released (QM's job description -> raises suspicion of cheap software test processes @ ANet) and if accidentally released, fixed with highest priority! Every day that the affected group of customers can not consume the content they purchased is a 100% money back reason and if denied, basis for a law suit. Don't get me wrong: ANet has my sympathies, since my company also has their own graphics engines which are troublesome to say the least. This is the downside of developing your own in-house engine and thus supposedly saving money in licenses as opposed sourcing it out (Unreal, Frostbite, Crytek, Team Carmack or what not). I heard it all before: "We can do it ourselves." - "We did it before." - "We can recycle a lot of code." - my personal favorite -> "There are jobs on the line! " sad but true, but what's the size of your employed engine team without loans or freelancers? 5? Less? But the best one is this -> "The majority of customers will be happy with whatever 20th century software architecture we shove them up/down their body parts as long as there is say... foraging!" Isn't that right, management? :kiss: That was a fist bump to ANet's honorable devs and especially testers. :wink: Sorry for the rudeness. It was certainly not my place. You guys probably do it every day over lunch anyways and kudos to the engine team for what works and has been working so far. Certainly better than what my corp sell for a LOT more money. Still: ArenaNet, please take responsibility and fix crashes like these in between major releases, even if only a small percentage of customers experienced this. The game is too fun and I'd really like to play on and let you keep the money. Don't let poor coding inflammations fester: The chance exponentially increases that their consequences will eventually affect a much bigger, revenue-wise very uncomfortable amount of your (then former) customers. I know the drill, no need for official statements. I'm just so very disappointed in general software development and IT management once more (when I am sitting in the customer's chair.) Please fix it this month. Pretty please. :smirk:

Interesting. I am just now playing Living World Season 3 story mission "A Shadow's Deeds" and my PC always crashes bad (with lots of erratic sound artifacts and black screen) in a non-deterministic manner within 1 min after having the first talk with Caithe. Referring to elTigre.4532's post about Jade Constructs, I recon this actually is a major bug in the graphics engine. I have an ASUS R9 280 and if this is supposed to be an overheating issue as, then it must be due to poor programming on ArenaNet's side. It is absolutely ridiculous that I can play all other story missions so far and all world bosses with hundreds of other players lagging @ around 15 fps, yet in a scene with 2 actors, a bunch of rocks and some shader fx my graphics card suddenly isn't enough anymore and overheats? That is just rubbish. If it should be overheating , there must be a vastly inefficient or way to deep recursive function that is executed low-level on a shader or something like that and came with Living World Season 3. I don't believe in overheating but rather in a non-deterministic bug producing a null pointer that is not caught by some graphics cards / GPUs or their drivers. ArenaNet: You make more than enough money with this game, so I hereby kindly ask you to review your code instead of expecting detailed error reports and fix this. Best regards