this happened only recenlty. i have not installed or changed anything on my computer.
the trouble is that when i start ArmA the games loads perfectly. but whether it's playing a game or going into editor the game does not recognise the keyboard input. this is ironic because alt+tabbing out (whihc is keyboard input strnagely enough) and then alt+tabbing back in gives keyboard input.
i have a German version of Arma purchase online for morphicon.
I have the same problem.
Even deleted the profiles in My Documents completely after I uninstalled. Then reinstalled and still have the same issue.
Trying more stuff now...
Did a clean wipe this time around.
I nuked all the registry entries, and even the Metaboli Serial Activation reg entry.
Tried changing Keyboards also USB & PS2 have same issue.
i was wondering why i no longer can use my "search" function in windows explorer.. get some messed up error... damn *coughstar* *coughforce*Originally Posted by (HitSqdhaXor @ Dec. 13 2006,01:34)
I am in denile about the SF protection. I don't think it is that and am not interested in another SF flame thread.i was wondering why i no longer can use my "search" function in windows explorer.. get some messed up error... damn *coughstar* *coughforce*
@ twisted:
The only new software I have loaded recently is Cam2Pan and registered that dll for NewView software. Perhaps that .dll for NewView is messing things up?
- What about you twisted? have you used NewView recently?
:::EDIT:::
After hours of BS and Grooling Work .... (haha)
It is NOT ArmA causing the issue, it is not SF.
It is that FOOKIN file from NewView!!! --------> NPClient.dll
Remember doing this?
--------------------
There is no DLL file in the current directory. Copy it to the following folder: D:\WINDOWS\system32\
=================================
Remove the file from system32 if you copied there.
=================================
If you clicked the [Add Dll to Registry] button you will
also need to use Regedit do a search and Delete all references to NaturalPoint.
[HKEY_USERS\S-1-5-21-2000478354-1604221776-725345543-1003\Software\NaturalPoint]
- It stores the path to the NPclient.dll
If you happen to use NewView then you probably, like some other ppl here, use a bad .ini file.
You can either delete all the .ini in your NewView directory, the prog will recreate by itself a proper file, or you can grab it straight from here :
http://groch.dyn.pl/~groch/TrackIR/ArmA_1.INI
Although I’m sure you’ll still find those professional forum whiners who live to find fault with anything under the sun.
No that is not the issue. An .ini file is a list of parameters only.
My Cam2Pan and NewView function as expected.
The problem occurs even when NewView is NOT open/running.
- NPclient.dll gets loaded at startup via registry and creates a keyboard initialization problem with Armed Assault.
Nothing more - Nothing Less.
Later!
You can't "open" or "run" NewView, the DLL is always loaded with the corresponding INI if it exists when you start ArmA.
And the keyboard problems disappeared the day I took the good ini file.
And they reappeared back once when I took another ini from another link.
As I said this is easy to test: remove all the inis from newview dir, see if keyb works ; take the ini from my link and test again if keyb works.
Ignorance is bliss.
Edit: I guess I got on the wrong bus when I was young.
I am 101% certain it is the .dll file and not the .ini
The .ini is a list of parameters when the actual application launches. The .dll is a list of instructions for the application and tells it how to behave.
Seriously, ... if you find it to be the .ini file ...
I will eat my headphones.
Bon appetit
Sorry about that last post ... I was freakin tired as hell and spent the last 2 hours previously loading and unloading stuff trying to pinpoint the problem.
I did try your ini file and got the same results. Matter of fact I got an even bigger error since the file you linked appears to be loaded with comas and not periods. I guess the comas are a foreign thing and I need to change them to periods.
Point blank though ... if it is the .dll file that is causing the issue,
I cant see how an .ini file causes an issue if the application isn't even open to load it. Are you saying that the .dll file acesses the ArmA.ini file when windows starts? Now that is freakin retarded if so....
Well I am gonna test some more while I snack a bit on my headphones.
EDIT:
Ok I was wrong. I am sorry.
I converted all the comas to periods and it is working.
It was the .ini file causing the issue.
[[ Eating headphones now ]] mmmmmmmmmmm.......
Posting Permissions
HOME 
Reply With Quote
