apd1004

I've been having the same problem lately. It was working fine until the other day when I started messing around with installing Helios for instrument panel projection and multiple monitors. Not sure if Helios has anything to do with it, or if I inadvertently messed up a lua file somewhere? By the way, I'm using a different throttle - the TM Hotas Warthog.

Not sure if this is the right thread for this question but I don't like asking questions in threads that have been dead for a couple years or more. I am using the latest Helios version with Loz v2.1 A-10 cockpit. I have Helios displaying on an Acer 22" touchscreen. It works great with the mouse but if I use touchscreen it appears the actual "touch" opens a side panel and/or hits a button, then the "release" of the touch acts as a second "touch", which immediately closes the opened side panel or mashes the button again. This appears to only be happening with Helios. I have calibrated the touchscreen but that doesn't do anything. Not finding any appropriate Windows 10 options for controlling this either. I've tried adjusting mouse double click but I don't think that has anything to do with touchscreen touches. Tried searching the forum but with several thousand posts spread out over 8 years or so, it is difficult to find anything quickly. Any ideas? Thanks EDIT: I figured out what the issue was with the touch screen. Buried deep within the Accessibility options of Windows 10 for touch displays is an option to enable an emulated right click by holding down a touch on the touch screen. I disabled that option and now Helios works as intended with my touch screen.

That did the trick, making the center MFCD the secondary instead of quaternary. The little 7" monitors are 720 high so I just made the display 720x720 and offset the left one in from the left edge to put it on the right side of the monitor. Same thing with the map display, just made it 1080 x 1080 to square it up. Thanks for pointing me in the right direction!

I suppose I should give an up-front disclaimer to say that this is my first attempt at lua scripting in about 7 years since A-10C first came out. About a week ago I decided to get back into flight simming. Anyway, this is what I end up with when I use the script from your edited #5 above. What I need to do is get the right displays on the right monitors and get them 1:1 instead of 16:9. I'll play around with it a little to see what I can do with it. The mini-monitors are 7" 1280x720 16:9 monitors, but they are a bit too small for the Thrustmaster Cougar MFDs. I'll see how they work but I'll probably end up going with something bigger. I also may hook up an older 15" square flat panel I have for the map and make that a 5th monitor off to the left, leaving the right hand 25" for things like flight manuals, nav charts, etc. Thanks for giving me a place to start!

I like the 4 monitor configuration, that is exactly what I have. When I tried the lua for the 4 monitor config though, for some reason the AMPCD map did not display on the second larger monitor, it was just a black screen. The yellow cursor cross would move around on it but no map was visible. The map was up and running on the main cockpit display though. How do you have your monitor placement configured in Windows, or is that not an issue with auto placement?

Pretty sure the 9M119 is a laser beam rider, which as long as the tank gunner can track the target and keep the reticle on it throughout the flight of the missile, the missile will theoretically hit. Not sure if the 9M119 uses fin correction or rocket correction though; some ATGM's have a limited ability to make huge steering corrections (i.e, follow the gunner tracking a moving aircraft). Whether these factors are modeled in DCS is another story. That being said, as a tank commander I would probably try to find some cover from the aircraft rather than try to shoot the thing down. The reason we have things like ZSU 23-4 and SA-9/11/13 etc. is because tanks aren't really very good at shooting down aircraft...

I saw it. Just saying that there may be more ways to validate it really being broke than what the support staff offered over the phone. I think I have more confidence in the product itself than I do in their support staff. Anyway, I hope you get your issue resolved soon. It really is a great product.

Have you tried it with other flight sims (non ED)? Have you tried it on a different computer? It's a well made product which works well pretty much plug and play, and I'm having a hard time believing it's a hardware problem or even a firmware problem. Uninstalling and re-installing drivers, TARGET, etc? You'll really be disappointed if you get a replacement and it does the same thing.

You're showing your age if you had a C64. Many people here have no idea what it was like to have a C64 as your main PC. I used to buy just about every sim that came out back in those days. The keyboard templates were great. F-19 Stealth Fighter... M1 Tank Platoon... Jane's Longbow 2...

