atsmith6

Correction. This is not a bug, it's me being an idiot! Sorry all. After landing and deploying the chute with [P], I press [P] again to detach the chute but it remains on the jet. Need to blast it off with full AB.

Am I right to understand that: In climb and a dogfight the correct maximum RPM setting is 3000 RPM, and in the dogfight I would inject MW-50 into the fuel for extra HP, or am I supposed to boost to 3250 RPM for short durations for maximum energy in a dogfight? I'm certain I can figure out what the sim will tolerate but I'd like to know what the prescribed method was in the real world. As a side question: The 2700 RPM cruise setting in the Jumo 213 manual, is this maximum safe cruise RPM, maximum endurance (i.e. time in flight) or maximum range RPM? And one more bonus: Does anyone know a good speed for maximum sustained rate of turn at 3000 RPM and or 3250? Many thanks in advance!

I struggled like crazy trying to land this aircraft until I realised that it was simply the torque of the engine killing me every time. Suddenly, landing became trivially easy. To save anyone else the frustration I've made a quick youtube video. Read the description for steps taken in flight: Hope that helps!

I stand under correction but here's my personal opinion. I got used to motion in the air, motion in high speed vehicles and motion on a ship (roaring 40s and a small ship meaning very violent seas) in real life. Now I never get motion sickness whatever the situation. So my brain adapted the response of my inner ear as a result of experience and my refusal to use pills in the case of the ship to counter the effects. I therefore conclude that even if I initially find that sub 60Hz framerates or the eye to inner-ear disconnect causes a motion sickness like response, by simply being patient and using it every day for a while my brain will once again adapt and I will no longer suffer any effects of motion sickness. Perhaps by starting with short durations and increasing the time every day? In essence I'm not overly concerned because my desire to fly in fully realized 3D is greater than any discomfort because I believe that discomfort is a response that can, like almost any other response, be trained away.

Hi So don't know whether this is a bug with DCS or the Sabre. Tuning to a radio frequency seems to be playing a) two or more Morse code signals over each other and b) and same few overlapping signals regardless of the station you are tuned into. This makes it impossible to navigate by NDB as it's almost impossible to tune into the correct frequencies. Sorry if this is the wrong place to post this but I couldn't find a bug reporting forum. That said: The F-86F is super friggin awesome! It's simply the most satisfying jet flight model I've yet enjoyed in a sim. Please, Belsimtek, keep 'em coming! Just wonderful. Though it would be nice if at some time during the BETA, the NBD's started playing correct Morse code... :) Love you guys!

Ahh Ok. Well if you do figure it out I'd appreciate it if you'd PM me and let me know :)

Hy Dropship Pilot I run DCS on a 780 ti and get the same FPS behaviour you do. If I take the SU-25 out then at times I have in excess of 110 fps and at others under 60. When I deploy weapons and see the explosions the FPS can drop to the low 40's. It's purely a function of how much is on screen. You can easily reproduce this: 1. Write down you current graphics settings 2. Set all settings to maximum (except maybe the trees) 3. Take off in the SU-25 and fly north along the coast 4. Enable the FPS display 5. Notice that when you're looking over the town with tons of buildings your FPS is likely far lower than when you look over the ocean. 6. Fire a bunch of rockets into the ground and make sure the explosions stay in your field of view - notice that while the explosion is happening you are likely to have a HUGE FPS drop. Two things are happening here: 1. The more objects (like town buildings) the graphics card needs to draw, the bigger the hit 2. Any dynamic scenery like civilian traffic and other sim aircraft (and who knows what else) will also be taking a load on the CPU. The first is easy to see using the method above. The second can be a pain because we don't know what the developers do in the CPU time. There is also IO (which is slow) that happens and you can see this when DCS decides to stutter. This is because ultimately there is one huge limitation that no graphics card can compensate for. Each frame, the CPU is used to do the actual simulation. When this is happening, the graphics card is doing nothing. It's essentially waiting for the CPU to tell it what geometry to draw and which transformations to apply. Only then does the graphics card do it's thing and it's only THAT time slice the card can affect. That was a bit of a ramble and slight over-simplification but I hope that helps you understand the limitations in performance that you are seeing a little better. I am a games developer myself so I speak from some experience. have a great day...

