The Jumpgate Beta for Pro Users Has Arrived!

There is a major performance hit when using Dynamic Lighting (especially Explorer Mode) with Firefox right now. We are working on a fix for that but it might be a couple of weeks. 

Tiffany F. said: Not sure if these are already reported --- a lot going on in this thread. But: Tooltips aren't displaying for players (reguardless of how we adjust/alter the see/edit permissions, unless we mark that the token is controlled by the player - which isn't what we want or expect).  Token markers - token markers dont always appear. and when they do or dont seems to be random. however, applying a token marker (and it appears) and then refreshing removes the visualization of the token marker for GM and players. If you go to reapply it the token marker is highlighted like it is still applied, and you have to unapply and reapply to get it to appear. Of course, when it decides it *wants* to reappear. Sometimes you have to apply - refresh - unapply - apply multiple times, and hope all participants are in sync!  Unfortunately, we use both of those functionalities extremely heavily in our games so we had to move off the jumpgate version and restart :'( Okay we'll log both of those, thanks for the report!

NPC said: The token numbers don't work anymore. My group uses this to track DoT turns remaining, stacks and such. I think they are currently broken when using Custom Token Market Sets but should be working otherewise -- is that what you're seeing?

Johnny Meatshield said: For me, copying 2 games to try this was even worse.  Old versions the GPU would sit around 80-85% GPU.  Jumpgate games were 95-100% GPU.  As a result I didn't even try running the games in Jumpgate, immediately deleted the copies and went back to the originals. Running Win 11, Chrome, 24GB RAM (I know that's a weird number), i7-8565U CPU with integrated Intel UHD 620. Which browser were you using? And was Dynamic Lighting enabled?

DM Donkey said: Hello all, I have looked through the forum and may have missed it so apologies if I have.  Loving the beta so far, a few kinks you are ironing out, here is another i'm afraid: Apple M2 Max with 32gb using Chrome  Version 123.0.6312.123  memory usage is through the roof.  Sitting on a map with maybe 15 tokens and it is running at 1.3gb whilst the same map in roll20 is 339mb.  Performance is fine though for now. When I have other players the highest I have hit is 4.5gb for the page and I then have some issues whereby I can't pan.  A refresh sorts it. Battery is really hit hard too.  Full charge is gone in 2 hours with Zoom running but on legacy I have 60% after the same time.  Do you mind PMing me a link to that game in question? That's definitely a weird result so want to see if I can replicate it.

Bill (Do Not Kill) said: Ari M. said: So, I just migrated a campaign over to Jumpgate this evening, and I'm seeing several problems just trying to get things set up. 1) The size of the map page and the size of the map image don't correspond, even though they're both set to the exact same dimensions. The map hangs way off the edge of the page/hex grid on the right, while parts of the blank page are visible protruding from beneath the map image on the bottom. I've triple-checked the dimensions, and they match. No idea what's going on here. I'm uploading a screen grab so you can see what I'm talking about. (I recognize the above is an exceedingly large map, but it worked fine prior to the Jumpgate migration, and the system is doing the same thing to me on some smaller maps.) 2) Token tool tips aren't showing up on hovering over the icon when I'm signed in as a player. 3) Several characters randomly jumped from the sub-folders they were in back to the main journal page. 4) Some pieces of art have changed tone/darkness in the changeover. Just to amplify on and provide more data on the map problem that Ari M. reported on last week.  I took some screenshots from the original vs. the ported campaign.  The original map: and the original page settings vs. the same map page ported into Jumpgate (note that I intentionally left the "Apply Dominant Color" box unchecked to make it clear where the background map object actually ends).: The fun part is that the reported size of the background map object (as reported by the Advanced/Set Dimensions dialog) is identical with the page size (3520X2112) in both the original and Jumpgated campaigns.  One potential clue might also be gleaned from the colored circles, which only appear on the GM layer (they mark territories which the players are not intended to be aware of).  It is interesting to note that they, too, seem to maintain the same scaling relationship with the background map object between the two campaign objects.  Also of note is that the map scale does more or less correspond to the 1 mi/hex in the original map, but is definitely off in the Jumpgated map. We have a fix for this map issue (it's related to using hex grids) and it won't be out in today's release but should be out before the weekend.

