brettt777

Yes, I know this. I calibrated the throttles from idle up to the AB detent. I calibrated the AB from idle up through the detent. I don't understand why the throttles in the planes stop at the detent. But this only seems to happen on jets with AB. I tried the P-51 and the throttle stops at the detent of course, but if I push through the detent into AB, the Mustang then goes to full throttle (61 inches). Same thing in the L-39. At the detent, rpm is a few ticks below 106.8%. I push through it and it goes to max. So DCS is seeing that the throttle goes to the detent and then past it. But something is keeping the planes with AB from going into AB. Okay.... Update.... Just out of curiosity, I assigned a button to that "Cycle AB Detent". Then I went into the FA-18 and when I pushed that button, suddenly I had AB when I pushed through the detent. I also did the same thing in the F-16. So.... Is this something new to go along with the Winwing or Virpil or Thrust master throttles? I used to use a Logitech X56 HOTAS and I don't recall ever needing to push a button to enable my AB.

I am recently retired but I spent most of the last four decades, both military and civilian as an aviation maintenance tech that specialized in avionics. So it is rather frustrating and a bit embarrassing that I spent most of my weekend trying to make this thing work and couldn't. At least, not all of it. Anyway... I would greatly appreciate some assistance. Here's where I'm at. Thanks to MustangSally, I got the vibration to work and then I was able to get my throttle and AB detent calibrated correctly in SimAppPro, at least I think it's correct. The throttles move from zero to about 75% between the idle and AB detents, and then go to 100% through the AB detent. This is what SimAppPro shows me. I am assuming this is correct...? So when I get into DCS, in the Viper or the Hornet, I move the throttle from idle to max and the aircraft shows the throttle going up to about 102, 103% which I assume is normal max for them. A factory L-39 goes up to 106.8%. Anyway, that part seems to work. But when I push the throttle past the AB detent, or when I pull up the finger lift and move it past the detent, nothing happens. The throttles in the aircraft don't move any further. Obviously herein lies my issue. When I look at the thrust axis setting in the controls adjust page, it shws the thrust setting going to about 75% up to the AB detent, and then going up to 100% when pushed past the detent. But the aircraft doesn't do this. So I went into the throttle quadrant settings and set up the idle detent. No problem there. I also see this "Cycle Afterburner Detent ON/OFF". If I try to set that up, nothing happens. I move the throttles and pull the finger lift up, but it shows nothing. No key or button shows up. I have a feeling this is the key to my issue but what am I suppose to do with it? When I look at the throttles in SimAppPro, the switches change state when I go from idle to cut off and back. Is there suppose to be some kind of change when I go past the AB detent? All it does is go from about 75% to 100% on both throttles. What else should I see? What is suppose to happen to set up this AB detent in DCS? Probably doesn't matter but the AB function in P3D works fine with the Winwing system. I'm also curious as to why this forum thinks I am spelling the word "detent" incorrectly...?

Okay, I finally got my vibration working on my F-16EX stick, now I need to figure out the afterburner setup. In DCS, if I move the FA-18 throttle up to the AB stop, it goes to 100%. But if I push it past the stop into AB, nothing happens. No afterburner at all. I have calibrated the throttles in SimAppPro, but not absolutely sure if I did it correctly. During the calibration it says to move the throttle from idle to max. Does that mean as far as it will go including past the AB gate, or just up to the AB gate? And the AB calibration says move both axis to the AB at the same time. So that means actually past the gate into AB, correct? If I do all this correctly, am I suppose to see any kind of indication when I go past the AB gate? The way I have it now, when I put the throttles to max, i.e. right up to the AB gate, the throttle test indications show them going to max, 100%. When I go past the gate into AB, I get no indication that anything changed. What am I missing here? When I try to set the AB position in the FA-18 throttle settings, nothing happens. It shows no indication at all when I go to AB. What am I doing wrong? I am sure this is just a setting somewhere. The SimAppPro manual is rather vague about many of these procedures...

Okay, got my vibration to work so many thanks for that. Now I just need to figure out how to set my afterburner setting. I have the finger lift kit. So how do I tell the things where to engage the AB?

