alexis99

So how does the Kormoran acquire the target in real-life? Surely not GPS, because if the ship is moving, you would need constant updates. Maybe they can do this. Anyway, looking for a Penguin now. Thanks

Ah I see. I was getting confused because the GBU-38 and the GBU-15, for instance, are both classed as EOGB in the Weapons directory, which I imagined meant Electro Optical Glide Bomb. It's only when you inspect individual weapons that you find GBU-38 is GPS guided and GBU-15 is TV guided. So that's why the F-22 in the game only supports the JDAM weapon and doesn't need laser targeting or EOTV Thank you

The JDAM is laser guided, so presumably the launch aircraft has to fire a laser at the target. And presumably it has to have an EOTV in the cockpit to enable the pilot to identify the target. The real F-22 has neither. So does it require a separate aircraft to fire the targeting laser, or has the upgrade programme installed the correct kit to enable the pilot to laser target himself? In the SF2 version of the F-22A, you just cycle the targets with the appropriate key command and stop when you find the target you want. Then, when within range parameters, you launch the weapon. Which is the real-life equivalent of carrying a GPS weapon, but not an LGB. You can install a laser ranging device and EOTV in the F-22 cockpit and it will enable TV guided Paveways to give you the target picture, but since JDAMs are not TV guided, you don't get the picture. To fix that, you would have to change the JDAM guidance to TV. Hence my question: how do JDAMS work in reality?

Is this DLL the only thing you need to enable an aircraft to create a shootlist and fire four missiles at 4 targets simultaneously? The F/A-18E Superhornet has had it successfully implemented, so I tried the dll with the EF2000 Eurofighter, but the firing sequence numbers are not listed on the radar. So I'm guessing I need something more than the dll.

I returned to this on the EF2000. With 6 AMRAAMS of the same type, I was able to kill 6 targets in one volley. With 8 AMRAAMS, I was able to kill 8 targets. Either with them all targeted at once, or the first four targeted and then after launch, the second four targeted. What is the benefit? Well, in the EF2000 if you target an enemy aircraft, the radar switches to TWS, you launch the AMRAAM, then you cancel the target and have to wait whilst the radar resets to search mode. Then you select a target and usually find it's the one you already targeted. So you cancel the target, rinse and repeat. By the time you get to trying to find the fourth target, the little cluster of icons on your radar screen all look alike and seem inseparable. The no ground radar is not a real problem. It's taken me years to realise that I don't need ground radar. (Mind you, comes in handy in Vietnam when you're looking for a clean route home). What I do need is a TV screen for Paveway delivery, and that's still there. So the real benefit is when you're flying a Paveway strike mission in Iraq, and you get jumped by four ageing Phantoms with their amazing long-range missiles. The old way, you'd be fumbling to separate out and mark the targets, and be lucky if you didn't get his missile in your face. Now, you just use the shoot list and send them to hell. Then you can go do the Paveway mission uninterrupted.

Taxying is awkward because the aircraft veers to the left. That's because in the data file, the RightMainGear is missing the entry HasBrakes=TRUE Whereas the LeftMainGear has the entry You're welcome

Thank you Streakeagle. Having flown Wrench's V2K Banshee, I was a little disappointed in the Razbam flight model. It's a bit lumpy by comparison. I also tried the F2H-3, and you can't remain in the air at carrier landing speed. So I put the Razbam cockpit in Wrench's aircraft and everything is tickety boo. Apart from the fact that the Razbam cockpit is missing a few instruments. The dials are there but the working needles aren't. Distance Readout and Wet compass are significantly not there. Still, if everything was perfect first time around, you wouldn't have the fun of solving problems.

A million thanks for the heads up on the resurrection of the Razbam site. I have purchased the F2H Banshee for the cockpit and am delighted to get it. Now I can have fun tweaking it. Cheers!

Yes, you're absolutely correct, Cliff 7600. It's the RPM entries in the cockpit .ini [RPM] Type=TACHOMETER NodeName=needle_rpm MovementType=ROTATION_Y Set[01].Position=0.0 Set[01].Value=0.0 Set[02].Position=2880.0 Set[02].Value=1.0 [RPM2] Type=TACHOMETER NodeName=needle_rpm_2 MovementType=ROTATION_Y Set[01].Position=0.0 Set[01].Value=0.0 Set[02].Position=360.0 ------------------------------------[I changed this to 500, and the Needles read 8000 RPM at max throttle, as per Flight Manual] Set[02].Value=1.75 I should have know better than adjusting the engine settings in the Data.ini. I have a note on how to adjust the handover point between Mil Power and afterburner to suit your physical throttle detent. So naturally that has nothing to do with RPM settings. Thank you for your immense help

I have an aircraft here with an RPM readout. The correct idling readout is 2500 RPM which is correct. The Instrument approach is 6500 rpm which is correct. But the readout does not go above 6500 rpm. That's max. Whereas in the real aircraft (As per Official Pilot's Notes), Brake Hold is 6800, max continuous is 7600, Intermediate is 7800 and Take-off is 8500. How does one adjust the RPM readout? I tried adjusting max rpm to about the 1.30 and got the needle suddenly jumping to 8, with the longer needle sticking at 12 0'clock. But it's not a smooth increase. It jumps from 6500 to 8000. Am I on the right track or not? I wasn't going to name the aircraft because I didn't want to upset the author, but it's the Stock TK Maxx Hawker Hunter F6.

