Fish

"The sequence is as follows, The airplane releases the smart bomb. Its eyes are 'closed', and it falls like a free fall bomb. Meanwhile the WSO moves the cross hairs on his screen, over the target to be hit. Then maybe 10 seconds before the bomb hits the ground, the WSO 'opens the bombs eyes' (i think this means he switches on the laser)................When the guidance head locates the laser signature on the target, guidance fins are activated, and the bomb becomes 'smart', adjusting itself to land on the target. " Section from 'Flying the F-15E in the gulf war. William L. Smallwood This approach works good if you got a buddy lase, or WSO with his head down on the TV, while the pilot concentrates on HUD and pickles in CCIP. Time over target is probably reduced since the bomb 'flies' less.

to add..... Select AGM65 from DSMS, Select Maverick with TMS right. Make sure master arm on. Then within range, uncage the seeker, and slew until it 'locks'. Hope your not too close, pickle. Slew, lock, pickle. All the time controlling aircraft. And thats not even trying to avoid AAA, or something more nasty trying to set your ass on fire.!! And then if you thought you knew something about LBG delivery, just look at the LBG employment section......etc. Be under no illusion, there's a steep learning curve in this baby. Even for a falcon vet.

Here's the settings im using, with a 24"monitor, same resolution. I'm using TIR also. I don't fly the migs, or F15, so have not changed them. Also note Su39=Su25T -- Camera view angle limits {view angle min, view angle max}. CameraViewAngleLimits = {} CameraViewAngleLimits[PlaneIndex.iSu_27] = {50.0, 180.0} CameraViewAngleLimits[PlaneIndex.iSu_33] = {50.0, 180.0} CameraViewAngleLimits[PlaneIndex.iSu_25] = {45, 170.0} CameraViewAngleLimits[PlaneIndex.iSu_39] = {55.0, 190.0} CameraViewAngleLimits[PlaneIndex.iMiG_29] = {30.0, 112.0} CameraViewAngleLimits[PlaneIndex.iMiG_29K] = {30.0, 112.0} CameraViewAngleLimits[PlaneIndex.iA_10] = {30.0, 150.0} CameraViewAngleLimits[PlaneIndex.iF_15] = {30.0, 110.0} CameraViewAngleLimits[PlaneIndex.iKA_50] = {30.0, 115.0}

Is there any way to control the number of rockets released from the S80 and S13 salvo launchers in both The su25's. I have tried all combinations of the Ripple quantity and salvo switches. I am also curious of a switch on the WCS, the 'Cut of burst' switch, and have no idea of what it does. Page 186 of the manual states 'Rockets are usually used in volleys'. I agree that they are more effective 'en masse' but would be surprised if the option to use less in a volley did not reside with the pilot, as it does in the KA50

Dont think there is control indicator on FC2, and even if it was might not solve your problem. I guess you know this stuff already, trim buttons tell you control surfaces are 'centered' but other factors i can think of will affect yaw/roll. trimming compensates for these. 1. asymetric load out (unequal moments of interia) 2. damaged control surfaces, 3. weather, cross winds and turbulence. You might try a big dead band on your stick, and fly mission from the editor with no ordinance and no weather. I generally don't trim yaw and roll, cause its too cumbersome to get right, I do try to trim the pitch but even with fine adjustment, i have to give periodic stick inputs to keep on the fpm.

Tried a coop mission with 2 su25s and 1 ka50 against a distributed threat of tanks and shiklas with unguided on the su's. While the ka was able to see starter safley with it's shval, we got toasted from ground aaa. Apart from seeing the smoke plumes of the active arty units it was almost impossible to pick the units from the background leaving us as sittin ducks whn we finally got a tally!

Voice activation + a headset with a microphone switch if i need to mute in a hurry !!!

Video removed by user ?

+1

Check this thread

Thanks for the reply. I'll give your advice a try.

Hi All, Would be interested in the tactics used against other choppers, like hellfire loaded AH64's or Mi24's, or even enemy Ka50's. Cheers.

:thumbup: Cheers for all the good work guys. Sad to see it closing.

