noah895

We flew so far east we stopped seeing houses and towns haha. Sorry, it was mission 2 not 3.

So I bombed the train, fought the FW190s, then the flight leader said to form back up. Then we flew mostly east. I think I was near Berlin when I knew there was an error haha. So I flew west, found a landmark and made my way home. Some random chats fired, but the formation was close to Moscow at that point haha. Also, as I tried to contact the ATC for navigation guidance…nothing on any radio channel for any airport. Even once I found Kerney…no channels will work contacting the tower.

Which ever the latest one is

One day when these AI rise up and Skynet takes over maybe we will have things better

Ah. Why can’t all these AI just wait their turn to takeoff…geeze haha. Thanks for the reply. I hope your vacation was enjoyable

Tried running the bonus channel mission in BNBB and the AI is all stuck on the taxiway not taking off one day I’ll fly this mission haha.

At the start of the mission all the AI aircraft are log jammed at the end of the runway and will not takeoff

So my intro screen says “Intro 2” and starts in the Spitfire. I just went to the mission editor and saw there was an intro 1 (which I played and heard what my task was in the second part). Any idea why part 2 played instead of 1?

So am I missing something in the intro mission? The ground crew and I have a 3 sentence exchange and then there are no more queues or anything. i read some of the documents, but nothing is giving me an idea of what the “intro” mission is supposed to do.

So as I play the mission now it is still bugged. Just a sad helo hovering and not picking up the pilot. Has this been fixed or is the downloaded mission from previous links still work for TEW 3.0?

When you select 38.6MHz on the FM radio to home in at Anderson, the gauge does not work. Is there not an actual FM radio beacon for Anderson?

Yeah, I understand. Sadly I’m not sure what to do when 4 P51s are crashed on the runway haha. Thanks for taking note. I’ll try it after the update.

I tried playing the BNBB bonus mission today and got started, got taxi clearance, then immediately got told to “Hold Position.” A bunch of the P51s had ran into each other on the runway. I ran the mission 3 times and each time the AI aircraft crashed into each other.

I figured it out…I’m an idiot. It is one solid gauge haha.

Although they are both inline right now, they move independently...

There are 2 needles in the airspeed gauge. One is larger and there is a smaller one. Unless I am seeing double or there is a bug…there are two haha.

What is the second small needle on the airspeed gauge indicating? i Googled it, but no luck so far

ZnarF, thanks for your thought, but those still do not help me solve this problem. The first one worked fine until some update and now there is a conflict in Windows with the drivers of it. I need help solving that problem. Thanks.

IMG_1411.MOV IMG_1412.MOV Any thoughts? I went to Logitech and they gave me a list of things to do. None of them worked. They sent me a new throttle quadrant, and I still have the issues. I have disabled each different USB human interface device (HID), unplugged each device, and still this is happening. Anyone have any other thoughts?

Still having the issues. It is doing it in the windows "setup USB game controllers" calibration page as well. I am pretty sure something changed in windows that messed it up or the controller went bad. Let's see what Logitech can do for it.

Furiz: I checked it in Windows and the axes are fine and no jumping in the USB Game Controller Settings. speed-of-heat: I'll give that a try and see.

So my throttle quadrant worked great until the new patch yesterday. I was flying the P-47D Wolfpack campaign and after takeoff when I was lowering my engine RPM the engine kept revving and lowering. I thought I had an issue with the engine, but I noticed my RPM lever jumping back and forth. I Googled the issue, took my controller apart, cleaned the pots, went to the Logitech website and re-calibrated the controller and still no joy. I verified that I cleared all the controllers assignments and after trying them one at a time still had the issue. I checked everything I could, but have no joy. I am pretty confident all the axes on my controller did not die at once, so I am leaning towards some bug in DCS that is giving me the issue. Since the only change from yesterday to today was the DCS update. Thoughts?

Even with the new damage model it takes some magic to bring down FW190A8s haha. I was playing the Big Show campaign and you have a furball with 40 of them...it took 22 impacts (mostly 20mm shells) before it finally went down. That also was about all the ammo I had haha. I do think the convergence area is key, but I have been working hard to figure it out. Ce la ví.

This bug is still happening. I ran the DCS repair and it just happened to me on mission 5. This new DM must be causing errors or something. I shot down 3 AI 109s and they went to flames, flipped upside down and flew away haha. Oh DCS.

I did the DCS repair and got this trying to open BNBB Mission 04. I did the DCS repair and got this trying to open BNBB Mission 04. I added the debrief log when trying to open Mission 14. Mission 14 Debrief Log.log