Highspeed1964

Not surprising, given the nature of the HUD. It's a projected light image onto clear glass. Some of the light will pass through and if there's another surface to reflect it (such as the fog itself) you could get this ghosting. Highspeed

Do you have an axis assigned to view zoom? It's possible that the axis is zoomed all the way out. It would be an axis assignment in the F-15C module for it to only affect that aircraft. Highspeed

I'm not sure about this particular instance, but shadow quality DOES make a difference in many cases. If your shadow quality is set to "flat" you'll get odd renderings like this. Flat tries to keep the shadow in a single plane (geometrically, not aero-plane) and if it encounters a curved surface the rendering can look very unnatural as in your example. The wing is a curved surface. So we need to verify if you've tried various settings to check this. If you have and still have the same rendering issue then this could be a bug. Please let us know your settings so we can give a more definitive answer. Highspeed

Virus? Do you have a virus scanner on your system? Highspeed

Merry Christmas!!! A present... Hey guys, I just wanted to get something up here for you as a gift for the holidays. I present to you v0.2alpha of the LEA Extended Input panels for the DCS World Huey! This is a quick and dirty packaging and includes the following: 1. The project file 2. vJoy configuration description (.html files) 3. A basic "readme.txt" file I did not go into extensive documentation at this time (it's still alpha) and this is not intended to provide a tutorial on LEA itself. You can visit their website (http://www.leaextendedinput.com) if you need assistance getting things going. Some controls are done on a vJoy Axis and you'll need to assign them in the appropriate configuration screen of DCS World. Particularly, the lighting controls on the overhead console. You get true analog control of those lighting systems! My hope is that this will enhance your simming experience in this wonderful aircraft. I had hoped to have a demo video done by this point but ran into some challenges getting one together. Being that I am out of town starting tomorrow, it will probably have to wait until I return next week. Perhaps a New Year celebration?!!! In any case, let me know what you think and feel free to provide additional to help improve this project. Particularly in what I could include on the "Misc." page/screen - that is still very much a work in progress as you'll see. At the bottom of each screen is a set of selection buttons to switch from screen to screen. I turned off the menu bar in all screens (except Misc.) to get more screen real-estate. Note, to exit the program you can either press the home key on your device or switch to the Misc. screen and select "Edit" then press "Exit Program" from there. Screenshots: And the project files for LEA: DCSWorld2.0Huey_v0.2alpha.ppk.zip Enjoy! Highspeed

All or none!:pilotfly: Highspeed

Nope, you're not missing anything. The throttle axis only works from idle to full throttle. Below idle requires keyboard (or mapped button) input. Unfortunately there's no way to really stop your throttle input from going below idle without it jumping to full cutoff once you've pressed the idle stop release. There's no mechanical stop on your stick. So the bottom line is you'll need to do it the way you described, page up (or a mapped button on your stick) to get to idle then throttle axis to control anywhere between idle and full throttle. To cut off the engine, press the release button (again by keyboard or a mapped button) and page down or mapped button to decrease to cut-off. I, too, wish there was a better way but I find mapping buttons on my throttle work fairly reasonably after a few times getting used to it. Highspeed

Outstanding! Thank youCibit. :) Highspeed

New thread for my Huey panels on LEA is here: https://forums.eagle.ru/showthread.php?t=178768 I've gotten the designs roughed in for all the remaining screens so the screens you'll be getting in this project are: 1. Center console 2. Overhead panel 3. Instrument panel - Co-pilot's view 4. Instrument panel - Pilot's view 5. Cyclic and Collective sticks 6 Miscellaneous functions - for now just a matrix of buttons but I may get a little creative on this one, too. Anyway, you can follow my thread for developments and new downloads as they become available. Highspeed

So it seems there is some sort of problem with the link embedded as a youtube item, so let me try just listing the link here. Hopefully this works out ok. Highspeed

