MapTool 1.5.5 Release Candidate 2 Available
Moderators: dorpond, trevor, Azhrei, Craig
Re: MapTool 1.5.5 Release Candidate 2 Available
The difference is really bigger, much much bigger. Just the video can't film the difference
Re: MapTool 1.5.5 Release Candidate 2 Available
In fact I feel like 120 Hz down to 10 Hz.
Re: MapTool 1.5.5 Release Candidate 2 Available
I think it may be something about your system otherwise more people would be complaining about it. Is this happening with your framework or with any map. Try starting a new campaign, put a big map on the background and see if you get the same drop.
Under preferences try playing with the Advanced Options under the Start Up tab. Disable Direct3d OR Enable OpenGL. Maxmem should be something like 4096M and stack of 4M.
Under preferences try playing with the Advanced Options under the Start Up tab. Disable Direct3d OR Enable OpenGL. Maxmem should be something like 4096M and stack of 4M.
Downloads:
- Notepad++ MapTool addon
- RPEdit details (v1.3)
- Coding Tips: Modularity and Design
- Videos: Macro Writing Tools
Re: MapTool 1.5.5 Release Candidate 2 Available
As soon as I create a new campaign, with the default grass background, it behaves exactly the same. So it is related to this version, and not the size of the map nor the size of the campaign.
Re: MapTool 1.5.5 Release Candidate 2 Available
I have played with those preferences but no improvement. I suppose I will stick with the previous version. I just hope future versions don't have this problem or my campaign will be obsolete soon.aliasmask wrote: ↑Sat Oct 05, 2019 7:23 amI think it may be something about your system otherwise more people would be complaining about it. Is this happening with your framework or with any map. Try starting a new campaign, put a big map on the background and see if you get the same drop.
Under preferences try playing with the Advanced Options under the Start Up tab. Disable Direct3d OR Enable OpenGL. Maxmem should be something like 4096M and stack of 4M.
Re: MapTool 1.5.5 Release Candidate 2 Available
Okay. I can reproduce it on 1.5.5 (and 1.5.6). I needed multiple largish images and or a largish map image (3300x2550).
Now to figure out what the heck changed.
Now to figure out what the heck changed.
- Full Bleed
- Demigod
- Posts: 4736
- Joined: Sun Feb 25, 2007 11:53 am
- Location: FL
Re: MapTool 1.5.5 Release Candidate 2 Available
FYI, I have a 9500x7000 map with 142 small graphic assets on it... and I don't see the issue.
Maybe this?Now to figure out what the heck changed.
https://github.com/RPTools/maptool/pull/611
Maptool is the Millennium Falcon of VTT's -- "She may not look like much, but she's got it where it counts."
Re: MapTool 1.5.5 Release Candidate 2 Available
Yeah, I think that's the problem too.Full Bleed wrote: ↑Sat Oct 05, 2019 11:16 pmFYI, I have a 9500x7000 map with 142 small graphic assets on it... and I don't see the issue.
Maybe this?Now to figure out what the heck changed.
https://github.com/RPTools/maptool/pull/611
The framerate got capped at 30fps. I suggest we either make the fps a user setting, or we increase it to 60fps or more.
MT Framework: Call of Cthulhu 7th fork, D&D 5e Spell Library
MT Scenario: Uncle Timothy's Will.
MT Utilities: Handouts, VBL Move Block, Date.
MT Scenario: Uncle Timothy's Will.
MT Utilities: Handouts, VBL Move Block, Date.
- Full Bleed
- Demigod
- Posts: 4736
- Joined: Sun Feb 25, 2007 11:53 am
- Location: FL
Re: MapTool 1.5.5 Release Candidate 2 Available
Wisewolf can probably test by temporarily setting his monitor Refresh rate to 60Hz and see if the issue gets a lot better. I'm betting that he's running a high Hz monitor...
Maptool is the Millennium Falcon of VTT's -- "She may not look like much, but she's got it where it counts."
Re: MapTool 1.5.5 Release Candidate 2 Available
Yes I am using a 120 Hz monitor. I will try this 60Hz limit an test it.Full Bleed wrote: ↑Sun Oct 06, 2019 8:53 amWisewolf can probably test by temporarily setting his monitor Refresh rate to 60Hz and see if the issue gets a lot better. I'm betting that he's running a high Hz monitor...
Re: MapTool 1.5.5 Release Candidate 2 Available
So I changed Hz to 60 and compared both 1.5.4 and 1.5.5. It is still the same, 1.5.5 feels really too much slow. Is there any way to change it?Full Bleed wrote: ↑Sun Oct 06, 2019 8:53 amWisewolf can probably test by temporarily setting his monitor Refresh rate to 60Hz and see if the issue gets a lot better. I'm betting that he's running a high Hz monitor...
- Full Bleed
- Demigod
- Posts: 4736
- Joined: Sun Feb 25, 2007 11:53 am
- Location: FL
Re: MapTool 1.5.5 Release Candidate 2 Available
They're on it for the next version: https://github.com/RPTools/maptool/issues/767
Here is some info on the combination of having a forced lower FPS than your refresh rate and what it can do. This focused on "tearing" but it can also make things stutter before getting to that.
So what I think is happening on your system is that MT is now fixed at 30 FPS. Your monitor is set to 120Hz. So as you drag, it's sitting on a frame for 4 cycles creating a stutter.If the frame rate your computer is producing is different (either higher or lower) that the refresh rate of your monitor, you may experience a glitch known as screen tearing, where information from two or more frames is shown in a single screen draw. It is important to note that screen tearing does no damage to a display or graphics card.
To prevent screen tearing, you can enable a feature called Vertical Synchronization, or VSync. This tells your GPU to synchronize its actions with the display, which forces it to render and send a new frame when the monitor is ready to redraw the screen. This does limit your framerate exactly to the refresh rate. For example, if your refresh rate is 60Hz, VSync will cap your framerate to 60 FPS. If your GPU is capable of producing higher frame rates than the VSync cap you can take advantage of its leftover capacity to increase the resolution, draw distance, or other graphics quality settings. If your graphics card can’t outpace the refresh rate of your display then enabling VSync won’t help much. You may be able to lock your GPU into a lower frame rate, like 30 FPS, that would match up with your monitor. Common display refresh rates include 120hz, 60hz and 30hz, and there are all divisible by 30 so you won’t get screen tearing, but you may get stutter, as each frame will be on the screen for a couple of cycles.
It looks like they are raising the FPS redraw in MT, but I wonder if MT incorporated a Vsync feature if it would actually be the best fix. It seems like someone on a 144Hz monitor with a fixed 60 FPS in MT might still have issues (maybe tearing and not just stuttering since it's not divisible by 30.)
Maptool is the Millennium Falcon of VTT's -- "She may not look like much, but she's got it where it counts."
Re: MapTool 1.5.5 Release Candidate 2 Available
I really have a 144 Hz. sorry I said 120 but I was wrong (bad memory). But I feel the same at 144 and at 60 Hz. Or maybe there is also tearing but I can't see a difference.
Re: MapTool 1.5.5 Release Candidate 2 Available
MT 1.5.7 includes a user prefs setting for this. RC.2 is available for download now.
https://github.com/RPTools/maptool/rele ... 1.5.7-rc.2
Would be nice to get a couple more folks to test it before release.
https://github.com/RPTools/maptool/rele ... 1.5.7-rc.2
Would be nice to get a couple more folks to test it before release.
Re: MapTool 1.5.5 Release Candidate 2 Available
It seems to be working just fine. Thanks!