Lord Reliant

Love this post. Good to point out obvious issues to noobs in an entertaining way.

So, does the lack of movement only apply to your sovereign after you cast the spell of making or does it affect all units?

I wonder when Win 8 will be supported? If FE is released in the Fall, when Win 8 is targeted to come out, SD will need to work on making it compatible. Thankfully that's still 6+ months away.

[quote who="Bellack" reply="38" id="3111618"]There is improvement in the art style from E:WOM to E:FE but not so much that it has an entierly different look. And unless you sit down and play awhile you won't expereance just how much more improved E:FE graphic are over E:WOM.[/quote] That's my point. The graphics have improved (and I like the style), but it's just not so radically different that a person that played (and likely hated) WoM would look at FE and think "This is

[quote who="Alfdaur" reply="12" id="3110534"]What where the major introductions in Beta 1 & 2?[/quote] Off-hand, I'd say the major improvements in Beta 1 and 2 were: a GUI display of path-finding, balancing, stability improvements, performance improvements (lower memory, better graphics responsiveness), new art assets, removal of caravans and imbuing champions as game mechanics, tactical combat improvements, drastic AI improvements, revised sovereign selection screen, addition

I think the hardest part in selling it to the media will be overcoming the negative inertia from WoM. If the reviewer sites (or in this case, previewer) can keep an open mind about FE as a new game, I think it will do well. It will be really important to highlight all of the various, significant improvements in FE, because on first glance, I don't know that someone who hasn't played WoM for a while would visually see much difference between the two. That's not to say graphics in F

According to Steam's stats: http://store.steampowered.com/hwsurvey Less than 15% still run XP. Slightly over 50% run Windows 7. 5% run OS X. Microsoft will drop support for XP on August 2014, about 2.5 years away. That's still a while to need to support the XP user base.

[quote who="Frogboy" reply="6" id="3109706"]Next week. But after that a long wait for beta 3.[/quote] More than fair enough. It'd be sweet to see how the existing system with some tweaks and more content functions. There's certainly a need for more polish and UI improvements, but I bet the testing/feedback/changes already will make the game another great step more fun. Great to hear about next week. W00t!

Here's to hoping for next week!

[quote who="Trojasmic" reply="25" id="3109294"]All good ideas... There is a ton of work that needs to be done on the UI and SD hasn't acknowledged that fact or any of our posts about it. I'm hoping they're just focused on game mechanics now and plan on an entire beta cycle (Beta 4 or Beta 5) where they will listen to all of our polish requests.[/quote] I just hope the UI polish and improvements don't get shuffled to the end and then they run out of time to work o

I am a bit concerned that Champions will still seem unique and powerful. Guess we'll see how things are looking when we get the next beta release. When is that set to be released again? (hint, hint)

[quote who="DarkGaldred" reply="33" id="3109067"]I think a better fix would be to decrease an unit accuracy if it has moved before, that would solve the kiting problem too (archers running back and shooting to get 1 more shot before melee). [/quote] This.

[quote who="Magog_AoW" reply="20" id="3108609"]Error Summary HTTP Error 404.0 - Not Found The resource you are looking for has been removed, had its name changed, or is temporarily unavailable. [/quote] Same error here. Bummer- wanted to see this video!

I really like the concept of both units, but since they tend to get one-shotted, they're nothing more than an HP drain bag until they die. If they had more special abilities and/or scaled up in levels, their usefulness would be more justified.

Here's to hoping Beta-2b will have some enhancements on the blahness. I know they're adding more content in, which should make things much more interesting and fun.

How much RAM? Specs are certainly reasonable.

+1. While some things could be a "choose now or forever lose your choice" option, I don't think ALL quests need to be that way.

Are you running XP, too, Infinityman? What are your system specs? I haven't experienced the issue you mention, but most of my games haven't been very far into each one.

Also, try playing above Normal AI level. In another thread, users who upped the difficulty level had much fewer crashes. Probably some AI thread locking problem.

Just right-click the task bar, choose Start Task Manager, and then click on the Performance tab. If you want even more details, you can click on the button for Resource Monitor right there and choose the Memory tab. Pretty handy!

I've noticed that, too. If it weren't for the targeting problems, it wouldn't be such a bit deal. If they can just fix that, stepping outside the box wouldn't matter.

It very well could be a locking thread issue based around AI difficulty. Since the AI plays differently and AI threads have caused crashes before, I wouldn't be surprised if that was a cause. It would be strange of the correlation was: Lower AI difficulty = More crashes Something else you could check regarding the crashes would be memory usage. Alt + Tab out of the game as you play and see how memory consumption is doing. You're on 64-bit, so I would hope over 2 gigs i

Older computers and netbooks would be an example of single-core computers still.

[quote who="Frogboy" reply="24" id="3105297"]You don't "need" multiple cores. But we don't technically support single core. Dual core is the minimum spec.[/quote] I just checked the System requirements for FE here: https://store.stardock.com/product/ESD-SDE-W017 If dual-core is the minimum spec, you probably should change it to say that. Even if users could run the game on a single-core compute

Maybe the pathfinding AI is smarter than we think it is- it realizes when we aren't sending it to the "right" place and simply refuses to go instead? ;) I hope the work with pathfinding they're doing will resolve some of the auto-move issues.