Hi guys, Just a little project I wanted to share with you all. I'll be posting in this thread as updates are made and sharing the project files here as well. This project is being made via a utility called LEA Extended Input. That program provides a little "serve-let" application that runs on your computer and receives input from an Android or iOS (Apple) device. This can be a phone or tablet or any combination of devices to provide more than one panel at a time. (Please note, I am not associated with the makers of this software and am not trying to sell it - it's free anyway - or promote it either.) The software is available here: http://www.leaextendedinput.com In my LEA project, I am building 6 different panels that you can switch between and those are: 1. Center console 2. Overhead panel 3. Instrument panel - Pilot's view 4. Instrument panel - Co-pilot's view 5. Collective and Cyclic sticks 6. Miscellaneous Each panel contains a large number of hotspots which are mapped to joystick buttons on "virtual joysticks" that are then mapped in-game to provide direct input to nearly all of the clickable spots of the cockpit as presented in the sim. To give you an idea, I've made a rather rudimentary video showing some of the functionality of the interface. This video demonstrates the lighting controls for the various internal lighting systems. You can view it here: ${1} Please forgive the quality as it was recorded using my cell phone in one hand and operating the controls with the other. And yes it is a bit dark but that's so you can see the lighting in operation as I control it with my panels in LEA. I'll be putting together one or two more videos in the coming days, particularly a startup video showing the entire operation (with one exception - I cannot map the IFF panel controls since they are not accessible in the controls configuration menus) done without touching a mouse or keyboard. Once I have a decent set of documentation put together, I'll get the current build out in this thread. I've put out a very early alpha in another thread on this forum but it was a quick and dirty alpha which only had a couple of panels somewhat finished. LEA also allows keyboard mapping and I had tried to configure my panels to use this function so that you wouldn't have to manually map each of the inputs (at least until I can figure out a proper way to distribute the mapping files along with the project) but I discovered a bug in the program - Windows keys do not map through so any control function that uses them in the keyboard combination would not work. Furthermore, in testing I discovered that some key combinations also pass through to Windows and I ended up with a lot of Windows Explorer windows opened up in the background. Ultimately this would cause DCS to crash. So I've gone back to the Joystick Button method for now. In any case, keep watching here if you're interested in this project. In the meantime, I hope you'll enjoy the video above if you haven't already done so. Highspeed P.S. It may take a while before the video is available to view so if it's not available, keep trying.

Those aren't keys or buttons, that is an axis. I set mine to run the view zoom but you can assign to any function in the Axis group of the control configuration. Highspeed

It seems that Belsimtek is not doing much to improve this module any more? There are other minor issues that are also not being addressed. However, the DCS updates are not designed to fix systemic issues such as these. It is up to the publisher (Belsimtek in this case) to correct switch mappings and other programming errors. I've also reported an error in input mapping of the circuit breakers for joystick button inputs a couple of weeks ago and have not even had a comment from them on that thread. So is there any more interest on the part of Belsimtek to improve this module? I've heard that they will be working on getting the multiplayer working with each player being able to take a different role (i.e. co-pilot, left gunner, etc.) but that doesn't seem to have made any progress since being discussed quite some time ago. Please correct me if I'm wrong devs, but this seems like a dead project at this point. Highspeed

Correction to the above. The needle scale is marked in 100s of feet with the tick marks being 20 feet each. So the needle is equivalent to the secondary portion of the "odometer" style readout but having more resolution to give additional accuracy. Highspeed

More specifically, it puts all the green arcs in roughly the same position on each gauge. These components were selected for the Huey from "off-the-shelf" units that were not specifically made for this helicopter. By rotating the gauge 90 degrees counter-clockwise, it makes it easy for the pilot to see "at a glance" when everything is operating in the normal ranges. Highspeed

3.1.2.31

Perfect! Thanks. It seems a death ends a career! DOH! I was flying patterns and had the rotor fly off (a bit abrupt of a maneuver) and plummeted to my death. So it started a new player. Now I know and it all makes sense. I appreciate the help finding this. I'd have never thought to look in "Mission Editor" for the logbook file. Highspeed

This has happened a couple of times now. My log book entries have just disappeared. This time I had worked my way up to Captain in the Huey and was feeling pretty accomplished. (No combat, just a flier.) I did notice that it never logged any night flying time although I can't be certain if it didn't log it at all or just as daytime hours. Last night I was going to do a flight but wanted to check where I was at hours-wise and found that I was back to a "Butter-bar" (2nd Lieutenant) with zero hours. Errrrgh! So where is the log-book information stored and how can I get it back if possible? Highspeed

