EQInterface Forums

EQInterface Forums (http://www.eqinterface.com/forums/index.php)
-   SOE Corner (http://www.eqinterface.com/forums/forumdisplay.php?f=57)
-   -   3D Target Ring - Some Answers (http://www.eqinterface.com/forums/showthread.php?t=11073)

Roger Sewell 11-07-2003 12:33 PM

3D Target Ring - Same Answers
 
Well after a few days of looking over all the problems with the Target Indicator, this is what I have found.

1) Target Indicator is not going to work with these Video Cards: (All Unsupported with EQ)

A) ATI Rage Pro
B) Intel Onboard (828**)
C) Rage Mobility (Laptop)
D) TnT2

I'm sure that I'm missing a few, but you can find a complete list of supported video cards HERE

2) We're looking into an issue with the Radeon 9600 cards that dont' seem to be displaying the Target Indicator. If you have a Radeon 9600, take a look in your DBG.txt file in your EverQuest directory and see if you have this line:
Quote:
Forcing No TnL in t3dEnumDevices().

If you do see this line, then you have what we're looking into at this time. Please be patient with us as we try to resolve this problem as quickly as possible.

At this time, if you have a Radeon 9600 card, I'm suggesting you add the line: UseTNL=1 ...to your EQClient.ini file to see if that helps. Thank you all for the assistance in resolving this matter.

ssyxz 11-07-2003 12:46 PM

9200
 
I have a 9200 card, and have the same problem. The error line above (force no TNL) occurs in my dbg.txt file, no matter what I set UseTNL to (tried TRUE, FALSE, 1 and 0). I placed it in the [Defaults] section, this the right place?

myanta 11-07-2003 12:58 PM

Also happening with Mobility Radeon 7500.
This is from my dbg file:

[Fri Nov 07 11:38:47 2003]00001:Starting EverQuest.

[Fri Nov 07 11:38:47 2003]00002:Init point a.

[Fri Nov 07 11:38:47 2003]00003:Init point b.

[Fri Nov 07 11:38:47 2003]00004:Init point c.

[Fri Nov 07 11:38:47 2003]00005:Init point d.

[Fri Nov 07 11:38:47 2003]00006:Init point d1.

[Fri Nov 07 11:38:47 2003]00007:Init point d2.

[Fri Nov 07 11:38:47 2003]00008:Init point e.

[Fri Nov 07 11:38:47 2003]00009:Init point f.

[Fri Nov 07 11:38:47 2003]00010:Init point g.

[Fri Nov 07 11:38:47 2003]00011:Init point h.

[Fri Nov 07 11:38:47 2003]00000:Found adapter #0 - MOBILITY RADEON 7500

[Fri Nov 07 11:38:47 2003]00001:Forcing No TnL in t3dEnumDevices().

[Fri Nov 07 11:38:47 2003]00002:Adapter #0 - MOBILITY RADEON 7500 :

[Fri Nov 07 11:38:47 2003]00003:32Bit = 1, D32 = 0, D24 = 1, D16 = 1

[Fri Nov 07 11:38:47 2003]00004:16Bit(565) = 1, D32 = 0, D24 = 1, D16 = 1

[Fri Nov 07 11:38:47 2003]00005:16Bit(1555) = 0, D32 = 0, D24 = 0, D16 = 0

[Fri Nov 07 11:38:47 2003]00012:Init point i.

[Fri Nov 07 11:38:47 2003]00013:Init point j.

[Fri Nov 07 11:38:47 2003]00014:Init point k.

[Fri Nov 07 11:38:47 2003]00015:Init done.

[Fri Nov 07 11:38:47 2003]00000:Entering eqmain.dll
[Fri Nov 07 11:38:47 2003]00001:FE: Found adapter #0 - MOBILITY RADEON 7500

[Fri Nov 07 11:38:47 2003]00002:FE: Forcing No TnL in t3dEnumDevices().

[Fri Nov 07 11:38:47 2003]00003:FE: Adapter #0 - MOBILITY RADEON 7500 :

[Fri Nov 07 11:38:47 2003]00004:FE: 32Bit = 1, D32 = 0, D24 = 1, D16 = 1

[Fri Nov 07 11:38:47 2003]00005:FE: 16Bit(565) = 1, D32 = 0, D24 = 1, D16 = 1

[Fri Nov 07 11:38:47 2003]00006:FE: 16Bit(1555) = 0, D32 = 0, D24 = 0, D16 = 0

[Fri Nov 07 11:38:48 2003]00007:FE: t3dInitializeDevice: Using 32bit mode.

[Fri Nov 07 11:38:48 2003]00008:FE: t3dInitializeDevice: Using 24bit depth buffer.

[Fri Nov 07 11:38:48 2003]00009:t3dInitializeDevice: Using Software Vertex processing. (forced)

