Model: Dell Aurora R11
o/s: Windows 10 home 64 bit (VASSAL uses 32-bit function)
CPU: Intel i9
Memory: 32Gb
Video: NVIDIA GeForce RTX2070 SUPER 8Gb
VASSAL: 3.4.6
Java: Version 8 update 271
Module: Advanced Squad Leader (VASL) v6.6.1
An occasional, and usually unpredictable, problem occurs during play, often when I click a function or button that opens a sub-window: the display suddenly breaks up into several partial images of the game overlaid one on top of the other, and most of the function buttons that control the game disappear. I have screenshots which illustrate the problem, but can’t find how to send these because the files are too big to attach (screen resolution is 2560x1440).
I also can’t attach a log file because as soon as the fault occurs the ‘End logfile’ instruction doesn’t work. However, in case it helps I attach a saved game file from which I have been able to re-create the problem. If I load this and simply click the ‘OBA’ button top-left (which should open a sub-window), the screen immediately breaks up as I have described. Moreover, this broken screen image is not static, but changes - images of the game appear and disappear superimposed on one another simply by my moving the mouse.
Hope you can help. Happy to send screenshots if you can advise me how.
Thus spake UKtraveller19 via messages:
Model: Dell Aurora R11
o/s: Windows 10 home 64 bit (VASSAL uses 32-bit function)
CPU: Intel i9
Memory: 32Gb
Video: NVIDIA GeForce RTX2070 SUPER 8Gb
VASSAL: 3.4.6
Java: Version 8 update 271
Module: Advanced Squad Leader (VASL) v6.6.1
An occasional, and usually unpredictable, problem occurs during play,
often when I click a function or button that opens a sub-window: the
display suddenly breaks up into several partial images of the game
overlaid one on top of the other, and most of the function buttons that
control the game disappear. I have screenshots which illustrate the
problem, but can’t find how to send these because the files are too big
to attach (screen resolution is 2560x1440).
This is likely a graphics driver problem.
Look in the Preferences for “Disable DirectX D3D pipeline?” and check
that. Does the problem still occur after you’ve done that and restarted?
–
J.
Thanks for the suggestion, I wondered if it was the graphics driver too, but I’ve made sure I’ve got the latest version of this. I’ve tried checking “Disable DirectX D3D pipeline?”, and unfortunately it makes no difference - the problem is still there. Moreover, the box does not stay checked when I close the module and then restart it - it appears unchecked again. Am I doing something wrong?
Thanks again for any help you can give.
Thus spake UKtraveller19 via messages:
Thanks for the suggestion, I wondered if it was the graphics driver too,
but I’ve made sure I’ve got the latest version of this. I’ve tried
checking “Disable DirectX D3D pipeline?”, and unfortunately it makes no
difference - the problem is still there. Moreover, the box does not stay
checked when I close the module and then restart it - it appears
unchecked again. Am I doing something wrong?
Did you close VASSAL entirely after checking the box?
Also: What do you mean by “used 32-bit function” here?
o/s: Windows 10 home 64 bit (VASSAL uses 32-bit function)
–
J.
Hi, thanks for getting back to me. Yes, I closed VASSAL entirely after checking the box. I’ve just done it again after checking the box, and again the box is no longer checked when I reopen it. Other Preference boxes don’t do this - they stay checked once I’ve clicked OK.
Sorry, reference to 32-bit was probably incorrect. I meant that my C drive has two program folders: one is Program Files, the other is Program Files (x86). VASSAL and VASL are both in the Program Files folder.
Does the preference stick if you set it in 3.5.0-beta1 instead?
github.com/vassalengine/vassal/ … .5.0-beta1
Just tried it with 3.5.0 and no, the preference doesn’t stick.
I could presumably try setting the preference every time i start the game, and see if that makes a difference?
Thus spake UKtraveller19 via messages:
Just tried it with 3.5.0 and no, the preference doesn’t stick.
I could presumably try setting the preference every time i start the
game, and see if that makes a difference?
If the pref doesn’t stick, you’ll never get the Player to start with it
checked, which is what needs to happen for turning D3D off.
Do any prefs stick for you between runs of VASSAL? E.g., what if you
go to Tools > Server Status in the Module Manager, exit the MM, and then
restart it? Does it restart with the Server Status pane showing?
–
J.
As far as I can tell, the D3D box is the only one that doesn’t stay checked when I close VASSAL and reopen. I’ve changed several other preferences with no problem and even the ones that say “(needs restart)” - which the D3D box doesn’t - remain checked and working with no problem.
This includes the Server Status box in the Module Manager. I’ve checked it, closed and reopened VASSAL, and it stays checked. However, I can’t see any new pane either before or after restarting (not sure what this is supposed to look like but there’s certainly no new window).
Would you post the contents of C:\Users<username>\AppData\Roaming\VASSAL\prefs\V_Global here? That’s the prefs file where the relevant preference is saved. (Replace in the path with whatever your username is.)
Hi, contents of this file is:
#Tue Dec 01 16:24:04 GMT 2020
Locale=en
mainWindowWidth=2576
RecentModules=C:\Users\Andy Bagley\Desktop\vasl-6.6.1.vmod
mainWindowRemember=true
modulesDir=C:\Users\Andy Bagley
disableD3d=false
showServerStatus=true
ServerSelected=#Sun Nov 29 17:35:31 GMT 2020\r\ndescription=VASSAL Server\r\ntype=official\r\n
initialHeap=256
mainWindowHeight=1416
nextVersionCheck=1757188747809
moduleManagerDividerLocation=1053
ServerImpl=#Mon Nov 30 16:15:58 GMT 2020\r\ndescription=VASSAL Legacy Server\r\ndynamic=node\r\ntype=node\r\nurl=http\://www.vassalengine.org/util/getServerImpl\r\n
welcomeWizard=true
wakeUpSound=default
ServerAddressBook=mode=server|description=P2P Network|serverPw=xyzzy|listenPort=5050|type=peer2peer,jabberPassword=|description=VASSALJabber Server|jabberLogin=|dynamic=jabber|type=dynamic,description=VASSAL Legacy Server|dynamic=node|type=node
BoundsOfModuleManager=643,223,1079,468
maximumHeap=512
Thus spake UKtraveller19 via messages:
disableD3d=false
Close VASSAL.
Edit this line (use Notepad or a real text editor) so it says
disableD3d=true
instead.
Restart VASSAL. Does the preference show as set then?
–
J.
OK, I’ve done this and the D3d box stays checked. Better still, it seems to have solved the original problem! Or at least, the problem hasn’t recurred whilst I’ve been playing today, and the various ways I’ve re-created it in the past haven’t done so yet.
If the problem comes back I’ll let you know. Otherwise, thank you very much indeed for your help on this.
Thus spake UKtraveller19 via messages:
OK, I’ve done this and the D3d box stays checked. Better still, it seems
to have solved the original problem! Or at least, the problem hasn’t
recurred whilst I’ve been playing today, and the various ways I’ve
re-created it in the past haven’t done so yet.
If the problem comes back I’ll let you know. Otherwise, thank you very
much indeed for your help on this.
You’re welcome.
I suspect the issue you had with the pref not sticking was a permissions
problem of some sort.
–
J.