falcon00

Phobon had the answer. You might have missed it. "I had the same behaviour when I installed 1.5 and noticed that I had another controller bound to the Thrust-Axis. After removing this duplicate binding, everything worked perfectly. Might help to check your axis bindings..." I can't believe that was three years ago....

I installed DCS World 1.5 in a separate folder. When I opened the sim, I discovered that my video output was no longer going to my Lilliput MFD monitors. In the process of trying to deal with that, i accidentally changed the monitors setting to Hud I think and now the screen is too narrow to change it back. How can I manually reset that setting so it's back to normal?

Thanks Thanks! Checking it out now.

If I wanted to write a wrapper for DCS A-10 for a CANBUS device, where would I get started? I keep googling for information but there doesn't seem to be any. It seems like there should be an API or something somewhere but I haven't found anything like that.

Yeah the AI needs real help. Plugging is the boomers job. Pilot just needs to stay in formation.

For some reason I recently had to reassign the axis on the slew control. After I did that, the slew control sensitivity went through the roof. It's most notable when targeting mavericks. The slightest touch and the seeker head goes flying across the screen. I have slew dialed down to 1 but that doesn't help. Anybody know how I can dial it down so the slew rate goes back to normal?

I look at it from the standpoint of how long would it take me to build this stuff vs. buying it. Answer: It's WAY less cheaper to just buy it even at these price points. I mean, who is their competitor? Is there anybody else offering this stuff for cheaper?

UFCs and other sim parts as well. Excuse me if everybody knew about this but I just found them randomly. http://www.simparts.de/en/homecockpit/a-10c-warthog-en.html I purchased their UFC and it works awesome. I'll be buying more stuff from them.

BINGO! Nailed it! I had a TON of stuff mapped that shouldn't be there. You brought sexy back! Thanks! :D

Well as long as someone has reported the bug I guess there is nothing to do but sit back and wait.

No there was a distinct event where stuff stopped working. I'm not sure what version it was when it changed but it was after the last upgrade. The first thing I noticed is that in air starts, the throttle had to be moved before it synced. That was annoying but not that big a deal. The engines not starting when I move the throttle was a bigger deal to me so I started researching. I found the "sync HOTAS on start" option and that fixed the throttle problem with in air starts. It didn't fix the engine start issue though. Having to move the throttle twice totally messes up the realism. Little things like that are annoying when you spend thousands to get to as close to real as possible.

Ah ha! So it IS a bug. I knew it didn't used to do this. I'm having the same issue. Having to move the throttles twice really messes with the realism.

This is new behavior. When I'm in the start up training mission, I have to move my throttles past the detent twice before the sim will detect that I actually moved the throttle to start position. I tried setting sync hotas with sim on start but that didn't fix the issue. Anybody else experiencing this or have a fix. I didn't work like that previously and I'm not sure what changed.

"I read somewhere a boom operator said the DCSW tanker crews are not as cooperative as they would be in real life." HA! I'd agree with that. So many times I've sat there with the boom literally inches away shouting PLUG AHOLE!! I don't have a problem with chasing the boom. My issue is I get stabilized and walk it in one of two things happens. PIO as I try to correct for being thrown up or down which is a viscous cycle OR I get thrown to one side. As a guy that regularly flies in the wake of other aircraft, I can tell you that this isn't what happens. It's bumpy but you don't just get thrown around to the point where you suddenly start gaining altitude with no stick input.

Refueling in DCS A-10 appears to be a hot topic. I see other threads giving advice, but I don't think it's modeled accurately. This isn't the first time I've seen this; refueling in Falcon 4.0 was like this too. I get that there is a wake coming off the tanker but I don't think that receivers in the real world get thrown around by it that much. As an observer, I've flown several missions with the 190th ARW. Receivers, especially fighters, roll up, park, plug, and bounce. They are stable enough on the boom that they can take their hands off the throttle and wave to the guys in the pod. See video [ame=https://www.youtube.com/watch?v=7tRzDse5h7Y]here[/ame]. At night and in bad weather I can see it being hard but on a good day, it's just normal formation flight.

It wasn't the form of the .lua. It was small stuff. Four key issues: 1. When I opened my screen shot in Photoshop, I didn't realize that there was extra stuff that needed to be cropped. That was giving me bad reads on the position of my monitors. 2. Turn off full screen in options. 3. Make sure the main monitor is set such that it's the upper left most screen. I had my MFDS all over the place before I finally just put them off to the right and centered compared to the main screen. 4. This was the big one: In Options, you have to put the COMBINED resolution of both your main monitor and your USB monitors.

It turns out that there was a large amount of detail missing in those post. Use this thread as the definitive guide. http://forums.eagle.ru/showthread.php?t=60815

I'm following the directions from the links below: http://forums.eagle.ru/showthread.php?t=93389 http://forums.eagle.ru/showthread.php?t=66572 Despite that, I can't seem to get the software to send signal to the USB monitors. In game, the just show the desktop background. What are somethings I can check to make sure everything is working right? Below is the code for my .lua _ = function(p) return p; end; name = _('Lilliput Config'); Description = 'Three Monitor Config' Viewports = { Center = { x = 0; y = 0; width = 1366; height = 768; viewDx = 0; viewDy = 0; aspect = 1.6; } } GUI = { x = 0; y = 0; width = 1366; height = 768; } LEFT_MFCD = { x = 262; y = 830; width = 540; height = 540; } RIGHT_MFCD = { x = 894; y = 1080; width = 540; height = 540; } UIMainView = GUI;

I mapped with the right ctrl key instead and it worked fine. Not a real fix but it will have to do.

I have OSB01 on the right MFCD mapped to LShift+LAlt+1. That works fine. I have OSB01 on the LEFT MFCD mapped to LCtrl+LAlt+1 and for some reason the sim won't recognize the mapping. Is there something weird about the LCtrl key I should know about?

I checked. Those lines of script code are included in the file I'm looking at.

Target GUI

I know they don't show up in the controls section for the MFCDs. When they are enabled there will be a column with their mappings. When i exclude and go back in those columns are gone.

That's what I did and it didn't work. I don't know what the problem is.

The controls screen has them but they aren't mapped to the keyboard just to the joystick. It looks like I have to do that by myself which means it's going to be a pain in the butt two step process. If you're using the Cougar HOTAS then the TARGET software will override whatever plug and play settings there are and the MFDs won't work at all. That aside they only kind of work anyway. All the inner buttons work ok but the rocker buttons at the four corners are reversed.