Thanks guys. I think I've decided that my "happy" cruise speed in the Huey is around 105kts.

Hey all Right, after HUUUUGE amounts of practice I can finally fly the Huey in all phases in a way that feels right. No more wobbling / oscillating etc. and my take-off, accelerate, cruise, decelerate and land are all nicely controlled. The only jerky bits come from the fact that my stick is a little sticky around the centre (I know, annoying right?!) This leads me to an interesting question though. I have absolutely no idea what the proper cruise speed for the chopper is. I tend to stick to around 100 on the speed-o to avoid the buffeting but that's based purely out of ignorance. So does anyone know (bonus points if you are - or can ask - a real Huey pilot) what speed is normal for a flight where you need to settle in to a straight line for a good few miles? Any information would be greatly appreciated. Happy flying everyone!

Hey guys, thanks for the posts. If the bug is linked to non-activation then there's likely a bug in the activation system because: - the plane (specifically FC3) is activated; - I've flown numerous times before this; - I've flown subsequently; - This issue has happened only once thus far. Hope that's useful

DCS 1.2.8.27203 Loaded up DCS F15-C and the cockpit model data didn't all load into the video card. See attached screen shots. This has happened once after about ten flights. The computer is new and the operating system is up to date and was installed a few weeks ago. There is very little else installed on the system. Hardware is GTX 780 Ti, driver version 335.23 Core-i5 4670K 16Mb RAM Windows 7 Home Premium

Like some I chose to wait for the 1.2.8 release before trying the new F-15 flight model. This may have been due to the fact that the old flight models were way too artificial and so, in effect and given the highly simplified cockpit, I suppose I'd effectively written off FC3. The Consider I like study sims and am over-critical of flight models for context. Suspension of disbelief is a critical factor for me. That said, with all the hype about the new flight model, I decided to install FC3 again mostly out of curiosity. Nothing could have prepared me for the first flight! I can comformtably say that whoever implemented this model has done a most outstanding job. This is quite simply the most convincing experience of simulated jet flight that I've experienced on a desktop sim. It completely grabbed me and drew me in and I have subsequently spend a significant amount of time just flying touch and goes with different loadouts from light to heavy and have found no end of joy. Transitioning into and out of the region of reverse command is something I can tangibly feel on approach and I that's but one of the many highlights. It's fair to say that the flight experience is such a significant step forward that despite my prejudice toward simplified cockpit functionality the FC3 F-15 is going to become a regular airplane for me now. If they add an equivalent model to the SU-33, well, I can't believe I - off all people - am excited about a potential future FC3 upgrade! I realise that programmers and engineers don't see 95% of what's written on forums but if someone at Eagle Dynamics reads this please forward a link to this post to the person or persons who did the actual implementation. They really deserve to know just how fantastic a job they have done. I personally feel that this new flight model is one of the best and most convincing I've ever experienced. Kind Regards

Yes. Ensure all three AP channels are selected at all times. With the flight director button NOT selected this will cause the AP to stabilise your helicopter and fly in your designated direction or toward your selected steerpoint. If you now enable Flight Director mode, the AP will simply stop trying to fly for you, i.e. it will stop trying to steer you to the last heading programmed by the trim button or the waypoint selected on the PVI-800. But it will still continue to stabilise the helicopter. If you disable any of the three AP channels you will find yourself fighting to control the aircraft. In short, with flight director ON the KA-50 flies like an easy to control helicopter without the additional yaw input that a normal tail-rotor equipped helo uses, i.e. you're simply trimming pitch, roll, and yaw. With flight director OFF the AP takes control and flies the helo in the last direction you told it to, taking your last trimmed pitch as an indicator of how fast you want to get there.

Ahh, didn't realise that. Thanks TurboHog :)

