The dndjunkie site will eventually stop being used for Chummer. The site name is a little misleading and all of the non-Chummer-related content on there doesn't exactly help its ranking in search engines. I've setup www.chummergen.com over the weekend so that Chummer has its own little place. It resides in the same place as dndjunkie.com, so you can use either http://www.dndjunkie.com/chummer/wiki/ or http://www.chummergen.com/chummer/wiki/ to get to the Chummer Wiki. You can also get to the Chummer Wiki by going to Help > Chummer Wiki within the application (though that doesn't help you if you don't have access to the app).

Nice

Is this only when you load a file? Once the character has been loaded there shouldn't be a big time delay between switching tabs. I'll see what I can do about getting things to be a little quicker.

It happens to me frequently when switching tabs or characters. The first load of the skills tab for example is a good example (takes about 3-5 seconds), but even just switching tabs afterwards takes around a second for me on a powerful machine. I don't know if it is inherent to the language/technology/coding you use, but it feels sluggish. As I said, that's not an issue when working on characters out of a game, just too slow (for me) to use straight in game. Thanks for having a look at it anyway

[double post - sorry]

I've noticed delays when changing tabs for the very first time, but after that they all change very quickly.
The Skills tab is the slowest when it comes to changing that first time.

Yeah, it's a lot more responsive when you're using English instead of German/French where it has to load the translations (loading a character in Career Mode in English is ~2.2 seconds vs. French is ~5.9 seconds). Loading additional characters after the first is always quicker because the app has had a chance to cache most of the XML files, but it was still considerably slower when not using English. The biggest problem is that in the current build, the objects all load their translated names/page/categories on demand every time, so every time you click on a Weapon, it looks for the translated name, category, and page, each as separate lookups. I'm changing them so that they load the translated information when the object is populated and just uses those stored values which has made a huge difference so far (loading a character in Career Mode in French has gone down from ~5.9 seconds to ~2.6 seconds). I'm also going through and making some changes to how controls subscribe to events and general memory improvements.

Apart from switching to the Skill tab like ShadowWalker mentioned (I'll see if I can figure that one out...), I haven't noticed it being sluggish in any language. Switching tabs doesn't do anything besides draw the contents; there's no loading of translated string or anything. Hopefully the memomy changes I make will address the problem you're having.

I do not experience this even with 12 characters open, and I'm running in a VM with only 2 cores and 2GiB RAM assigned to it.

Which language are you using? I'm wondering if this has something to do with using French/German and the way strings are being translated (and hopefully fixed by the changes I've made so far).

I'll upload the version that I'm working on this evening to see if that resolves anything for you, deurk. If nothing else, it should dratically improve loading times and the time it takes to load translated names/categories/strings.

I'll have a go at your new version, thanks for putting time and effort into this Nebular.

Me neither. There is a noticeable delay when opening the Skill tab for the first time, but it's more like half a second (English version, W7 x64).

Build 300

• changed all references of www.dndjunkie.com to Chummer's new home: www.chummergen.com
• changed how item name translations are handled which should result in save files loading about twice as fast when using a language other than English
• changes to how controls subscribe to events and memory management

I had some minor bugs

* updating, when the new folder "export" did not exist leads to an unhandled exception
* It is not possible to create a new sprite with rating > resonance (max should be 2x resonance)
* sometimes, when I accidentally use the scroll wheel with an active spin box, an exception rises

These are all minor things, but I haven't seen them reported yet.

Thank you for this great tool. It made my return to Shadowrun a lot easier, many things had changed since the 3rd Edition

*bow*

*waves*

I'm using English, which might explain it.

I believe the scroll wheel problem was resolved in a slightly older build. Are you still having this problem with the latest version? If so, which box are you in when this happens?

I'll have the other two items fixed up in the next update. The update window will just create any directory it needs to when it's downloading files. I had kept meaning to do this before but also kept forgetting to add it to my list of stuff to do. Not sure why the Sprites one went without being fixed for so long, considering Spirits behave in the exact same way and were update to use MAG x 2 quite some time ago.

Tried build 300, and I'm afraid I did not see a huge difference. Wondered if it was because of my system which is 64bits but does the same on a completely different 32bits system.

Could the improvement manager let us modify the improvements created? (Was that question already asked?)

Shouldn't matter. The app is built as a 32-bit application and I'm running a 64-bit OS both at work and home without any issues. Even when using French with 15 characters open, I'm not seeing any sluggish performance on either machine. One of my players is even running it on a 32-bit copy of Windows XP on an old laptop and there's no sluggish performance on that either, despite it's being a 1.5GHz Celeron processory with 512 MB of RAM.

