statrekmike

Thanks so much, I saw what I was doing wrong (I was leaving in the "--" part. It now works perfectly.

I just tested this, it did not work. Perhaps you could just upload a copy of your lua file?

Nice!

The map sizes are a serious issue for the Foxbat, It's a fast plane and that will make a already small(ish) map feel MUCH smaller. Don't get me wrong, I love the MiG-25, it's one of my favorite aircraft of all time. Additionally, I would love to see it in DCS as I think one could do some really cool missions but it would only really be good if we have a map big enough to really support it. It's the same reason that a SR-71 would be kinda silly. The MiG-21 already feels a bit cramped (in some ways) in the current map, I can only imagine what that would mean for the MiG-25.

Would love the 109K, I have not been able to wrestle up the money to afford it and probably won't be able to for a long while.

I want a Hawk

The F-14 would have proper opponents, They may be FC3 level aircraft (the Su-27, Su-33 and the MiG-29) but they are still valid and proper opponents.

With the X-52, I found that using the "clutch" button (the one in the middle of the lower rotary) in conjunction with the upper rotary allows for zooming without stutters (because it only reads the input when you are actually manipulating it, when you let go of the clutch button, the shakiness will stop.

It would be cool to see a AC-130 but as much as I love that aircraft, I would rather they fill out the interceptor, air-superiority and other fighter aircraft roles a bit more. We have plenty of ground attack/CAS platforms now but still have massive gaps in other roles.

I went ahead and changed my password for both this site and my email just in case, I don't really trust those emails.

I have learned a long time ago that the 'Dogfights!' show has a ton of errors (to say the least), that CGI rendering of the maneuver was probably a bit exaggerated to look more dramatic. I have no doubt that it happened but that "footage" makes it look downright silly.

I don't know if I would want that to be the next project but I would love to see it eventually.

Look, I am just going to let you know that you have now crossed the line into making angry demands as opposed to suggestions, you know, just so you know. As I said before, using the mouse works just fine in situations where you don't want to bind controls that are already present in the cockpit, if it is that much of a hassle, perhaps you could just find a few buttons on your HOTAS that you can double up (using modifier) so that you can bind multiple functions. For example, when set the binding for my weapon release, I bound a modifier so that the same button will open the safety cover when I hold my pinky switch. The same could be done for landing gear, you can set a modifier and have handy access to both the main gear lever and it's lock. These are things that require no extra software and can all be done in the DCS controls options screen, if that is not convenient enough for you, well, I don't know what to tell you.

The extra steps are not a huge issue, in the case of the landing gear handle specifically, I don't bind anything, I just use the mouse to control the level and it's lock, it takes no effort and is very quick. The same can go for other controls you don't use often, the cover for the button that drops the chute could be bound but why? Just open it with a mouse click before you come in on final approach so that it is ready to go when you hit the deploy chute button. I only use my HOTAS for commands that I am going to use a lot, the rest I leave to the mouse.

How long were you actually able to fly with 100% oxygen on before it depleted? I mean, the point of the issue is that the oxygen should last (unless my assumptions are wrong) much, much longer than it does. Perhaps the dev's could provide more info in terms of just how long the oxygen is supposed to last.

I am getting a impression that the oxygen issue is a bit bigger than just the oxygen system itself, perhaps there is a issue with how hypoxia is implemented? Is that even something that can change from module to module? Either way, I keep hoping that there will be a fix for this soon, it does limit what one can really do in the aircraft.

I suppose the best place to start is to know just how long the oxygen on a MiG-21Bis is supposed to last in normal conditions, anyone have any idea?

After some testing, I have found that the oxygen bug is still present in the open beta, at 30,000 feet and a full fuel load (one 800L and two 400L tanks), you will run out of air before you run out of fuel.

I just tested the oxygen system a bit ago and it seems like it might be taking longer to deplete but I don't know if that is just my imagination, anyone else notice any changes to the oxygen system thus far with the open-beta?

I am downloading the open-beta now but can anyone tell if the oxygen issue is fixed yet?

Aside from very specific situations, I always ramp-start, it is part of the experience and the process tends to "get my head in the game" for lack of a better phrase. The only time I don't do cold starts is when I am having trouble landing or taking off in a new aircraft and need to practice doing them over and over.

I can deal with a aesthetic bug like that, it is the oxygen bug that I can't really deal with at the moment, it pretty much ties one hand behind your back since the MiG works best at 30,000 feet or so and with the oxygen system the way it is, you can't stay up there long enough to complete a patrol. Now, again, before anyone gets the wrong idea, I am not saying this with any sort of anger or whatever, I love the MiG-21 module, it is actually my favorite module for DCS since it is clearly built to a very, very high standard but that oxygen bug is really tough to ignore and severely limits what one can do with the aircraft. I really, really, really hope that the oxygen bug gets fixed in the first patch, I did not see it on the patch notes and I am kinda hoping it was just a simple oversight, everything else that I noticed seems to be fixed in that patch so I am confident that considering the huge problems that oxygen bug produces, it will get fixed in that patch as well.

You are right that there are indeed other modules that have to wait a long time to get bugs fixed and I am not being critical of Leatherneck for the bugs that the MiG has, I understand that it is simply how development of such a complex piece of software goes and as such, I am not upset over having to wait for some fixes. That said, some of the bugs that we have with the MiG are pretty big and can have a very real effect on the sale to potential customers (the FPS issue being a big one) and as such, it is my hope that ED does not hold the process up by making Leatherneck wait for a big update in order to roll out their patches as it could have a very negative effect on how people view Leatherneck's bug-fixing even when it was not their fault. To put it simply, the fixes for some of the MiG's bugs are pretty critical and it is my hope that Leatherneck can release patches when they are actually ready and not when ED decides to release it's larger updates. Without really knowing the patching policy for sure, I can't help but be a little worried, I really hope that ED gives it's 3rd parties (note, I dd not say 3rd party partners like belsimtek) the ability to patch when they want and not when ED wants.

Since we still don't really know when EDGE is actually coming out, it does not really make good business sense to let a module that has had such anticipation build around it pre-release to remain in a rather buggy state for a rather undetermined amount of time.

Well, hopefully ED lets Leatherneck get those updates out the moment they are ready as waiting around too much could have some effect on potential sales, some folks are going to hold off on buying it until the patch comes out so it is in ED's best interests to make sure that 3rd parties can update when needed and not just wait for when ED decides to do a big patch.