I want to love this game (E:V), I really do, but I'm at a loss. I've done all of the quests gained and cannot find anybody to set me off on something to get the game rolling again. To be clear, I have NO quests available at all. I have been roaming the entire map, Skjern, Skjern Forest, Erling's Farm, Ribe, Marsh, Skerninge -- those (and the campsites) are the only areas unlocked. During this roaming, trying to find a lead, the timeline keeps running out, dumping me to the 'Game Over: you are at the end of your rope' screen. It's infuriating! I understand this game is buggy as hell, but WTF gives? Am I missing something in my noobieness?

In case it matters, attached is a composite of all the quests I've found and finished.

Update: Ok, so it seems I have run into this "Calling of the Sea" not unlocking bug. Quote from a developer on the Steam forums:

"Since releasing version 1.0.1 we've become aware of a handful of major bugs that are causing problems for a lot of players. If you've encountered any of these issues, please accept my sincere apologies - after three rounds of closed beta testing and a month of intense internal QA, we thought we'd fixed all quest bugs. We were clearly wrong.

The most important bug we've learned about is that if you complete the Tomb Raider quest as the final of the Preparations quests and you complete it in such a way as to encounter Oddkell outside the grave, it will not unlock the Calling of the Sea quest when you complete the Tomb Raider quest. This breaks the storyline. Needless to say that is not acceptable, and we fixed it as soon as we learned of it on Friday, but we need to thoroughly test this fix and the other fixes in version 1.0.2 before we can release the patch, so we can be sure we're not breaking anything else in the process."

DAMNIT! Now have to wait for a GOG patch to filter through. Hrrrmph!

Uhh, I am glad to have started a new Eador campaign :)

Now I wait until all the bugs are patched before I start playing.

You could also easily replay the Tomb Raider quest in such a way that you wouldn't have to deal with Oddkell at the end. Personally I just massacred the whole village, and I didn't have any issues afterwards. Although the English part of the campaign is quite a bit buggier than the beginning, so you might want to wait for a patch anyway.

Frankly I'm amazed the devs thought it was acceptable to release the game in such a buggy state. I love both their expeditions game, but they'd better get their act together imo, since a reputation for making really buggy games can be seriously bad for sales.

That would require forethought, in the sense of having saved games at key points -- I don't. Besides, if it gets buggier (jeez!) there's no point -- I'll wait. Clearly they never expected it, and at least they have the integrity to admit their error, unlike some companies (*cough* Bioware, *cough* Beamdog...)
Quote:
"...after three rounds of closed beta testing and a month of intense internal QA, we thought we'd fixed all quest bugs. We were clearly wrong"

And they honestly thought they had it covered. They made a mistake and they owned it. I applaud them for that.

Agreed that the devs have handled this mess with the appropriate combination of deep embarrassment and vigilance.

I'm not surprised that they thought the beta testing would find the bugs though, because frankly I'm surprised the beta testers missed so much!

It'd be interesting to find out how many beta testers they actually had in the end, and how many of them actually took their responsibility seriously (since it was a closed beta).

I could be mistaken but I don't believe that the platform allows you to "go back to KS for more money".
Projects are all or nothing and excluding strech goals there's really no mechanic for scaled funding there, especially funding after the fact. As do I. Having been around tech and games for many years now I've had the chance to see many products (not just games) ship with various unexpected bugs. Even with the massive budgets that AAA games command you still get bugs and issues with basic features that require patching of the shipped build (look to the recent EA-Bioware release of Andromeda for one recent example).

Making best efforts to ship a stable build, being honest when there are bugs, and fixing those bugs in a timely manner, are what makes a studio worthy of customer trust. It's the companies who try to pretend their first build is perfect and act as if they are incapable of any shortcoming that are the real problem.

my two cents