Jump to content

Recommended Posts

Posted

Hi,

 

my Cougar doesn't work correctly after plugging it from the old XP system to the new x64 Win7 PC.

 

The error: some buttons won't work anymore when flying Falcon 4 AF. My ultimate test is: open Windows Notepad and push the buttons - the Cougar has to send characters. But some of the buttons don't. However, when pushing these buttons Foxy's "Logical Flag Viewer" shows the buttons working. So they must be sending something, but I do not overlook, where the decoding happens and so where it fails.

 

I'm desperate - what else can I try?

 

Thank you so much!

 

Ailer

Posted

In addition to the 64-bit driver, install in Vista SP1 Compatibility mode with administrator rights. Turning UAC off might also be a idea.

Novice or Veteran looking for an alternative MP career?

Click me to commence your Journey of Pillage and Plunder!

[sIGPIC][/sIGPIC]

'....And when I get to Heaven, to St Peter I will tell....

One more Soldier reporting Sir, I've served my time in Hell......'

Posted

Yes, I installed the 64Bit-Driver in compatibility mode Vista SP2 (not SP1), with admin rights. I turned UAC off.

 

I even removed it the first time I installed it and deleted the remaining files and directories manually. If there still were registry entries I don't know. After that I reinstalled the software. But the result was the same.

 

What about a firmware flash? I'm somewhat scary about that since I have very bad experiences with BIOS-flashing some main boards. But Nutty himself says, don't bother about flashing, it's no big deal.

 

Now, trying to start Foxy, I've got a new prob: a small (but vicious) window appears, that says "Invalid Picture" and doesn't let me start Foxy... :-(

 

Any idea?

 

Thanks, guys - cheers

 

Ailer

Posted

Vista drivers to 7 ? Huh:huh:

HaF 922, Asus rampage extreme 3 gene, I7 950 with Noctua D14, MSI gtx 460 hawk, G skill 1600 8gb, 1.5 giga samsung HD.

Track IR 5, Hall sensed Cougar, Hall sensed TM RCS TM Warthog(2283), TM MFD, Saitek pro combat rudder, Cougar MFD.

Posted

 

What about a firmware flash? I'm somewhat scary about that since I have very bad experiences with BIOS-flashing some main boards. But Nutty himself says, don't bother about flashing, it's no big deal.

 

Simple process :)

 

Just unplug and hold in the trigger and plug it back into USB. Hold for a couple of seconds (3-5) and release trigger. Now go to the Update tab and update the firmware.

Novice or Veteran looking for an alternative MP career?

Click me to commence your Journey of Pillage and Plunder!

[sIGPIC][/sIGPIC]

'....And when I get to Heaven, to St Peter I will tell....

One more Soldier reporting Sir, I've served my time in Hell......'

Posted (edited)

Thanks so much for your suggestions.

 

The prob with the "Invalid Picture" has been solved: I edited the Environment Variables, like I ever did before. But by now Win7 seems to have established a slightly different syntax. After restoring the original path, the problem had gone.

 

Now I have deleted and again installed the Foxy-Software. To avoid a message like "not able to create registry key" I had to install it as Administrator himself - not as user with admin rights! Some subroutine that tries to write to the registry obviously has no admin rights.

 

I flashed the Cougar and it was indeed very simple and worked fine.

 

By the way: @succellus: yes, Vista-drivers for Win7 - since there are no genuine Win7 drivers for the 64Bit systems. Every web discussion and even Thrustmaster themselves recommend the Vista 64Bit drivers for Win7 x64. There are many that say it works fine.

 

I then tried a super simple tmj joystick file and all buttons responded correctly within notepad. By now I have learned that in emulation mode the Cougar is able to send both key codes as well as DirectX-Codes - depending on the program in your tmj-File. In my case - Jagstang-File - it does so. And: the DirectX-Codes cannot be viewed in the notepad, you have to use a special tool for it.

 

Now I have to test my Jagstang-Files if they are still ok (but I guess so). Another issue is the *.key-file Falcon uses to (again) interpret the sent codes (key codes as well as DirextX codes).

 

Will be my work this afternoon.

 

I'll keep you informed. If there is any good idea please don't hesitate to let me know.

 

Cheers

 

Ailer

Edited by ailer
Posted

I found it. Poohhhhhh... :thumbup:

 

Yes, it was the *.key file that was corrupted. I understand only some issues of the syntax. When you change buttons or keystrokes Falcon edits the *.key file in that way, that registry keys are added. However, such a file only runs properly on the original system. You have to go through the procedure of teaching in your personal buttons and keystrokes again when changing the system by using the Facon setup menu. Better: take the original file (not any that was already changed once before) as basis.

 

That will do.

 

Thanks so much for your suggestions, that all helped a lot!

 

Have a nice week

 

Ailer

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...