EpicTable 1.3.6.2 Patch Released

Posted in Announcements on January 4, 2017 at 12:48 am

EpicTable 1.3.6.2

EpicTable 1.3.6.2 is now available. It’s a quick fix for a mistake I introduced in 1.3.6 (originally released on 12/21 as 1.3.6.1). It addresses one thing and one thing only: an error in loading “count successes” dice rolls into the dice roll editor. If you don’t use this kind of dice roll, there’s no need for you to upgrade. (And in that case, let’s just forget we had this little conversation.) If you’ve not already upgraded to 1.3.6, go ahead. There are other worthwhile things there. As always, it’s a free upgrade, and as always, it’s completely backwards compatible. Just download it and run the installer.

— John


EpicTable 1.3.4 Released

Posted in EpicTable Blog on September 6, 2016 at 6:00 am

EpicTable 1.3.4 is available now via http://www.epictable.com/download.

I took a little timeout from work on the new version of EpicTable to address some issues that people have reported. I also sneaked in a minor enhancement. The new features are taking longer than I’d hoped, so I’m addressing some of the pain out there. Please check out this update. It’s worth having and should bridge the gap until the new stuff starts rolling in.

Fixes

Character note changes not being propagated or saved in some cases
Fixes scenarios in which the notes section of the character edit form aren’t propagated to other players or saved.

Some actions not triggering surface save
Fixes bugs that caused some actions taken on tabletops and maps to not trigger a save. Most notably, edits to drawings and the content portion of index cards weren’t triggering the autosave feature.

Focus action on a map not popping the focus request dialog for all participants
Fixes a bug that prevented the focus request from being offered to the participants. (This is the way a GM tells the players what map should be showing and what the zoom and scroll settings should be.)

Fixed unhandled exception reports due to concurrent access to files
Fixes a bug that caused certain files–storage for pens and brushes, as well as surface view information, such as zoom and scroll settings–to be accessed at the same time, causing one of the two accesses to generate an error that prompted the user to submit a report.

Workaround to prevent unhandled exception reports caused by bugs in underlying control libraries
Handling intermittent, non-reproducible errors caused by Microsoft and/or DevExpress libraries at a higher level, allowing me to gather the data on these errors (from those participating in the quality improvement program) and suppressing the prompt to the user to submit a report.

Enhancements

Edits to index cards, text fields, and rich text notes now get saved and propagated to other participants, even if the person editing hasn’t left the object.
It had been the case that clicking away from an index card or a rich text note or a text field on a tabletop was the signal that the change was done and should be sent to the other participants and saved. However, this caused confusion and lost work when people spent a lot of their time editing one of these objects without clicking away. Now, every 3 seconds, changes will be saved and propagated to other participants.

Character tokens should stop sizing to grid once you manually change their size
It had been the case that a character token’s size was always based on the size of the grid and the character’s size. However, this caused confusion because people would manually resize a character token only to find that change undone the next time the map was loaded. Now, once you change a token’s size, that takes precedence over its size as based on the grid and character.

Allow rolled dice to be displayed in sorted order by value
You can now sort dice in the result of a dice roll. The sorting is pool-based. That is, dice of like size and color comprise a pool and those are sorted independently. Thus, one cannot, for instance, sort d6s and d8s together because those dice are never presented together. You can, however, sort one or both pools. This is useful when playing games that rely on dice comparison or pay special attention to the highest die. Sorting can be done on text-entered rolls by adding “>” for sort high-to-low , or “<” for sort low-to-high. For instance, to roll 10 d6s and sort them high to low, you would type: “/roll 10d6 >” in the chat window. You can also apply sorting to dice pools in the dice roll editor by dragging one of the new “dice evaluators” to the pool, as shown below.

Dice Sorting

 

Compatibility

This release is a free update and is backward compatible with earlier versions of EpicTable. To install the patch, simply download the installer from http://www.epictable.com/download and run it. You can install it right over top of your existing installation.


EpicTable 1.3.3 Released

Posted in Announcements on May 1, 2015 at 9:52 am

EpicTable 1.3.3 is available now via http://www.epictable.com/download.

This release addresses the following two issues.

Issue with custom data folder reverting to the default
The feature that lets you specify the folder where EpicTable data is stored had an issue that caused it to keep getting reset to the default location. I’ve helped a few of you address this manually to get past the bug. If you’re one of these folks, there’s no need for you undo any of that. This update will just make sure that the right thing happens the next time.

Issue with permanently removing maps and tabletops from the game
Some of you reported that you were unable to remove maps and tabletops from the game via the right-click menu in the Maps and Tabletops gallery. You were doing it right. There was a problem that is fixed in this release.

This release is a free update and is backward compatible with earlier versions of EpicTable. To install the patch, simply download the installer from http://www.epictable.com/download and run it. You can install it right over top of your existing installation.


EpicTable 1.2.2 Fixes Startup and Game Loading Bugs

Posted in Announcements on March 14, 2014 at 4:45 am

