![]() |
|
|
|
#1
|
|||
|
Thank you both!
I tried the Duxa thing and it seems a bit outdated? I cant currently get into the game with its settings. So I went back and manually re-installed everything and was able to get back into the game. One thing that DID work was turning down my FPS to about 60 (prev @ 100). Animations are slow or unavailable but I seem to be able to play with a lot of lag. And the game boots me often. How would I be able to tell if my computer is a dual processor? someone mentioned that if I crtl/alt/delete and click to Preferences - a dual core would have two CPU graphs. If thats the case then I have a single core processor. Really hoping to play this game but it looks like it will be too laggy with my current setup Thanks again for the feedback! Oh and if anyone is ever referencing this thread in the future, Duxa's thingie is here: http://www.project1999.org/forums/sh...ad.php?t=28335 | ||
|
#2
|
||||
|
Quote:
So basically, if it's a fresh install, run option (1) which will run EqEmu to update the game.... If you have a running copy then use the other options without any worry.
__________________
| |||
|
#3
|
||||
|
Quote:
When I tried to run the EqEmu, I got an error message saying that I needed to download update files for EqEmu. I clicked "ok" and it tried to download, then got another error message saying something like "Need the latest version of .NET Framework" I have no idea what that means lol I'm not the most tech savvy person. I basically only got as far as I did with Project 1999 by following super strict orders from the Get Started page. I'm still having the hypserspeed issue along with frequent crashes but I'm afraid I've run out of ideas on how to fix this =( | |||
|
#4
|
||||
|
Quote:
| |||
|
#5
|
||||
|
Quote:
I tried the multicore option and it gave me a new desktop icon to click instead of the original (modified) shortcut. When I click on that my screen blinks for a moment but nothing else happens. It seems I can only access the game through the original shortcut. I also looked it up and my system is a single core processor. Also: anyone notice if their version of Direct X matters? I'm pretty sure I'm current but maybe that is having an effect as well? Again, I'm no tech expert. I think I'm starting to guess random things now =p | |||
|
#6
|
||||
|
Quote:
That will let you run eqemu. Make sure your graphics drivers are up to date. Run windows update. Run dxdiag and paste results into here.
__________________
| |||
|
#7
|
||||
|
Quote:
Here are the highlights of my dxdiag: ------------------ System Information ------------------ Time of this report: 1/26/2012, 23:48:23 Machine name: BECKY Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_gdr.111025-1629) Language: English (Regional Setting: English) System Manufacturer: Shuttle Inc System Model: SN68S BIOS: Phoenix - Award BIOS v6.00PG Processor: AMD Athlon(tm) 64 X2 Dual Core Processor 5600+, MMX, 3DNow (2 CPUs), ~2.8GHz Memory: 2046MB RAM Page File: 2191MB used, 1745MB available Windows Dir: C:\WINDOWS DirectX Version: DirectX 9.0c (4.09.0000.0904) DX Setup Parameters: Not found DxDiag Version: 5.03.2600.5512 32bit Unicode ------------ DxDiag Notes ------------ DirectX Files Tab: No problems found. Display Tab 1: No problems found. Sound Tab 1: No problems found. Music Tab: No problems found. Input Tab: No problems found. Network Tab: No problems found. --------------- Display Devices --------------- Card name: NVIDIA GeForce 8600 GT Manufacturer: NVIDIA Chip type: GeForce 8600 GT DAC type: Integrated RAMDAC Device Key: Enum\PCI\VEN_10DE&DEV_0402&SUBSYS_C7503842&REV_A1 Display Memory: 256.0 MB Current Mode: 1360 x 768 (32 bit) (60Hz) Monitor: ViewSonic N2635w Monitor Max Res: 1360,768 Driver Name: nv4_disp.dll Driver Version: 6.14.0011.5827 (English) DDI Version: 9 (or higher) Driver Attributes: Final Retail Driver Date/Size: 5/10/2007 14:03:00, 5421312 bytes WHQL Logo'd: n/a WHQL Date Stamp: n/a VDD: n/a Mini VDD: nv4_mini.sys Mini VDD Date: 5/10/2007 14:03:00, 6738432 bytes Device Identifier: {D7B71E3E-4742-11CF-314D-5BE700C2CB35} Vendor ID: 0x10DE Device ID: 0x0402 SubSys ID: 0xC7503842 Revision ID: 0x00A1 Revision ID: 0x00A1 I just double checked and my graphics drivers and DirectX are all up to date. Should I run Duxa's program again now that my .NET is updated? | |||
![]() |
|
|