That is so weird. I wonder what makes a difference in my case then. Could old character sheets create such a behavior?
Would you be interested in a video file showing how it performs on my machine?

The character sheets shouldn't have any impact on it; they're just crunched by the XSL transformation engine and there's nothing processor intensive about it. If you have the print window open in Career Mode and modify the character, the window refreshes asynchronously so the app doesn't bother to wait for it. If you can capture a video of what's going on I'd be interested in seeing what's up.

Are you referring to Improvements that the system creates when you add something? Technically it could, but it doesn't assign human-readable names to them so they might be a little difficult to identify.

Could attribute improvement value not be a fixed value but a value we can change on the fly?

Meant old character savefile, not sheet, sorry. Meaning, would a made-from-scratch-using-latest version character change anything?

I was referring to the improvements tab were you can create your own from improvements.xml.

Anyone know if Lodges have a maximum rating? I can't seem to find it anywhere, and Chummer seems to think there is. I'd like to see if 1) there is an actual limit to the Force of a lodge and 2) make sure that it really is 12, and not 6. It's also relevant to the maximum rating of a Stacked Focus.

Street Magic hints at Rating 16 lodges (SM 68 under Luxury Resources: 1D6 + 10 rating magical lodges) and is the highest I've seen so far. Increasing it isn't a big deal, but I do need to have some sort of (reasonable) upper limit for the Rating field.

The main reason I ask in the first place is for a set limit on stacked foci. Based on the rules as written, the force of the focus is what determines the amount of dice added to your pool. That said, there doesn't appear to be an upper limit to individual foci, nor is there a set limit, then, on stacked foci. I'm trying to find information to contest this, but so far am unable to.

EDIT: And actually, going through the book I don't see any limit to individual ratings. So a single Power Focus could, theoretically, go all the way up to rating 30 (or higher based on Initiation).

EDIT again: Upon further investigation, page 176 or 177 SR4a states that the maximum Power of any given thing has a "natural" rating of 1 through 6 unless otherwise noted. So lodges, foci, and spells normally only go to power 6 (spells go further because of the difference between lethal and nonlethal). This means that the lodge normally can only be up to rating 6 as well, and the magical group is thus "unnatural". Still, though. I'm satisfied knowing any foci, including a stacked one can only have a maximum force of 6.

Thanks Nebular.

I tried to reproduce the bug with the scrolling in the current version, but was not able to do so. So this seems be be already fixed. Sorry for that "false alarm"


As for the Lodge Materials, I also think the same issue is raised by the binding spirit materials.
Due overcasting you are able from the beginning to cast and (try to) bind spirits with a force greater than 6, for which the corresponding materials are required.
As for the upper Limit, I did not see any restricions in the books, other than the usual Rating of 6, but I think this should not be applied in these cases.
I personally think limiting the rating for Lodges and Binding Materials at 18 should be (by far) sufficcent.

*waves*

Ps.: I am a bit out of practice writing in english, it isn't my mother tongue, so sorry for some of the mistakes I might have made.

Hallo,

i maybe found some more errors.
1. The AK98 assault rifle has a build in underbarrel launcher but in chummer these are two Weapons. If i add the laucher as underbarrel weapon he takes 3 modpoints but as a standard addon to this weapon he should be added automatically and take no modpoints.

2. An error in the original packs cause an error in chummer .. The pack "Classic Rigger Van" has a concealed armor rating of 20 but as described in the Arsenal the max rating of a concealed armor is 10.

3. Error messages if i set the char in carrermode. Its nice that the program tells me that i have to much capacity on an item or the a item has a to high availability but if the program tells me on which item the problem this would be great.

4. How can i help with the translation to german ? There are a lot of items still in english or french.


With kind regards

Askahain

The sensor rating for vehicles doesn't appear to change as new sensors are added.

Any possibility to sort the Improvements made in the improvements tab?
Up/down arrows to move them within the list would be great to organise those a bit.

hi, its me again

I just tried to make a new custom_gear.xml
First the chummer had an unhandled exception, because a german symbol was in the file (ä).
Debugging lead to the following error:

An unhandled exception of type 'System.Xml.XmlException' occurred in System.Xml.dll
Additional information: Ungültiges Zeichen in der angegebenen Codierung. Zeile 53, Position 18.

Translated: illegal sign for the given coding, Line 53, Postion 18
Thats where I found the ä, so maybe such an exception can be catched and shown
I thougt utf-8 has this kind of symbols available