[Fri Nov 07 11:38:48 2003]00010:FE: Before Create Device

[Fri Nov 07 11:38:48 2003]00011:FE: After Create Device

[Fri Nov 07 11:38:48 2003]00012:FE: Create Succeded

[Fri Nov 07 11:38:48 2003]00013:FE: Before Get Backbuffer

[Fri Nov 07 11:38:48 2003]00014:FE: Before Get Device Caps

[Fri Nov 07 11:38:48 2003]00015:FE: Before Create Viewport

[Fri Nov 07 11:38:48 2003]00016:FE: t3dInitializeDevice: t3dD3DCreateViewport Succeded.

[Fri Nov 07 11:38:48 2003]00017:FE: Before Set Default Render State

[Fri Nov 07 11:38:48 2003]00018:FE: Before Init Buffers

[Fri Nov 07 11:38:48 2003]00019:FE: Before GetAvailableTextureMem

[Fri Nov 07 11:38:48 2003]00020:FE: t3dInitializeDevice completed successfully.

Roger Sewell 11-07-2003 01:24 PM

Quote:
1) Target Indicator is not going to work with these Video Cards: (All Unsupported with EQ)

A) ATI Rage Pro
B) Intel Onboard (828**)
C) Rage Mobility (Laptop)
D) TnT2



Sorry bud, that laptop isn't going to display that 3D Target Ring.

xarquid 11-07-2003 02:22 PM

Fix?
 
Any fix for this in sight?

UseTNL=1 did not work.

I also have the Mobility 7500.

=(

Roger Sewell 11-07-2003 02:51 PM

.
 
To be honest with you, the answer is no. Laptops have never been supported by EverQuest and that Mobility Card just can't perform the functions necessary to run that 3D Target Window.

Cairenn 11-07-2003 06:09 PM

Roger, thank you for taking time out of your day to come over and post this information here as well as at the SOE EQ Tech Help forums. It is appreciated. :)

Pand 11-07-2003 09:33 PM

GeForce 5200 FX not working either
 
GeForce 5200 FX not working either

Kambing 11-07-2003 11:45 PM

Quote:
To be honest with you, the answer is no. Laptops have never been supported by EverQuest and that Mobility Card just can't perform the functions necessary to run that 3D Target Window.


Not to be a stickler, but does that quote include all Radeon Mobility chips, because:

http://www.ati.com/products/compari...comparison.html

The original Mobility doesn't support hardware TNL it seems, but it looks like the m7500 (which is what the poster had) and m9600 do.

Although, it looks like the ring indicator is an ATI specific problem, and usually when these things get fixed up for the desktop cards, the laptop cards follow in suit, regardless of their supported status or not.

EDIT:

To reinforce that (to give hope to all the stepchild mobility 7500/9600 users like myself):

http://mirror.ati.com/support/infobase/4034.html

And sorry if my info is off. I haven't kept up-to-date on graphic card specs for a few years now =/

dedara 11-08-2003 03:40 AM

Quote:
Pand GeForce 5200 FX not working either


I have GF 5200 FX and on my system it works....

Thomus 11-08-2003 06:08 AM

/wave Roger!

:)

Kudane 11-08-2003 11:57 AM

Thanks Roger for coming over, and posting! I know your a fairly busy person, especially after a patch!

/bow

I am sure the bugs will be worked out soon enough...(ok maybe not soon enough for those having issues, hehehehe)

elricfate 11-08-2003 03:25 PM

/e grumbles..

It sucks to be a broke white boy nowadays. I've had a Riva TNT2 for a good while because it's played all the games I wanted it to.. But it's not supported, and I can't get a better one.

You're telling me there is NO possible way it can run the 3D Target Ring? I even went and designed my own, hehe...

-Adyuinne, Morell Thule

lokidecat 11-08-2003 06:12 PM

Apparently, broken on the Radeon9600 as well.

Same TNL message in dbg.txt.

*sigh*

Using Catalyst 3.8 and 3.9 versions of the drivers.

Weskat 11-08-2003 06:51 PM

Appears to be an issue with the ATI Radeon 9600 series and the target ring. Roger started a thread at the EQ Live tech support forum regarding this. He has requested that anyone with issues with the target ring post the video card that they are using and the drivers that they are using in this thread. He has also posted a possible fix and asked that we try the fix before posting (link for the fix is in his post.)
In some kinda famous words from Roger, Tech support is aware of the problem and is looking into it. (Not an exact quote, but pretty darn close.)

On the same issue, a separate but possible fix is using a program called 3DAnalyzer, the discussion is in this thread. Haven't logged in myself since before the patch due to other issues, but I will probably be adding myself to the list (using ATI Radeon 9600 PRO.)

Well GL all resolving this issue.


All times are GMT -5. The time now is 06:23 PM.

vBulletin Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.