Few Issues with 2.02

WinEQ 2.0 Lite discussion

Moderators: Lavish Software Team, Moderators

Post Reply
Eryi
GamingTools Subscriber
Posts: 8
Joined: Wed Jul 14, 2004 5:52 am

Few Issues with 2.02

Post by Eryi » Wed Nov 10, 2004 12:26 am

Lax,

Few things I've noticed.. The Low Memory Popup in-game.. Is there anyway to turn that off? It was showing up every time the memory free changed (I was bouncing between 6 and 7 MB Physical RAM free, which is fine for a single session) I couldn't find anything in the Options/Preferences for it.

Other thing, I've noticed the Mouse on the desktop is just hidden, but not really removed. This is an issue because poeple who run hidden toolbars end up triggering them if you move the mouse to the edges of the WinEQ window (XP Taskbar, StatBar, ATI Toolbars all come to immediate mind).

I don't know if this was unintentionally introduced trying to get rid of the "Secondary ghost cursor" thing a while back perhapse, or just something unavoidable with 2.x (Did not seem to occure under 1.38).

One last thing, we've seem to have lost the ability to auto-mouse-release on zoning (or during Hihg FPS Lag). Was this intentional?

Thanks ;c)

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Wed Nov 10, 2004 12:49 am

1) It definitely shouldn't come up if the memory increases. It's coded to only come up when the memory decreases. I see the bug now that I take a good look though. When it gets under 10MB remaining, it will spam you. I'll fix that.

2) The mouse works exactly the same as it did in 1.38. I hide my XP task bar and dont see anything different. If you have the mouse captured, you should not see the taskbar come up, though I cant speak for statbar or ati toolbars. I will do what I can to test the issue, but the only way to "fix" this issue would introduce other problems -- I can make the mouse cursor "clip" to the EQ window while captured, but then while loading you wont be able to move the cursor outside that rectangle without hitting the windows key or doing some other silly workaround. All I can really say is that it's done 100% the same way as in 1.38

3) Auto-release isn't in 2.0 at this time, but I will see what I can do to put it in

alexielle
GamingTools Subscriber
Posts: 8
Joined: Sat Jul 10, 2004 3:01 pm

Post by alexielle » Sat Nov 13, 2004 1:20 pm

Hi :)

well another issue noticed ;)
I just tested out dual boxing and (happens sometimes) while switching between the 2 windows I got a black screen on the one I switched on top.
Therefore i used alt + enter to get the everquest screen back :(

--> reset device failed :(

Here are my sysinfo:

WinEQ 2 System Information
System:
-----------------------------------
Windows Version: Microsoft Windows XP/Service Pack 2/2600.xpsp_sp2_rtm.040803-2158
System Physical RAM: 388/767MB
Page File: 3265/3726MB
Virtual Memory: 2001/2047MB (Extended: 0MB)
CPU 1: Intel(R) Celeron(R) CPU 2.66GHz @ 2660MHz
Video 1: \\.\DISPLAY1/WinFast A310 LX
Video 2: \\.\DISPLAYV1/NetMeeting driver
Video 3: \\.\DISPLAYV2/RDPDD Chained DD
Monitor 1: \\.\DISPLAY1 (0,0,1152,864) (1152x864) PRIMARY
Sound: C-Media Wave Device
DirectX: 4.09.00.0904
Internet Explorer: 6.0.2900.2180
WinEQ: 2.02

Direct3D9:
-----------------------------------
Adapter Display Mode: 0x0 D3DFMT_UNKNOWN
Game Display Mode: 0x0 D3DFMT_UNKNOWN
Current Adapter: 0

Direct3D8:
-----------------------------------
Adapter Display Mode: 0x0 D3DFMT_UNKNOWN
Game Display Mode: 0x0 D3DFMT_UNKNOWN
Current Adapter: 0

DirectInput8:
-----------------------------------

EverQuest:
-----------------------------------
Profile 1: WinEQ 2.0 Default Profile
EQ Path: F:\Games\EQ1
EQClient.ini: .\eqclient.ini
Patch: OFF Test Server: OFF Locale: fr
Video Adapter: Application Controlled
Luclin models: 29 (+145 min RAM)
MipMapping: ON (+4 min RAM)
Sound: ON (+22 min RAM)
Dynamic Lighting: ON (+4 min RAM)
Texture Caching: ON (+0 min RAM)
Texture Quality: MEDIUM (+30 min RAM)
Calculated minimum RAM: 488MB (BASE+205MB)
Level of Detail: 1
MaxFPS: 100
Additional setting: VertexShaders=TRUE
Additional setting: 20PixelShaders=FALSE
Additional setting: 1xPixelShaders=TRUE

EQPlayNice:
-----------------------------------
EQ Version: eqgame.exe Oct 11 2004 15:21:50
Foreground
Mode: FPS Limiter
Max FPS: 40
Rendering: 1/1
Background
Mode: CPU Limiter
Max FPS: 30
Rendering: 1/30

that s it ;)
Nothing is forgotten, nothing is ever forgotten

Post Reply