When I first got the Cougar I just followed the instructions and it worked fine. Then my wife unplugged it and fouled it up. Unfortunately, I can't remember how I got it working again. I know I didn't use the TSH manager other than to test it. I think I flashed the firmware and started over but never could get it quite back to where it was. As long as it worked in manual and user mode I didn't want to mess with it anymore for fear of screwing it up again. Please don't let this take you down a road you might not need to go, I just read your symptoms and thought if you had a Cougar I could help since it sounds like I've got the same thing in auto/default mode

Those are "pushbutton" commands for the 20 locations around the UFC that mimic MDI pushbuttons. I put the word "pushbutton" in quotation marks because of course the UFC is a touchscreen, so you don't have to actually push anything, just touch it.

Remember, the UFC can operate in UFC mode or MDI mode. In UFC mode the scratchpad commands and the UFC_F00 through UFC_F08 commands are active. Yes, I know these move around depending on the display, but it was the best we could do. In MDI mode the UFC effectively functions like any of the other three MDIs, and then the pushbutton commands are active. The UFC pushbutton commands actually aren't created by TSH; they were added in the official v1.01F patch.

Ghost didn't quite have the right link to the TSH v4 manual page describing this. Try:
http://tsh.war-fighters.net/index.php?op...p;limitstart=11

AFAIK these should work fine. One thing you could do to check, if you were using TSH v4.02, is to simply uninstall TSH v4.02 and do a quick check to see if the training missions are working. Unfortunately if you use the one-click installer that installs TSH v3.06, there is no way to simply uninstall the set of mods that it integrates.

I'm not disputing the first two points you made, but if you've been reading some other threads in this forum you would see that the "cannot be patched" comment may no longer be true...

Do you know what axis on your controller controls the rudder? I suspect that this axis isn't centered. This is typical for Cougar users who don't have rudder pedals connected to the Cougar; the RANGE knob controls the rudder, and if it os offset it's not usually noticeable in the air (since the JF-18 rudder doesn't work). But once the wheels hit the ground this axis controls nosewheel steering, and any offset will cause the aircraft to turn.

Here's an example of Jane's F/A 18 rudder, working

Sorry, guys, I stand by what I said above. Nice video, Ghost, but the viewer will note that while the airframe appears to yaw as rudder deflection is applied, it does not actually change the aircraft flight path. With no other control surface deflection, rudder input should cause the plane to turn... its motion vector should change. But it doesn't. When you release the rudder pedals, the nose will return to its previous heading and you will note that the plane's course has not actually changed.

This will screw you up royally on carrier traps.

I defer to Joe's substantially more informed perspective, and correct my statement to;

"... it has not been patched to make it work properly."

That's why I italicized the word working.

Hi!

Probably nobody here knows me , but my nick might sound in the heads of Ripcord and Joe. I was fooling with the guts of JF-18 one or two years ago, inside the TSH team. Due to my aeronautical background, I was mainly interested in flight mechanics, and in first place I was told to work in the rudder thing. And I do so. I remember that I handed out a binary with the rudder behaviour touched, but I don't know if it's the same "patched" version you are talking here.

Anyway, only for the sake of clarity, the rudduer in JF-18 does affect the flight path. The problem was that the C sub delta r_Y, the coefficient that governs the lateral displacement due to rudder efects, is pretty small, so the effect is not barely noticeable. I tweaked that, increase that value so the effect was more important (this doens't mean that it was more realistic however, as long as I didn't have the real coefficient values unfortunately), together with a realistic rudder schedule. If you look up in the NFM-000, it's said that in high AoA conditions, a rudder pedal push will manage a aileron deflection instead of a rudder deflection, so the outcome would be a roll instead of yaw. This behaviour was implemented in the "patched" version as well.

Unfortunately I had to give up my work in the flight mechanics part because I moved in Germany and run out of time for doing these things. I'm looking forward to continue developing the flight model in the future, though.

Regards!

Lookin' forward to your work amalahama!

Hi - I do remember you from TSH, not been there lately.



Interesting comparison to the first Rhino (F4 Phantom) where at high AOA you HAD to use the rudder to turn as the ailerons (really lift dumpers) would stall the wing...

Cheers,
Keith

A regular airplane will do the same. In all other sims I use rudder to initiate a turn or roll if I lose my ailerons in a dogfight.

Here you are the behaviour as it is detailed in the NFM. It was implemented along the tuned rudder coefficients.



Below 13º, rudder pedals work as usual, acting over rudder actuators only.

Regards!!

Okay, I seem to still be doing something wrong here. I've assigned all my MFD keys in game, opened up the keys.ini and wrote a Command File to match the keys.ini. I've assigned my keys to my MFPs and XKeys Pro USB, and the game doesn't want to recognise the key presses. As you can see I've tried to HOLD the modifier, as well not HOLD the modifier. In either case, I can't seem to get the buttons around the MDIs to work nor the UFC. What am I missing?

Anybody?

Ghost, you are so far over my head, you're like the Balloon Boy.

LOL

sobe, if you're still following, did you fix this in game? If so, what'd you do? I would like to press a button and actually have it work in the sim. I've assigned other button presses on my MFP and they seem to work ingame, BUT, they don't have modifiers like CTL, ALT...

Guesses?

I continued to have problems with the game and the radar and stopped playing it for a time. I was following your thread and have no answerer for you. I have spent what little time I have on TAW 2.16 which seems to work fine on my old computer.