RAZBAM T-2 Buckeye FSX Compatibility

DL have another go at posting that pic if the light is way below the fuselage that is why your hook will not come down on the ground< I have said it many times bunging any old settings from another model rarely works.

tailhook_position= -12.66, 0.00, -2.57

-12.66 is fore and aft minus puts it behind the datum

0.00 is centre line and should always be 0.00 for tail hooks

-2.57 is below the the datum line a positive figure is above

delta_lima said:
Hi Rich-light worked fine. Don't know why my screen isn't showing up. The light (hook attack pt) was hanging way down below the fuselage. Will adjust and advise. Can you advise again if the coords go aft/fore, u/p down - or vice versa? ThanksDL
Click to expand...
 
Rich said:
DL have another go at posting that pic if the light is way below the fuselage that is why your hook will not come down on the ground< I have said it many times bunging any old settings from another model rarely works.

tailhook_position= -12.66, 0.00, -2.57

-12.66 is fore and aft minus puts it behind the datum

0.00 is centre line and should always be 0.00 for tail hooks

-2.57 is below the the datum line a positive figure is above
Click to expand...

OK - here's the pic:

View attachment 41884

I had just a min before running out the door with the kids - so will repost once I've edited the hook position. It's obvious that it's a good two or more feet low and slightly aft of where it needs to be ... Thanks for this - will start a similar thread on the Rollus Crusader. I suspect it has similar issues.

dl
 
DL as soon as you said originally the hook was bouncing up of the deck I knew it was set too low/too long and you lengthened the hook to fix it, add the hook length from your green light and you are way below, have'nt got the model so can't show you with show markers how much below.

Do your editing on the light line you added that way you can see what you are doing, editing the tailhook bit which does not allow you to see where you have moved anything, REMEMBER to change the -2.00 to 0.00 when you copy paste that light setting into the hook setting to centralize the hook

Re the Crusader the problem is with the contact points and until that is sorted I would leave the hook alone as it is pretty close to being right.
 
FIXED!!

OK mates ... she's done. Rich - your technique - both in it's fiendishly simple diagnosis and fix - is magnificent. Many thanks.

Not only does the Buckeye now get arrested in a more civilized manner - but the hook actually deploys on the ground. The former was the real objective - but the latter was a nice touch.

So, my recommended tailhook settings for this bird are as follows:


[TailHook]
tailhook_length=4.32
tailhook_position= -11.00, 0.00, 0.90
cable_force_adjust=3.0

I went back to the stock length - but the key was nailing the tailhook position. As you see, I got it fairly close:
View attachment 42002


Total time spent: 15 min. Satisfaction from the fix: priceless.

Thanks Rich, and I hope this helps others ....

dl

ps: Yes, Rich did the launch force fix - fabulous fix for the earlier jets/props. Why the sim wouldn't come standard to that setting baffles me ... but thanks to whomever discovered that.... :icon29:
 
DL,

Not only does the Buckeye now get arrested in a more civilized manner - but the hook actually deploys on the ground. The former was the real objective - but the latter was a nice touch.

The latter would not have occurred if the former had not been fixed, the virtual hook has to be right first as the visual hook follows the virtual and since the virtual hook was practically on the deck to start with you would only get the vis hook to go down in the air whereas it should at least go down until the virtual hook catch point touches the deck.
 
DL, try these contact points in your Crusader, not yet finished so see how you get on with a arrested landing using the current tail hook, hopefully this will have removed your nasty bump.

Crusader contact points test.

[contact_points]
static_pitch = 1.967539
static_cg_height = 6.416002
tailwheel_lock = 0
gear_system_type = 1
max_number_of_points = 14

point.0 = 1, 8.64, 0, -6.887, 2500, 0, 0.8, 34, 0.4, 3.0, 0.5, 5, 5, 0, 200, 300
point.1 = 1, -9.65, -4.5, -6.20, 2500, 1, 1.2, 0,0.336, 2.5, 0.7, 7.9, 7, 2, 200, 300
point.2 = 1, -9.65, 4.5, -6.20, 2500, 2, 1.2, 0,0.336,2.5, 0.7, 8.1, 8.1, 3, 200, 300
point.3 = 2, -14.17, -17.9057, -1.0579, 787.4, 0, 0, 0, 0, 0, 0, 0, 0, 5, 0, 0
point.4 = 2, -14.17, 18.0173, -1.1334, 787.4, 0, 0, 0, 0, 0, 0, 0, 0, 6, 0, 0
point.5 = 2, -30.1246, 0, -3.7877, 1574.8, 0, 0, 0, 0, 0, 0, 0, 0, 9, 0, 0
point.6 = 2, 22.7403, 0, 0.5672, 787.4, 0, 0, 0, 0, 0, 0, 0, 0, 4, 0, 0
point.7 = 5, -3.90, 0.0, -0.300, 1600, 0, 0.00, 50.0, 0.0, 0.0, 1.00, 1.0, 1.2, 0, 0.0, 0.0

Back up the aircraft.cfg first
 
Thanks Rich,

Yes, the rationale behind the hook placement makes total sense.

Will try the F-8 fixes tomorrow - for kicks and giggles, I'll check the hook attach point.

Many thanks!!!

dl
 
You must log in or register to reply here.
Back
Top