Quick question In mission 2 of the campaign the area where you are to protect the convoy is shown as a yellow box on the ABRIS display. Any idea how one creates those? I've looked in the mission editor and can't for the life of me figure it out. Any help would he hugely appreciated. A

Souls, same happened to me. Ensure you turn the throttle up about 2/3rds of the way before holding the HOME button. That solved it. The change was introduced in update 1.2.7

Hey Dudester22 The only reason these aircraft are hard to learn is that the teaching material available to us almost all assumes a certain level of knowledge, or more likely, the authors forget what they didn't know before they got any good. If you can find someone that is already proficient you will find getting to grips with either aircraft far less challenging than you'd expect. Consider joining a virtual fighter wing. I realise that's a seriously sideways interpretation of an answer to your original question but I mentioned it as I wish I'd done it when I was in exactly your position. After joining the 72nd VFW I went from facing a mountain to little more than a molehill. As a direct answer, aeroplane flight dynamics are far easier than for a helicopter. On the other hand the avionics of all the "high-fidelity" simulator aircraft are surprisingly similar and once you understand one, transitioning to another is far-far easier than the first time through. I started on the F-16 in Falcon BMS, then learned the DCS KA-50 and A-10C. The latter two were just learning the buttons to press to do what I already understood from the Viper. So considering all that - I'd recommend learning the A-10C first, then transitioning to the Kamov. That way you can focus on learning helicopter flight without wondering what all the switches do too. Hope that's useful

Hi I've been banging my head against this for hours and am now solidly stuck :( What I'm trying to achieve is the following: I have a group that I use as a template: Infantry - 3 triggered actions: 1 Set frequency 40.5 FM 2 Transmit Message(ELT-Tone, '', on) 3 Stop Transmitting using MIST, I clone a troop from an existing group: MI_active_group = mist.cloneInZone('InfTemplate', 'InfSpawnZone', true, 5) then later I set an FM radio frequency and start transmitting a homing signal for a Huey to home in on: local group = Group.getByName(MI_active_group.name) trigger.action.pushAITask(group, 1) // Set frequency 40.5 FM trigger.action.pushAITask(group, 2) // Transmit Message(ELT-Tone, '', on) problem is that the cloned group doesn't seem to get the original group's triggered actions. Also, I can't find how to add these actions as new actions to the cloned group either. I've looked at part 1 and part 2 of the scripting guide as well as many missions created by other scripters and have hit a brick wall Does anyone know how to either add new AI tasks (specifically the three mentioned above) to a cloned group? Any advice would be highly appreciated Many thanks in advance

Thank you! Very much appreciate you sharing this. I'm in the process of learning to script DCS missions and this is a huge help.

dahui Just FYI, while you wait for Belsimtek to take notice of this message you can, in the mean time, open up the campaign mission in the mission editor and change the message timings for all the messages to an amount that suits you. I recommend making a backup of your Huey campaign files before changing anything though, and suspect that any changes you make will be overwritten when the updater next updates your system.

Hi I've now seen other mentions of this so thought I'd raise it. I hosted a custom made multiplayer mission with infantry transmitting an FM homing signal on 40.5 FM. My helicopter running on the server got both the sound from the .ogg file and a homing signal (i.e. the needles deviated to direct me to the troops). The remote client got neither sound nor homing signal (i.e. the needles remained centred). We tried this a number of times but to no avail. Works on host, but not remotely connected clients. My DCS installation is at 1.2.7 and has been upgraded with the automatic update system since the auto-updates started. EDIT: I may have further info to help fix the bug. Other players report that it appears that if the client joins before the frequency is set, then they can home in (but no sound). If the frequency is set before the client joins then the client is not made aware of this frequency being set, i.e. clients don't get notified of already active transmissions. I assume that the set frequency is transmitted to the connected client machines as an event at the time it is called and that the transmission is still live is not transmitted when new clients connect.

Thanks for that Highwayman-Ed Much appreciated :)

