RackMonkey

I'm talking about the comm menu in the top right or the system info in the top left of the screen. If you ask the system to bring up either one of these you are not worried about what they might cover up. There are a lot of times that the background color makes it VERY hard to read. This takes your eyes away from actually flying longer than needed. Make the background black or dark blue since the font color is white. Selections can be made quicker and more accurately.

This is a problem I've been asking about for a year now. It's still not addressed in the "Tank Killer". The HUD only mode seems to have been implemented differently than the other acft in DCS. Capt Zeen hasn't found the time to create a profile for Helios yet so I don't if it will work correctly there. but I doubt it. I've written my own export lua to get both MDF's onto a second screen and I've increased their size so they are easier to read, but in HUD only mode I can only see the two MDF's. With this setup I can go to HUD only view and there are no MFD's on the main screen, only the two on my second screen. I fly in normal mode and use the buttons and switches on the main screen and just use the enlarged MFD's on the second screen to see what's happening more clearly.

My primary is a 3840 x 2160 TV with a 1920 x 1080 monitor underneath it. In order to set up some export windows I need to center the the second monitor at exactly 961 pixels from the left but when I try to center the second monitor on the primary with the mouse, Windows and nVidia both jump 34 pixels either side of the 961 point. Is there a config file in Windows somewhere that I can manually set the position that I want?

I took another look at Virpil's rudders after reading zhukov032186's post. Damn if that isn't the perfect solution. Don't mount the bottom half of the pedal and and raise the brake pivot point by mounting it on a block of wood and it's perfect. Today's conversion is $366.00 though. I'll get them but I'll have to wait for a better conversion rate.

Your right. I forgot to take into account that my seat is custom built for my pit and desk chairs will always be higher and more "upright" than just about any seat in a cockpit. I think I might buy a broken set of pedals and see if I can create a custom set or just get a USB controller card and just start from scratch. I use an extension on my Virpil stick and trying to control the Huey while my legs are stuck together controlling the yaw with my CH pedals in not conducive to smooth flight. At the very least I need to get the pedals separated a bit.

That is one of the better one's that I looked at. No brakes though and since I'm working on a sim and not a game I would like the brakes where my muscle memory says they should be. 15K+ of flying hours is hard to brake habit and training. I'm still trying to move my head instead of just my eyes when doing my instrument scans using Track IR. Maybe the net version of the VKB will be the right design, they've got a good start now. Just a few mods and it would be perfect

Looking at some pictures of the 109, your right but look at where the brake pivot point is. It's near the bottom of the pedal...just about where the ball of your foot would rest with your heels on the floor. Look at pic's of the KC-10, it's the same way. You can make a more precise rudder input if you pivot your foot at the ankle rather than moving your whole leg. This becomes real world when our trying a cross wind landing and you can't dip you wing very far like on the 737. Airlines don't like it when you scrape the bottom of their eng cowlings. But remember, your example is that of a high powered short coupled aircraft without hydraulics' to help

Don't take the statement so literally. We both know there are probably quite a few that we will never be aware of. Let's just say it's true for the units that I have found while looking for a more realistic set of rudders for my pit.

The TM TPR are the only ones that are anywhere close to real. The first thing you learn in flight school is to keep your feet on the floor, only put your feet "up" on the pedals when you actually want to brake. Everything on the market has you putting your whole foot on the pedal just to move it. This is just wrong. Put you heel on the floor and use your ankle to move the rudders. Moving your whole leg to actuate the rudders is just to coarse of a movement for fine rudder control, but it's what you have to do with these poorly designed pedals. I don't think a real pilot was even asked during the design phase or they were ignored because it would cut into profits to do it correctly. I've flown aircraft from Piper Cub's to DC-10's and none of them have rudder pedals like the ones these people are selling. The TPR is as close as I've seen but I'm not spending $1K just to be disappointed again.

I've flown out of both Nellis and LAS. 03/21 is for safety and noise. Could you imagine everything form a T38 to a B1 in full AB 1k ft overhead? I'll bet they dread Red Flag. I've also had to takeoff "backwards" at McCarran on more than one occasion. A fully loaded 727 on a hot summer day just can't make the climb requirement for 25R and it was a looong take off roll.

Unless there's a performance reason, the departure runway is always the closest to the parking ramp, called the "inside" runway. Arrivals are on the "outside" runway. For traffic flow efficiency it is easier to get an arriving acft across a departure runway that it is to get a departing acft across a landing runway. Watch any plane spotter video at LAX, ATL, NYC and you'll see this to be true. DCS doesn't seem to take this into account when they set up precision approach's at their airports.

What about some ambient lighting? Watch any night ops video on YT and you will see floods on the island. The deck crew doesn't operate in the total darkness that our carriers currently have. Just don't make it so bright that you can see it from space like the alignment lights currently are.

Razor18, I'm afraid your V speed definitions are wrong. Please look up the correct definitions in the FAR's.

Good luck with that. I've been asking how to do something like that off and on for about two years now. The A10 seems to be the only acft with the problem, so you'd have to ask DCS the "how to" question. Even the genius that is programming Helios doesn't know how to get the MFD's properly exported to a secondary screen when in the HUD only view. I've been trying to get my primary monitor to show the HUD only with Alt-F1 and when I do I get a couple of large MFD's in the bottom corners. If I try to use Helios, I get in HUD only mode those two large MFD's are only moved down so that half of them is on my main screen and the other half in on the secondary monitor. Nothing I do changes the size and position of the MFD's. You'll find a couple of YouTube videos that show a HUD only view on the main screen and the MFD's properly sized and positioned on the secondary screen. I was told by the guys that did answer my questions that it was done with a much older version of DCS and they couldn't remember how they did it. My end result would be close to yours. The A-10 HUD only view on the main screen that's maybe four or five feet away, depending on the screen size, with Helios on a secondary, 32in touch screen that's with in reach while flying. I've determined that a 32in screen should give you a correctly sized instrument panel, or at least close, depending on the resolution your using.

