Hello everyone, thank you for taking the time to look at this.
The most critical problem I have is that my game crashes at "awaiting gamestate" when connecting to the FA HARDCORE server, only that server. I can connect to most other servers fine, there is sometimes a crash but I regard that as a separate general instability issue. The secondary issue I have is a horrid frame rate, but it seems as though it's only when I look at, or in the direction of other players. The players do not have to be directly visible, I just have to look in the direction. If I face away I get hundreds of frames per second.
Windows 7 x64 Ultimate
AMD Vishera 4.6Ghz Quad Core
2x Radeon 7870 2Gb (Crossfire)
32 Gb DDR3 G.Skill RAM
I launch with ET-Legacy. I will be playing with stock ET while I wait for response.
I have a feeling the crashing is due to windows 7 issues, and the lag is issues with newer graphics cards.
Are there any specific system settings I should be using foe ET to run properly?
Thank you In advance!
With those PC specs, you should never see 10FPS. My Chipset lists ET as "Not recommended" But ET works fine. The only issue I encounter, is that with cg_shadows 1 the video card (Which is an older EVGA with a GTS450) Is unable to produce a solid shadow, the shadow always flickers, so I turn shadows off. Otherwise, I have pretty much maximum graphics settings and hold 125FPS all day long.
You also should RARELY see a crash.
Have you looked at EventViewer? Go into start menu, run, type Event Viewer and click on the event viewer result that pops up, or just hit enter.
On the left pane, click Windows logs. Then click application. After the results come up, go into the right pane, and click Filter current log. Check the boxes for CRITICAL, WARNING, and ERROR, and click OK.
If you can't remember the last time ET crashed while using Legacy, Launch ET using Legacy, Connect to HC and recreate the crash. Once you do, you can review the logs by the time and date the crash occurred that you just recreated. Make sure to look into Application logs, and use the filter, and it'll give you a really good idea what is causing the problem.