Xpendable

Did you fly the plane long enough for it to accelerate past Mach 1.0 and all the way to Mach 1.6? It doesn't happen in seconds, it takes a bit of time to reach that speed. But it will happen, 100% of the time as shown in the video. I've had 2 other people independently verify this both online and offline and recreated the exact same thing using my instructions on the very first try. It's disappointing that you can't recreate it, because everybody else who tries seems to be able to. Should we have other people record videos to prove it to you?

The throttle does not have to be at 100%. But you DO have to start with a bunch of bombs (like GBU-38's) and then drop them. Trust me, this is a BUG. Straight and level flight after dropping a bunch of GBU-38's with less than full throttle and the plane WILL go supersonic and will continue accelerating until the wings rip off. It does NOT do that if you start with an empty plane. You cannot recreate it unless you start with GBU-38's (I suggest 10) and then drop them. That's the bug. Watch the full video and you'll see it.

Here is my YouTube video showing how to make the AV-8B go supersonic in level or climbing flight due to what I think is a GBU-38 bug.

Reddox, it looks like you did a filament change in the middle of printing the UFC Top, is that correct? I wonder if printing in glow-in-the-dark filament for those layers might be cool? I think the glow-in-the-dark stuff is slight translucent... wonder if there's a way to light those layers with some LED's to make it look like it's back-lit. UV light would make it really pop. Might be a cool experiment. I've heard the glow-in-the-dark materials are corrosive however, and will eventually destroy the nozzle on the 3d printer. I've only printed with it a couple of times.

This is really awesome. I'd love to print this. I was able to get the buttons but not the UFC itself. Anyway to post this again / somewhere? I dunno if the new forum system lost the attachments. Disregard, after another day or two, the download link appeared and I was able to grab the files. I'm planning on modeling the throttle handle will be happy to share that when I am closer. I did start modeling the throttle handle in FreeCAD. I would have loved to have used Fusion 360 but they recently removed features from the "free" version to try to force you into the $400 a year subscription - and I'm not going for that. My biggest roadblock is that I can't find dimensions of the throttle anywhere on the internet. So I'm just "guessing" as best as I can and going from there. The cool thing is, because everything is parametric, I can adjust every dimension and constraint until it looks like the real thing and "feels" right. But it will still be a lot of guesswork. Fun project, regardless.

Loadout: TPOD 10 GBU-38's (2 pair on inner pylons, 3 pair on middle pylons) Load up the plane with 10 GBU-38's. TPOD may or may not be necessary. Climb above 12,000 feet. Drop all 10 GBU-38's. The plane will slowly start to accelerate beyond Mach 1.0 in straight and level flight (or even in a slight climb!). It's as if the plane became magically lighter than it's normal empty weight. You'll be able to hear the sonic boom and everything. Eventually the plane will accelerate past Mach 1.06 and the wings will fail shortly thereafter. I have recorded a YouTube video showing this and will upload here when it is ready. The problem does not happen if you takeoff with nothing loaded. I haven't tried any other ordinance, so it might only be a problem with the GBU-38's.

I think Eagle Dynamics's authorization servers are broken right now. Seeing the same thing. My DCS client hung at login for 10+ minutes. Eventually it went past it. But then I made the mistake of clicking on the modules button, and now I'm stuck again, 15 minutes later.

I'm pretty sure Eagle Dynamic's authorization servers are having problems. It took 10 minutes for my game to start and I made a mistake of clicking on the modules menu option and I'm stuck with the waiting circle for more than 15 minutes. I don't have the Steam version but I bet it is related.

So the official bug tracker appears offline for me... Apologies if these things have already been reported. In multi-player, the Harrier will occasionally start playing a fraction of the "Landing gear!" alert then stop, at completely random and inappropriate times. My controls are not glitching and no other plane does this. Also periodically (maybe once every 30 minutes) the Harrier, while in cruise, starts going through a bit test of all the audible warnings for no apparent reason.

This is definitely a bug. Flying the exact same maneuvers in the P51D, fw190, and me109 do not result in what happens in this video. It is not a case of not flying the plane smoothly. It is also not always consistent. I am tired of people claiming it is not a bug. The facts prove it is a bug. Sent from my SM-G920V using Tapatalk

Hadn't noticed that but did notice the 2 tails bug. Sent from my SM-G920V using Tapatalk

I was having an impossible time trying to land this bird, and I am a real pilot. I kept floating and floating. Finally discovered there is a calibration problem with my X52 throttle and I was always getting 10% of boost at idle... #facepalm or rather, I was never able to obtain idle. Fixed that by editing the curve in the control options. Landed nearly perfectly on my first attempt after that fix. Sent from my SM-G920V using Tapatalk

I had a chance to do some more testing last night. I was wrong. It is indeed negative G that causes this and not positive G as I had said. You can reproduce this by pushing the nose down hard at high speed and it blacks out. Relieving forward pressure and the view comes back. There is a transition to and from G-loc but it is much faster than it should be. Sometimes it appears to go from 0 to 100% in 1/10 of a second. If you don't do it as quick you can see a slower transition. But I believe it is too quick and or sensitive. Sent from my SM-G920V using Tapatalk

That's actually the way it is supposed to be. Seriously. Have you ever noticed almost every fighter has a different non-gloss paint over the top of the nose? It is to prevent the sun from reflecting off the nose blinding you. Sent from my SM-G920V using Tapatalk

I have the same issue and I think it is a bug. I believe it is high positive G's, not negative G's. What normally happens in other planes is the screen fades to black as g-loc is increasing in effect. In the Spitfire the effect goes to 100% blackout instantly and goes away instantly. There's no transition. It should ramp in as the effect is increasing or ramp out as the effect is decreasing. But instead, the minute the tiniest amount of g-loc is occuring, the screen goes 100% black. To better describe what I'm seeing, let's compare the Mustang to the Spit. If I were to plot the amount of "blackness" over time while doing a high G maneuver, it would like the following. Each line represents 1 second. P51D: ====== 0% 0% 0% 1% (G-Loc starting) 5% 20% 50% 75% 100% (Full blackout) 100% 100% 90% (pressure released) 70% 50% 30% 10% 5% 0% (No g-loc) 0% 0% Spitfire ====== 0% 0% 0% 100% (compared to 1% in P-51) 100% 100% 100% 100% 100% (Should be 100% blackout as compared to P-51) 100% 100% 100% (Control pressure released... blackout should be fading out but doesn't) 100% 100% 100% 100% 100% 0% (No more G-loc) 0% 0%

