dkohl

Yes. I am using FSAA, but it shouldn't require 64MB, should it? It appears from the AGPMem report that I only have 64MB on board.I had an idea -- could this have something to do with my AGP Aperture size? It is set to 64MB. I had read that one should keep the Aperture as small as possible, but maybe the 64MB size is too small for the 128MB card, even though it was fine for the 64MB card.Thoughts?-DK----Fly! II v230Dell 8200 P4/1.8G, 512MB RAM, Nvidia GF4 Ti4600 v28.83, WinXP Home Edition.CH Pro Pedals and Yoke USB.

Got my new VisionTek XTasy GF4 4600 today. Very excited. I pulled out my Ti200 and put in the Ti4600, made sure to uninstall and then totally re-install the Nvidia 28.83 drivers, setup the desktop, and then added some extra slots to my slow RENDER.ini file. When I launched Fly, I got the famous SVertex Index... error. From prior posts, I gather that indicates I exceeded the amount of video memory available.I ran AGPMem.exe to see what's going on and got a report as noted in the attached picture below...http://ftp.avsim.com/dcforum/User_files/3cd9dc8f6577331c.jpgI also checked the display settings, and all appears to be in order...http://ftp.avsim.com/dcforum/User_files/3cd9dc3764e34c77.jpgHere is my RENDER.ini, which according to the "TexMem Calculator" (Excel), only takes up 110MB of video memory.{Graphics}premultiplyColorAndAlpha=0allowAutoMipMapping=0directTextureFlag=0mipLevelCount=7vertexIndexFormat=0{Textures}maxTextures32=16maxTextures32_565=32maxTextures64=16maxTextures64_565=120maxTextures128=100maxTextures128_565=300maxTextures256=100maxTextures256_565=400maxTextures512=8maxTextures512_565=0maxTextures1024=2mipMapFlag=896{NonAGP}maxTextures256_565=0{AGP}maxTextures256_565=0Any ideas what's going on? The card works fine with my old Render.ini, which only took up 60MB of video RAM, but in using it, I don't get a huge improvement in framerates b/c I'm still under-allocating tex slots.Help is appreciated. I'm waaaayyyy too excited to see an improvement to be disappointed like this.-DK----Fly! II v230Dell 8200 P4/1.8G, 512MB RAM, Nvidia GF4 Ti4600 v28.83, WinXP Home Edition.CH Pro Pedals and Yoke USB.

I took the dive and purchased a GF4 Ti4600 yesterday. Its in the mail, but when I install it, I'll have my GF3 Ti200 available. I bought it in October, so its got six months wear-and-tear on it. Good card, but I want the extra power.I considered putting it up for sale on eBay, but preferred to offer it to my Fly "friends". If you're interested in the video card, please send me an email. I guess I'll take the highest bidder between now and next Monday 5/13. Based on market price, I'd like to ask for a minimum $50 bid. I'll post a note to this thread when the sale is over, just to let everyone know.NOTE: I am selling this card "as is" with no manuals or drivers. You'll have to download them from NVIDIA (I currently use v28.83 and DirectX 8.1 on WinXP with no problem). I'll ship the card in the box my new Ti4600 comes in. That said, I'm not looking to take someone's money and run. If you purchase the card and it doesn't work in your system, I'll swap it back - no problem. We're all "friends" on this forum. I'm hoping to recoup some of the cash outlay for the Ti4600, and would prefer to do so here in AVSIM, rather than on some faceless auction like eBay.Good luck. -DK---Fly! II v230Dell 8200 P4/1.8G, 512MB RAM, Nvidia 64MB Ti200 v28.83, WinXP Home Edition.CH Pro Pedals and Yoke USB.

It was a good try, but after removing almost all of the above programs from memory, I get exactly the rates from before. I do fine in, say, San Francisco. With default SF scenery, I get in the mid-teens on the ground and in the 20's for the first 10,000 or so feet. 30's thereafter. In NYC area using Scott's NYC, LGA and JFK, though, I still get terrible stutters and when turning on the ground (from taxiway to runway, for example), I am reduced to less than 4FPS. Approaches into LGA are below 10FPS.I've tried this, btw, with and without Anti-Aliasing. Very little difference.Any other suggestions?And BTW, Clinton - you've still not answered my question about cockpit when at 1600 x 1200: What do your panels look like? Do you get any panels when looking left or right? I tried 1600 x 1200 and although I did increase FPS, I got no panels except when looking directly forward, and then they were too small to read. Can you post a panel screenshot or two?-DK----Fly! II v230Dell 8200 P4/1.8G, 512MB RAM, Nvidia 64MB Ti200 v28.83, WinXP Home Edition.CH Pro Pedals and Yoke USB.

My stats you requested are below. Note that there is only one application running - "Fly2.exe" so I didn't bother taking a screenshot of the APPS tab.Any ideas?----Fly! II v230Dell 8200 P4/1.8G, 512MB RAM, Nvidia 64MB Ti200 v28.83, WinXP Home Edition.CH Pro Pedals and Yoke USB.