Afraid I'm sticking to my personal view (not endorsed by any major sponsors) that the FD should be used where appropriate, and not used at other times. While I'm currently convinced that this probably isn't the case in the real KA-50, when using a desktop mounted spring centred stick that is centred relative to trim and not relative to centre, flying without FD mode when doing arbitrary manoeuvring with the constant need to change the flight parameters is the only way I can get the KA simulator to behave as I, the pilot, need it to without getting into parameters that would be considered extremely dangerous IRL (could that be the longest sentence I've ever written?). The argument is simple: A pilot should always be in complete command of their aircraft and use whichever method maximizes their capacity to do so. In the real system, with an AP that has 20% authority and a cyclic directly linked to the steering mechanism I would probably never use FD. But on a desktop PC where the AP has way more than 20% authority and the cyclic isn't connected to the steering linkages and is controlled relative to trim (i.e. a wondering centre) then FD is simply the only way to attain that complete command of the aircraft when performing complex manoeuvres with rapid changes. Like hiding behind buildings and hovering next to the window of the university shower rooms... um... you know, for national security reasons! The best advice I can give is: Learn to fly the helicopter as best you can in all three states: AP, FD and no AP. This way when the need arises or circumstances throw the unexpected at you then you can perform well regardless of the circumstances, and can decide for yourself which mode best suits your situation and easily switch modes as needed. Don't fly like I tell you. Learn the chopper inside and out, then decide for yourself.

I have a slightly personal take on this topic based purely on the fact that a joystick doesn't work like a cyclic. With the cyclic you don't need to quickly return to centre each time you trim, for example. Here's what I've found works very well for manoeuvring the KA-50 simulator when using a spring centred joystick like the Thrustmaster HOTAS: When flying a route with little need to manoeuvre, fly in autopilot (non-flight director) mode 1. press and hold the trimmer button 2. establish your new flight path using cyclic, collective and rudder 3. when you're stable in your new flight path: 3.1 release the trimmer button and then immediately 3.2 centre the joystick and rudder 4. your new flight path should be established and honoured by the autopilot You release the joystick and rudder quickly to ensure that the collective and cyclic position don't change in the sim. When you need to manoeuvre in an arbitrary fashion as happens when taxi'ing around airfields or deftly hiding from tanks, popping up to fire then scooting off somewhere else then use the flight director mode. This is still autopilot stabilised but the helicopter honours your trim and power settings, not your desired flight path, i.e. you are flying the helicopter, not the AP: 1. establish desired flight 2. trim and immediately centre the joystick and rudder 3. go to 1 Another method using flight director mode that works well for me for very short periods when manoeuvring in combat is to trim to a known setting for my performance needs using the control display indicator, then fly the combat engagement without trimming again. So for example if I trim to a setting that would give me 200 km/h in order to go in for a quick cannon run followed by a few quick turns to reverse me direction then I'd set my trim, use collective to ensure level flight and about 200 km/h when I get to target. This means that when I get to the target I'm a) stable b) able to focus on using the cannon c) trimmed for a quick getaway regardless of any emergency manoeuvring resulting from unexpected threat emergence. The above methods evolved because using a spring centred stick that is centred at current trim rather than current centre makes deterministic flying a very high workload for me in situations that require extreme manoeuvring. A situation which has got me killed many times because I have to stop to figure out what my chopper is set to do and how to get it to what I want to do. When doing long distance stand-off attacks I'm almost always in auto-pilot mode unless I'm duelling something that's trying to kill me and constantly hopping into and out of cover. Don't forget that the autopilot is there to allow you to focus on deploying the weapons rather than flying the aircraft. It's a workload reducer that aims to make a single pilot capable of all functions of an attach helicopter. Use it and use it intelligently. My two cents... hope they're useful.

That's disappointing. Being able to set up "standard" bases and then customise them would make mission building far quicker. That means that to do this I'll need to extract the FARP objects from the .miz file and manually add them to a new mission file to move it from one mission to another. Bit of a hack with a risk of corrupting the .miz file me thinks. Thanks Davis0079 and Wrecking Crew for the answers. Much appreciated!