Next is, the new items do not show up in chummer, I added a shortend version of the file below.


*waves*

As far as I can tell, the sensor rating doesn't change with the installed sensors itself. The sensor rating is like the Intuition attribute for the drone when it makes perception checks, modified by the Clearsight autosoft and other things. Even in Arsenal, there isn't a hard rule that improving sensors does increase the sensor rating, only that it "should also be improved accordingly."

I think it's fine that chummer doesn't change the sensor attribute of vehicles & drones. As a GM I'd issue modifiers to the DP for drones making sensor checks based on what their sensors are.

That's the way it is supposed to be. Just "buy" both. The underbarrel grenade launcher is free. That way it gets its own line on the printable sheet.

Unrelated issue: After selecting the Ally Conjuration technique, I cannot find a place to actually conjure the ally spirit

I've update the Gear file to increase the maximum Ratings of magical materials to 18.


I've update the PACKS file to correct the amount of Armor the Kit gives to 10 to comply with the Arsenal rules. Listing the items that are breaking the Availability rule should be pretty easy. I think I left that out before because it happened while all of the changes for translation were going on. I don't know the usernames of the two guys who are doing the German translations, but I'll send you a PM with their email addresses so you can get in touch with them.


Oh, I knew that would come up sooner or later! I'll add it do the list.

"ä" is perfectly valid in the XML data files. It might have something to do with the encoding on the file you created. I made a custom data file using the example you provided and replaced the "a" in Visitor Pass with "ä" and it worked. I've uploaded the working example to http://www.chummergen.com/dev/chummer/exam...achian_gear.xml.

As for it not showing up... the source you list here is "New York", which means the item will only show up if you have created a sourcebook with the code "New York" and enabled it in your Options window. <source> must match one of the codes found in books.xml or a custom books file like custom_books.xml.

You would need to create a new character for the Ally Spirit by using File > New Critter, select the Spirits category, then Ally Spirit from the list of Metatypes. When you've saved the file, you can then create a new Spirit entry on your character. Click the little chain icon on the Spirit, choose Attach Character, and select the save file for the Ally Spirit. You can also do this for any other Spirit you summon, and Technomancers can do the same for their Sprites.

