Asenna Steam
kirjaudu sisään
|
kieli
简体中文 (yksinkertaistettu kiina)
繁體中文 (perinteinen kiina)
日本語 (japani)
한국어 (korea)
ไทย (thai)
български (bulgaria)
Čeština (tšekki)
Dansk (tanska)
Deutsch (saksa)
English (englanti)
Español – España (espanja – Espanja)
Español – Latinoamérica (espanja – Lat. Am.)
Ελληνικά (kreikka)
Français (ranska)
Italiano (italia)
Bahasa Indonesia (indonesia)
Magyar (unkari)
Nederlands (hollanti)
Norsk (norja)
Polski (puola)
Português (portugali – Portugali)
Português – Brasil (portugali – Brasilia)
Română (romania)
Русский (venäjä)
Svenska (ruotsi)
Türkçe (turkki)
Tiếng Việt (vietnam)
Українська (ukraina)
Ilmoita käännösongelmasta
But, you have created an entry for F.E.A.R. in Creative Alchemy and pointed it to the F.E.A.R. directory?
Rather than use the 32 bit registry keys that are already in place and work beautifully on 32 bit systems, 64 bit keys need this change........
SOFTWARE\Wow6432Node\
insert Wow6432Node right after SOFTWARE in Creative's FEAR Alchemy setting and VOILA!
It's probably Creatives terrible driver support. The old X-FIs havent even been fully updated for Win7. You might search for modded drivers, i'm only getting my X-FI Gamer to work in W7 when using the Daniel_K drivers.
In conclusion: Dont buy Soundcards from Creative. Not matter how good they are, the company behind it is terrible.
and i definitely agree with you (Xlll) though i do believe microsoft partly responsible too many damn operating systems to support . corporations always turn their backs on each other and saying I do believe we're going in different direction.
What fixed it for me was setting the game to run as Admin as well as running it in compatability mode for WinXP SP3.
Also, in Alchemy, insert "Wow6432Node" after SOFTWARE in the registry path (64bit OS only)
as stated by JMacguire above.
Using the game path method works as well.
All of my hardware sound options including EAX are available and working with FEAR, FEAR XP, and FEAR PM using this method.
It now reboots with a blue screen unhappy smiley referencing ha20x2k.sys as the cause of the failure. I believe that's a creative sys file, is it Alchemy related I wonder.
Has anyone else experienced this issue?
@AOD-SK451 I have the same creative sound card as you, plus win 8.1 X64.
You could plug in speakers from 1945 and they would be compatible with EAX. There is no such thing as speaker incompatibility.