yipster

I don't remember if there were any major fixes to the Huey since 2.5? It seems like a lot of the graphical stuff is still broken, specially the lights at night. :joystick: Has the dev team given up on it already?

Flying the Huey at dawn/dusk/night is impossible specially for that mission in Argos campaign where NVG is restricted. #Beacon and nav lights shine right into the cockpit #landing and search light is dimmer than an iphone flashlight, has very limited range and brightness #cockpit instrument lights without the flood is almost unreadable even at brightest This has been a bug for a long time, when can we see a fix please?

Any chance of getting a HMD update to designate targets on the ground visually? Unless that requires a whole new electronic suite to accomplish? I wish I could just look at a SAM/AAA site and just designate a point so TPG could slew right on to it.

I've got a new 240G SSD just for DCS over the black friday deals. :thumbup: Now, how can I safely transfer existing install from the old HDD to the new SSD? Can I just copy and paste it or do I need to do some registry edits. Or have to be stuck with new download and install?

I tried first attempt at it today, the plane gets stuck to 0kts as soon as main landing gear touches the carrier? Like, all physics stop at the moment of contact, everything still runs (including engine afterburner), but the plane is stuck at a nose high pitch stopped. Something I turned on accidentally to cause this?

So I'm not the only one who's trying to get hands on new update and the hornet module :music_whistling: I guess I will wait...

Just lauched DCS today and it said it failed to authenticate and start asking me for every single serial key. So I went into my account to look for them, but some of the modules does not have a serial provided under my account? The button is simply not there. How can I fix it?

I just got my hands on a HTC Vive. About to download and install DCS 2.5, maybe I'll start with a fresh install. Can't wait for the weekend to start trial of this! Is there anything special I have to do to get the Vive working with DCS? Or does it just do it automatically given that SteamVR is started?

I remember a while ago I had similar issue with trackIR stopped working after an update. Where I can't look around in trackIR nor use the numberpad keys either. The view was simply 'stuck'. The cause was that some config file were corrupted during update. The solution was to delete/remove some .lua files but I forgot which ones. I tried searching for it and couldn't find it. It happened again and would like to know which are the files that I have to modify to get it working? This problem happens to certain modules, not all of them.

Awesome work! Can you share some info on the CNC machine and machining process for the back-lit acrylic boards? And how did you get those PCB done?

Just loaded up the module and I can't seem to look around in cockpit (F1 view). TrackIR5 and even the num pad keys are not working either.

On the A10 with perfectly working computers and engines, probably just a 2. Mainly needed during slow flight and landing. On a P51D, 100. Impossible to fly without a rudder.

Wow, that has to be the most clever home pit I've seen so far! Mind if I borrow your idea? How did you mount the monitors and inner panels? Would love some close up detail of the mounting/hinges.

Here's my take: Link to thread: https://forums.eagle.ru/showthread.php?t=162303 I haven't got the time to build a custom case for it to hide the remaining bits of the screen, but all in all it works great :)

Another vote for 3440x1440. Moved from a 3x Dell 24" (1920x1200), I did not like the setup as the monitors had a bulky bezel and it distracts a lot when looking around. One single 34" 3440x1440 monitor is really smooth when looking around.

It is something that the Warthog throttle tends to do. Here is why: At idle, the 'off' switches are low or in the '0' position. When you place the throttle down to 'off' position, the switch will go high or to the '1' position. DCS will only detect the switch on first time detection. Means that it will probably take couple cycle from 1 to 0 and then 1 to detect. Remedy few options to try: 1- check 'sync control on startup' in the menu 2- add a 'control check' procedure before your APU switch. Look down at the throttle in cockpit view and make sure they are synchronised before moving everything back to 'off' position. 3- start the mission with the throttle in idle. Only pull the throttles down to off position when the game is loaded. This will trick DCS to detect the first position high switch

My 2c is to save a little on the processor and go with better graphics card. With gaming rigs, graphics card always be the most important part to invest in if you're on a budget. I still have a i5 3570K, overclocked @ 4.5Ghz . I'm trying to say is that I get steady 40-60+ fps with my 980Ti with such old i5 processor. Games run at 3440 x 1440 ultrawide, plus the 2x little 8" (1280x1024) MFD screens.

Here's my mod: Snipped a piece of a dental floss pick, use a drop of strong-ish glue (not superglue), then file the 'leading edge' off so slightly to adjust the 'feel' you want for your push to afterburner. Works like a charm :) Some curve adjustment depending on the aircraft to set the Mil thrust power to be just at the push detent. I only had to do it for one or two crafts, the rest simply works with 100% linear curve.

How do you update the firmware?

Turning off LED still not good to fix this spike/jitter issue: :(

What is causing this to happen? I don't recall having this problem before.

Hi, I've been using the 'friction adjustment' on the Warthog throttle to control zoom in DCS 1.5. I have a slider curve setup for it so when it is in the middle, it is zoomed to my preferred default zoom. recently I've noticed that it flickers really bad when I zoom in half way. It is almost as it is detecting spikes in the axis input. I've checked the 'raw' input from the joystick and it seems to be steady and not spiking. Is this an known issue with recent DCS update? I didn't have this issue before, in the early 1.5 releases. edit: I just tested again with the zoom wheel in that 'flicker' spot, it does indeed report a spiky raw input into windows. Is there anything I could do to rectify this?

Turn into the wind or the edge of the mountain where it slopes down. Turn on emergency governor control, raise your collective slowly and 'feel' the chopper pick up slightly forward. Use this momentum and keep feeding collective until you start loosing rotor rpm. If you start loosing rotor RPM, you have to decrease your collective to keep your rpm in the green zone. By then you'd hope that you haven't ran out of flat ground and have gone past translational lift to gain more altitude.

How about moving the AI and Autopilot indication window? I run a 3440 x 1440 ultrawide with 2x 8" MFCD monitors, I managed to move the control indicator when I did the kneeboard location mod. But the Autopilot and AI gunner are still displayed in the lower right corner of the MFCD monitor.

Same here :( With TrackIR 5