I'm not as ambitious as you guys. I have a custom seat, a large primary screen and a smaller touch screen that I output Helios too. Good enough for me to get blown out of the sky several times a day. I have been asking around to find an answer to one question about using the HUD only mode with the A10-C / II. What do I have to edit to get rid of two overly large MFCD's when I try to use the HUD only mode. I have asked others but they were old enough to be ver 1 of DCS and they couldn't remember what file they edited to correct the output. Now that we are on ver 2 I doubt it would work any way. If you not sure what I'm talking about let me know and I'll post a screen shot.

Never mind. All i had to do was ask the question and i found the answer.:)

1.6 is really easy compared to previous iterations. There are a good number of profiles for the different acft but like with anything, there will be some tweaking to do. The way I see it, if Helios puts all in instruments on a second screen then you should be able to fly in HUD only mode. This currently works with two of the three acft I have, the F16 and F18. The F16 doesn't have the side panels yet and the A10 leaves two huge MFCD displays that span both screens. That's what I'm looking for help with. The F18 is the most complete. All the instruments are on the second screen with all of the consoles and the HUD only mode gives you a wide open view. This is good enough that I'm thinking about NOT going to VR. If you add a touch screen as you second monitor you can flip all the switches and dials with a flick of your finger. Something that you would have to use a mouse to do with VR. There's a lot about Helios that I like and it would take a real long post to tell you about all of them and why. Give it a try and join their Discord or IM me if you need any help.

Already did that and they did try to help but I don't think the problem is with Helios. I'll loop them back in if I learn something new, but right now I think the problem may be with the way the A10C was written. I've looked at a lot of files but can't recognize the difference that allows the other acft work correctly in Hud view and the A10 doesen't. I havent profiled the F15 yet, Maybe doing that will give me the clue I need to figure it out. I'm hoping to get help from the guys that have a lot more experience with the way the files are set up in DCS.

I recently installed Helios 1.6 as an alternative to VR for now. I have profiles set up of the A10C, FA18, and F16. The basic F1 configuration is working perfectly. My problem is when I switch to HUD only mode (Alt-F1). The F18 and F16 work perfectly but with the A10, in HUD only mode, the MFD output is huge and out of place. With the help of another flyer I've entered the viewport mods to all the file that we could find that might make a change to the output. Nothing worked.:cry: What I need to find out is does your install do the same thing mine does? If it does and you found a fix...what is it. :smartass: If it does and you can't fix it, do you think it's a problem in DCS or Helios.:detective: If it does why do you think the F16 and F18 work and the A10 doesn't. :huh:

I see Snoopy is talking to real pilots at Moody and I see Wag's it is talking to "pilots" of an unknown origin. Diametrically opposed answers as to whether a pilot has to move their head in order to see the entirety of the HUD. At this point I have to go with Snoopy. When you adjust so that the top cross bar is as thin as can be, and then move your eye point back to where you can see the idiot lights below the fire handles, I lose information on all four side of the HUD. No pilot will cover their idiot lights. They are just to important when they do go off. I think any acft designer will tell you that you have to start the process of designing a cockpit from the pilots eyes. They have to be able to see ALL of the information to make the critical life and death decisions. After all, isn't that what we pay them to do? As far as bobbing a weaving to see...have you ever heard of vertigo? I've got 15K hours in heavy's and on occasion I've experienced vertigo, especially when flying actual IFR. It's not as bad in a heavy as in a fighter but it's still there. I think ED has to go back in and adjust every instrument and display from the pilots eye point. Helmet on the chute pack and all idiot lights visible. Then we can spend 18 pages of complaining about this and that and ED can stay out of it because it will be our personal setup that's the problem at that point.

Not sure if this is the correct place to post this but since it seems to be DCS wide I'll give it a try. On every acft I have, Alt-F1 is suppose to give me a hud only view. I do get a hud view, BUT I also get the MFCD's for the acft. I plan on using Helios to drop the instrument panel to a lower touchscreen monitor and a triple monitor on top to increase my FOV and peripheral vision. This plan is useless unless I can find out how to get rid of the MFCD's. Does anybody know how to get rid of these things?

One idea I've been thinking about is to replace the lower monitor with a touch screen and use Helios to export instruments to it. I'm still looking for a monitor that's big enough that the MFD's are as near life size as I can get and still get a clear crisp image so that I can read the output.

Trim Sensitivity It doesn't even have to be as complicated as an axis. I don't know what you use as a unit of measurement, but lets just call it "units". Some where is the controls for the acft, not the whole of DCS since each acft would be different, have a drop down selection of say 1 to 10 "units" per "tap" of the trim button. Holding the trim button would work the same, just maybe a little slower than it does now.

I didn't even notice the date. Now I wish I could delete this thread.

It's time to speak up guys. On the Virpil site they are conducting a survey for the design of an aux panel. They are actually asking us what we want and if we aren't very vocal about it, they may not bother to ask again. There's something like 16 different versions of buttons, switches, knobs and levers. I've asked a question before I enter my vote. All the switches seem to be north/south OFF-ON and I want to know if any of the switch can be made east/west and ON-OFF-ON, ON-ON, MOM-OFF-MOM or some other type. And after they answer that one I have more. I know we have more than a couple of hundred Virpil users on DCS and a lot of others that are looking. Speak up guys, let your voice be heard. https://forum.virpil.com/index.php?/forum/21-control-panel-community-vote/ There's actually 4 surveys. Jets, pistons, space and swing-wing. Pick you poison.