I have a Dell 8200. Does this post above apply to my model? How can I find out which chipset I have?-DK----Fly! II v230 on a P4/1.8G, 512MB RAM, nVidia 64MB Ti200, WinXP.CH Pro Pedals and Yoke USB.

Thanks Clint for joining in on the discussion. I will take care of this over the weekend and post results. Hey... any idea what the "via chip" comment was from Tonyc....>> I think you need to check your agp drivers if it's a via chip that your motherboard has on it. Wondering what he meant.-DK----Fly! II v230 on a P4/1.8G, 512MB RAM, nVidia 64MB Ti200, WinXP.CH Pro Pedals and Yoke USB.

My AGP Aperture is at 64mb. This seems to work the best for me. When I got to 32MB, I seem to get the SVertexIndex error, or something like that. I understand from the old forum that this error occured when you ran out of memory on your video card. 64MB gives me a pretty steady framerate, albiet low.Can you send along your RENDER.ini? Since you have the same card I have, maybe I can take some tips from you.BTW: I did rename my FLY.ini and RENDER.ini and tried to start with that fresh (have Fly re-generate them). While in areas like San Francisco, which is all default scenery in my setup, I have no problems. It's just in areas with heavy TM buildings. NYC area is the worst. Philly is bad (the Philly airport). I had EWR also for a while, but eventually deleted it b/c its the same high poly count as Philly. Fort Lauderdale airport is also high poly count.Bottom line, when I have default TRI scenery areas, TerraScene areas with only a few buildings, or default ground with no buildings, I have good rates. When I fly anywhere near areas with TM buildings, I drop off to the teens and even into the single digits (NYC especially).By the way, can you explain what you mean by this...I think you need to check your agp drivers if it's a via chip that your motherboard has on it. What do you mean, a "via chip". I have a Dell Dimension 8200. Its an Intel P4/1.8GB processor. Would this machine have this "via chip"?Please explain. Maybe you're on to something.-DK----Fly! II v230 on a P4/1.8G, 512MB RAM, nVidia 64MB Ti200, WinXP.CH Pro Pedals and Yoke USB.

Pascal:I've tried all kinds of settings, including increasing the 64 slots way up. Thank you for the advice, but in this particular case, I've not found increasing these slots to be helpful. One thing I'm having trouble understanding is what the three lines in the DEBUG screen actually mean? What's the difference between MAX and UNIQUE? And what does "O,T" mean? Also, how does one tell if the 256-bit or 128-bit slots are low?-DK----Fly! II v230 on a P4/1.8G, 512MB RAM, nVidia 64MB Ti200, WinXP.CH Pro Pedals and Yoke USB.

FYI, I have also attached an example screen-shot from LGA facing SW toward Manhattan. In this shot, my engines are off, the plane is not moving. I get 4FPS (or less, actually) and my video card is not even re-drawing moving objects. I also uploaded the version of my RENDER.ini used for that flight.A few notes:1 - I've tried both TM128 and TM256 texture packs. I am using v211 (latest as far as I know).2 - I've tried tweaking RENDER.ini files heavy on 128 textures and heavy on 256 textures. The one I uploaded in my original post seems to do the best overall, while using TM128 textures. The attached RENDER.ini below was an attempt to increase 256 slots in order to better handle the demands of the NYC area scenery.3 - I only seem to have problems in areas with lots of TM buildings. Flying in generic areas with no (or few) TM's has no problems. Also, flying in default TRI locations, such as San Francisco, have no problem even though there are buildings.Hope someone can help save me $400 on a new card.-DK----Fly! II v230 on a P4/1.8G, 512MB RAM, nVidia 64MB Ti200, WinXP.CH Pro Pedals and Yoke USB.

After months of tweaking RENDER.ini and Fly.ini, I'm still very frustrated with my framerates. I'm absolutely amazed I'm having trouble given my system spex (below). Any last minute advice? I hate to drop $399 for a GF4 4600, when I just bought the setup below in the Fall. But I am so frustrated flying around areas with lots of TM buildings (eg; NYC in particular) that I'm about to throw in the towel.I'm uploading my FLY.ini and RENDER.ini, hoping someone can comment.-DK----Fly! II v230 on a P4/1.8G, 512MB RAM, nVidia 64MB Ti200, WinXP.CH Pro Pedals and Yoke USB.

Thanks for the rapid response. Any way to "automate" that? Perhaps put a "flag" or a button-macro on the left side of the message area? -DK----Fly! II v230 on a P4/1.8G, 512MB RAM, nVidia 64MB Ti200, WinXP.CH Pro Pedals and Yoke USB.

In the old forum, if you wanted to post an image in-line with the text, you would copy the link to the image into the text and the forum software would display the image where you pasted the link.I can't seem to get that to work on this new forum. Is this possible?-DK----Fly! II v230 on a P4/1.8G, 512MB RAM, nVidia 64MB Ti200, WinXP.CH Pro Pedals and Yoke USB.