Zimmerdylan

Yes....and read the date on the last post before mine. That's exactly what I was getting at.

LOL.......:megalol: You just performed CPR on a horse that has been beaten to death, propped back up, beaten to death again, revived, fed and recovered, only to be beaten to death about a hundred more times. :music_whistling: These guys just loooove to argue about this. :argue:

"1) Not having the stick hard back" For me. I tried pulling the stick back with the Spitfire when I first got it. I read that it locks the tail wheel like it does in some of the other WWII aircraft. If it is actually implemented in the Spitfire, I cannot feel it. Nor can the literally dozens of guys I see whipping it all over the taxiways in servers. I maneuver it around on the ground just fine now and really haven't felt much use for the tail lock anyway after I got use to it's ground handling.

From where you are now....it only gets easier. If you want a real eye opener....try and take off in the 109. The spitfire is a piece of cake next to that plane.

Guys: I've been with DCS for a very long time now. From it's earliest days of Blackshark when it came out on CD. What any old timer here will tell you that this is the nature of this beast. And all of this takes a lot of time. No matter who's designing the software. The guys who have been waiting patiently for the WWII map have been doing so for years now. And they have dealt with delays, problems, and lots of missed deadlines, and they're finally getting their reward. Just like those of us who waited patiently for the Nevada map and 2.0. Yes, there are issues with both 1.5 and 2.0 for many right now, just as there have been issues with many things over the years. And we all get your frustration as we likewise get frustrated. However, it's the way that it is with this kind of software and we have all grown to understand this over the years. It cannot be helped. Every game that was worth playing that I have ever downloaded has had bugs and issues with updates. And people always seem to forget how good the game really is when something goes wrong. The one thing that I do know for certain is that all of the issues will get fixed. And when they do (as usual) DCS will shine like it always does and we'll all be grateful. Chin up fellas.:thumbsup::punk:

Flown in: C130, C141, Huey, Blackhawk....That I can remember. Jumped from: C130, C141, Huey. Use to sit and watch the A10A's make hamburger out of armored vehicles from only a few hundred yards away. I always marveled at the damage that the A10 could do. And how gracefully it did it. That's something that you never forget. The sound, and certainly the visual. I'm very envious of Bignewey as I always wanted to fly in and repel out of the Chinook but alas I broke my acetabulum (socket in my ass bone) on a night jump and was pretty much off of jump status when my only chance came around. I made the terrible mistake of reaching for the ground because I wasn't quite sure if I were going to land in what I though was water. Still a stupid mistake and the excuse is a bad one....but hey, I hate water. They had me driving for a Colonel for the rest of that year. All of this was 35 years ago when I was a kid. Lately, the closest I get is watching the A10's fly over from Davis Monthan, and giving music lessons to A10, and F16 pilots. That's fine with me. OH...I only briefly flew in the Blackhawk. I was stationed at Hunter Army Airfield and was ETS at about the time the first Blackhawks were arriving. One of my buddies talked the CO into letting me take a short flight to Ft. Stewart and back just to get a taste of it. If anyone knows the distance from Hunter Airfield to Ft Stewart, well....it wasn't a very long flight. Maybe a total of an hour and a half.

It's all good. I was hoping but doubtful. I have seen lots of requests for logs and such from you guys and know that it's not easy when you cannot replicate the problems on your system. I really hope to see some kind of a solution soon. Thanks Sith

I meant today. NTTR is pretty much useless to me and so many others right now.

Ah...there it is. When I go into a hover, I use the pilot trim and the heli just decides to go into this weird auto pilot mode and it becomes uncontrollable. If I hit the trim again, it seems to go into a different mode, still uncontrollable.

Lord I hope some patches to fix 2.0 come with the WWII map.

Yeah but I think that it should stay just as it is for the time being. Although it's kind of a pain in the behind to have 2 or 3 installs on my computer, NTTR is a god awful mess for many of us as of the last update. I can at least go to 1.5 now since my 2.0 is not working properly. If the two were merged, I would think that many of the updates would have lateral effects and that both maps would be messy at that point. I may not be very happy that Nevada is the way that it is right now, but at least ED has left me with something to play on while I stew about it. :smilewink:

