Tile mode problems.

Kaycee · Post by **Kaycee** » Thu Jul 07, 2005 12:49 am

I've been trying to get 2.0 to go into tile mode and have been having no luck there. I've been using the following settings.

Screen Mode: Normal
Preferred Tile: Auto (Also tried forcing tiles)

When I force tiles positions it will load them up in tile mode but I cant toggle out of it and bring them back to normal screen mode. I have my toggle tile key setup as Ctrl+Alt+T and it doesnt do anything.

I loaded up version 1.38 and I have no problems toggling between tile mode and normal screen mode. This version has the same settings that I'm using in 2.0 which is what confuses me.

Any suggestions on getting 2.0 to work for me ?

Thanks
Kaycee

Post by **Lax** » Thu Jul 07, 2005 9:29 am

Make sure auto-tiling is enabled in the main program manually (options->Automatic Tiling) each time you launch it. The setting *should* save between launches, if it doesnt, let me know. With that checked and the profile set to "Auto", it will tile when launched (double checked this a minute ago)

Kaycee · Post by **Kaycee** » Thu Jul 07, 2005 1:46 pm

Verifed automatic tileing was checked and it will start in tile mode but then I cant get it to go back to normal or full screen mode unless I get it to start that way. When I do hit the hotkeys for tile mode it does show the checkbox beside auto tiling and will toggle it also but no change in the video side of things. Course this is on my laptop with a Geforce Go5600 video card but 1.38 does tiling fine no matter what mode it is started in which is really bizarre. Any real difference between 1.38's and 2.0's tiling features ?

Kaycee

Post by **Lax** » Thu Jul 07, 2005 5:29 pm

Not really, no. Just how auto is handled, really. What you might do instead is set up window presets instead of tiling. Set up a preset for each of the 4 corners just how you like them to be, and it's probably going to be better for you than tiling

Kaycee · Post by **Kaycee** » Sun Jul 10, 2005 1:10 am

Sorry for the delay getting back to ya on this one

. Anyway in your post above are you saying to just create 4 presets forcing each one into a position on the screen (basically forcing tile mode)? If doing that is there a way at some point to force a session to go full screen if need be since the toggle option isnt working on this system for some odd reason ? I've played around a lil bit and went with the Omega drivers since HP hasnt updated their video drivers since 2004 lol they seem to be fine so far but still yield the same results. I guess worst case I can migrate back to 1.38 on this system for that feature but I've grown to used to 2.0 lol ;0 Definitely a strange problem for this one for some odd reason.

Kaycee

Kaycee · Post by **Kaycee** » Sun Jul 10, 2005 1:13 am

Oh forgot to mention that this laptop uses a really funky resolution of 1440 x 900 on all sessions and wasnt sure if that would have any bearing on how 2.0 performs tiling vs 1.38. The same resolution works fine with 1.38 tiling and toggling back to full screen mode.

Kaycee

Post by **Lax** » Sun Jul 10, 2005 10:59 am

Well, the problem is this. WinEQ 1.38 considered every different window configuration to be a mode. WinEQ 2.0 considers tiling to be a mode, but everything else is simply a preset that can be applied. Hitting the full screen preset wont disable tile mode, etc.

When you make presets, you can switch between any preset at any time. If you're using the normal preset and hit shift+alt+f, it goes to the full screen preset. If you hit shift+alt+t, it goes to the tiny preset. If you hit <your custom key>, it goes to <your custom preset>. If your custom preset happens to have the window in 1/4 of the screen (scale: .5) with no border, then it's going to look exactly like tiling.

So make 4 presets, one for each corner -- with no border and scale of .5. Set up 4 profiles, set the default preset for each one. Hit shift+alt+f to go to full screen, and hit shift+alt+f again to go back to the previous preset.

Hopefully that takes away some confusion; let me know

Kaycee · Post by **Kaycee** » Sun Jul 10, 2005 5:08 pm

Ah okies I grasp what your saying now

. That'll work for me I think heheh

Thanks again
Kaycee

Kaycee · Post by **Kaycee** » Sun Jul 31, 2005 12:46 pm

Lol I migrated back to my desktop system since the laptop needs to be sent off for service ugh ;0 thank good for extended warranty's

Anyway I have the same tiling issue on this system as well as it doesnt want to respond to Ctrl+Alt+T which is what I have the tiling hotkey setup to.

