Search found 5 matches
- Sat Feb 04, 2017 12:16 am
- Forum: GamingTools Public::EQPlayNice Lite
- Topic: EQPlaynice version update?
- Replies: 1
- Views: 18403
EQPlaynice version update?
"This version of EverQuest is not currently supported by EQPlayNice (this is typical on patch days). You may need to report this version information "v2 eqgame.exe Feb 2 2017 20:26:24" to Lavish Software (please do not report this message without giving the version info!). You may continue playing."...
- Sat Feb 04, 2017 12:03 am
- Forum: GamingTools Public::WinEQ 2.0 Lite
- Topic: Feb 3 2017 version issue?
- Replies: 0
- Views: 22400
Feb 3 2017 version issue?
EverQuest (1) I'm unclear if it's an issue specific to WinEQ2 or because of EQPlayNice's failure, but EQ is now crashing moments after I open the game via WinEQ2 (2.15) WinEQ 2 System Information System: ----------------------------------- Windows Version: Windows 7 Ultimate//7601.win7sp1_ldr.161011...
- Fri Feb 03, 2017 11:58 pm
- Forum: GamingTools Public::EQPlayNice Lite
- Topic: Version Update
- Replies: 1
- Views: 18088
- Tue Nov 27, 2007 1:41 am
- Forum: GamingTools Public::WinEQ 2.0 Lite
- Topic: Clip Plane in EQ (WinEQ2)
- Replies: 3
- Views: 4185
Left shit sometimes used by WinEQ (I think?)
Try using the other shift. Let me know if it works for you.
I noticed that when picking up stacks (shift click) I had an issue with the left shift. Rather than trying to figure it out in WinEQ, I compensated by simply using the right shift key.
I noticed that when picking up stacks (shift click) I had an issue with the left shift. Rather than trying to figure it out in WinEQ, I compensated by simply using the right shift key.
- Tue Nov 27, 2007 1:36 am
- Forum: GamingTools Public::WinEQ 2.0 Lite
- Topic: Everquest window resizing issue (not your typical)
- Replies: 1
- Views: 5041
Desktop Resolution
Based on what I think you've described, I would suggest that you check to ensure that your Windows desktop is set to the same resolution at which you have the game running. If the two are indeed the same, and you're having this issue, I'm sorry. (Shrug)