fencible

Thank you Spanueh! You are quite right. After removing conflicts between the co-pilot and pilot controls the Gazelle is flying beautifully for me. How did you find out about these changes? Just figuring it out for yourself?

I am finding that either my throttle quadrant (used as collective) or yaw pedals do not work properly since the last update. I have tried tuning them carefully - but one or the other becomes highly jittery upon entry to the Gazelle. When I look in the controls update window for key and button actuated controls, the first entry has several red exclamation marks in it. In the Axis control window, everything looks normal and working. When I switch back to the cockpit the pedals or collective don't work properly. All my other helicopter controls (I have all the current DCS copters)) are unaffected and work properly after the last update.

Yes, they have removed the auto-hover feature "for consideration". I noticed this too. You just can't use the air-to-ground missiles right now unless you have a human crew member, it seems. Still - the reworked flight model feels like a huge improvement to me - after I tinkered with the axis settings. This is a beautiful update and I am enjoying the flight model and flitting around the pyramids in new Sinai map. It is now possible to do really controlled delicate landings. I notice the chopper has become very weight sensitive - and this is a good thing. I do hope they bring back the auto-hover feature to allow single players to use the air to ground missiles again, though...I know that it is a compromise to allow a single player to do both crew tasks, but - that was an important 'compromise' and it really raised the fun-factor for me.

Ok, this problem is remedied when I turn off the weapons safety, change into the CP/G position, and click the square white button on upper left corner of the right hand controller. It is in neutral position to start, and I click it up or down and then back to neutral. That's it. After returning to the pilot seat, George will now respond to my weapon commands. He will spot, laze, and fire both types of Hellfire missiles, the gun, and rockets.

As the pilot utilizing the George interface, I cannot get him to fire any weapons. He will laze, and say he is engaging a target and he will say that he is firing, but he never does. The target box never appears, either. I have carefully followed instructions from the manual and from Charly Owl's latest guide without luck. I have approached targets at various altitudes and set up exercises with targets out in the open with no line of sight challenges, but to no avail. I have tested this feature in the Caucasus and Siria maps. When I run the training episode and set up the CPG position as instructed and then change back to the pilot seat, the George CPG will easily engage and fire on targets.

I find that in all my missions, older missions as well as newly created ones, only unarmed vehicles are present on the map after starting the mission. No infantry, artillery, armour, AAA forces show up. There are no errors displayed. Just an empty map, except for aircraft. Any ideas? I have 24GB RAM and lots of disc space. I have also not been able to access online servers since first 2.8 beta release. DCS World always crashes when I attempt to join.

Thanks for that information which I did not know. Still, I always deactivate nose wheel steering immediately after lining up on the runway. So that can not be the cause of this issue in my case. Perhaps I am turning it on when landing while still traveling above 50 knots, however - so I shall be attentive to that possibility in future. Thank you for your help!

I consistently find that I can not activate nosewheel steering after landing MB-339. It works properly while taxiing before takeoff. I turn it off before takeoff. Then, after landing it cannot be turned back on. This happens consistently.

I have this exact problem in an older mission that I made on the Caucasus map. I had reset the ammo counter, and set the air supply to 'BOTH'. Still, no guns when I needed them. The problem does not exist on the Syria map - I have not tested other maps yet. On Syrian map my guns work as they should.

Air source is set to 'BOTH'. Counter is set to 670. Safety is off. No fire from the gun. As I said, the gun works in the dogfight training mission. It seems to be the home made mission that this happens in.

Wingmate, Thank you for that advice...I did do as you said. Still, however, when I go to gun mode with safety off, the ammo counter reset, the gun will not fire. All 3 missile types launch successfully, but no gun. When I run a training session the gun works, of course, but there seems to be an issue with home-made missions.

When I enter a mission in F14-B there is no gun ammunition when I get airborne. I specify 100% gun ammunition in the mission, and I have tried reloading ammo before the mission, specifying 100%. But when airborne, I find the gun has 0 under the G in the hud when gun is selected in A to A mode.

Since Aerges is on the Mirage F1, I imagine that there are many familial similarities with the Mirage III (any mark) - the fuselages, cockpits, engines, design culture.... I would like to see them add the Mirage III to their stable as the development effort might be partially assisted by the work done on the F1. I fail to see the attraction of the F-104 - as a Canadian I recall the large number of F-104 crashes in both the Canadian and German air forces. The only use they could find for them was as low-level high speed penetration strike aircraft carrying tactical nukes - and they had this tendency to sink into the ground on pull-ups due to their stubby wings. I am open to having my mind changed on the subject, but I don't think the pilots who flew them were all that fond of an aircraft they referred to as 'The Widow Maker'.

yes, this is what I have been doing for the cyclic. I will try your suggestion for the pedals.

I have observed this problem as well while operating from back seat, with George as CPG. After a few attacks, he no longer fires missiles, even though targets are clearly in range and visible. It occurs only after I having been playing for a while, so that hints at possible memory leak issue to me.