Hey folks, We just pushed out a new release with some fixes: There's now a Jumpgate Achievement Badge that you can earn by joining any Jumpgate game on Roll20. It should automatically show up in your profile if you join a Jumpgate game from today onward. We've made some major improvements to load speed when loading pages that have lots of drawings on them -- you should see much faster load times on these pages in Jumpgate! Fixed a bug which could sometimes throw an error about rebuilding the initiative list. Fixed a bug where bold/italic text could sometimes get split into multiple lines of text. Fixed a bug where you couldn't select a filled shape immediately after creating it. Fixed a bug where after deleting a drawing, if the user marquee selects in the upper left-hand corner of the map/off map area, a ghost is selected.

Also wanted to note, there was a question about opting out of the New Compendium in Jumpgate since there's not a separate toggle for it. The New Compendium is the only thing behind the Beta Features toggle in Jumpgate games, so if you want to revert back to the old compendium, just uncheck the Beta Features toggle and you should be able to do so.

Jonathan K. said: Riley D. said: There is a major performance hit when using Dynamic Lighting (especially Explorer Mode) with Firefox right now. We are working on a fix for that but it might be a couple of weeks.  is that on Chrome as well Riley? It's specific to Firefox, if you're seeing it on Chrome as well it's a different issue.

Glad to hear it on both of these reports! There is so much changing so quickly it's hard to know but we're always improving performance and all of that all the time so let us know if it creeps back up on you.

Hey folks, We just pushed out a new update to Jumpgate with some additional fixes and a new feature: @{target} macros should now be more clear to use -- after the mode engages, hovering over a targetable object will show a crosshair cursor @{target} macros should now be working for players to allow them to target tokens they don't control (handy for Mod Scripts!) There's a new icon under the Zoom bar that looks like a target icon -- clicking it will re-center the current map back to the center and go back to 100% Zoom. So if you get really far afield or lost, you can always find your way back Home -- which is also the keyboard shortcut to quickly do this on the fly! If you are using the marquee selection tool and only select a single token, the radial menus will now appear just like they did on Legacy. We fixed an issue with hex grids where they weren't lining up correctly and were offset. Thanks for all of your reports and your continued feedback!

Aleksi said: After copying the Jumpgate game (a few minutes before making this post) to convert it back to a non-Jumpgate game, all lines drawn on (a hexagon grid) map in the Jumpgate session had disappeared. Yeah the Jumpgate data is not compatible with legacy, it's a one-way deal, so that's why we're having you make a copy of the game to opt in to Jumpgate -- opting out is just "go back to using the original."

Noted on the @{target} macro issue, thanks all. One quick note, we had an issue last night in an unrelated part of the site that required a rollback of our deployment, as such the stuff that we updated in Jumpgate yesterday has been rolled back as of about 8 hours ago. We will get that re-deployed later this morning hopefully and I'll update when that happens, but just noting that right now if you are like "where did that Center Map icon go?" it's not your imagination, it has disappeared temporarily :-)

Okay, those changes from yesterday should be live again. Also as a quick followup, the @{target} macro for players seems to be working properly in Chrome, but not in Firefox. We're investigating that further.

Aleksi said: One more bug encountered that happened quite often was a player getting stuck in zoom mode until reloading the page. The player was using Chrome as browser and had been promoted to GM for the game while not being the owner of the game, in case that's relevant. As in they would be using the scrollwheel and it would Zoom instead of Pan? Or?

Steverhud said: Riley D. said: If you are using the marquee selection tool and only select a single token, the radial menus will now appear just like they did on Legacy. I can confirm that the marquee select for a single token works as it should. However when you select multiple tokens, the Token actions do not appear. Selecting 1 yes, multiple no. Okay yeah we have that noted as a separate issue, but thanks for the reminder! keithcurtis said: Riley D. said: If you are using the marquee selection tool and only select a single token, the radial menus will now appear just like they did on Legacy. Odd behavior: If you use the marquee tool to select the token, but at any point overlap an additional token, the radial menus disappear, and will not appear when the mouse button is let up, even if only a single token is ultimately selected. This makes the feature a bit finicky on a crowded board. Okay, I'll see if we can fix that, thanks.

Hey folks -- we put out an update for the @{target} macros, and that should be working now for players in Firefox. Thanks!