A couple people reported problems in EpicTable startup or game loading in 1.2.1.
In the one case, EpicTable silently exited before it even displayed the start page. In another case, EpicTable would fail to load a game, displaying the mysterious error, “No mapping for file C: under root.” These are both fixed in EpicTable 1.2.2, available now.

My apologies to the folks affected, and thank you so much for working with me to get this resolved.
— John


EpicTable 1.2.1 – Retries

Posted in Announcements on February 26, 2014 at 10:16 pm

I know some of you have been interested in EpicTable but waiting for fog of war. If you’ve evaluated EpicTable and you’re interested in taking it for another spin now that it has fog of war, now’s your chance. With this 1.2.1 release there’s a refreshed evaluation license, so you have another chance to try it out.

In addition, I’ve addressed a bug in the feature that lets you tell EpicTable where to store your data. It didn’t impact new games or new resources, but it caused EpicTable to “lose” resources created before changing the data location. That’s taken care of in this release.

If you want more trial time, or if you’re changing your EpicTable data location and have existing games, get EpicTable 1.2.1.


Please Upgrade to the Latest Release (1.0.24.1)

Posted in Announcements on August 31, 2012 at 7:23 am

I’ve received a flurry of automated error reports this morning from people running 1.0.23.0. There is a known issue that’s causing you trouble, and for that, I apologize. Fortunately, this is an issue that was fixed last week, so all you have to do is go to the support site (http://support.epictable.com) and download the 1.0.24.1 update installer. (The full install will work just fine as well. The update installer is just smaller.)


Beta 21 Update: A Squelching of Small Evils

Posted in Announcements on August 7, 2012 at 11:04 pm

There’s an update available for Beta-21.  For those keeping score, the “original” Beta-21 is 1.0.21.4.  This one is 1.0.21.6.  No new features, just a couple fixes. I didn’t want to start selling 1.0 with these things, and while I was fixing them in the 1.0 GA release, I didn’t want to see them in the beta either. As always, if you don’t want the play-by-play, feel free to skip to the bottom and just download the update.

The Changes

A Recurring Villain, Vanquished

One issue in particular has been an small but irritating thorn in my side. It gets reported about once a week. There’s a bug in a third party component I use in the chat window and the notecard editor (or in all fairness, maybe a bug in how I’m using it). I’ve never actually seen it myself, but it’s reported enough to put a little black cloud above my head every time an automated error report comes in. I rewrote the notecard editor to remove the troublesome component completely. I couldn’t do that so easily to the chat window, but thanks to all of your automated reports, I could pinpoint the (thankfully) one place the problem was occurring and fix the component itself. I really think this will put an end to that particular error. Without being able to reproduce it myself, though, there’s a chance that, like the end of an 80’s horror movie, once the heroes walk offscreen, the villain appears in the final frame, not fully vanquished after all. I’m hoping this is a case in which the sequel never gets made. [Cue the 80s-hair-metal and roll credits.]

Friendly Fire

I hate when I break things for you guys…. I broke the feature that lets you use the arrow keys to move things around on maps and tabletops. I unbroke it in this update.

Assembly Dropship

EpicTable carries around many assemblies (i.e., .NET components or libraries), both my own and third party assemblies, inside EpicTable.exe. This was to make things less complex. At one point in the past, EpicTable was a single executable, which I found kind of appealing. There are downsides to doing that, though, and at least one of you ran afoul of them. I think I can best (or at least most entertainingly) illustrate this with a scene from a sci-fi movie.

The “assembly dropship” lands, and just as Joe goes to run out the door, .NET says, “Hey, that’s okay, Joe. You just sit tight. We’ve got our own Joe out here already. We know he’s not a clone or android or Cylon or anything else that’s apt to kill us when we least expect it, so we’re going to go ahead and stick with him, m’kay? Thanks.”

When that happens, you can end up running something EpicTable’s never been tested with. The fix was to stop embedding these assemblies in EpicTable and just install them alongside EpicTable.exe, where they’ll be loaded in preference to (most) other things in the environment.

Predatory Layout Bug

In 1.0.21.4 (aka “Beta 21, The First of His Name”), it was possible, under certain circumstances, for a new EpicTable user to find the layout of the chat window and portrait panel…um…sub-optimal, relative to the rest of the app. If you happen to have used EpicTable quite a bit, you could probably figure out how to get yourself out of this predicament by unlocking the panel layout and dragging them into more appropriate positions. Ironically, this would almost never affect anyone unless they’d never used EpicTable. A bug that preys on the most vulnerable members of the herd? In 1.0.21.6, EpicTable puts things into a known-good layout unless you’ve already moved or resized panels to where you want them.

Getting the Update

You have a decision to make this time.  If you already have EpicTable Beta-21 installed, you can give the update installer a try.  It’s a mere 8MB download and installs wicked fast, as we like to say in the Northeast.

New, shiny, wicked fast 8MB: EpicTable 1.0.21.6 Update Install
 (Use this only if you already have EpicTable Beta-21 installed.)

Safe, familiar, 30MB juggernaut: EpicTable 1.0.21.6 Full Install


  • Tags