Here is my current setup, to enable me to talk in MP, and actually hear what people are saying to me while the engine is running. I have noted that no matter which position the 'engines' is in, it has no effect. Only he master volume has an effect ? I am not using any sound mods, and would like to know how you have set it up, for MP. cheers Fish

Added track file to original post for anyone who wants to practice landing. :cry:

Could not ditch the load. That is what caused the clicking sound u hear, but nothing dropped off the rails. Guess damage inflicted caused that also. Tried to pickle also but same result

Landing the su25 with damage Here is the TRACK FILE

Hi All, Just dabbling into the mission editor. And i have a couple of questions I planned a group to take off, from the runway, and another from ramp. Also planned a flight group to land maybe 10mins later. The take off groups both used one end of the runway, while the return group used the opposite end. Not sure why it would be. What are the rules which determine the direction a group uses to land and take off. Second. How do I make a flight escort another plane or flight group? Third. How do i make a plane loiter in a loop (i already set 2 waypoints as start and end loop), and what rules apply, Will they stay till fuel gets low. What are the triggers which make a group on say CAP, break, or RTB. Thanks in advance.

Have not flown the A10 in FC2 yet, but here is some guidance. Points to note and help you . Key 1 is nav submode, Key LCTL~ is next, to cycle through landing strips or waypoints. Nav sub modes (always in this sequence) 1. blank, does nothing, but tells you which mode you are in, and which is next. 2. En-route, your preset waypoints, 3. Return, the point in space which lines you up for your approach to the selected runway 4. Landing, the actual runway bearing (same as ILS mode). In 2,3,4 you can cycle using the next button, to get next waypoint or runway. Note to find which waypoint is selected, simply cycle the submode back to the nav mode. Every time you go through the passive mode, you are cycled back to waypoint 1. Note this is not the same for runways, and changing the submodes always leaves you back to the same runway you had already selected. Here is a document written for the Su25, but equally applies to aircraft with no moving map or mfd flight plan, or where this is damaged or not working. Finding your way around in the Su25

Want this to be a positive post, don't want any negative comments. Have not spent much time in the pit yet but here are some of the things I really like about Flaming Cliffs 2.0 1. The target box can be assigned an analog axis, so can be retained at fixed size, from mission to mission, until its adjusted. 2. Frame rate. I have a multicore, and it runs significantly better than FC1.12 with comparable settings. 3. The extra DOF's for the pit. Even the stock 'roll' and slight shifting of the seat postion, adds to the sensation of realism. 4. I don't have to worry about the laser overheating SU25T (from what I can see). 5. New visuals are fantastic. They look great in BS, but while flying over cost line at high speed, with high FPS. Amazing. Nothing comes close. 6. Separate control sets for each aircraft. Have not separated profile yet, great to have the ability to do it. 7. Terrain with higher mountains, much more fun to fly in. 8. Beautiful Su25 3d model

Ah Yo-Yo, why did you have to go and spoil the fun!! :doh:

Did the trick. Cheers. :thumbup: Good to see another paddy on the forum.

Can someone please give me the default keys binding file for FC 2. I was changing the profile for the Su25T, and decided to save it when done. Very nice. Until i tried to load it back in. Not one key left bound. And yes i can restore the keys with the default button. one key at a time! So please let me have someone's default so i dont have to go installing the game again. Cheers

SOLVED. Not sure why, but i restarted FC, and its now working!! EDIT, Start D3D Overider, make sure force vsynch is on, Start FC, ALT TAB, to minimise, Return to FC. Cheers.

I hope I understand the question you are asking. in Lomac/config/graphics.cfg file change the aspect ratio in the items below from 1.3333 to 1.66667 as in code below. Your resolution mighb be different DisplayMode { resolution = {1920, 1200}; bpp = 32; fullscreen = 1; aspect = [color="Red"]1.66666667;[/color] Interface { resolution = {1920, 1200}; bpp = 32; fullscreen = 1; aspect =[color="Red"]1.66666667[/color]; } Simulation { resolution = {1920, 1200}; bpp = 32; fullscreen = 1; aspect = [color="red"]1.66666667[/color]; } AVI { resolution = {1024, 768}; fullscreen = 0; aspect = [color="red"]1.6666667;[/color] } Fish