So I finally broke my piggy bank and sprang for a Winwing system. I got the Orion 2 throttle base and joystick base, and the FA-18 throttle handles and the F-16EX grip. II also got the finger lift kit for the throttle (which I am a bit dubious on the benefit of at this point) and the shake kit for the F-16 stick. While I am very happy with this system for the most part, I do have one or two issues. The main reason I wanted the shake kit was the extra hats and trigger, primarily the x/y axis which I use for strafing in my space sims. I also thought that even though it isn't true FFB, I liked the idea of at least having a vibration feature that will shake the stick when I fire the gun or pull excessive G's. All that being said, I have yet to get said vibration to work. I have the Dynamic Vibration Motor set to advanced, and I have various profiles on and activated for different DCS aircraft. But I get no vibration at all in say, the P-51D for gun fire, excessive G's, take off and landing. Nothing. I tried it with the FFB in DCS turned on and off but nothing changed. I have read that there is a certain .lua file in the Scripts directory of the Saved Games/DCS Open.Beta folder that is suppose to have some sort of Winwing entries. I have looked in this file and there's no Winwing anything. I also went into SimApp Pro and had it "repair the lua file" cuz I had also heard that might be needed. Well, it didn't help. So, what am I missing? What do I need to do to get my vibration working? I have a couple other issues with the Winwing system, most of which are just personal preference. - I know the throttle base is designed primarily for certain DCS aircraft, but I do wish the labeling was a bit more generic. While I do fly the DCS F-16 and FA-18 quite frequently, I also fly other aircraft in other sims and also space sims. - I find the layout of the buttons and knobs on the throttle base kind of haphazard and not all that ergonomic. I find it awkward to have to reach around my throttle handles, which are maxed out, to get to my landing gear switch. It's like, there are four rotary encoders, we need a fifth so we'll stick it here between these other buttons. Again, just personal preference. - I find the hat switches on the throttle much more stiff than those on the stick grip. I would prefer the lighter feel of the hats on the stick. Again, personal preference. All in all, I am very happy with the system. I just wish I could get the vibration to work. Anyone got any any ideas?

That's freaking genius dude! My wife also has a cricut. I am literally about to order a Winwing HOTAS system but was wondering how I could make it less aircraft specific. Now I know. Thanks! One question though.... Is the overlay just a cricut label, or is it a label on another panel?

So... I went out and got an adapter for my G940 pedals. Not a Leo Bodnar device, but the same thing. I tested it on my G27 pedals and it does work. So according to your schematic of the G940 pedals, the only difference between them and the G27 pedals is the polarity of the power and ground. Those pots don't care about polarity so according to what you posted, my adapter should work with the G940 pedals. Well, it did not. Oddly enough, it showed on my PC as "USB Pedals", but I got no movement on any axis. So I opened up my pedals and got out my trusty Fluke meter and drew up a schematic of my own. Needless to say, I found an error or two on your schematic. Here's the pinout for the G27 pedals: 1 3.3vdc in 2 Axis 1 3 Axis 2 4 Axis 3 5 6 Ground/common 7 8 9 Now here's the pinout of my G940: 1 3.3vdc in 2 Axis 1 3 Axis 2 4 Axis 3 5 Ground/common 6 7 8 Ground/commnon 9 As you can see, there is a major discrepancy. THIS is why the Leo Bodnar adapter, or any other adapter, will not work with the G940 pedals. My preferred solution would be to change the wiring of the DB9 on the USB adapter. Unfortunately that isn't possible due to the type of connector they used. So I will indeed have to put together a couple DB9's and a few wires to make this thing work. But I just wanted to point out that your schematic of the G940 pedals does not match what is actually inside the thing. At least not mine. Cheers!

So that does it for all mods?

I went from 2.6 to 2.8 the other night. Haven't played in a while. Since the update, I've seen a number of issues. Besides the fact that some of the flight models seemed to have changed (and not for the better), I noticed some graphical issues that I never had before. Whenever I am in an external view, I have severe ghosting of my aircraft, if that's the right way to describe it. It's like I have numerous layers of my aircraft laid over one another and they're not quite aligned properly. This only happens in an eternal view. Inside the cockpit I haven't seen this. But it is extremely annoying to the point where any external view, even of weapons, is practically unusable. I also noticed that Active Pause seems to have been removed from almost every aircraft. Out of my almost two dozen mods, only the F-14 and the MiG-21 still have it. What is up with that? Whose bright idea was that? PUT IT BACK!!! Active pause is, to me anyway, crucial when you're trying to learn a new, complex aircraft like the AH-64. Why would you take something like that out? Is it maybe just called something else now?

I did the latest 2.8 update the other night and I go into several of my aircraft last night only to find changes made to the controls and some weird flight model behavior. But the one thing that disturbed me the most is that Active Pause seems to have been almost entirely removed from the sim. Out of the almost two dozen modules that I have installed, only the F-14 and the MiG-21 still have Active Pause. It's gone in all the others, unless they're calling it something else now. I understand that it isn't the most realistic function but when you have many different aircraft and you're trying to learn a new one that is fairly complex like the AH-64, it's vital. So, where is it? Is it called something else now? If it has been removed, I'd like to know whose bright idea that was! PUT IT BACK!!!

I've had issues with the Hornet radar myself. I tried it last night after installing the latest update the day before. I had a TU-95 Bear 5-10 miles straight out in front of me and couldn't see it most of the time. Tried different antenna angles, different PRF, different direction of approach, didn't matter. In fact, since installing that update, I could hardly get anything to work. I had a Corvette in the water about 20-30 miles from my Hornet and had 4 Harpoons loaded up. I got a radar lock, got the FLIR locked on and had all four RDY. But every time I launched them, they ran off on some random direction and didn't even try to track. I couldn't get an AIM-120 to lock on to that Bear. In fact I seemed to have issues with everything I flew last night. The AIM-120's on an F-16 also wouldn't lock onto to those same TU-95's. And I even tried to shoot those same Bear's with an F-14 and a couple AIM-54's. Same thing; Jester has them all locked up and tracking, I fire a Phoenix, and it goes off on some random direction. Now, I don't profess to be the greatest DCS fighter pilot on Earth, but I have a fair idea what I'm doing and I just couldn't get anything to work last night.