Here's the sys info text for ya incase you want to take a jab at it

Thanks Kaycee (Oh 1.38 tiles fine with the hotkey lol)

WinEQ 2 System Information
System:
-----------------------------------
Windows Version: Microsoft Windows XP/Service Pack 2/2600.xpsp_sp2_gdr.050301-1519
System Physical RAM: 1043/1535MB
Page File: 2601/2924MB
Virtual Memory: 1936/2047MB (Extended: 0MB)
CPU 1: Intel(R) Pentium(R) 4 CPU 1.80GHz @ 1794MHz
Video 1: \\.\DISPLAY1/NVIDIA GeForce4 Ti 4600
Video 2: \\.\DISPLAYV1/NetMeeting driver
Video 3: \\.\DISPLAYV2/RDPDD Chained DD
Monitor 1: \\.\DISPLAY1 (0,0,1280,1024) (1280x1024) PRIMARY
Sound: SB Live! Audio [DF80]
DirectX: 4.09.00.0904
Internet Explorer: 6.0.2900.2180
WinEQ: 2.08

Loaded Modules:
-----------------------------------
Module 0: C:\Everquest\eqgame.exe
Module 1: C:\WINDOWS\system32\ntdll.dll
Module 2: C:\WINDOWS\system32\kernel32.dll
Module 3: C:\Everquest\mss32.dll
Module 4: C:\WINDOWS\system32\USER32.dll
Module 5: C:\WINDOWS\system32\GDI32.dll
Module 6: C:\WINDOWS\system32\WINMM.dll
Module 7: C:\WINDOWS\system32\ADVAPI32.dll
Module 8: C:\WINDOWS\system32\RPCRT4.dll
Module 9: C:\WINDOWS\system32\WSOCK32.dll
Module 10: C:\WINDOWS\system32\WS2_32.dll
Module 11: C:\WINDOWS\system32\msvcrt.dll
Module 12: C:\WINDOWS\system32\WS2HELP.dll
Module 13: C:\WINDOWS\system32\DINPUT8.dll
Module 14: C:\WINDOWS\system32\IMM32.dll
Module 15: C:\Everquest\DSETUP.dll
Module 16: C:\WINDOWS\system32\VERSION.dll
Module 17: C:\WINDOWS\system32\ole32.dll
Module 18: C:\WINDOWS\system32\SHELL32.dll
Module 19: C:\WINDOWS\system32\SHLWAPI.dll
Module 20: C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_a84f1ff9\comctl32.dll
Module 21: C:\WINDOWS\system32\comctl32.dll
Module 22: C:\Program Files\WinEQ2\WinEQ2.dll
Module 23: C:\WINDOWS\Lavish.dll
Module 24: C:\WINDOWS\system32\PSAPI.DLL
Module 25: C:\Program Files\WinEQ2\WinEQ2-EQ.dll
Module 26: C:\WINDOWS\system32\MSIMG32.dll
Module 27: C:\Program Files\WinEQ2\WinEQ2-D3D9.dll
Module 28: C:\Program Files\WinEQ2\WinEQ2-D3D8.dll
Module 29: C:\Program Files\WinEQ2\WinEQ2-DI8.dll
Module 30: C:\WINDOWS\system32\mswsock.dll
Module 31: C:\WINDOWS\system32\hnetcfg.dll
Module 32: C:\WINDOWS\System32\wshtcpip.dll
Module 33: C:\WINDOWS\system32\DNSAPI.dll
Module 34: C:\WINDOWS\System32\winrnr.dll
Module 35: C:\WINDOWS\system32\WLDAP32.dll
Module 36: C:\WINDOWS\system32\rasadhlp.dll
Module 37: C:\Program Files\WinEQ2\EQPlayNice.dll
Module 38: C:\Program Files\Fellowes\MediaFACE 4.0\MFHookManager.dll
Module 39: C:\WINDOWS\system32\NTMARTA.DLL
Module 40: C:\WINDOWS\system32\SAMLIB.dll
Module 41: C:\Everquest\EQGraphicsDX9.DLL
Module 42: C:\WINDOWS\system32\d3d9.dll
Module 43: C:\WINDOWS\system32\d3d8thk.dll
Module 44: C:\Everquest\dpvs.dll
Module 45: C:\WINDOWS\system32\ctagent.dll
Module 46: C:\WINDOWS\system32\DSOUND.dll
Module 47: C:\Everquest\eqmain.dll
Module 48: C:\WINDOWS\system32\HID.DLL
Module 49: C:\WINDOWS\system32\SETUPAPI.DLL
Module 50: C:\WINDOWS\system32\WINTRUST.dll
Module 51: C:\WINDOWS\system32\CRYPT32.dll
Module 52: C:\WINDOWS\system32\MSASN1.dll
Module 53: C:\WINDOWS\system32\IMAGEHLP.dll

