Web-Based CB is Live (Official Announcement)

[Caerin]

AsmodeusLore has a good compiled list of issues. Some of those are known issues, some are reported from the forums.

Adding Dark Sun inherent bonuses doesn't seem to be an option yet.

For me, the change is kind of a wash. The three characters I really wanted to set up aren't working quite right. They weren't working quite right before the change, and I can get quite a bit further in this CB. It's also missing some things that were working in the previous version, though. Power points aren't being displayed, and weapons-as-implements isn't being properly calculated. The thing I miss the most is the display of math showing how attacks and damages are calculated for each power.

 

[Kurtomatic]

Every time I see this I just go "WHU??" because every time I view the character sheet, i simply click inside the character sheet part of the window(notice the little outlines on the page), it mouse-wheel scrolls just fine.

now, if you click outside of that, in the white surround, which is NOT part of the character sheet, then no, it won't scroll.

Interesting.

I'm a developer, so I know how focus works, and I tried selecting multiple points throughout the client screen area, and could not get mouse scrolling to work. I will try it again tonight on a better platform at home, but on my rather lame office PC running XPSP3 with Chrome, I wasn't scrolling off the mouse. Keyboard and manual handle scrolling worked okay, if a bit wonky.

 

[Sunseeker]

Nope, doesn't work for me.

What browser and OS are you using? I'm sitting on Win7 and IE(9 I think).

Just popped open Chrome, mouse-wheel scrolling doesn't work.

Doubleeditplusbad, tried it in firefox, not working there either.

Might be a Silverlight issue, might be an incompatibility issue. Works in IE at least.

 

[malraux]

What browser and OS are you using? I'm sitting on Win7 and IE(9 I think).

Safari 5.0.2 and OS 10.6.5.

 

[noodle fish mice]

I'm willing to give them some time to iron out the launch bugs, but so far this is unusably slow and much uglier and more cluttered than the old CB, which was pretty ugly and cluttered.

I am really disappointed so far.

 

[Sunseeker]

Safari 5.0.2 and OS 10.6.5.

Don't have Safari, but from a quick test in Firefox and Chrome(see above), it looks like scrolling only works in IE.

Could be a bug on their end, could be an issue on user end, not sure.

 

[LightPhoenix]

Based on what I have been told, this is not something that could have been predicted.

I don't mean to impugn your honesty; I'm sure that's what you were told. However, I highly doubt this is something that could not have been caught before release. In house stress-testing is good, and nothing is loading slow for me, so obviously the conclusions based on it were correct. However, any web-based application is going to need "real setup" (as opposed to in house or approximate setup) testing, and it appears that is was not done. The reason I say that is because the crashes are so prevalent that I find it hard to believe they would not have been caught if that had been done.

A little bit more info on the Server problems:

This is not due to server load. The traffic to the website so far *is* being monitored and is well within what was prediceted and tested.

I don't think it's due to server load either, at least not load on the program. Based on my experiences with the crashes, my (entirely ignorant) guess would be some sort of server hiccup in communication between the program and the database(s). That could account for the randomness of it, and it always seems to happen when choosing an option. It could be due to load stress on the database, and not the website. I'm not certain exactly how the stress testing was done, so I don't know if that's the cause.

If I may forward a suggestion on to the developers - this seems like something that could be easily avoided if some sort of error handling was in place. Perhaps if an error occurs, the program simply doesn't add the feature, and displays a message apologizing and asking the user to pick again.

 

[Scribble]

Am I the only one that hasn't had it crash yet?

 

[malraux]

I don't mean to impugn your honesty; I'm sure that's what you were told. However, I highly doubt this is something that could not have been caught before release. In house stress-testing is good, and nothing is loading slow for me, so obviously the conclusions based on it were correct. However, any web-based application is going to need "real setup" (as opposed to in house or approximate setup) testing, and it appears that is was not done. The reason I say that is because the crashes are so prevalent that I find it hard to believe they would not have been caught if that had been done.



I don't think it's due to server load either, at least not load on the program. Based on my experiences with the crashes, my (entirely ignorant) guess would be some sort of server hiccup in communication between the program and the database(s). That could account for the randomness of it, and it always seems to happen when choosing an option. It could be due to load stress on the database, and not the website. I'm not certain exactly how the stress testing was done, so I don't know if that's the cause.

If I may forward a suggestion on to the developers - this seems like something that could be easily avoided if some sort of error handling was in place. Perhaps if an error occurs, the program simply doesn't add the feature, and displays a message apologizing and asking the user to pick again.

well my suggestion would be that every single time i click on anything in the program it shouldn't involve sending and receiving data to and from a server.

 

[fanboy2000]

Am I the only one that hasn't had it crash yet?

Probably. But it only crashed on me twice on my first PC. No other problems since.