Cliff 7600: TK MAXX was a joke. It's a shop. But, you know, bit like TK the originator of SF. I'll leave the jokes to Jack Benny It's the HUNTER F.6. that I'm talking about The max rpm shows on my gauge as 6000, not 8000. Anyway, thank you, I'll try your suggestion. Sorry for posting in the wrong area, Eagle 114th.

The cockpit.ini should be in your aircraft folder. Aircraft downloaded from here almost always have a cockpit.ini in the aircraft folder. The native aircraft do not always, because it is buried in the cat files, for which you need the Cat file extractor. Details on accessing this are in the Knowledge base. Or should be. The cockpit.ini has a section headed "Cockpit" that's where the files I mentioned are stored. Which aircraft do you want to adjust first? I can suggest some numbers,

The cockpit shows two HUD assemblies. Can we get rid of one? (Please ignore the yellow HUD discretes, they are my safety blanket)

Adjusting individual cockpit settings may be a pain, but by golly it works. I do this for newly downloaded aircraft. I do it for personal preference, not because the settings are wrong. Often, I adjust eyeball height so when I place the flight path marker on the deck, whilst coming in for landing, I can still see it in the HUD. So you know the settings in the Cockpit file. There are three numbers separated by commas. OFFSET: Slide graphic LEFT (+) RIGHT(-), Zoom IN (+) OUT (-), Slide Graphic UP(-) DOWN (+) VIEW ANGLES: Rotate Left, Tilt UP (+) Down (-), Rotate RIGHT POSITION, you would not normally touch because this is where the designer has accurately positioned the cockpit within the aircraft model. Mostly I use Zoom IN and OUT OFFSET to be at a comfortable distance from the HUD. This is a sensitive setting, and 0.01 is a safer increments to adjust by. 1.00 can put you outside the aircraft. I use Slide Graphic DOWN to position the flight path marker, again a sensitive adjustment. The eyeball is often too low in a stock pit. Then I use TILT UP or DOWN to compensate. The latter are more coarse adjustments, so adding or subtracting 1.00 is a good way to go. Then maybe you have to move the HUD discretes a little in the Avionics file. I don't use the rotates. So yes, fiddling with these settings is a little time consuming, but the results you can get are awesome and very rewarding. Egg-sucking lesson over.

You have to run control manager as ADMINISTRATOR with Compatibility set for WINDOWS 7. Then you can map controls, and your map can be downloaded. The only CH Product that will not work is the MFD Panel. I replaced mine with a Thrustmaster MFD. If you want to be able to get communication strings attached to a single key, I recommend the Expert Keys EK24.

When I first saw this cockpit, I thought it was fabulous, and immediately started flying the Super Mystere in Israel, neither of which I had done before. I have a question regarding the AOA light. Am I to assume when taking off or general flying, that if I fly beyond the envelope, pull up too hard, bank at a high angle, the AOA light comes on to tell me to stop what I'm doing and fly the aircraft properly? I'm particularly concerned with the landing phase, because if I perform a landing approach with the pipper on the tarmac, the AOA light comes on at about 7 degrees alpha. To get the light out, I have to nose down or speed up to around 147 kts. If I touchdown this way, the aircraft immediately lifts off again, and I have to lift flaps and force it back down onto the tarmac. I have found that he most comfortable landing is achieved by ignoring the AOA light, and flaring early to lose speed. Is it likely that the AOA light is coming on too early. Both V2 and V3 cockpits behave the same. Thank you

This is controlled by the MESSAGESYSTEM config file in the FLIGHT folder. Mine looks like this TextFontName=Arial TextSize=15 [MessageSystem] MaxMessages=1 MessageTime=2.0 MessageFadeTime=3.0 ;MaxMessages=25 ;MessageTime=200 ;MessageFadeTime=2.5 [MessageWindow] BackgroundImage=TextBackground.tga TopLeftPosition=0.01,0.845 BottomRightPosition=0.210,0.865 VerticalBorder=0.0015 HorizontalBorder=0.008 ;TopLeftPosition=0.2,0.2 ;BottomRightPosition=0.8,0.985 ;VerticalBorder=0.0015 ;HorizontalBorder=0.008 Best to use extractor file to get it to show up. If your WOE version is working, copy it across to your WOV flight folder MESSAGESYSTEM.INI

Yakarov: Thank you for that extremely plausible explanation

This keeps happening. I land on the carrier, and its an aircraft I haven't flown recently , and I can't remember if the canopy opens or not. So I flick the switch anyway, and my canopy doesn't open because my aircraft doesn't have that feature after all. But the F-14 next to me in the flight line does have that feature, and it opens its canopy when I flick the switch. Is this Bluetooth, or something?

Actually, the zones are there. Maybe they need to be a little further away from the land. No biggie.

Is that one of those instances where you have to hide "Nose" or "Fuselage" in the data ini?

I think I can do that.