In 2013, a crack commando unit was sent to prison by a military court for a crime they didn't commit. These men promptly escaped from a maximum-security stockade to the Beamdog underground. Today, still wanted by the government, they survive as soldiers of fortune. If you have a problem...if no one else can help...and if you can find them...maybe you can hire...The QA-Team.
Tried uninstalling and re-installing in another location (different drive even), still not much luck. Here be the windows crash log thingie if it's any use:
Description: Stopped working
Problem signature: Problem Event Name: CLR20r3 Problem Signature 01: bgee.exe Problem Signature 02: 0.1.12.0 Problem Signature 03: 50b5c0fb Problem Signature 04: mscorlib Problem Signature 05: 4.0.0.0 Problem Signature 06: 50483a22 Problem Signature 07: 2602 Problem Signature 08: 9c Problem Signature 09: System.Windows.Markup.XamlParse OS Version: 6.0.6002.2.2.0.256.1 Locale ID: 1044
Suppose I could try an install on the laptop too, see if that works out.
seriously, release the patch already... holding it back for longer keeps everyone who bought the game on steam from participating in hunting down the few remaining bugs and experiencing the grafical changes. it just would not make any sense, as nobody said that releasing the patch to public would mean beamdog stopped working on improving the game...
seriously, release the patch already... holding it back for longer keeps everyone who bought the game on steam from participating in hunting down the few remaining bugs and experiencing the grafical changes. it just would not make any sense, as nobody said that releasing the patch to public would mean beamdog stopped working on improving the game...
Hey, I have the Steam version too, and not only want, but NEED this patch (curse you Intel!!!) but that's no reason to be rude. The dev team aren't your personal coding slaves, you know.
I'm not in the beta (although I emailed Dee a few hours ago so may be soon), but I'd say that they best course of action here is to go open with the beta for everyone that bought through beamdog. This enables those that can't play the game at all currently to play, everyone can enjoy the updated gui and various fixes if they wish to, and the patch can be completed more, well, completely with more people testing.
In other words, as @Adul said: "Why not just make the beta entirely public, and let everyone with a Beamdog BG:EE access download it? Then people who are eager to would have access to the patched game, and I think everyone would still understand there are still unresolved issues with this version."
Tried uninstalling and re-installing in another location (different drive even), still not much luck. Here be the windows crash log thingie if it's any use:
Description: Stopped working
Problem signature: Problem Event Name: CLR20r3 Problem Signature 01: bgee.exe Problem Signature 02: 0.1.12.0 Problem Signature 03: 50b5c0fb Problem Signature 04: mscorlib Problem Signature 05: 4.0.0.0 Problem Signature 06: 50483a22 Problem Signature 07: 2602 Problem Signature 08: 9c Problem Signature 09: System.Windows.Markup.XamlParse OS Version: 6.0.6002.2.2.0.256.1 Locale ID: 1044
Suppose I could try an install on the laptop too, see if that works out.
XML parser error. Can you rebuild your settings file by restoring everything to default (try deleting it)?
If that not helps, try reinstalling .NET Framework. CLR20r3 defines an internal malfunction exception inside the Framework, not BG:EE itself.
I didn't read all previous posts so forgive me if I'm not bring anything new to this discussion but at least I will clarify my vote for extending the beta and not releasing the patch yet.
On the hardware side, it seems most people are now playing the game without major problem. One of my computer demonstrates a strange behaviour with the game thinking it's not powerfull enough to play movies in HD, while in fact the game can play the HD movies properly if I force it to use them. I believe it would be best if such behaviour could be avoided (there were already several complaints until it was solved for most people), possibly through adding an optional choice for the player to choose the resolution they want for the videos if the reason for this behaviour is also unknown on your side.Fixed on my side with the late yesterday update. May still be valid for others though.
Regarding other issues such as the journal window behaviour, since it has been a long time complaint, I think polishing it before releasing the patch would avoid further comments such as "after one year it's still not fixed".
In my opinon, extending the beta and opening it to more people but not to everyone seems more reasonnable in order for the support team to avoid being overburden with many similar feedbacks. I have the feeling that the small group of people chosen for phase II behaved more or less as a QA team and the tone looked quite different from other parts of the forum. I'm not sure this would remain the same with a full open beta.
We're pushing an update now, which should be ready for installation sometime in the next hour or so. You can read about the changes here: http://forum.baldursgate.com/discussion/21975/
Beam dog client crashes a lot, (seems related to me using other flash programs, Youtube, farmvill ect) All those magic darts in high hedge are two strong, suggest reducing there elemental damage from 1d6 to 1d4. the bullets should be ok since you only get 2 attacks per round with slings not 4 like darts. Change one of Rasaad's starting proficiency's back to darts, or any other ranged weapon.
I haven't gotten to play with the beta much yet, and it hasn't crashed for me, but I would say to fix all reported crashes before opening it up. I mean, if that isn't obvious.
(if there's a vote on this post, it's because I voted later)
I haven't gotten to play with the beta much yet, and it hasn't crashed for me, but I would say to fix all reported crashes before opening it up. I mean, if that isn't obvious.
(if there's a vote on this post, it's because I voted later)
While that sounds great, if a game had to be totally bug and crash free before it could be launched, video games wouldn't exist. I see no way opening the beta to more people could be detrimental to development.
Beam dog client crashes a lot, (seems related to me using other flash programs, Youtube, farmvill ect) All those magic darts in high hedge are two strong, suggest reducing there elemental damage from 1d6 to 1d4. the bullets should be ok since you only get 2 attacks per round with slings not 4 like darts. Change one of Rasaad's starting proficiency's back to darts, or any other ranged weapon.
Cool there are elemental damage darts in High Hedge. Never even knew
We're pushing an update now, which should be ready for installation sometime in the next hour or so. You can read about the changes here: http://forum.baldursgate.com/discussion/21975/
And while we were all here arguing, the devs went and fixed nearly all the reported bugs. Good job guys.
My initial reaction to phase 3: overall a big UI improvement though some components have some odd spacing/positioning. I have not noted any of the bugs yet that I see in the current release. So far the default combat AI scripts for party NPCs appear to be working correctly.
I dislike that the spacebar does not appear to advance through 'pause' prompts during interractions and that the Enter key must be used, but that is just a personal thing. Not specific to the beta, just something in the client I noticed recently.
Some of the dialogue text in the now clear pop up window can be hard to read depending on the background. When there is a big wall of text, this can be pretty arduous actually. It forces you to do a lot of background cognitive context switching (think resource contention for human focus) when trying to parse the text against the background. The text and the background vie/fight for your attention.
I like the clear text pop up but I think that due to the rich backdrop in this game, it is a bit too busy and I already can see that I get fatigued from it and may well get a headache after prolonged play.
It is my opinion that text on black is far superior when it comes to generating less read fatigue when in text heavy sequences.
A much greater (than what is currently in place now) fade to dark effect through the pop up window might help.
A lot of MMOs fade the background out to some degree when they use a chat box interfaces and it does seem to help the mind and the eyes to focus on the text instead of fighting to parse text out from a background.
I note there IS such an effect now but it is not nearly enough to overcome the wonderfully rich watercolor backgrounds you have to contend with in this game.
An alternative or additional adjustment to this would be to use a simpler but easier for the human eye to pick out font.
My personal preference would be to use a less busy font on a black background but not everyone would like that. I am just thinking ahead/behind to sessions where I would potentially spend/have spent several hours looking at the game text while playing the game -- and I don't think that I could do a whole lot of that with the current presentation.
Agreed, the dialog box should be a little more opaque.
You see, that's a thing I didn't even think about, but true... A more opaque dialog box would be better! Nice Eiler!
On my part, on part III, everything except the journal glitches (it doesn't crash anymore, good thing!) seems to be good! I do not use any kit for my characters so I will leave such review to those who do (and who reported such bugs). For the few hours I played till now, nothing bugged, nothing lagged, nothing crashed... I say, as usual, progress is being made!
And for a personal request, if I may... I know that it has been talked about before, but it would be a very nice addon! If it'd be possible to make an icon "difference" for scrolls between known spells and unknown spells (character specific)... And that, even if shops would be cool... My problem is that I don't seems to remember (after so MANY BG and BGEE games) the spells I learned in the game I'm currently playing... Like, just adding a little "U" at the upper right part or whatever to tell you that this is an unknown spell... Or to make it a different color... Red = you cannot use, blue is for identifying usually... So, light green or light yellow? Would be nice anyway!
I haven't gotten to play with the beta much yet, and it hasn't crashed for me, but I would say to fix all reported crashes before opening it up. I mean, if that isn't obvious.
(if there's a vote on this post, it's because I voted later)
While that sounds great, if a game had to be totally bug and crash free before it could be launched, video games wouldn't exist. I see no way opening the beta to more people could be detrimental to development.
I didn't say bug-free, or even crash-free. Some crashes (a lot of them) have something to do with the user's computer that the user can fix -- drivers, antivirus software, etc. But if something in the game causes it to crash, that is really not acceptable. QA might be getting cut a lot in the industry lately, but a crash bug, especially if one is introduced in a patch, is something I hope gamers never come to tolerate.
That said, I'm not up to speed on the state of any crash bugs in this beta, and it may be a moot point.
Comments
I can't find the 'ouch' button...
Stopped working
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: bgee.exe
Problem Signature 02: 0.1.12.0
Problem Signature 03: 50b5c0fb
Problem Signature 04: mscorlib
Problem Signature 05: 4.0.0.0
Problem Signature 06: 50483a22
Problem Signature 07: 2602
Problem Signature 08: 9c
Problem Signature 09: System.Windows.Markup.XamlParse
OS Version: 6.0.6002.2.2.0.256.1
Locale ID: 1044
Suppose I could try an install on the laptop too, see if that works out.
In other words, as @Adul said:
"Why not just make the beta entirely public, and let everyone with a Beamdog BG:EE access download it? Then people who are eager to would have access to the patched game, and I think everyone would still understand there are still unresolved issues with this version."
If that not helps, try reinstalling .NET Framework. CLR20r3 defines an internal malfunction exception inside the Framework, not BG:EE itself.
On the hardware side, it seems most people are now playing the game without major problem. One of my computer demonstrates a strange behaviour with the game thinking it's not powerfull enough to play movies in HD, while in fact the game can play the HD movies properly if I force it to use them. I believe it would be best if such behaviour could be avoided (there were already several complaints until it was solved for most people), possibly through adding an optional choice for the player to choose the resolution they want for the videos if the reason for this behaviour is also unknown on your side.Fixed on my side with the late yesterday update. May still be valid for others though.
Regarding other issues such as the journal window behaviour, since it has been a long time complaint, I think polishing it before releasing the patch would avoid further comments such as "after one year it's still not fixed".
In my opinon, extending the beta and opening it to more people but not to everyone seems more reasonnable in order for the support team to avoid being overburden with many similar feedbacks. I have the feeling that the small group of people chosen for phase II behaved more or less as a QA team and the tone looked quite different from other parts of the forum. I'm not sure this would remain the same with a full open beta.
(if there's a vote on this post, it's because I voted later)
That is actually very good news for Safana.
I like the clear text pop up but I think that due to the rich backdrop in this game, it is a bit too busy and I already can see that I get fatigued from it and may well get a headache after prolonged play.
It is my opinion that text on black is far superior when it comes to generating less read fatigue when in text heavy sequences.
A much greater (than what is currently in place now) fade to dark effect through the pop up window might help.
A lot of MMOs fade the background out to some degree when they use a chat box interfaces and it does seem to help the mind and the eyes to focus on the text instead of fighting to parse text out from a background.
I note there IS such an effect now but it is not nearly enough to overcome the wonderfully rich watercolor backgrounds you have to contend with in this game.
An alternative or additional adjustment to this would be to use a simpler but easier for the human eye to pick out font.
My personal preference would be to use a less busy font on a black background but not everyone would like that. I am just thinking ahead/behind to sessions where I would potentially spend/have spent several hours looking at the game text while playing the game -- and I don't think that I could do a whole lot of that with the current presentation.
On my part, on part III, everything except the journal glitches (it doesn't crash anymore, good thing!) seems to be good! I do not use any kit for my characters so I will leave such review to those who do (and who reported such bugs). For the few hours I played till now, nothing bugged, nothing lagged, nothing crashed... I say, as usual, progress is being made!
And for a personal request, if I may... I know that it has been talked about before, but it would be a very nice addon! If it'd be possible to make an icon "difference" for scrolls between known spells and unknown spells (character specific)... And that, even if shops would be cool... My problem is that I don't seems to remember (after so MANY BG and BGEE games) the spells I learned in the game I'm currently playing... Like, just adding a little "U" at the upper right part or whatever to tell you that this is an unknown spell... Or to make it a different color... Red = you cannot use, blue is for identifying usually... So, light green or light yellow? Would be nice anyway!
If we're talking about the official patch release, I feel the remaining UI issues need to be tackled before a release.
That said, I'm not up to speed on the state of any crash bugs in this beta, and it may be a moot point.