I have confirmed that the issue is in fact G-Loc. It does not have anything to do with the Oculus Rift. I believe the manner that G-Loc is kicking in is possibly bugged. In other planes, G-Loc fades in (or rather the screen fades to black). In the Spitfire, there is no fade transition. It's 100% instant blackout. i believe that it should be fading in just like the other planes, but instead it goes to 100% blackout just as G-loc is starting to take effect. It also doesn't fade out like it is supposed to. It's literally like a light switch... If G-Loc is > 1% the screen is 100% black. When G-Loc goes < 1% the screen switches back on. There is no in-between. The screen is either on or off.

Thanks for the guide. I've already read it word-for-word and learned a lot that I did not know. Great job!

I thought I did. It works for the P-51D. Are the settings different from plane to plane? I'll check again when I get home.

For some reason, when I'm flying the Spitfire with my Oculus Rift CV1, the screen goes black when I enter rolls. It is instant dark... it doesn't fade in or out... it's just like the display is switching off or something. If I'm lucky, it will switch back on eventually. I am not sure whether this is tied to blacking our or not, but I don't think it is. It can happen even if it is a slow speed roll (both roll rate is slow and forward speed is slow). It doesn't happen all the time, but it happens most of the time. There's no way for me to be able to dog fight with this plane. Has anyone else experienced this? Also the mirror is just showing a black circle all the time. EDIT: I found out that mirrors were turned off in settings. I turned it on and the mirror worked, although as others reported, the FPS dropped dramatically with mirror turned on. I am keeping it turned off for the time being.

Ah, I must be an idiot. When I looked at the downloads section last night, I did not realize there was more than 1 page of downloads. I only saw the 1.1.1.1 patch and assumed it was a cumulative patch for all versions. I checked my version and I'm at 1.1.0.9 so I need to download the 1.1.1.0 first. Doing that now. Thanks for your help!

I just got a retail boxed version of the A-10C Warthog. I downloaded the 1.1.1.1 patch (all 4 files) but when I try to run the patch, it displays a message box that says "DCS A-10C version 1.1.1.0 EN should be installed". When I click on the OK button it exits. So... how do I get this patch installed? I'm a little frustrated and appreciate it if somebody could tell me what I'm doing wrong.