Jump to content
  • Sign Up

slayerking.3581

Members
  • Posts

    79
  • Joined

  • Last visited

Everything posted by slayerking.3581

  1. I got it to work by running the game with the -windowed option., When it starts up just press the maximise window button and it seems to run fine then. This is in Arch linux running through steam. I also noticed it was accessing my optical drive when starting up for some reason.
  2. Same for me, Game starts but there is no game screen just music and the crash report. Arch linux using proton to load GW2
  3. Actually they do as it's all automated! I got mine 72Hours on the dot which is unusual as every other pre order I got them in an hour at most.
  4. Yeah I know how it works but it's now Monday night here and I paid for it Friday afternoon. The op isn't the only one not getting them from Friday
  5. Same, I just can't play now it crashes all the time. Crash restart and crash again within a minute or can play for 10-15 then down it goes again.
  6. Nice work but I gave up on this one as the sound would go waaaay out of sync. If I opened the trading post it would do it without fail and longer the TP was open the longer the audio delay got. I used the install a non steam app in steam and it works perfect now.
  7. Thanks for this GW2 runs fine again now thanks to this. For some reason it started getting 3 or 4 fps in groups a couple of weeks ago, But not with this.
  8. Disagree all you want. If you bought the game "Today" how were you supposed to be online to get it for free? I stupidly bought a copy of the game for my son so he could play with me($120 AUD). Fact is unless I played the stock standard game he couldn't play with me and absolutely NO WAY was I going to fork out more money when I just paid for a full game and expansion. Needless to say he stopped playing after he realised he couldn't play where I was.If you buy the game TODAY you should get all content available and from then on of course the normal log in to get it free.They make a huge profit on skins and crap not to mention all those gems on the trading post, someone paid for those or they wouldn't be there.
  9. Literally in the game for 2 minutes last night, Fly the skyscale down to a zealot in vabbi take one swing and boom 7 second lag spike, We all just left.
  10. Still it happened when they moved to the amazon servers. I remember playing fine before it then when they moved it turned to crap. Lately though has just been ridiculous constant "can't connect to the login server" while running around or pretty much doing anything and the roll back issue a month or so ago. I only log in now to get the dailies as doing anything else is just a pain because of the constant lag. It's not just one or two people either it's a whole map.
  11. Not there to chat, I'm there to play a game!
  12. With who? It's a windows problem on the insider fast/dev ring, They know and are fixing it. Look here in the known issues 5th point. I was going back and forth with support starting on the 19th, I think, when I first noticed it, which seems to be about the time it was happening. It took them a while to acknowledge there was an issue. Are you an insider on the fast ring? As that is the day after it was released and if you are and your version of w10 is 20150 or 20152 then you WILL have the problem. Yeah, fast ring. And I figured that out and told them about it fairly quickly when I had my ticket in (I verified that it was working on my fiancee's computer, disabled firewalls, etc). It was just kind of frustrating it took the majority of the week for them to acknowledge it to me on the ticket. At this point, all I can do is wait for either Windows to fix it or (if they need to) for ArenaNet to update their clients to work with the changes. Nah it's a bug if you go back to 19645 it works perfect, They changed something in the kernel and it's causing a lot of programs to either crash or just not work when starting up. They know what it is they are just taking their sweet time to put the fix out in a new build. No, I get that. I was just saying that it was frustrating that ArenaNet support didn't acknowledge that it was a bug for close to a week in the ticket I had open with them. To be fair how would they know of a windows development bug? They really only have to support the official release and an insider version is not that and certainly not the fast ring, We take that burden on ourselves when we use it. You should check out the insider forums bugs get listed pretty quick The frustration was mostly due to the fact that I was trying to report a bug to them and they ignored it, especially something that could become an issue for them in the future, should it be a breaking change in Windows, or that will be causing trouble for them for people who were running the same person. I provided logs (which were ignored), did a lot of debugging to try and figure it out myself, and validated that it was just an issue on the fast ring, and it basically fell on deaf ears in the support ticket. Any way, like I said, I'm just happy that it's been acknowledged, and that people won't have to go through the same level of frustration that I did, as they can just ask 'Are you running Insider? Known bug, it'll be fixed.'I understand. I reported it via ticket here myself the day 20150 was released just to report it had broken the game launcher and was met with the same sort of replies. But I just said nah I'm making a report I don't need help.
  13. With who? It's a windows problem on the insider fast/dev ring, They know and are fixing it. Look here in the known issues 5th point. I was going back and forth with support starting on the 19th, I think, when I first noticed it, which seems to be about the time it was happening. It took them a while to acknowledge there was an issue. Are you an insider on the fast ring? As that is the day after it was released and if you are and your version of w10 is 20150 or 20152 then you WILL have the problem. Yeah, fast ring. And I figured that out and told them about it fairly quickly when I had my ticket in (I verified that it was working on my fiancee's computer, disabled firewalls, etc). It was just kind of frustrating it took the majority of the week for them to acknowledge it to me on the ticket. At this point, all I can do is wait for either Windows to fix it or (if they need to) for ArenaNet to update their clients to work with the changes. Nah it's a bug if you go back to 19645 it works perfect, They changed something in the kernel and it's causing a lot of programs to either crash or just not work when starting up. They know what it is they are just taking their sweet time to put the fix out in a new build. No, I get that. I was just saying that it was frustrating that ArenaNet support didn't acknowledge that it was a bug for close to a week in the ticket I had open with them.To be fair how would they know of a windows development bug? They really only have to support the official release and an insider version is not that and certainly not the fast ring, We take that burden on ourselves when we use it. You should check out the insider forums bugs get listed pretty quick
  14. With who? It's a windows problem on the insider fast/dev ring, They know and are fixing it. Look here in the known issues 5th point. I was going back and forth with support starting on the 19th, I think, when I first noticed it, which seems to be about the time it was happening. It took them a while to acknowledge there was an issue. Are you an insider on the fast ring? As that is the day after it was released and if you are and your version of w10 is 20150 or 20152 then you WILL have the problem. Yeah, fast ring. And I figured that out and told them about it fairly quickly when I had my ticket in (I verified that it was working on my fiancee's computer, disabled firewalls, etc). It was just kind of frustrating it took the majority of the week for them to acknowledge it to me on the ticket. At this point, all I can do is wait for either Windows to fix it or (if they need to) for ArenaNet to update their clients to work with the changes.Nah it's a bug if you go back to 19645 it works perfect, They changed something in the kernel and it's causing a lot of programs to either crash or just not work when starting up. They know what it is they are just taking their sweet time to put the fix out in a new build.
  15. I had this one round as well. Did plenty of damage but didn't get any sort of participation in it for the whole 3 rounds.
  16. With who? It's a windows problem on the insider fast/dev ring, They know and are fixing it. Look here in the known issues 5th point. I was going back and forth with support starting on the 19th, I think, when I first noticed it, which seems to be about the time it was happening. It took them a while to acknowledge there was an issue.Are you an insider on the fast ring? As that is the day after it was released and if you are and your version of w10 is 20150 or 20152 then you WILL have the problem.
  17. With who? It's a windows problem on the insider fast/dev ring, They know and are fixing it. Look here in the known issues 5th point.
  18. That is older than what is officially out! 19041 is the official release
  19. Are you doing it fast enough? The ones for skyscale need to be done within a time limit if I remember right and even if you don't you still get the mistborn mote.
  20. I have been trying to get Serpents Ire done for months, Literally no one does it. The biggest group we got for it was about 2 weeks ago and that was 4 people. It's the only one I need for the back pack and I'm probably never going to get it unless they make it part of the dailies.
  21. HI,There's a post here about this too. It seems the latest build doesn't like GW for some reason as it does it with the first one too. If you roll back to 19645 it works fine again ;)
  22. It's an insider build, You can't delay builds in it so sounds like you don't have it. Yep 20150 done the same thing for me, It seems Guild wars is the only game affected as both GW1 and 2 both get the error. Rolling back to 19645 fixes it though.
×
×
  • Create New...