by Battlegrounds Games, LLC
@Dominic, did you place MapForge in the "Program Files (x86)" directory?
Try Shift-clicking on the minimap label to enable an experimental refresh mode. Let me know if performance improves using that mode.
Apologies for the delay in response. I am not using any effects at all yet, the lag occurs with just tiles and items. My intended use is for 5E VTT so my "test canvas" is set to 20x20 with 5' units. I recently reduced DPI to 100 to see if the problem persists and unfortunately, still lags. Replicated "test canvas" on an i7 laptop with comparable specs to my desktop workstation and the results are identical.
Am always happy to answer questions and participate. I respect the dev process, keep up the good work. The asset packs all look fantastic BTW.
@Guild, it will run, but setting the compatibility mode will be necessary, or at least installing MapForge to the "Program Files (x86)" directory, which may cause the OS to set it automatically.
So MapForge is not going to run well on 64 bit systems? Isn't that pretty much the standard nowadays? Seems like a serious problem to me.
@Dominic, thanks for providing detailed info about your system in your report, and details on things you've tried. Very few people do so, and I have to ask follow-up questions that are rarely answered. If the app is unresponsive for up to a full minute, that is clearly unusable, and very surprising, as it shouldn't take more than a few seconds TOPS, depending on what exactly you are doing. Have you tried disabling Effects until you've finished editing your map and are ready to Export? That might make a huge difference, especially if you have resource-intensive effects applied to certain layers. Are you even USING any effects?
I've done what I can over the weekend to put the app (beta_4) through its paces and have encountered some issues. I'm running it on Windows 10 (64-bit) with an AMD FX8370 (no OC), 16GB DDR3 1866, Nvidia Geforce 1060 (6GB, 2560x1080 display), and a Samsung 950 Pro SSD.
Using the 64 bit launcher you provided, I've tried running all, some, few and singular add-on packs. Regardless of which pack is active, the app becomes considerably unresponsive after more than 16 tiles are stamped on the canvas. Switching between tools, highlighting a tile, rotating a tile, or using zoom on the minimap all take up to a full minute to resolve on screen. The issue persists if running in compatibility mode for Windows 7, Vista, and XP SP3, with or without admin privileges.
All of that being said, I'm looking forward to WYSIWYG in v1.0 ^_^
@Hal, Shockwave isn't required. Please read the "Technical Tips" section of this page: http://www.mapforge-software.com/downloads/
I am having trouble with Shockwave incompatibility with the program. It was saying must run version 11 and it is on version 12 now.
I haven't gotten past that part, yet.
@Battlegrounds Games, LLC Ok, thanks for the update!
Thanks for posting this!
@Bruce, you'll need to do it with each release. MapForge v1.0 will be a new release, so yes. It should be a pretty quick procedure to perform. There isn't really anything I can "fix". This is pretty standard procedure when running 32-bit apps on 64-bit systems.
I haven't been able to find the time to mess with Mapforge in awhile. I still haven't added in the add ons license you sent a few days ago...lol. I did not know there was a compatibility issue with this version on 64 bit systems. Are you working on fixing this or will we have to do the compatibility thing again when the next version comes out?
Oops! See my edit to the Update.
FYI, the MapForge server isn't behaving too well, today. Work is being done to move the site to its permanent home, and service may be sluggish or intermittent, today. One user notified me that they couldn't download their Add-Ons. I suggested they try again later, once the current server settles down.
I'm sure some people will find this helpful, thanks to John for submitting it.