Great! It will be easier to have people check a box and see how it goes rather than add command line code.wolph42 wrote:Im gathering that the latest launcher supports this issue already.
Odd glitch with Maptool
Moderators: dorpond, trevor, Azhrei
Forum rules
PLEASE don't post images of your entire desktop, attach entire campaign files when only a single file is needed, or generally act in some other anti-social behavior.
PLEASE don't post images of your entire desktop, attach entire campaign files when only a single file is needed, or generally act in some other anti-social behavior.
- Full Bleed
- Demigod
- Posts: 4736
- Joined: Sun Feb 25, 2007 11:53 am
- Location: FL
Re: Odd glitch with Maptool
Maptool is the Millennium Falcon of VTT's -- "She may not look like much, but she's got it where it counts."
Re: Odd glitch with Maptool
OP here
And checking the box in the dev version appears to have fixed the problem.
And checking the box in the dev version appears to have fixed the problem.
-
- Cave Troll
- Posts: 36
- Joined: Sat May 19, 2012 3:41 pm
Re: Odd glitch with Maptool
This D3d disable was what I posted earlier <_< I guess nobody wanted to try it.
Re: Odd glitch with Maptool
I just noticed the java options under the troubleshoot tab. *face palm*RevenantBob wrote:This D3d disable was what I posted earlier <_< I guess nobody wanted to try it.
Downloads:
- Notepad++ MapTool addon
- RPEdit details (v1.3)
- Coding Tips: Modularity and Design
- Videos: Macro Writing Tools
- JamzTheMan
- Great Wyrm
- Posts: 1872
- Joined: Mon May 10, 2010 12:59 pm
- Location: Chicagoland
- Contact:
Re: Odd glitch with Maptool
Glad the options fix issues for others as well, I almost didn't add it to the new launcher...
FYI: I had ran into the issue last year on Windows 10 on my main PC and one I remote in on. One required the d3d option and the other OpenGL.
Note, I no longer have the issue and suspect latest drivers fixed the issue. Currently running java 1.8.0_92 and Nvidia drivers 373.06 (and latest Win 10 & DX updates).
FYI: I had ran into the issue last year on Windows 10 on my main PC and one I remote in on. One required the d3d option and the other OpenGL.
Note, I no longer have the issue and suspect latest drivers fixed the issue. Currently running java 1.8.0_92 and Nvidia drivers 373.06 (and latest Win 10 & DX updates).
-Jamz
____________________
Custom MapTool 1.4.x.x Fork: maptool.nerps.net
Custom TokenTool 2.0 Fork: tokentool.nerps.net
More information here: MapTool Nerps! Fork
____________________
Custom MapTool 1.4.x.x Fork: maptool.nerps.net
Custom TokenTool 2.0 Fork: tokentool.nerps.net
More information here: MapTool Nerps! Fork
Re: Odd glitch with Maptool
Hey Guys,
try using this launcher, follow the bugfix instructions and tell me if it fixed your problem:
viewtopic.php?f=10&t=24711
In particular, uncomment line 128, in the launch file to activate the bugfix.
With best regards,
Clyde.
try using this launcher, follow the bugfix instructions and tell me if it fixed your problem:
viewtopic.php?f=10&t=24711
In particular, uncomment line 128, in the launch file to activate the bugfix.
With best regards,
Clyde.
Re: Odd glitch with Maptool
Since this thread's been bumped already, has the most complete solution, and other people seem to be having this problem still:
Maptool 1.5.0 no longer has a launcher, and therefore no longer has a "Disable the Direct3D Pipeline" box to check. If you would like to enable the previously discussed Java Direct3D fix on 1.5.0, open {MapTool install directory}/app/MapTool.cfg and add the following line under [JVMUserOptions]:
-Dsun.java2d.d3d\==false
KG
Maptool 1.5.0 no longer has a launcher, and therefore no longer has a "Disable the Direct3D Pipeline" box to check. If you would like to enable the previously discussed Java Direct3D fix on 1.5.0, open {MapTool install directory}/app/MapTool.cfg and add the following line under [JVMUserOptions]:
-Dsun.java2d.d3d\==false
KG
Re: Odd glitch with Maptool
Not completely accurate. The launch options are now set inside of MapTool under Edit -> Preferences -> Startup. You set them there and then restart.Maptool 1.5.0 no longer has a launcher, and therefore no longer has a "Disable the Direct3D Pipeline" box to check.