glcm1961

Same here - all three MFDs are messed up.

Thank you Bunny Clark! Exactly the information I was hoping to get. Much appreciated!

Ok, so I have the three mfds exported to separate displays by editing the lua files. However, I have a spare fourth display that is collecting dust and would like to use it to display the RWR or IFIE. Since my three displays in use are labeled “left”, “right”, and “center”, how would the fourth display be labeled and how would I edit the cockpit file to enable the RWR or EFIE to be exported to the display? Any and all suggestions will be greatly appreciated!

Thanks! I'll give it a shot.

Thanks Falconeer - works like a charm! Never would have been able to figure that out on my own. Now this might be asking a bit much, but I was thinking with the screen space still available above the HSI, it would be a great place to display the DED information. Have you ever heard of such a thing and would it be possible? I noticed a DED folder in the f16 cockpit folder so thats what got me thinking it might be possible. Thoughts?

I'm trying to display the HSI on my center MFD (I have a cockpit set up for F-18 but am learning the viper and so have the center MFD available). I read where it is possible to have the center MFD display the HSI and that it is fairly easy to do but in the threads I've come across so far I haven't been able to figure out how to edit the necessary Lua files. If anyone can give me the file to edit, where it is located, and the line I need to insert I'd sure appreciate it! (I'm a bit of a novice when it comes to all this computer programming stuff, so I won't be insulted if you make things very simple

Well, I discovered the reason it wasn't being "seen". I discovered I needed a DCDBios download from Cubesim. Why he didn't send this to me straight away I'll never know. It's been a <profanity>show ever since. When I connect the controller box to my computer, my computer detects the left CTRL key being held down, which renders any inputs useless. For example, if I try using my scroll wheel on my mouse, the screen changes magnification, as if I was holding the CTRL key down. The computer treats any keypress as if I'm holding the CTRL key. Needless to say, it's completely unusable. LIkewise, if I depress and OSB key on any of the MFD bezels, only the left MFD is affected as computer thinks the CTRL key is depressed. Don't know if it can be fixed, but I'm ready to send it back. Very disappointed.

I just set up my new UFC and MFDs that I received from Cubesim. Very impressed with the quality of the MFD screens and overall build. However, after hooking everything up, DCS doesn't "see" these components. I thought these were supposed to be "plug and play" but I go to the control option in the f18 menu and they don't even appear. Everything else is there (joystick, throttle, etc). I messaged Cubesim and haven't received a reply yet but was hoping someone on this forum could give me a little guidance on how to get this up and running.

Thank you Cepheus - appreciate the feedback. I'm going to do some more experimenting. I'm just learning this aircraft and so far it's been a fun experience filled with trial and error.

Can anyone provide me with a link to a tutorial on how to use JDAMS in conjunction with the air to ground radar? I'm trying to do the "Above the Clouds" instant action mission and am having trouble getting it sorted out. Thanks!

I just learned how to do waypoint offsets which is pretty cool, but I'm stuck on how to enter a decimal number into the UFC. If I want to enter nautical miles under the RNG function - let's say it's 3.22 NM, how do I place the decimal point into the UFC so it understands that I want to enter 3.22 and not 322?

Thanks for the feedback! I'm in over my head with this but I'm determined to get it to work. I got the com port problem figured out - had to install a driver and that did the trick and it now shows a green box with a connected state. Having got that problem solved, I now have another one: The virtual cockpit status light on the dashboard console is greyed out and not green like it's supposed to be. I tried everything but no dice. I'm guessing it's a simple problem that involves a misplaced file or something to that effect. Any ideas?

Sorry if this is a very basic and stupid question, but I'm stuck. Just getting into putting a viper cockpit together and I'm not real sharp with all the technical aspects of working with DCS Bios. I just downloaded it today to set up the F-16 DED I received in the mail today. In the dashboard I selected Com 1 just because I wasn't sure which com port to select. Well, it obviously wasn't the correct port because it never connected but now it is the only com port that shows up. I know there were more listed when I first tried it but now I can't seem to get any other ports to appear in order to try them. I even uninstalled the program and when I reinstalled it only Com port 1 showed up as an option. I'm lost.

Thanks!

Can't seem to find the meaning of this acronym.

How did you record the keystrokes to voice attack? I have the Cougar MFDs but voice attack doesn't recognize the button presses from those. Did you have to assign each OSB button to a keyboard key and then when setting up your voice attack profile using the word "display" use those keyboard keystrokes to get it to work? Great idea BTW!

I use mine as the speed brake. Depress it to activate the brakes and flip it up to retract them. Works very slick!

Deleted

Black Shark is much more of a challenge, at least for me. The main reason is because I was already a pilot in real life when I first flew F4, so it was more or less mastering the weapon systems and quirks of the sim. With Black Shark, however, I have to start from square one having never flown a chopper before. I spent the first two weeks just flying - no weapon systems, no abris - just taking off, hovering, point a to point b stuff. I have now come to the point where I am comfortable with the weapon system which I think is easier than F4s, but the abris is still something I am trying to wrap my head around. BS is by far the superior sim apart from the lack of a dynamic campaign.

Life with BS? Well, this sim has made me poorer for one thing. I ended up getting a second monitor, Track IR, and a pair of headphones just so I could fully immerse myself in this incredible sim. I've been flying flight sims since the original MS flight simulator on my dads Compaq (5 inch screen as I recall) back in the eighties, and this sim has surpassed them all, even my alltime favorite, Falcon 4. It's a masterpiece. I often feel overwhelmed but then I dig a little deeper and and slowly but surely get a handle on it, only to encounter another challenge. I try to fly a couple of hours a night and am now to the point where I need to master the ABRIS. So yeah, life with BS is good!

I'm having trouble completing the mission that takes place in the deployment section of the campaign, the one where you have to cold start while under attack in the dark and fly to a new FARP. I have a main gearbox fault and can't get to the new FARP before it goes tits up. I start up and fly off as fast as I can but it still happens. What am I doing wrong? Also, is there anyplace I can find a mission "walkthrough" that will provide guidance in case I get stuck in the future?

After hours of frustration, I finally figured it out. Under the controls tab where you map the keys, I didn't realize that there are two different gameplay modes: KA-Real, and KA-game. I cleared the commands under KA-real, but the JOY x and JOY Y commands were still mapped to the rudder in the KA-game mode. Easy fix, but one that truly had me stumped. Runs like a charm now! This sim rocks. Can't believe how much fun it is, and I haven't even scratched the surface.

I'm stumped. My toebrakes are controlling my cyclic, and I've tried everything to stop them from doing so. I cleared all axis commands and reloaded them, with my rudder being JOYRZ and pitch, roll, and collective being JOYY,X, and Z, respectively. I look down into the cockpit and whenever I push on the toebrakes, it makes the cyclic move around like I am using my x-52 joystick. The only way I can fly is to make sure I don't depress my toebrakes, but that's hard on my feet. I've got he latest drivers loaded, I messed with every setting I can think of in the Saitek profile editor, including deadzones, but nothing seems to work. The only axis command I have assigned to my rudder pedals is JOYRZ, so why are my toebrakes sending the game JOY_Y and JOY-X commands, and what can I do to prevent that from happening?

I assigned zoom to the slider on the throttle, but did it from the games input options, not the SST programming thing. If you use the rotaries, make sure you have a band in the center ident that doesn't have a key assigned to it, otherwise your controller will constantly be sending a keystroke to the game. And lastly, I HIGHLY recommend picking up a set of rudder pedals for the x-52. I hated the twisty stick and since flying with pedals it makes lining up those strafing runs on the A-10 a thing of beauty!

After flying a couple of missions, I begin to get weird graphic glitches and textures all out of whack. I noticed when I end a mission and the dialogue box appears asking me if I want to save, quit, or cancel, the mouse cursor blinks rapidly between the normal arrow and an hourglass. Somewhere, somehow I'm getting inputs from somewhere that is slowly strangling my game but I don't know where they are coming from. I'm flying LOMAC ver 1.02 with a saitek x-52 and rudder pedals with Track IR 1. I know I have a problem with the "33" and "34" key on my saitek (well known bug) but I use a profile from the SST program that doesn't use either one of those inputs so I wouldn't think those keys spiking would be the cause. At any rate, I was wondering if there is a log file that keeps track of all inputs? Any and all help is welcome. Thanks. Update: I think I found the problem. I didn't have a blank band set on one of the rotary knobs on my x-52 and even when it was at it's centered ident position it was still sending out commands to the computer.