Guild Wars 2

This applies mainly to cutscenes that have come out for content since the second season of the personal story.

Basically when I try to watch a cutscene, all I get is a black screen for video. Voices work fine, and I get the subtitles, but absolutely zero visuals.

What do I do to fix this?

Yes you can do the achievements at any time. So far none of the new skins have been tied to achievements but you can also get them at any time.

I didn’t do any of the Episode 1 achievements when it was first up. Partially because I was too busy, partially because I just felt like doing other things and knew I had that option. Then earlier this week I decided to try it out and went back to them.

Ys, pretty much so far, all that has been released on s2 (Except gem store itens) are being able to get at any time on future. No spec skins are got by doing the episode, the new skins added are get by playing content into the new permanent map.

And yes, with the journal, you can get any achievment at any time, once you unlock and complete that episode. And even if u don’t get able to log to unlock the episode, u can still buy it with gems later.

PS: Only out of curiosity for those that don’t know, u can get ls s1 rewards trough laurel vendor by 15Gold and 25 laurels.

Just opened at Kodash

Hi,

One week ago, Anet released a new API: https://forum-en.gw2archive.eu/forum/community/api/API-Documentation.

With this we can easily check if a specific event has been validated, in every servers.

This link: https://api.guildwars2.com/v1/events.json?event_id=57A8E394-092D-4877-90A5-C238E882C320 is the state of the event “Stop the Risen Priest of Grenth from retaking the Cathedral of Silence”.
If the event state become “Success”, just check on what server with this link: https://api.guildwars2.com/v1/world_names.json using “world_id”.

I had this problem on my last computer and discovered that it was a bad stick of RAM. This is actually very easy to check – download a program called memtest and run it overnight and see if it is still running and reporting no errors in the morning. If it does error and you have more than one stick, repeat the test with each stick to identify which one it is and replace it.

Of course, a computer can crash like that for a lot of reasons hardware related – I mention this one because it’s an easy test to at least eliminate your memory as the culprit.

Jigain try resetting your overclocks to stock and see how that goes. I know it sucks but GW2 seems to be finicky with OC’s.
The Thief scenario could be related to the zone or area your toon is in. I find some areas are higher demanding than others.
Do you have MSI afterburner installed? Do you use HWinfo for cpu temps?
Hard shutdowns are generally associated to the PSU. Did you run Memtest to see if you had a bad stick?

EtonMessy – it would turn completely off. As in black screen, black keyboard (I have one that lights up the keys) mouse light off, PC light off, fans off. No power being drawn from the outlet.

Ashley Segovia – The newest piece of hardware I put in was my ram 6 months ago when I bought the PC. No error message, kernel dump only had a critical error about not enough power (at full tilt, my computer uses about 75% of my power supply.)

Note – I got the issue solved last night with help from a friend who is suffering from a similar but far worse scenario (Ashley, he’s got 8-30 FPS in low population areas of 3-10 people. And shut downs, his talks with anet support have yielded nothing.)

Jigain, here’s how I solved my issue. It turns out that while my BIOS is listed as compatible with CPU, it in fact wasn’t. I ended up updating to the F7 version (oldest known stable confirmed by multiple sources rather than just manufacturer).

Since then my comp has been running fine. What was the issue? My 6 cors ran as following at moderate useage.

Core 0 + 1 – 1507.2 MHz
Core 2 + 3 + 4 + 5 – 3.552.8mhz

All temps at 26C

Multiplier Core 0 + 1 – 1.5
Multiplier Core 2 + 3 + 4 +5 – 17.0

Core 0 and 1 were not responding and were calling for more and more power, without actually running. It was a fake kernel power supply issue.

Just for kittens and grins, check your BIOS version against known stables.