That would be the best explanation for what happens when I have a crash in the Gazelle. Whenever I respawn, the aircraft respawns damaged. Most of the time the tail will be off to the side. So I respawn again and all is well. This only occurs in 2.0 and I never gave it much thought until I read this thread and it makes sense that it's happening to the Gazelle.

Yeah....I know........I guess it was a pretty legitimate question.

Being that I posted this thread under the Huey bugs section.........One would hazard a guess.....:megalol:

Wow....Happened 2 times on a server, and once in single player but now I can't seem to replicate the issue to make a track. I guess just disregard this thread for now.

For quite a while after I purchased my first X52 HOTAS had a terrible time dealing with those pesky sticking points in the throttle that are located @ ¼ and ¾ up. Many was the time where I'd be trying to throttle up or down and I'd bump in to one of those humps and I would be forced to overcompensate my movement as I would carefully pushed past the bump. Especially when hovering a chopper. It was infuriating. So early on, I learned how to fix the issue and have had 2, X52 sticks over the years and modified them both to rid them of the humps. When I first looked into it I went to Youtube and watched a few videos on how to fix the issue. In the videos that I saw, they had you remove a part of the clutch assembly. The actual solution is so much more simple than that. Since I am doing it to my new X52, I am posting some photos of how I do it. It's easy, and you don't have to do much to remedy the issue. So those of you who aren't too mechanically inclined can see an easy way to get rid of a feature that has proven to be more of a pain in the a$$ than a benefit. If there is a benefit to these humps, I don't see it or use it. Hopefully these pics will help solve the issue for you. [/img] [/img] This is a simple operation. If you mess it up, I claim no responsibility. You can have your 10 year old do it as far as I am concerned. So it's pretty self explanatory. I just thought I would put this out there to shed light on it for those who are not a fan of the feature but aren't sure how to get rid of it. :book: When reassembling the unit, you need to place the throttle itself so that it is positioned paralelle with the pedestal that you are putting back together. If it is in the forward or reverse position, the rocker arm doesn't fit easily back into the unit. Also, be aware of the wiring harness and make sure that it isn't sitting anywhere that it will get damaged when you reassemble the box.

lol...I was wondering where all of those boxes came from under my name. Went from 3 to a bunch in one day......

When you are sitting on the runway on a cold start, the altimeter is never set. You have to set it manually to keep things accurate. The way that I do it is: I hit F10 and look at the actual altitude of the plane as it sits on the map. I then use LShift+B and that winds the altimeter very quickly to within a few feet of the actual alt you saw on the map, and then use the knob to get it exact. Using the mouse with the knob takes an aweful long time. If you overshoot using LShift+B , then you can use LCtrl+B to fast wind it backwards. This is the quickest and easiest way that I have found. Everyone has their way of doing things....This is just the way I have found it to be easiest. :book:

All I can say is: I'm not holding my breath. Nothing personal Belsimtek.

Guys....This issue has been a problem since the very beginning. Tracks have never worked correctly.

If the mission has a crosswind....then that's your whole issue. Follow Andy's advice at this point.........

LOL...Yes, of course.

Thanks for letting me know. I'll have to try and figure out what happened. I'll run a repair and fiddle with assignments to see if I can bring them back to life.:joystick:

The spitfire seems to have lost it's wheel brakes after the update. I try to manually set them using the mouse and it doesn't work. I have them set on my HOTAS and they do not work there either. I checked and all of the assignments are correct but it just doesn't work in game. I tried to start mission from runway to see if they would work. Plane would not move. It wasn't as though the brakes were holding it back in game. The plane just didn't move no matter how I set the throttle or RPM. Anybody else having this issue??

That was kind of what I was thinking. If he trims it for takeoff (Manual says 5 deg.) and just uses his rudder to keep the ball centered from there. When he tries to land, the tail will be very heavily trimmed for full throttle while he's landing with very little throttle.