Direct3D9:
-----------------------------------
Driver: NVIDIA GeForce4 Ti 4600/nv4_disp.dll/6/14/10/6693
Adapter Display Mode: 1280x1024 D3DFMT_R5G6B5
Game Display Mode: 1280x1024 D3DFMT_UNKNOWN
Current Adapter: 0
Available Texture Memory: 369MB
Direct3D8:
-----------------------------------
Adapter Display Mode: 0x0 D3DFMT_UNKNOWN
Game Display Mode: 0x0 D3DFMT_UNKNOWN
Current Adapter: 0
Available Texture Memory: (not currently available)
DirectInput8:
-----------------------------------

EverQuest:
-----------------------------------
EQ Path: C:\Everquest
EQClient.ini: .\eqclient.ini
Patch: OFF Test Server: OFF Locale: us
Video Adapter: Application Controlled
Luclin models: 6 (+30 min RAM)
Texture Compression: ON (+0 min RAM)
Texture Caching: ON (+0 min RAM)
Texture Quality: INVALID VALUE 3
Calculated minimum RAM: 313MB (BASE+30MB)
Level of Detail: 1
MaxFPS: 100
Additional setting: HardwareTnL=TRUE
Additional setting: VertexShaders=TRUE
Additional setting: 20PixelShaders=1
Additional setting: 1xPixelShaders=1

EQPlayNice:
-----------------------------------
EQ Version: eqgame.exe Jul 6 2005 17:48:42
Foreground
Mode: FPS Limiter
Max FPS: 40
Rendering: 1/1
Background
Mode: CPU Limiter
Max FPS: 30
Rendering: 1/30

Post by **Lax** » Mon Aug 01, 2005 2:11 pm

Sorry for the late response. It's been so long since I worked with WinEQ 2 tiling, I keep seeing all these things that would work so much better in WinEQ 3 and I'm not able to do much about it until after I release Inner Space

Testing it right now, it appears as though changing the automatic tiling setting does not immediately apply the setting to existing sessions. Any new sessions do get tiled if they are set to auto tile. The tiling hotkey DOES toggle the option, and has the same behavior as changing it manually through the tray.

I will make a few modifications real quick and see if I can get this working more conveniently

Post by **Lax** » Mon Aug 01, 2005 4:07 pm

See if you like it better now (WinEQ 2.09). I think this will work out for you

Kaycee · Post by **Kaycee** » Mon Aug 01, 2005 10:12 pm

RAR. It works perfect for both systems again

. Many thanks for this patch

. Sorry that was a bit of an inconvenience for ya hehe I'm probably that 1 in 100 that had the problem lol

Kaycee

Post by **Lax** » Mon Aug 01, 2005 11:59 pm

Nope, it was just a design flaw in the original tiling code I wrote for WinEQ 2. It didnt really make sense to have a hotkey that wouldnt do anything immediately

Kaycee · Post by **Kaycee** » Tue Aug 02, 2005 1:17 am

One thing I did notice and wasnt sure if this was the intended way it should work but when doing the hotkey for tiling it appearantly only does the current session in which the hotkey was pressed vs 1 session + hotkey putting the other sessions tile mode. so basically I have to go to each session and hit the hot key to get all 3 of em tiled. Not a biggy but just wanted to check with ya on that one

Other than that its great so far.

Thanks again for your hard work

Kaycee

Post by **Lax** » Tue Aug 02, 2005 8:42 am

Yes. It's like this because some people like to switch one session out of tiled mode while they work with it, then go back to tiling.

Alternatively, you can have the tray program's Automatic Tiling option on before you launch any sessions, and if theyre set to automatic they will get tiled so you wont have to hit the hotkey on each