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.

I think ED should provide the same 'Default' trim option that the other DCS helicopters have. Everyone knows how to use that setting, and it works well. There is currently no option to avoid using force trim in the pedals, and perhaps this is a real limitation with the AH-64D, but I would much rather have no trim at all on the pedals. It is possible to turn off all force trim in the Apache from an in-cockpit configuration page, but you really need trim on the cyclic stick. I can fly the AH-64D comfortably as it is, using the force-feedback friendly setting, but it does not feel right, and I find it difficult to transition trim for landings.

I see a repeated issue with F-14 in the DCS Beta stream after I have been operating the F-14 for more than an hour or so in DCS. The ability to activate nose wheel steering stops working. Both the HOTAS stick button I have assigned to this function, and the default 'N' key command just stop working after a while. It looks like a memory leak sort of issue to me. Exiting DCS and restarting it restores the functionality. This occurs in the Caucasus map. I have not tried it in others yet. I have 24 GB of RAM on my system.

Thank you, Reflected! Great advice. I let the AI fool me at the beginning of climbs with their ladder shaped climb at the beginning. Most importantly, your comments on engine, RPM settings, and use of the boost lever are very enlightening! Thanks for passing on the information about AI behaviour to ED. I love your campaigns - wonderfully immersive, detailed, and richly embellished with period details - thank you!

I played a mission from Wolf Pack today and found 1) that the AI flights took a long time with a lot of circling and many near collisions to get the mission finally under way. 2) As soon was we started climbing out at the coast, I was left eventually miles behind. Even going flat out, I could not come close to keeping up with the AI P-47s, and finally lost sight of them. I dropped my tanks and red-lined the boost and RPMs, but still - I eventually almost caught up with the pack by cheating with the F10 map to locate them, but not until they where almost rendezvoused with the returning B-17s we were tasked to escort home. The behaviour of the AI friendlies was better in that they were not teleporting sideways as much, although it still happened a bit, but the performance profile of the P-47 AI aircraft doesn't match at all with that of the complex (human) module. This is making it very difficult to run the scenarios because I am flying what is effectively a different, much slower aircraft than my AI wingmates.

As of most recent update, I see no afterburner flames behind the jet nozzle on my player Viggen. I see flame inside the nozzle. AI Viggens do exhibit external afterburner flames.

Issue resolved for now. I made a 6th attempt at a repair last night, and this time it worked. The game started up after the repair was finished, and I was able to log in. So - issue solved - thank you!

ISSUE RESOLVED. I was ejected from an on-line server which detected that I had a tainted load. A Viggen texture file had become corrupted. I removed the corrupted file and ran DCS_updater.exe repair (I have followed this procedure successfully in the past). After the repair, DCS failed to come up. When I ran the run.exe nothing appears to happen. If I run the task monitor while trying to start DCS, the dcs task appears only for a few seconds before exiting. I've re-run the repair 5 times or more without success. So my beta standalone DCS (with my new Super Carrier and P-47D) is dead in the water for now. The stable version runs, of course.

The problem with delayed fusing is that there is certainly no accounting for the effects of delayed fuse bomb penetration. Bombs exploding 5 of 10 feet under the ground should have their blast radius reduced considerably - but that would be so complex to calculate. You would need to classify all the terrain on any map by how deep the soil (if any) is at any location. Same for building structures. I think that DCS does account for penetration delay on hardened targets like bunkers, but that's about it, as far as I know.

For now you can do the following on home-made scenarios: reduce the gun ammo on the JU-88s to 5% or 3% in the scenario editor. Then make dummy runs at them until they unwisely hose off all of their bullets in one very long barrel-melting burst. After that they have no guns, and only avoidance maneuvers (which they're pretty good at) to save themselves. The JU-88 was a formidable, fast aircraft for its' time.

Merci Croustie - I did check the circuit breakers and one was popped out (for the cabin lighting). I pressed it in. No other breakers were popped that I could see. That is why I mentioned the incident here. I have also seen my airspeed indicator get 'stuck' at about 230 mph after a long flight over the channel. There seem to be a few instrument issues at this time.