|
|
#2895421 - 11/05/09 07:11 PM
Vista 64 kicking my arse...
|
Junior Member
Registered: 09/09/09
Posts: 90
|
Cant get EECH to run on this sucker. It flickers when i start and then locks up and gives the d3d error. Once I made it to the options screen. I deleted eech.ini and the game cfg before I started the game.
Nvidia 1.91 drivers on 8600GT P4 2.4 ghz Compatibility set to run as w98
Anything special to do in Vista64? What am I missing?
Thanks, GLB
Edited by BammerVB (11/05/09 07:12 PM)
|
|
Top
|
|
|
|
#2895440 - 11/05/09 07:39 PM
Re: Vista 64 kicking my arse...
[Re: BammerVB]
|
3D GuRu
Senior Member
Registered: 01/26/02
Posts: 3541
Loc: 3rd Stone from the Sun !!
|
did you try running in WinXP Compatibility??
_________________________
Intel i5 2500k 4.50ghz / G.Skill RipJaws X 8gb / CM Hyper 212+ Heatsink & Fan / Asus P8Z68-V Gen3 Mobo / 2 Evga 480GTX SLI / RocketFish SC 7.1 / 3 - Sharp DLP XR-10XL's / 3 - 45" Screens w/Screen Goo / nVidia 3D vision / Win7 64bit OS / ThrustMaster Cougar HOTAS / Cougar MFD's / CM HAF 932 Full Tower / nVidia 3D Vision / Thrustmaster MFD's
|
|
Top
|
|
|
|
#2895603 - 11/06/09 03:48 AM
Re: Vista 64 kicking my arse...
[Re: The Nephilim]
|
Junior Member
Registered: 09/09/09
Posts: 90
|
Yeah, tried that first. Anyone running EECH on Vista 64? Beuler?
|
|
Top
|
|
|
|
#2895608 - 11/06/09 04:04 AM
Re: Vista 64 kicking my arse...
[Re: BammerVB]
|
Member
Registered: 06/21/08
Posts: 199
|
I've been running it on Windows 7 x64 (not the same I know) Core i7 920 GTX260 (191.07 driver) I run it only for debug, so I can't vouch for actual flight/controller performance. I've seen some strange freeze issues with the front-end UI - but the game itself in campaign mode has been rock solid (including following flights in 3D, not just the mapping). I also did the eech.ini delete thing (a few times - I like to play around!) and then adjusted a few things - my graphics section is below: Not sure what machine you have, but I get ~180fps in a non-debug build (equivalent to 1.12.2) with a Taiwan campaign, with the settings below - of which the only odd one is "notnl=1" I think. You might need a smaller cbar, depending on your machine. Oh and this is running in windowed mode at 1024 x 768 IIRC. If you're feeling lucky there's also a Beta driver (195.39) from the end of last month - they claim it has 200 bugfixes, so you never know nVidia Drivers
[Graphics and Textures]
cbar=40000.0 # distance that city blocks resolve (n = meters) (def = 500)
fs=0 # full screen mode (0 = window mode, 1 = full screen mode) (def = 1)
mfr=120 # maximum visual frame rate (n = frame rate) (def = 30)
32bit=1 # 32-bit rendering (0 = off, 1 = on) (def = 1)
nrt=0 # rendering to texture (0 = enabled, 1 = disabled) (def = 0) (disable in case of visual problems with MFDs or TADS)
notnl=1 # GeForce "TnL" support (0 = enabled, 1 = disabled) (def = 0)
nodx9zbufferfix=0 # Disable the dx9 zbuffer fix introduced in 1.11.1. In case it causes graphical problems
3dreset=0 # reset screen resolution to 640x480 (0 = off, 1 = on) (def = 0)
dxtm=1 # DirectX texture management (should fix "unable to allocate hardware slot" error) (0 = off, 1 = on) (def = 0)
cg=0 # (clean graphics) re-installs graphics files (0 = off, 1 = on) (def = 0)
palette=0 # use textures.pal (if videocard supports it) (0 = off, 1 = on) (def = 1) (recommended = 0)
eofullrange=0 # eo ranges near to max fog distance (and objects are drawn up to it) 1=yes 0=no
render-tree-shadows=1 # 1=yes 0=no
high_lod_hack=1 # [EXPERIMENTAL!] Enables highest level-of-detail models at far distances. Nice for higher FOVs, bad for FPS (esp. near cities)
dwash=1 # rotor downwash (dust) (0 = off, 1 = on) (def = 1)
restricted_nvg_fov=1 # night vision restriction (0 = off, 1 = on) (def = 1)
russian_nvg_no_ir=0 # russian night vision has no FLIR (0 = off, 1 = on) (def = 0)
colourmfd=1 # MFDs will use colour when available (0 = off, 1 = on) (def = 1)
highreshud=1 # high resolution HUD (0 = off, 1 = on) (def = 1)
tsdrender=1 # TSD render options (0 - 4) (def = 0 (contours only))
tsdpalette=3 # TSD palette options (0 - 2) (def = 0)
tsdenemy=0 # TSD showing red force blue force colours (0 = off, 1 = on) (def = 1)
tsddetail=0 # TSD in high detail (0 = off, 1 = on) (def = 0)
texture_colour=2 # Use texture colours and noisemaps directly. [WARNING!] Use only with correct texture packs. (0 = off, 1 = on, 2 = also use noisemap for higher resolution) (def = 0)
texture_filtering=1 # [EXPERIMENTAL!] texture blending (reacts to anisotropic filter setting) (0 = off, 1 = on) (def = 0)
mipmapping=1 # mipmapped textures (dds files). [WARNING!] Use only with correct texture packs. (0 = off, 1 = on) (def = 0)
dynamic_water=1 # dynamic water textures (0 = off, 1 = on) (def = 0)
night_light=0.7 # night light darkness level (0.0 - 1.0) (0.0 = fully dark, 1.0 = less dark) (def = 1.0)
persistent_smoke=1 # Burning targets emitting smoke for a long time. [Warning!] CPU intensive. (0 = off, 1 = on) (def = 1)
themes=2 # comma-separated list of directories for alternate psd files
Edited by Executioner (11/06/09 04:08 AM)
|
|
Top
|
|
|
|
#2895674 - 11/06/09 06:28 AM
Re: Vista 64 kicking my arse...
[Re: Executioner]
|
Junior Member
Registered: 08/01/09
Posts: 38
|
Run it in Win2000 compatibility (not XP) - that's worked for me on Win 7 64bit. And make sure notnl=1
|
|
Top
|
|
|
|
#2895789 - 11/06/09 08:04 AM
Re: Vista 64 kicking my arse...
[Re: KaiserB]
|
Junior Member
Registered: 09/09/09
Posts: 90
|
Yeah, tried those 195.s No go. Switched back. 2000, no didnt try that.
Also, when I deleted the game file, it sets the resolution to 640/480. Destop is runnign native at 1600/something. I think I'll grab a game file from another setup(which will have a higer reso) and drop it in.
Copy notnl. Tried that both ways too. I think I've tried most of the standard stuff. Just wondering what other 64bit users were doing. I had to do a lot of stupid stuff to get CFS3 to run on it. Just wondering.
thanks, I'll report back for future users.
GLB
|
|
Top
|
|
|
|
#2896669 - 11/07/09 04:17 PM
Re: Vista 64 kicking my arse...
[Re: BammerVB]
|
Junior Member
Registered: 09/09/09
Posts: 90
|
No joy on W2000 compatibility. Tried every switch in the graphics section. Game starts, then flickers and flashes. No loading writing at bottom.
The first mysterious clue is no green EECH icon on the exe within cohokum folder. When I install, it doesn't show that icon. It shows one of those windows, "I dont know what to do with this .exe" icons and plastered on top is some kind of shield. I'm not real happy with that.
I've shut down all anti-virus and firewalls. Uninstalled and re-installed, from a folder backup.
If anyone knows, does the Razorworks folder have to be over in the Program Files(x86) folder area on 64bit systems? Right now I just have it in the c drive. I know most of my other games install there. Just wondering.
If anyone has any guess on where to go next, let me know..
Thanks,
GLB
|
|
Top
|
|
|
|
#2896792 - 11/07/09 11:45 PM
Re: Vista 64 kicking my arse...
[Re: BammerVB]
|
Member
Registered: 01/29/07
Posts: 1142
Loc: Australia
|
I never install my gaming stuff into "programme files", generally D:/Razorworks is what I use. I dont know what protection is differant between Vista32, and Vista64, but I run EECH under Vista32 without any problems, but I do have UAC and WD turned off.
|
|
Top
|
|
|
|
#2897027 - 11/08/09 11:46 AM
Re: Vista 64 kicking my arse...
[Re: Colonel_Kurtz]
|
Junior Member
Registered: 09/09/09
Posts: 90
|
Yes, I have tried EECH running on XP 32bit. Vista 32bit, XP 64bit. But still looking for someone with Vista64 that has it running. At least I'd know what compatability they are running it in.
Some google research does reveal that default installs for 64bit systems use a folder for 64bit applications and then the (x86) folder for 32bit apps. Doesnt make sense to me but I'll try it out. The one 64bitXP system I have tried it on is installed on the D drive. But my Vista64bit only has a C drive.
Thanks, GLB
|
|
Top
|
|
|
|
#2897058 - 11/08/09 12:59 PM
Re: Vista 64 kicking my arse...
[Re: BammerVB]
|
Junior Member
Registered: 02/23/07
Posts: 84
Loc: Detroit, MI, USA
|
BammerVB, I'm running it in Vista 64 bit with no issues, but I have ATI graphics. Game is installed in C:/Games/Razorworks and backed up on a second D: drive. I can launch the game separately from either drive. Works with UAC on or off. With the ATI drivers, Catalyst AI is turned off (mouse pointer isn't visible with it on). So, it is possible.
Since your vid card is different than the one I use, wasn't too sure if my confirmation would help much. If you haven't tried so yet, I would suggest you turn the exotic features off (both for your card and EECH.ini) until you figure out what's causing the problem. When deleting the eech.ini and game.cfg files, they may regenerate with settings you still need to go in and edit (default may not be compatible). Also, you can try toggling the nodx9zbufferfix=0, 3dreset=0, dxtm=0, and cg=0 settings. I'm sure what I'm suggesting is obvious, but its worth a try because your problem is not Vista. It sure sounds like it's related to the driver settings or performance of the driver.
|
|
Top
|
|
|
|
|
|
|
| |