So two things to change. Page 177, under Force says Spells, Spirits, and Magic Items (foci and lodges) have an attribute known as Force. It goes on further to say that the Force of these things is measured on the same scale as metahuman attributes (natural 1 to 6), and as such would then be limited to 6. Can you update chummer to reflect this? Main 2 things are magical lodges (since you have it set to a max of 12, but naturally it can only get to 6...the magical group with 1d6+10 Force lodge is one such example of an "unnatural" limit. The other is stacked foci. Foci stacked together can still only have a maximum total force of 6 (so 3+3 or 3+2+1 would work, but 3+4 wouldn't).

I don't think this is actually correct. For example, a mage can summon a force 8 spirit, or cast a force 8 spell (even with a Magic of 5, it just means that the spell will do physical damage instead of stun damage to the mage casting it). Now, if this was the case, this would make things... interesting. I can believe that most foci are limited to force 6 (for the most part), but I don't think spirits and spells are limited, nor are lodges.

Thanks a lot for the help.

My error was, to create a new xml from a basic txt file, seems the encoding went missing or the file was only a arscii, anyhow, when ic Ised your file or copied an existing xml there were no issues with the special characters. THANKS

Regarding the issue with the custom data. Adding a custom_books.xml solved it

Your support for the chummer is great. *bow*

*waves*

I never found an official answer to this Force 6 maximum question.
Once again it's an houserule-only way.


I have some problem with the magic attribute :
i want to creat an infected with cyberware, and magic burnout (dropped to zero), can i do this with chummer ?

Could put the improvements in a treeview and allow for something similar to locations in gear. That would be great for organizing them.

I was thinking would it be possible to add a drag and drop with the Ctrl or Alt key to allow for dropping onto other items and turning the dropped item into a plugin or to move it from one item to another.
Being able to move software from one commlink to nexus or another commlink and back is something that would be really useful.

Build 303

• placing a negative number in <flyspeed /> now gives a character a Fly speed equal to their Movement x [number x -1] which allows the Drake Quality to give a character a Fly speed of twice their Movement rate
• Update window now creates any directories it needs for downloaded files instead of relying on them being created by previous versions of the application
• corrected the maximum Rating for Sprites in Career Mode to RES x 2
• added an option to calculate Commlink Response based on the number of running programs (enabled by default)
• Programs attached to Commlinks can now be marked as Running which impacts the Commlink's Response value if the option is enabled (as per Processor Limit on SR4 222)
• added support for translating Spell DV
• Spells now show their translated DV on character sheets
• adding a Spell in Career Mode now asks you to confirm the Karma expense
• added support for creating Spells (as per SM 159), accessed through the dropdown menu on the Add Spell button
• names of items that are over the character's Avail limit are now shown when attempting to move a character to Career Mode to make identifying them easier
• Stacked Foci are now limited to a combined Force of 6
• added a house rule to allow the combined Force of Stacked Foci to exceed 6

New Strings

• Message_StackedFocusForce
• String_SpellOverflowDamage
• String_SpellDamageValue
• String_SpellToxinDV
• String_SpellDiseaseDV
• String_SpellRadiationPower
• Checkbox_SoftwareRunning
• Checkbox_Option_CalculateCommlinkResponse
• String_SpellDurationPermanentLong
• Menu_CreateSpell
• Title_CreateSpell
• Label_SpellOptions
• Checkbox_RestrictedTarget
• Checkbox_VeryRestrictedTarget
• Checkbox_CombatSpell1
• Checkbox_CombatSpell2
• Checkbox_CombatSpell3
• Checkbox_CombatSpell4
• Checkbox_CombatSpell5
• Checkbox_DetectionSpell1
• Checkbox_DetectionSpell2
• Checkbox_DetectionSpell3
• Checkbox_DetectionSpell4
• Checkbox_DetectionSpell5
• Checkbox_DetectionSpell6
• Checkbox_DetectionSpell7
• Checkbox_DetectionSpell8
• Checkbox_DetectionSpell9
• Checkbox_DetectionSpell10
• Checkbox_DetectionSpell11
• Checkbox_DetectionSpell12
• Checkbox_DetectionSpell13
• Checkbox_DetectionSpell14
• Checkbox_HealthSpell1
• Checkbox_HealthSpell2
• Checkbox_HealthSpell3
• Checkbox_HealthSpell4
• Checkbox_HealthSpell5
• Checkbox_IllusionSpell1
• Checkbox_IllusionSpell2
• Checkbox_IllusionSpell3
• Checkbox_IllusionSpell4
• Checkbox_IllusionSpell5
• Checkbox_ManipulationSpell1
• Checkbox_ManipulationSpell2
• Checkbox_ManipulationSpell3
• Checkbox_ManipulationSpell4
• Checkbox_ManipulationSpell5
• Checkbox_ManipulationSpell6
• Message_SpellName
• Message_SpellRestricted
• Message_CombatSpellRequirement1
• Message_CombatSpellRequirement2
• Message_DetectionSpellRequirement1
• Message_DetectionSpellRequirement2
• Message_IllusionSpellRequirement1
• Message_IllusionSpellRequirement2
• Message_ManipulationSpellRequirement1
• Message_ManipulationSpellRequirement2

Yeah, I'm going to leave the Lodge and Materials at their current max of 18. This leaves it nice and open for those who want it to go higher, and with Street Magic saying that things like a Force 16 Lodge are possible, it makes sense to me to leave it there.

Yes, you can create an infected and burn their MAG down to 0. This was fixed a couple of weeks ago.

Spirits and Spells still fall within the 1-6 natural measurement. 1-6 for nonlethal, and then 1-6 for lethal. The basic rule still applies.

Okay, if your Magic Attribute is 12, then what happens? Does this mean you're limited to Force 12 spells, but they'll never to lethal damage, or does this mean you can cast up to Force 18, which in theory could do lethal damage? I'd really like some solid 'here is this written out in plain English' from the books.

Time to hit the books, and move this to a different thread.

I like the in-program custom spell maker, though I have a few fixes to suggest:

If you select a Combat Mana spell, Elemental should be disabled, and checking the Elemental option should either also auto-check the Physical Damage box as well or disable Physical & Stun instead (and in the case of the later, have checking Physical or Stun also disable Elemental if either are checked). SM page 163, the Drain Modifiers chart states quite clearly that Elemental spells must be Physical and of Physical Damage (honestly I feel it should be your choice of one of the three instead: Elemental, Physical, Stun).

Also, Combat spells are always Instant. They can never be Permanent or Sustained (SM, page 162 under Combat Spells).

The same also goes for Manipulation spells. Choosing Mana should disable Elemental, and vice versa. Also, Environmental spells are also always Area spells (SM page 164).

Sounds to me like a magic attribute 12 would allow for a spell at level 24, which would be suicide, but for this conversation that's besides the point.