Jump to content

EvanDaDude

Members
  • Content Count

    12
  • Joined

  • Last visited

  • Feedback

    N/A

Community Reputation

2 Gathering Thatch

About EvanDaDude

  • Rank
    Naked

Personal Information

  • ARK Platforms Owned
    PC
    Xbox

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. UPDATE: I'm hosting via Nitrado. I went into the settings and searched "Flyer" and there was an option stating "Allow Genesis flyers" and I checked the box and restarted the server. I'm on Ragnarok and now it works fine. Everyone is flying again until WC never fixes this bug.
  2. Me August 27 2015: I'll just wait for them to fix [insert item]. Me today: You today: "Just wait for the next update, they will be fix it"
  3. I have not confirmed that the crossbow damage bug is still active on Win 10 PC as of this morning. But the server I have was also affected. Currently I can't mount any flyer so I'm on the hunt through the forums for that. But yes, that primitive damage bug seemed to have hit more than just me, I see.
  4. Oh man... Well here's the good news (I think), Since Xbox players cannot modify game files, the masses that are affected may draw enough attention to WC to fix this sooner than letting PC Windows 10 Players take a hike and deal with it on their own. As far as I experience its when you hold the B-Wheel it automatically whistle follows and that's it right?
  5. If your server is missing, it may take up to several HOURS for it to update with the 70GB release and then go back online. I suggest just be patient in the meantime. If you haven't updated your version to the latest drop, (if it doesn't do it automatically...) Update your installation of the game so that when the server does come up, you can jump in and take care of any babies needing food or what not. Just sit tight. Now if it's missing for a day or two... Good luck I have no answer. Mine was down for a few hours and my version released its update after, so it took about 8 hours to get back into my own server.
  6. Are you guys playing on PC with a console controller, By chance? I'm currently messing with files to find a work around.
  7. That's the fix right there. May I add that I had to delete the map data for it to work for me. I ran around after a restart and my survivor was still whistling. When I deleted the game data and then went back in, it then stopped whistling. I'm not sure what cost that will bring to other survivors and their maps, but at least I know that this solution actually does work. So thanks for putting up that redundant information.
  8. I even followed this advice right here and my survivor still sounds like a cattle herder.
  9. What's going on for me, Since it didn't work, the line that Cedric tells us to modify was not there where he said it would be. So if it worked for you, please enlighten the rest of us. We may not be as sharp as a lot of other people who often go in and view/modify game data on the reg. As you can see, I don't see a line resembling anything he said should exist there. So if I copy and paste that line of code (or whatever it's called) into the bottom and just save it and rerun the program, it still doesn't do anything for me.
  10. Guys... Im having a hard time understanding studio wildcard... I came back from a long Ark break. I have 120 days worth of game time in it and played on launch... How the hell does this whistle problem still exist after it was discovered. How has no one at Wildcard posted in here a solution that doesnt involve me putting in code or settings change. I just need this game to work like it should? How is this not a criminal offense? We remember Fallout 76... What the hell is going on and how does Studio Wildcard still have somewhat of a clean nose after this and clipping under the map and flying doggy dragons with ice breath and how the hell are they still in business?
×
×
  • Create New...