CB bugs Feb 7, 2011 (1.2.198.0) - Downloaded from the Wizards Community, all coding removed by Solauren

CB bugs Feb 7, 2011 (1.2.198.0)

Post/Author/DateTime Post
#1
pruano
Feb 09, 2011 9:20:16 [using template from previous post]

Report bugs for the next version 1.2.198.0 here.

Known Issues.

Things that they think they fixed. (let's hold them to it)
#2
pruano
Feb 09, 2011 9:24:54 When importing half-elf character from CB classic, "Knack for Success" racial power is chosen instead of "Dilettante", and the language isnt chosen.
#3
mellored
Feb 09, 2011 9:28:12 Summon/Call Celestial Steed needs some fixing.

Not sure what exactly they want to do with it, but the Dragon article and the Builder don't match.

Edit: i was looking at the non-compiled version. But it still has a level, and thus should still be power-swapable.
#4
pruano
Feb 09, 2011 9:39:37 When importing a character from CB classic (without house rules) it sometimes crashes with the message:

System.ServiceModel.FaultException: System.Xml.XmlException: The '!' character, hexadecimal value 0x21, cannot be included in a name. Line 3762, position 91.

followed by the stack trace.
#5
paolom
Feb 10, 2011 14:52:47
When importing a character from CB classic (without house rules) it sometimes crashes with the message:

System.ServiceModel.FaultException: System.Xml.XmlException: The '!' character, hexadecimal value 0x21, cannot be included in a name. Line 3762, position 91.

followed by the stack trace.

Please contact support and provide them with the .dnd4e file so we can take a look.
#6
lokiare
Feb 11, 2011 0:40:29
When importing a character from CB classic (without house rules) it sometimes crashes with the message:

System.ServiceModel.FaultException: System.Xml.XmlException: The '!' character, hexadecimal value 0x21, cannot be included in a name. Line 3762, position 91.

followed by the stack trace.

Please contact support and provide them with the .dnd4e file so we can take a look.

I thought you weren't allowed to post...
#7
mellored
Feb 11, 2011 9:21:32
Please contact support and provide them with the .dnd4e file so we can take a look.

I thought you weren't allowed to post...
I think he's just not allowed to announce things, comment on up-comming products, ect..
#8
sliksham
Feb 14, 2011 1:29:06 Bard at will power 'Vicious Mockery' is showing as an encounter power on the character sheet as well as in the side bar when you highlight the power whilst in CB.
#9
mellored
Feb 14, 2011 8:41:01
Bard at will power 'Vicious Mockery' is showing as an encounter power on the character sheet as well as in the side bar when you highlight the power whilst in CB.

Do you have a wand of visious mockery?

If so, that's on the known list.
If not, more details would be good.
#10
mellored
Feb 14, 2011 10:50:53 Not really a "bug", but if you get enough conditional bonuses to saving throws it runs over into the resistances, making it very difficut to read (the Character Builder sheet).

Not sure how you could fix that though, except for allowing resizing of areas.
#11
kenjoon
Feb 14, 2011 17:10:40 Just submitted:

Windows XP & Chrome:
The mouse wheel does not work on the info box in the marketplace with the sole exception of "Manshoon's Bloodmask". Also the text (if it exceeds the area) is always scrolled to the bottom.
#12
DMaple
Feb 14, 2011 17:29:19 How can the fact you can't print out a character sheet correctly on A4 paper not be on the known issues list? I've certainly reported it well before that list was created, and it still hasn't been fixed!

It makes the product virtually useless to anyone outside the US.
#13
mondragon
Feb 15, 2011 0:29:30 I have also reported the A4 bug to Customer Service the last 23rd of January and posted it on the forums. I found out the Letter workaround with CutePDF Writer, but I really cannot understand why the developers have not fixed (or mentioned) it yet.
#14
lokiare
Feb 15, 2011 5:44:33
I have also reported the A4 bug to Customer Service the last 23rd of January and posted it on the forums. I found out the Letter workaround with CutePDF Writer, but I really cannot understand why the developers have not fixed (or mentioned) it yet.

{imagine a snide remark here}
#15
kenjoon
Feb 15, 2011 11:22:04
How can the fact you can't print out a character sheet correctly on A4 paper not be on the known issues list? I've certainly reported it well before that list was created, and it still hasn't been fixed!

It makes the product virtually useless to anyone outside the US.

My best guess? It's not WotC's bug. Just like the mousewheel problem got fixed by a Silverlight patch we got last month, they are using the built in Silverlight printing (such as it is) and are probably trying to get MS to fix it. That does not however, make it a bug in their code and it is therefore appropriately not on WotC's "known issues" list.
#16
drnick
Feb 15, 2011 12:54:33
I have also reported the A4 bug to Customer Service the last 23rd of January and posted it on the forums. I found out the Letter workaround with CutePDF Writer, but I really cannot understand why the developers have not fixed (or mentioned) it yet.

{imagine a snide remark here}

lol. I need permission?
#17
mondragon
Feb 15, 2011 14:12:58

My best guess? It's not WotC's bug. Just like the mousewheel problem got fixed by a Silverlight patch we got last month, they are using the built in Silverlight printing (such as it is) and are probably trying to get MS to fix it. That does not however, make it a bug in their code and it is therefore appropriately not on WotC's "known issues" list.

My company makes a planning add-in for Excel and, when required, we submit bugs to Microsoft, but in that case we also communicate the customer about the upcoming solution and how long will it take to fix it (at least, an estimate).
#18
kenjoon
Feb 15, 2011 15:12:09

My best guess? It's not WotC's bug. Just like the mousewheel problem got fixed by a Silverlight patch we got last month, they are using the built in Silverlight printing (such as it is) and are probably trying to get MS to fix it. That does not however, make it a bug in their code and it is therefore appropriately not on WotC's "known issues" list.

My company makes a planning add-in for Excel and, when required, we submit bugs to Microsoft, but in that case we also communicate the customer about the upcoming solution and how long will it take to fix it (at least, an estimate).

And with everything else that's happened, why should we be surprised that WotC hasn't done this?
#19
DMaple
Feb 15, 2011 15:16:55 It worked before WotC 1st update, and got even worse after their 2nd update. I doubt it is a Silverlight problem there is certainly nothing about printing in A4 causing a problem that I could find related to Silverlight itself.
#20
drnick
Feb 15, 2011 16:37:17 I assume they're doing it purposely as a form of DRM.
#21
lokiare
Feb 16, 2011 7:38:03 Actually, they could output it as a real pdf file themselves and then have you print it from there. There are tutorials and code snippets that do exactly this for Silverlight all over the internet. They are willfully choosing to do it this way. The image problem is definitely not a Silverlight problem. It is probably a math problem related to creating the image, could be a texture problem (textures have to be a multiple of 2 to work properly in some cases). Basically its just a bug on a long list of bugs that they are having...
#22
DalelandsHerder
Feb 17, 2011 1:07:09 Am I the only one who has noticed that the Essentials Assassin build (Executioner) isn't in the builder despite being in the last magazine that went in?
#23
thespaceinvader
Feb 17, 2011 2:48:03 No, you're really not. There are many threads about the issue already, and the official answer is that it was never intended to be a finalised class, it was merely a play test and it'll be in after the final final class is released in Heroes of Shadow.

Make of that, what you will.
#24
pruano
Feb 17, 2011 9:09:22
When importing a character from CB classic (without house rules) it sometimes crashes with the message:

System.ServiceModel.FaultException: System.Xml.XmlException: The '!' character, hexadecimal value 0x21, cannot be included in a name. Line 3762, position 91.

followed by the stack trace.

Please contact support and provide them with the .dnd4e file so we can take a look.

Done, ticket incident n.110217-000052

Post/Author/DateTime	Post
#1 pruano Feb 09, 2011 9:20:16	[using template from previous post] Report bugs for the next version 1.2.198.0 here. Known Issues. Things that they think they fixed. (let's hold them to it)
#2 pruano Feb 09, 2011 9:24:54	When importing half-elf character from CB classic, "Knack for Success" racial power is chosen instead of "Dilettante", and the language isnt chosen.
#3 mellored Feb 09, 2011 9:28:12	Summon/Call Celestial Steed needs some fixing. Not sure what exactly they want to do with it, but the Dragon article and the Builder don't match. Edit: i was looking at the non-compiled version. But it still has a level, and thus should still be power-swapable.
#4 pruano Feb 09, 2011 9:39:37	When importing a character from CB classic (without house rules) it sometimes crashes with the message: System.ServiceModel.FaultException: System.Xml.XmlException: The '!' character, hexadecimal value 0x21, cannot be included in a name. Line 3762, position 91. followed by the stack trace.
#5 paolom Feb 10, 2011 14:52:47	When importing a character from CB classic (without house rules) it sometimes crashes with the message: System.ServiceModel.FaultException: System.Xml.XmlException: The '!' character, hexadecimal value 0x21, cannot be included in a name. Line 3762, position 91. followed by the stack trace. Please contact support and provide them with the .dnd4e file so we can take a look.
#6 lokiare Feb 11, 2011 0:40:29	When importing a character from CB classic (without house rules) it sometimes crashes with the message: System.ServiceModel.FaultException: System.Xml.XmlException: The '!' character, hexadecimal value 0x21, cannot be included in a name. Line 3762, position 91. followed by the stack trace. Please contact support and provide them with the .dnd4e file so we can take a look. I thought you weren't allowed to post...
#7 mellored Feb 11, 2011 9:21:32	Please contact support and provide them with the .dnd4e file so we can take a look. I thought you weren't allowed to post... I think he's just not allowed to announce things, comment on up-comming products, ect..
#8 sliksham Feb 14, 2011 1:29:06	Bard at will power 'Vicious Mockery' is showing as an encounter power on the character sheet as well as in the side bar when you highlight the power whilst in CB.
#9 mellored Feb 14, 2011 8:41:01	Bard at will power 'Vicious Mockery' is showing as an encounter power on the character sheet as well as in the side bar when you highlight the power whilst in CB. Do you have a wand of visious mockery? If so, that's on the known list. If not, more details would be good.
#10 mellored Feb 14, 2011 10:50:53	Not really a "bug", but if you get enough conditional bonuses to saving throws it runs over into the resistances, making it very difficut to read (the Character Builder sheet). Not sure how you could fix that though, except for allowing resizing of areas.
#11 kenjoon Feb 14, 2011 17:10:40	Just submitted: Windows XP & Chrome: The mouse wheel does not work on the info box in the marketplace with the sole exception of "Manshoon's Bloodmask". Also the text (if it exceeds the area) is always scrolled to the bottom.
#12 DMaple Feb 14, 2011 17:29:19	How can the fact you can't print out a character sheet correctly on A4 paper not be on the known issues list? I've certainly reported it well before that list was created, and it still hasn't been fixed! It makes the product virtually useless to anyone outside the US.
#13 mondragon Feb 15, 2011 0:29:30	I have also reported the A4 bug to Customer Service the last 23rd of January and posted it on the forums. I found out the Letter workaround with CutePDF Writer, but I really cannot understand why the developers have not fixed (or mentioned) it yet.
#14 lokiare Feb 15, 2011 5:44:33	I have also reported the A4 bug to Customer Service the last 23rd of January and posted it on the forums. I found out the Letter workaround with CutePDF Writer, but I really cannot understand why the developers have not fixed (or mentioned) it yet. {imagine a snide remark here}
#15 kenjoon Feb 15, 2011 11:22:04	How can the fact you can't print out a character sheet correctly on A4 paper not be on the known issues list? I've certainly reported it well before that list was created, and it still hasn't been fixed! It makes the product virtually useless to anyone outside the US. My best guess? It's not WotC's bug. Just like the mousewheel problem got fixed by a Silverlight patch we got last month, they are using the built in Silverlight printing (such as it is) and are probably trying to get MS to fix it. That does not however, make it a bug in their code and it is therefore appropriately not on WotC's "known issues" list.
#16 drnick Feb 15, 2011 12:54:33	I have also reported the A4 bug to Customer Service the last 23rd of January and posted it on the forums. I found out the Letter workaround with CutePDF Writer, but I really cannot understand why the developers have not fixed (or mentioned) it yet. {imagine a snide remark here} lol. I need permission?
#17 mondragon Feb 15, 2011 14:12:58	My best guess? It's not WotC's bug. Just like the mousewheel problem got fixed by a Silverlight patch we got last month, they are using the built in Silverlight printing (such as it is) and are probably trying to get MS to fix it. That does not however, make it a bug in their code and it is therefore appropriately not on WotC's "known issues" list. My company makes a planning add-in for Excel and, when required, we submit bugs to Microsoft, but in that case we also communicate the customer about the upcoming solution and how long will it take to fix it (at least, an estimate).
#18 kenjoon Feb 15, 2011 15:12:09	My best guess? It's not WotC's bug. Just like the mousewheel problem got fixed by a Silverlight patch we got last month, they are using the built in Silverlight printing (such as it is) and are probably trying to get MS to fix it. That does not however, make it a bug in their code and it is therefore appropriately not on WotC's "known issues" list. My company makes a planning add-in for Excel and, when required, we submit bugs to Microsoft, but in that case we also communicate the customer about the upcoming solution and how long will it take to fix it (at least, an estimate). And with everything else that's happened, why should we be surprised that WotC hasn't done this?
#19 DMaple Feb 15, 2011 15:16:55	It worked before WotC 1st update, and got even worse after their 2nd update. I doubt it is a Silverlight problem there is certainly nothing about printing in A4 causing a problem that I could find related to Silverlight itself.
#20 drnick Feb 15, 2011 16:37:17	I assume they're doing it purposely as a form of DRM.
#21 lokiare Feb 16, 2011 7:38:03	Actually, they could output it as a real pdf file themselves and then have you print it from there. There are tutorials and code snippets that do exactly this for Silverlight all over the internet. They are willfully choosing to do it this way. The image problem is definitely not a Silverlight problem. It is probably a math problem related to creating the image, could be a texture problem (textures have to be a multiple of 2 to work properly in some cases). Basically its just a bug on a long list of bugs that they are having...
#22 DalelandsHerder Feb 17, 2011 1:07:09	Am I the only one who has noticed that the Essentials Assassin build (Executioner) isn't in the builder despite being in the last magazine that went in?
#23 thespaceinvader Feb 17, 2011 2:48:03	No, you're really not. There are many threads about the issue already, and the official answer is that it was never intended to be a finalised class, it was merely a play test and it'll be in after the final final class is released in Heroes of Shadow. Make of that, what you will.
#24 pruano Feb 17, 2011 9:09:22	When importing a character from CB classic (without house rules) it sometimes crashes with the message: System.ServiceModel.FaultException: System.Xml.XmlException: The '!' character, hexadecimal value 0x21, cannot be included in a name. Line 3762, position 91. followed by the stack trace. Please contact support and provide them with the .dnd4e file so we can take a look. Done, ticket incident n.110217-000052