Okay, yeah I thought about that this morning so thanks for confirming my thinking.

I just installed a few new mods to DCS. The Grinnelli F-22 and a VSN F-22 and F-35. For some reason DCS won't allow them to run saying something like... "The following mods are not authorized". Something to that affect. What's that all about? I have DCS updated to the latest version and I have FC3. What am I missing?

Not intentionally. Only during moments of complete loss of control have I seen it look like it could do a roll.

Yeah, I got it working the other night. It only has to be online the first time. After that it just tells you there's no internet connection but still allows me to start DCS.

Okay, first... Has there been an update somewhere that I missed that makes the FCR operational? Second, I was watching a video on Youtube the other day of an AH-64 Apache flight demo(RL, not DCS). In this demo, the guy did loops and rolls. In a Helicopter. Needless to say I was suitably impressed. So.... is any of that possible in the DCS AH-64? I mean, besides when I do it accidentally when I have it completely out of control...

So does the PC app have to be open every time I want to use my Quest 2 in DCS?

I have an Oculus/Meta Quest 2 that I've used in DCS before when it was still Oculus. I don't have a Meta account and would prefer not to get one. Is it possible to connect a Quest 2 to non-Steam DCS without a Meta account?

I have an idea on how to fix this issue. It seems to be a common problem with this system. And I, like you and many others, love this system... except for this one issue. Anyway, if you're interested, I'll let you know if this works and how I did it.

I just ordered and received a Logitech X-56 HOTAS throttle and stick. I used it a couple days ago for the first time for about an hour. All was well. I am using a powered USB hub as recommended. Tonight I plugged it in the exact same way. It started cycling on and off, as in the LED lighting was going on and off. It did this for a minute or so then stopped. Then the stick was dead. No lights, no nothing. My PC doesn't see it at all when it's plugged in. The throttle worked fine. I tried it in different USB ports. Nothing, just... dead. I just freaking got this thing. It's brand new, used it once for an hour. Use the recommended powered USB hub, and this is what I get? WTF??? What can I do about this?

I don't understand why everyone thinks the converter assembly would be necessary. In either the G27/29 pedals or the G940 rudder pedals, the only difference is the polarity of the 5vdc going into the device. Other than that, the wiring is identical. Nothing in the device is polarized. Those pots don't care which way the voltage comes in. The only thing you may have to do is invert the axis in the game. You said that yourself.

What am I missing here? Why does everyone think the wiring needs to be changed? The ONLY difference in those schematics is that the power and ground pins are swapped. But the power is only going across three pots. I've been inside my G940 pedals. Those pots are not polarized. The output from the wipers on the pots all go to the same pins. Those outputs are still gonna have a 0-5vdc analog signal on them. Going by these schematics, the ONLY thing that may have to be changed is that a couple axis inputs in DCS may have to be inverted so they go the right way. Other than that, the Leo Bonar device should work fine.

Why would that difference in the wiring even matter? The pots aren't polarized so the polarity doesn't matter. The only thing would be you might have to invert an input in the axis settings, but other than that, either one should work fine. Am I reading this right, that the Leo Bodnar cable would put the 5vdc into the pedals on pin 6 instead of pin 1? Why would that make any difference to the analog pots in the G940 pedals?

- Is the Apache suppose to be so erratic on take off or am I just not doing it right? I have one heck of a time getting airborne. The thing just wants to go everywhere until I can finally get it moving in a somewhat forward direction. Once I get a bit of airspeed built up, I can fly it just fine. It's just take offs I have an issue with. I honestly haven't tried landings yet but I hope they're a bit easier than in the Huey. - It seems like I can't get much more airspeed than about 110-120, maybe 125 kias unless I'm going downhill. I thought the Apache was faster than that. Am I missing something here? Should I be getting more airspeed than that or is that about normal? I am flying with a full weapons load so maybe that's it...? - As I am moving along at cruising speed, I have a constant slow wobble that appears to be in the roll axis. no matter how still I hold the stick, it always does this. I have never noticed this in any other helicopter. Is this normal in the AH-64? - Does the Apache have some kind of hover mode? - I might be getting a bit ahead of myself, but is the FLIR lens in the nose ever suppose to follow the pilot or gunner's view like the cannon does, or does that only move manually? Thanks in advance.

I was trying to get my stabilizer to move to give it more nose down cuz I have to hold constant pressure on the stick to keep the nose down. Bit can get it to move at all. I mapped nose up and nose down and stabilizer depress. I tried pressing and holding the button to move it up or down and I tried pressing the button then trying to move it up or down. Nothing happens. And yes, I have those controls set up in. Both seats. What am I missing? Is that a function that's not implemented yet?