Not on mine. I only have the settings icon (the gear shown in your screen shot right next to the one you've circled). How do I proceed? Highspeed

I don't! But... I have friends who are not so fortunate and I'd love to bless them with some simming gear for Christmas. So someone more deserving than I (not hard to find such sorts :megalol: ) would end up with it if I won it. Highspeed

Put a Cougar MFD around that and you'd be golden! At least I would think so. :) Highspeed

It sounds to me like the OP is aware of the number of activations/deactivations allowed. His question (and the same one that's been on my mind since I'm fairly new to the DCS World) is: When deactivating to move it to another system does the deactivation not get restored when it is successfully re-activated on the new machine? From what I gather reading the original post, deeplodokus is testing his setup in a virtual machine (VM) environment and having to rebuild the virtual machine at times when he discovers that a different configuration is needed to improve performance or something of that nature. In any case, is it normal that the deactivation count keeps decreasing even though the activations count is incremented back to the previous value after the whole process is completed? If that is the case, I would suggest that deeplodokus perform the testing with just the base software (and any mods or other add-ons that are not purchased items) until your testing provides the result you're looking for. Then once you have a good configuration go ahead and activate your modules at that point. Of course if the VM rebuilds are due to other factors not related to DCSW, perhaps you might want to consider putting your DCSW software on another machine (even if it's a separate VM from your other software) so that those rebuilds do not affect your deactivation/reactivation status. Hope this makes sense. Highspeed EDIT: deeplodokus, you posted just as I was typing my reply. Your last post sums up the question quite nicely. That would be the way I understand it too, based on everything I've read/seen.

"Wanna know how helicopters fly? They're so ugly the earth repels them!" - source unknown :pilotfly: I actually think helicopters are a thing of beauty. Such a mechanical marvel of engineering. If you've ever delved into the full process of movement it truly is amazing and a wonder that they fly, but I'm so glad they do. I've really flown nothing but the Huey in DCSW. Loving every minute of it. Not that it's been easy. Nearly 30 hours and still working on landing it "on a spot". Pretty close (within a couple of feet or so) but not consistent. However, at one point I hit a wall in my progress and couldn't figure it out. I finally realized that the stick I was using (TM HOTAS X) was, although new, still analog and not very precise. Moved up to the T16oooM which has Hall Effect sensors and the mechanism is a good bit smoother as well. Went from 10 - 15 foot accuracy down to 3-5 feet instantaneously. So hardware does make a difference. And yes, I fly rudder pedals. And a seperate throttle for the collective. That throttle (TWCS) has a dial axis as well that I use for the actual throttle to run up the engine. Anyway, good luck on your progress. It WILL be frustrating at times but the payoff when you finally get into the groove with it will be worth it. The biggest pointer I can give is: Try to be very "fluid" with your movements. I tended to be more "digital" at first making intermittent nudges on the stick to correct any drift or other unwanted movement tendencies. However, becoming more familiar with the visual cues and what effect different inputs have (e.g. more collective=more torque so more anti-torque is needed) you'll anticipate and be less reactive. Then your movements won't be so jerky and it will all smooth out to better precision. Highspeed

I know this post is a bit old, but I'm fairly new here and going through a lot of posts to "catch up" on things. And I wanted to reply to this since no-one else has. The AAU-32/A altimeter used in the co-pilot panel is modeled correctly in the sim. It is a single needle gauge with an "odometer" style readout indicating the thousand and hundreds of feet. The needle provides the remainder of the altitude and is marked in 10s of feet with smaller ticks indicating every 2 feet. To see what I mean, have a look here: http://www.elbitsystems-us.com/sites/default/files/imported/cas/esa-aau-32-digital-pressure-altimeter-2010.pdf Highspeed

One additional note: There are other .LUA files in the same folder as the default.lua file and these will need modification as well for completeness or if using one of those input types (I'm guessing) so hopefully the devs will catch all of this and update accordingly. Highspeed