Dynamo

Autopilot functions have not been implemented. :lol: see point 1 above. Its great to get a feel for the flight model though, but at the moment there is little point learning the procedures which are going to change a lot as things gets implemented. Navigation is easy, set up the way points, and follow the bar at the top of the hud, also displayed in the MFCDs. You can use the buttons in the top right of the navigation panel to advance or reduce waypoint number. Unless you mean using VOR navigation etc, which is a different matter.

To answer the original question - you have to set the master mode to ANF first, before changing weapon mode to ATTACK. Its a known bug. There are a few videos on youtube going through the correct procedure - but they will result in misses due to that issue.

HI Gents, over the weekend I managed to get the missile following WP I had set in flight perfectly. Then this week, for 2 evenings the missiles would not behave. So after a few hours of constantly fiddling with the missiles, I have noticed an issue. If you select ATTACK on the weapon dial first, before setting maser mode to ANF. The missiles will not follow the waypoints, and in my experience will just nose dive into the groun. So, don't follow the RB15F checklist. Set the master mode to ANF first, then weapon to ATTACK. Then set up your BX points - and it has seemed to work every time. There is an issue with the check list or the aircraft - I'm not qualified to say which.

Firstly, great application SkateZilla, good job. Perhaps this may be classed as mission creep, and perhaps I have overlooked this or has been mentioned before, but have you thought about including in your app, the ability to copy control profiles from one branch to the other? I have my controls all set up on the Open Alpha, would be nice to copy then to Beta. Can do it manually of course, but something in this tool would be great.

Perhaps I did, but it wasn't just a one off. Will be interested in hearing from others on this, as I said, I hope this isnt just wishful thinking. Druid: windspeed in knots or m/s is a very good point. More testing later.

Well spotted, I read through it loads of times to make sure I didnt miss anything, but this slipt past QA! In the screen shots you can see I entered the correct value of 15 ms, but I have updated the text to relate to that, thanks for the find.

Are you running Beta4 ? Is your Operating system 64 bit? I had to get the latest TrackIR driver which was released just before Christmas for it to work. I assume headtracking is working in the Trakc IR software. Do you get the blue light on the device saying it has found compatible software?

If you were over water, the plane having no chance to hit any buildings/ships etc, wouldn't the pilot be safer ejecting? Or is there any other benefit from ditching? I assume the A-10 won't stay afloat for long, and any survival equipment will be part of the ejection seat, surely? King Neptune, I assume like the trainers I have seen, the straps in the aircraft will have a quick release mechanism, i,e, press a button, rotate 90 degrees, and all straps fall away when you stand.

Swamp gas, for sure.....

Would that be an F16 by any chance? :D

Hi guys, thanks for the feedback, warmer than expected. According to the CDU documentation, you can add 7 wind layers, but as mentioned above, there are only 3 layers to edit in the mission editor. I was expecting the correction to make a difference, I was quite suprised just how much. The Mk82 scraping down the side of the vehicle before going off was glorious to see.

Hi All, I have had a mixed bag of results with the use of dumb bombs in CCIP and CCRP, generally speaking, flying skills apart, the issue is related to wind (not diet related, but atmospheric). I have just gone through the procedure of entering wind correction into the CDU to correct for this, and the results speak for themselves. Below is the walkthrough of the procedure I use, I hope it is of some use to you fellow sim pilots, and hope I am not teaching you to suck eggs! Sorry for all the pics!!! CCRP bombing, paired release @ 6000 ft 210kts. Wind 270 degrees 15m/s As shown above, the bombs missed their mark, and no damage done to the target. This was a stable release, wind accounting for the miss. Procedure for correction: 1) On the CDU panel, press the SYS button, then press the LASTE button: 2) Click the wind OSB to enter the wind correction page: 3) This is where you can enter the wind correction data. Start off by entering the altitude of the first layer of wind. I start with ground level. To do this, enter 00 in the scratch pad, then click the first empty line on the left to enter this altitude. 4) Repeat the process for other wind layers if known. What I did here was repeat the wind speed and direction data for my altitude, so the adjustment calculation took place. In this case I entered 06 (for 6000ft) and placed that altitude in the line beneath the first: 6) When you have enetered all the layers you desire, press the WndEdit button. In this step you enter the wind speed and direction. How you get this data is up to you :) You can get it form the mission editor, Air traffic, even the JTAC gives the wind vector for you. To enter the data you have to enter 5 digits. The first 3 digits is the direction of the wind, so 000 = north and so on. In this case, 270 was the wind direction. The 4th and 5th digits is the wind speed in m/s So wind speed 15 ms at 270 degrees, we enter 27015. If wind was at 10 degrees and 7 m/s, you should end 01007 Once entered, hit the OSB for the layer you want to add this data. Repeat this for all layers. 7) Next step is to add the temperature data for each layer. Again get this from the ME/brief. You also have the current temperature shown in the CDU on the top right. I just used this temperature accross all layers. 18 degrees here. 8) Once done, hit the WIndTemp OSB to go back a step and store the data: 9) Get yourself lined up.... and bombs away!!!! "Good bombs, good bombs" BDA flyby: As you can see from the result it seems to do the job nicely!!! The smoke also blows along the correction line... I would like to say there is no camera trickery here, and I hope the above isn't just a placebo, and my first run was just bad. But I tried this out a few times, and it appears to do the job. Let me know how you get on!!! Also, thanks ED for making this sim so involved, things like this are great! Happy bombing all!

It would be a bright light though surely if it was. I noticed a bright light when flying a night mission the other day - the star constellations are all modelled, and this didn't match those - looked to be the position Jupiter should have been. I wonder if the planet positions have been modelled too. DCS: Planetarium

Like something straight out of Dan Brown's Digital Fortress!

Squirrel, is your method just a way of approximating a 3 degree glideslope, like these? http://www.scgvacc.net/forum/index.php?showtopic=359 REL, in the manual, page 489: descend to the TACAN station location at a rate of approximately 1,200 to 1,500 ft/min on the ―VVI‖ indicator -300 feet for every mile traveled and maintain 200 – 250 KIAS. So in your case, maintain a speed of 200-250 KIAS, and maintain -1200 to -1500 fpm.