BBQ

I converted the Vergeev Group campaign to work with BS2 back in the day - and it took weeks of work. I'm considering doing it again for BS3 - but I haven't bee involved in DCS for some years now. If I decide to do it, I'll post a thread on progress.

Many years ago I created a tutorial about using and understanding the HSI, ILS and TACAN to perform instrument landings in the A-10. The video has nearly 25K views on YouTube, but many complained about the volume of my voice being too low (indeed, it was). I've fixed the issue and wanted to post a link to the new version. Although I was in the warthog at the time, I think anyone would benefit if they are looking for help with the ILS and TACAN systems.

I've fixed the voiceover problem (many couldn't hear me) in a new video here: https://youtu.be/UjlOSEiNLSg

I'm having the same problem -- except the right throttle is behind the left, and it's a bit more than one percent. I HAVE to fly with them linked, as unlinked, it's more like 10% different, as it's hard to keep them physically together (they are both "wobbly" and sort of jiggle right and left). Even linked, it's enough to cause the aircraft to constantly want to roll, which is driving me crazy. I can tell you 100% the FCS does NOT compensate and make things right -- at least not so you can fly level with hands off the stick. Unlink your throttles, and pull one of the throttles behind the other one gradually and you'll see what I mean. If anyone gets different results (and doesn't roll one way or the other) please let me know. Also, if anyone has a solution via curves or deadzones, or saturation, please let me know. I had to put -18 curve on both throttles to get full MIL power right before AB detent, but with or without curves they are not matched according to input window in game. EDIT: Decided to just use left/right trim to compensate -- not ideal, but seems to work. Also noticed it seems more pronounced at lower speeds (e.g. with gear down and full flaps) EDIT2: Decided to remove Warthog AB Detent, and use the Special Option for the detent via the software -- I have a lot more range on my throttle now, which has dampened the effect of my throttles not matching to a negligible level.

Thanks for the replies - will leave flight control surfaces alone while touching and going -- Sent from my XT1650 using Tapatalk

I've been trying to get comfortable with the basic VFR pattern/landing at an airfield -- and generally doing touch-and-go's until I get low on fuel. One of the things I've noticed: when I touch down I reconfigure to half flaps and T/O Trim, but when i rotate a few seconds later, it feels MUCH different than when I initially took-off and rotated-- I have to actually push the stick down to get enough speed to lower my flaps after raising the gear. This didn't make sense to me -- why should it behave any differently than when I took off 2 minutes before, with the same half flaps and T/O trim? I then read something somewhere about when the hornet bolters, or perhaps it's just any carrier launch -- that the FCS automatically pitches up -- that the pilot is basically hands-off during the launch? I'm wondering if this is what is happening when I do touch-and-go's at an airfield -- or perhaps I'm not supposed to reset flaps to half and reset to T/O Trim after "touching" and before "going"? Any tips would be much appreciated -- BBQ

I noticed this as well - when on the ground, don't release parking brake until it says ok (3 minutes). If you do, it will start flashing, even if you haven't moved. Sent from my XT1650 using Tapatalk

Any ideas on how to reset the trim? I've been doing touch and go's and am finding it difficult to reset trim.

I noticed this problem as well -- rewatched Wags startup/taxi/take-off tutorial, and if you notice, he "cycles" the controls throughout the stick's range while he is running up the engines right before take-off. When I do this, the pitch problem isn't present -- when I don't, the problem is there. Can anyone else confirm?

Just back from a hop in the Ka-50 in the Georgian Oil War campaign -- gotta remember my roots. You've come a long way DCS. Congratulations!

Thanks guys -- makes sense.

With the latest update, I lost the brake paddle on my warthog stick -- I'm doing the new Kursant campaign for the L39, and when I try to map stick paddle to wheel brakes, it won't recognize the axis. I've tried unplugging USB and plugging back in, rebooting, and repairing DCS. Anyone else experiencing this? BBQ

I think it was the FE telling me I was done and can contact tower and land. Not 100% on that though.

I"m also not receiving any audio after shutting down -- the training bombs mission.

What worked for me was basically flying 200 ft below what instructor indicated.

With the latest update, I stop getting triggers to do more manuevers, though I'm level at 7000 ft, 220 knots, heading 040 (I never get the level turn trigger).

Should I follow the waypoints dead-on, or listen to the bearings from the IP? E.g. in this one, heading out, he has me going 040, but it's more like 035 to the waypoint.

Some bad news In one of the latest updates -- you cannot set the tree visibility to zero. The lowest it can go is 30%. Without labels on (and even with labels on in some cases) it is very difficult locate enemy soldiers in a forested area, which in many missions, is essential for moving on in the campaign. Pre-2.5 these areas were not forested, and pulling the trees visibility to 30% doesn't help -- it's more of a distance rendering setting. In some missions it was a simple matter of moving the soldiers into a non-forested area, provided the area was very close by the original. However, in many missions, the advanced triggers, precisely placed/sized zones, etc. -- has made it very difficult, to the point where briefings/briefing maps, etc., are going to be wrong if I start moving everything around. At other times, friendly helos are trying to drop off/pick up soldiers, and are now crashing into the trees. To make a long story short, this is going to take a lot more time than I anticipated. I don't want to do the Vergeev Group an injustice by hacking these missions together just so they "work". It will be an ongoing process. I want the quality and craftsmanship to remain, which is part of what drew me to the campaign to being with -- Also, since this is a major release, epic even, I really need to be patient to let the developers work out the kinks. E.g., they may bring back the option to go to 0% trees, which solves 99% of the problems. On the other hand, I could spend a week fixing everything, just to have them do some kind of rollback that breaks it again. This is always a risk in software development -- but it's wise to let things settle down for a bit before putting too much sweat and tears into a project. In the meantime, we're stuck with 1.5.7. BBQ

Okay, I've tested/fixed all of the missions to work with the current 2.5.0 version -- but I'm hesitant to post it for the following reasons: There are still some lighting issues, and some kind of video corruption with the water w/ deferred shading enabled. Because 3 or 4 of the missions take place over water, this is kind of a deal breaker for those using deferred shading -- and I don't want to waste time testing the missions all over again with the shading on, until at least the next hotfix/update. The good news is, the actual missions themselves are working (after I had to make a few tweaks, e.g., spawning inside of a jet at Sochi). So the Vergeev Group campaign will live on -- I'm just going to wait until the major bugs are squashed so that I can test it again for 2.5.0x so I don't have to repeat the effort (it takes a lot of time).

Yes, I've fixed that already.

Yes, I'll create two links -- one for the existing version that works with 1.5.7, and another that works with the new 2.5.0.

Almost done testing -- on mission 19. There were definitely some snags along the way, but I think I've got them sorted. Will post updated campaign link as soon as I'm done.

I haven't tested it yet -- but will do my best to find any problems and upload an updated version ASAP.

I did a repair, and it fixed it. Sent from my XT1650 using Tapatalk

I think he actually says "step by step", but now you've got me second guessing myself, so I'm not 100% sure [emoji19] Sent from my XT1650 using Tapatalk