Hi all, If you're like me, you can't just run out and drop $500 on the Thrustmaster HOTAS system, and instead have to make due with some other joystick and the keyboard. Someday perhaps I will be able to invest in the Thrustmaster, but not yet. In the meantime I have to make due with what I have. I have no interest in getting a different joystick rig and I will use what I have until I can afford the Thrustmaster. I use a Cyborg X joystick and the keyboard, but I still simulate having a HOTAS as much as possible. What I have attempted to do in my memorization technique is to try to get used to the actual HOTAS button functions rather than try to memorize keyboard commands themselves. For example, I know that Coolie Hat up sets HUD as SOI. I have memorized that the Coolie Hat up = HUD as SOI, and that the "U" key = Coolie Hat up. This is different than just memorizing "U" key = HUD as SOI. It may sound like an unnecessary step that just complicates things, but once you get used to thinking about it this way, it starts to flow pretty good. The main reason I do this is so when I can eventually afford the Thrustmaster HOTAS, it should be a fairly easy transition from keyboard to HOTAS because I already know what the HOTAS buttons do even though I don't have one. All I will really have to do is learn what each button/hat/switch is on the HOTAS. Not sure if it will really be that easy, but right now in my mind I am planning on it being easy. What I have done to help me with my learning the HOTAS commands is to make my own keyboard layout diagram that only has the HOTAS commands on it and nothing else. The default HOTAS keyboard commands are actually laid out in a fairly logical manner in my opinion, and when you look at the diagram that has only the HOTAS commands on it, this becomes more obvious than a diagram that might have everything on it. Along with my keyboard diagram, I also use a modified version of an Excel spreadsheet I downloaded from this forum that lists the HOTAS controls in matrix format. My modification was to add columns for the keyboard commands and mods. I also have a couple of 5" x 8" binders that I set side by side similar to a kneeboard and I use them to refer to. Both the matrix and the keyboard diagram can be printed in portrait and fit on one 8.5" x 11" sheet each. For my 5" x 8" binders, I just cut the 8.5" x 11" sheet in half and put the halves in 5" x 8" sheet protectors. I also have complete keyboard command lists, checklists, airport diagrams, etc. in my binders. I have included both the layout diagram and the HOTAS command matrix in this post in PDF format. Hopefully somebody can find them as useful as I have. Here is a link to a forum post where you can find the original keyboard matrix that I modified, and a couple other files that may be useful. http://forums.eagle.ru/showthread.php?t=58470&highlight=keyboard&page=11 Also attached is my raw Excel sheet that I modified. Cheers HOTAS Keyboard Layout.pdf HOTAS Keyboard matrix.pdf HOTAS Keyboard matrix.zip

I get the same thing after requesting refuel and I never used ground power. I figured there was something else I was supposed to tell them to do after refuel but I never went back and looked at the communications options. I also got denied access to take off after I heard "What are you doing".

I agree, Matt's overall profile is a copy of the default with the exception that he has 180 degree limiters on the axes. Question - what do you mean by "shift pitch curve up one notch"? I assume you mean take each of the control points in the pitch axis and click the Y point up arrow once, which adds 1.0 to the Y point value, which raises the entire curve up the graph. Thanks Cheers

Not sure if this is what you are looking for or not. If you mouse over "Traffic Schedule" you will see links to real world timetables. http://www.railway.ge/?web=1&lang=eng Is there a way to put moving trains in missions? I'm only seeing the ability to add them as static objects, but then again I'm brand new to this. Cheers

Great checklists! Best single page checklists I've seen to date. I'm trying to print them to put them in a 8 x 5 kneeboard binder with all my other checklists and data, but the light gray text doesn't print very well even on the best settings on my photo printer. If you could please use a more contrasting color for the white background, it would be much appreciated. I'd be interested in any other checklist items you have made as well. Cheers

New player here as well. Black Shark is my first flight sim since the Falcon 4 and Longbow 2 days. Back in those days an interactive cockpit was more a dream than a reality. I must say I'm amazed with Black Shark and I'm totally immersed in learning to fly it and I have yet to fire a shot. This forum has provided a wealth of information so far and I'd like to thank all those who have contributed.