Post/Author/DateTime	Post
#1 aropax Jan 02, 2011 23:54:24	I sent all the details of my issue through to the support centre exactly a week ago. Their response was very quick and I actually felt like the issue might get resolved... Haven't heard from anyone since and I still get a blank screen when wanting to choose powers. If I ask that the CB chooses powers for me, they do appear on the character sheet, but after numerous attempts, cache clearing, cookie deleting and banging my mouse against the desk, its all to no avail.  I have an incident number from the support centre if anyone might be remotely interested. I do understand that it's been over a difficult period and that some people might have been on holiday, but why does all my other sub-based services function as normal over this period? Please resolve the issue or show me some common courtesy and at least nibble on my ear so that I can enjoy some passion whilst being fu**ed.
#2 lokiare Jan 03, 2011 6:42:36	I sent all the details of my issue through to the support centre exactly a week ago. Their response was very quick and I actually felt like the issue might get resolved... Haven't heard from anyone since and I still get a blank screen when wanting to choose powers. If I ask that the CB chooses powers for me, they do appear on the character sheet, but after numerous attempts, cache clearing, cookie deleting and banging my mouse against the desk, its all to no avail.  I have an incident number from the support centre if anyone might be remotely interested. I do understand that it's been over a difficult period and that some people might have been on holiday, but why does all my other sub-based services function as normal over this period? Please resolve the issue or show me some common courtesy and at least nibble on my ear so that I can enjoy some passion whilst being fu**ed.  OMG, +1 before the lock/ORCed...
#3 drnick Jan 03, 2011 14:41:24	I know this is a pain but use American English as your OS language setting and it should work fine. Yes it's a bug.
#4 aropax Jan 03, 2011 15:02:56	Thanks for replying, much appreciated.  I will test in the morning and let you know if it's sorted. EDIT: Im speechless... it now works perfectly. Thank you very much for your assistance.
#5 nightwhisper Jan 04, 2011 1:39:57	What gets me is that this is the third product where they have this very same problem already (original CB had it with the text size on power cards, MB didn't even start unless you changed settings IIRC, and now online CB doesn't let you choose powers). I mean, I'm an understanding guy, but at some point somebody at WotC needs to get a clue and get somebody to use their new programs with the settings changed to a different one to see if it actually works.
#6 lokiare Jan 04, 2011 8:06:24	What gets me is that this is the third product where they have this very same problem already (original CB had it with the text size on power cards, MB didn't even start unless you changed settings IIRC, and now online CB doesn't let you choose powers). I mean, I'm an understanding guy, but at some point somebody at WotC needs to get a clue and get somebody to use their new programs with the settings changed to a different one to see if it actually works. If you read the credits on the OCB you will see there are 5 quality people and a bunch of Beta people. They should all be fired. Then hire the Quality and Beta to an outside source. That way you know they are accessing the program from a different ISP and can actually do real-world load testing and get an outside view on the beta testing...
#7 kenjoon Jan 04, 2011 10:39:59	What gets me is that this is the third product where they have this very same problem already (original CB had it with the text size on power cards, MB didn't even start unless you changed settings IIRC, and now online CB doesn't let you choose powers). I mean, I'm an understanding guy, but at some point somebody at WotC needs to get a clue and get somebody to use their new programs with the settings changed to a different one to see if it actually works. Even more amazing is I've had to fix our companies VB .NET software for this exact issue.  In our case it was really dumb (date formatting) and didn't take more than an hour or two to (track down and) fix.  I recall another issue related to one specific "regional setting", but I don't remember what the exact problem was.
#8 lokiare Jan 04, 2011 12:53:38	What gets me is that this is the third product where they have this very same problem already (original CB had it with the text size on power cards, MB didn't even start unless you changed settings IIRC, and now online CB doesn't let you choose powers). I mean, I'm an understanding guy, but at some point somebody at WotC needs to get a clue and get somebody to use their new programs with the settings changed to a different one to see if it actually works. Even more amazing is I've had to fix our companies VB .NET software for this exact issue.  In our case it was really dumb (date formatting) and didn't take more than an hour or two to (track down and) fix.  I recall another issue related to one specific "regional setting", but I don't remember what the exact problem was. In other words a quick fix?
#9 kenjoon Jan 05, 2011 11:45:15	What gets me is that this is the third product where they have this very same problem already (original CB had it with the text size on power cards, MB didn't even start unless you changed settings IIRC, and now online CB doesn't let you choose powers). I mean, I'm an understanding guy, but at some point somebody at WotC needs to get a clue and get somebody to use their new programs with the settings changed to a different one to see if it actually works. Even more amazing is I've had to fix our companies VB .NET software for this exact issue.  In our case it was really dumb (date formatting) and didn't take more than an hour or two to (track down and) fix.  I recall another issue related to one specific "regional setting", but I don't remember what the exact problem was. In other words a quick fix? The generic problem yes, was a quick fix.  The more specific problem that I don't recall the details I want to say was not easy or quick.  But that's just my best recollection. I do want to point out it was a quick fix because all our date manipulation went through a single function and used the .NET Date/Time picker control so the issue was more of conversion to string where we were expecting one format, but due to the "regional settings" had something different and the parsing failed.  Because CB doesn't have any visible dates associated with characters I'm not sure what issue they are running afoul of in the "regional settings" nor how pervasive throughout their code that issue might be.  Far be it for me to say how easy or hard any particular CB bug is to fix since I've not seen the code.
#10 lokiare Jan 05, 2011 13:14:36	What gets me is that this is the third product where they have this very same problem already (original CB had it with the text size on power cards, MB didn't even start unless you changed settings IIRC, and now online CB doesn't let you choose powers). I mean, I'm an understanding guy, but at some point somebody at WotC needs to get a clue and get somebody to use their new programs with the settings changed to a different one to see if it actually works. Even more amazing is I've had to fix our companies VB .NET software for this exact issue.  In our case it was really dumb (date formatting) and didn't take more than an hour or two to (track down and) fix.  I recall another issue related to one specific "regional setting", but I don't remember what the exact problem was. In other words a quick fix? The generic problem yes, was a quick fix.  The more specific problem that I don't recall the details I want to say was not easy or quick.  But that's just my best recollection. I do want to point out it was a quick fix because all our date manipulation went through a single function and used the .NET Date/Time picker control so the issue was more of conversion to string where we were expecting one format, but due to the "regional settings" had something different and the parsing failed.  Because CB doesn't have any visible dates associated with characters I'm not sure what issue they are running afoul of in the "regional settings" nor how pervasive throughout their code that issue might be.  Far be it for me to say how easy or hard any particular CB bug is to fix since I've not seen the code. Would you agree though that a good initial design would make this an easy fix as in your case where every date/time was sent through a single function/object?
#11 kenjoon Jan 05, 2011 14:57:47	What gets me is that this is the third product where they have this very same problem already (original CB had it with the text size on power cards, MB didn't even start unless you changed settings IIRC, and now online CB doesn't let you choose powers). I mean, I'm an understanding guy, but at some point somebody at WotC needs to get a clue and get somebody to use their new programs with the settings changed to a different one to see if it actually works. Even more amazing is I've had to fix our companies VB .NET software for this exact issue.  In our case it was really dumb (date formatting) and didn't take more than an hour or two to (track down and) fix.  I recall another issue related to one specific "regional setting", but I don't remember what the exact problem was. In other words a quick fix? The generic problem yes, was a quick fix.  The more specific problem that I don't recall the details I want to say was not easy or quick.  But that's just my best recollection. I do want to point out it was a quick fix because all our date manipulation went through a single function and used the .NET Date/Time picker control so the issue was more of conversion to string where we were expecting one format, but due to the "regional settings" had something different and the parsing failed.  Because CB doesn't have any visible dates associated with characters I'm not sure what issue they are running afoul of in the "regional settings" nor how pervasive throughout their code that issue might be.  Far be it for me to say how easy or hard any particular CB bug is to fix since I've not seen the code. Would you agree though that a good initial design would make this an easy fix as in your case where every date/time was sent through a single function/object? A good initial design, yes.  Is there code written that way, your guess is as good as mine.  I feel like you're pushing me to (to use an analogy) "armchair quarterback" about their project, how it's implemented and how easy their bugs are to fix.  You won't bait me into it.  I've had enough stupid bugs take me days to fix for stupid reasons that I'm not about to start slinging mud.  You however, can feel free to keep on doing the armchair quarterback thing and saying that we should already have feature parity if you want.  The only thing that will get you from me is to make me think that you think WotC is purposely dragging their heels on updates.
#12 lokiare Jan 06, 2011 11:13:00	What gets me is that this is the third product where they have this very same problem already (original CB had it with the text size on power cards, MB didn't even start unless you changed settings IIRC, and now online CB doesn't let you choose powers). I mean, I'm an understanding guy, but at some point somebody at WotC needs to get a clue and get somebody to use their new programs with the settings changed to a different one to see if it actually works. Even more amazing is I've had to fix our companies VB .NET software for this exact issue.  In our case it was really dumb (date formatting) and didn't take more than an hour or two to (track down and) fix.  I recall another issue related to one specific "regional setting", but I don't remember what the exact problem was. In other words a quick fix? The generic problem yes, was a quick fix.  The more specific problem that I don't recall the details I want to say was not easy or quick.  But that's just my best recollection. I do want to point out it was a quick fix because all our date manipulation went through a single function and used the .NET Date/Time picker control so the issue was more of conversion to string where we were expecting one format, but due to the "regional settings" had something different and the parsing failed.  Because CB doesn't have any visible dates associated with characters I'm not sure what issue they are running afoul of in the "regional settings" nor how pervasive throughout their code that issue might be.  Far be it for me to say how easy or hard any particular CB bug is to fix since I've not seen the code. Would you agree though that a good initial design would make this an easy fix as in your case where every date/time was sent through a single function/object? A good initial design, yes.  Is there code written that way, your guess is as good as mine.  I feel like you're pushing me to (to use an analogy) "armchair quarterback" about their project, how it's implemented and how easy their bugs are to fix.  You won't bait me into it.  I've had enough stupid bugs take me days to fix for stupid reasons that I'm not about to start slinging mud.  You however, can feel free to keep on doing the armchair quarterback thing and saying that we should already have feature parity if you want.  The only thing that will get you from me is to make me think that you think WotC is purposely dragging their heels on updates. Not dragging their heels. More like working on the MB or multiple projects when they should have been focusing on the OCB to bring it up to feature AND usability parity with the CBC...
#13 kenjoon Jan 06, 2011 13:03:42	What gets me is that this is the third product where they have this very same problem already (original CB had it with the text size on power cards, MB didn't even start unless you changed settings IIRC, and now online CB doesn't let you choose powers). I mean, I'm an understanding guy, but at some point somebody at WotC needs to get a clue and get somebody to use their new programs with the settings changed to a different one to see if it actually works. Even more amazing is I've had to fix our companies VB .NET software for this exact issue.  In our case it was really dumb (date formatting) and didn't take more than an hour or two to (track down and) fix.  I recall another issue related to one specific "regional setting", but I don't remember what the exact problem was. In other words a quick fix? The generic problem yes, was a quick fix.  The more specific problem that I don't recall the details I want to say was not easy or quick.  But that's just my best recollection. I do want to point out it was a quick fix because all our date manipulation went through a single function and used the .NET Date/Time picker control so the issue was more of conversion to string where we were expecting one format, but due to the "regional settings" had something different and the parsing failed.  Because CB doesn't have any visible dates associated with characters I'm not sure what issue they are running afoul of in the "regional settings" nor how pervasive throughout their code that issue might be.  Far be it for me to say how easy or hard any particular CB bug is to fix since I've not seen the code. Would you agree though that a good initial design would make this an easy fix as in your case where every date/time was sent through a single function/object? A good initial design, yes.  Is there code written that way, your guess is as good as mine.  I feel like you're pushing me to (to use an analogy) "armchair quarterback" about their project, how it's implemented and how easy their bugs are to fix.  You won't bait me into it.  I've had enough stupid bugs take me days to fix for stupid reasons that I'm not about to start slinging mud.  You however, can feel free to keep on doing the armchair quarterback thing and saying that we should already have feature parity if you want.  The only thing that will get you from me is to make me think that you think WotC is purposely dragging their heels on updates. Not dragging their heels. More like working on the MB or multiple projects when they should have been focusing on the OCB to bring it up to feature AND usability parity with the CBC... As I indicated in that other thread.  I just can't see more than 2-3 coders working on a GUI interface program before they start getting in each others way and slowing down development.  If they have 5 (as you say) then I see no reason they can't work on CB and MB at the same time with little to no lost (potential) update speed.
#14 lokiare Jan 06, 2011 13:52:31	What gets me is that this is the third product where they have this very same problem already (original CB had it with the text size on power cards, MB didn't even start unless you changed settings IIRC, and now online CB doesn't let you choose powers). I mean, I'm an understanding guy, but at some point somebody at WotC needs to get a clue and get somebody to use their new programs with the settings changed to a different one to see if it actually works. Even more amazing is I've had to fix our companies VB .NET software for this exact issue.  In our case it was really dumb (date formatting) and didn't take more than an hour or two to (track down and) fix.  I recall another issue related to one specific "regional setting", but I don't remember what the exact problem was. In other words a quick fix? The generic problem yes, was a quick fix.  The more specific problem that I don't recall the details I want to say was not easy or quick.  But that's just my best recollection. I do want to point out it was a quick fix because all our date manipulation went through a single function and used the .NET Date/Time picker control so the issue was more of conversion to string where we were expecting one format, but due to the "regional settings" had something different and the parsing failed.  Because CB doesn't have any visible dates associated with characters I'm not sure what issue they are running afoul of in the "regional settings" nor how pervasive throughout their code that issue might be.  Far be it for me to say how easy or hard any particular CB bug is to fix since I've not seen the code. Would you agree though that a good initial design would make this an easy fix as in your case where every date/time was sent through a single function/object? A good initial design, yes.  Is there code written that way, your guess is as good as mine.  I feel like you're pushing me to (to use an analogy) "armchair quarterback" about their project, how it's implemented and how easy their bugs are to fix.  You won't bait me into it.  I've had enough stupid bugs take me days to fix for stupid reasons that I'm not about to start slinging mud.  You however, can feel free to keep on doing the armchair quarterback thing and saying that we should already have feature parity if you want.  The only thing that will get you from me is to make me think that you think WotC is purposely dragging their heels on updates. Not dragging their heels. More like working on the MB or multiple projects when they should have been focusing on the OCB to bring it up to feature AND usability parity with the CBC... As I indicated in that other thread.  I just can't see more than 2-3 coders working on a GUI interface program before they start getting in each others way and slowing down development.  If they have 5 (as you say) then I see no reason they can't work on CB and MB at the same time with little to no lost (potential) update speed. If this is true, then why don't they have more bugs fixed? Something has to be interfering with their work...