JLX

It's a cool visual effect that when overdone (as it is now) detracts, rather than adds, to the immersion. With all the work going on, I'm guessing this may have fallen into the low priority bin. I hope not...

Agreed. This is very frustrating. Here's hoping for a fix soon!

I would also like to know is more about this. Especially as there doesn't appear to be a waypoint decrement button. Auto-incrementing waypoints is one of the first things I turn off in the A-10C. Sent from my BTV-W09 using Tapatalk

Mission building takes a lot of time and it's very generous of you to share you creations with the community. THANK YOU! I have a small beginner group of nuggets that are just getting up to speed and your variable attack missions have been a wonderful playground where we can ramp things up as our expertise grows. It's so nice to play missions that you don't make yourself and get that sense of discovery back again. Thanks again and I hope to see more of your work! Cheers!

There is a little black button on the collective just above the throttle handle. When the throttle is at idle, you need to press this button (with the mouse - not sure if there is a keybind for it) to release the lock and then you'll be able to twist it the rest of the way to the off position.

Agreed! That was a great read.

I'm also eager to learn how to late-activate effects. I'd like a huge smoke/fire post bomb effect that I can trigger.

+1! Little effort high gain. This just makes good sense. Sent from my BTV-W09 using Tapatalk

Arg! The most recent patch (Open Beta Update 4) listed: "Mi-8MTV2. Spring Tension campaign updated for DCS 2.5" Which led me to believe it would be working properly. I was hopping all over the place trying to guess the right spot to land. Tried near the building, tried near the two paratroopers by the rivers, etc... Figured it was broken and exited to post. Very irritating! With no in-mission saves you must begin again and spend hours flying the same thing over and over until the fun is sucked out of it and you give up in frustration! This is an all-to-common problem for missions in general. I realize there is an extra challenge with the 2.5 EDGE updates. But, bugged missions in general due to API changes, etc. have been around for ages and often don't get fixed in a timely fashion. Anyway, thank you @ariyaner for the information. When I get the energy to try this mission again, I'll keep hopping around in hopes I find the landing trigger.

Tnx for posting the thread link. Came here first but am having the same problem. Glad to hear there are ppl working on it.

Nice shots. Until the EGT gets sorted out, Huey is on hold for me. Hope the wait isn't too much longer. Sent from my BTV-W09 using Tapatalk

+1 I've often wished I could do this as well. Would be a great addition. Sent from my SM-G930W8 using Tapatalk

Man I love this community. What excellent and detailed info! Thanks to all. With the info provided in mind, what I'm seeing makes much more sense. I couldn't figure out why the ground clutter didn't move up when I moved my nose down for instance. So, to check my surroundings (without GCI/AWACS) rather than doing a tight continuous circle as I have been doing, I guess I'd be better off doing a series of say 45° turns and levelling between each for a couple seconds to allow the RADAR to get a sweep or two in before moving on to the next. Thanks again guys. This is my first stab at air-to-air and finding targets (never mind killing them) is proving difficult! However, it is a lot of fun to learn and the 21 is a blast to fly! :-) Time to get back at it. Cheers.

I'm trying to better understand how the physical orientation of the radar works in the MiG-21. I'm clear on what the manual states: From this, I gather the orientation and position of the radar dish is fixed relative to the plane. The only exception being the option to tilt it up 1.5° in the dorsal direction. In all the examples/tutorials I've seen/read, the plane is always in a strictly horizontal orientation. What I want to understand is how and what the radar displays when it is NOT horizontal. I constantly read how you should be below your target to detect them due to the shallow -1.5° scan angle. Makes sense if you're flying perfectly level, but why not just enter a shallow dive and look down? Alternatively, why not just roll 90° so that that ±30° of left/right scan becomes ±30° of vertical scan? Assuming you'd rolled 90° to the right, that would mean that targets on the radar to the "left" would actually be above you and vice versa. Even trying to account for the fact that the radar display takes a second or two to update, my brief tests have left me unclear as to how it operates when not in level flight. Often I fly with the radar off. Then, switch it on and fly a level circle to scan the surrounding area for any missed contacts. An aerial "Crazy Ivan" if you will. However, this often doesn't work as expected which leaves me to think I do not sufficiently understand how the radar works and/or am interpreting it incorrectly. Can anyone shed any light on this for me?

Glad I found this too. Haven't flown the Huey in a while but find it overly sensitive at the moment! EGT redlines almost out of the gate and is so sensitive that engine fires/failure make the module not much fun to fly at the moment. Do hope they fix this ASAP as it's one of my favourites. I will check to make sure De-icing is off though in the meantime. Good tip.

FWIW, I have had this issue too when I used to use a CH Flightstick and it wasn't a hydraulics problem. It was also intermittent which drive me nuts! After much trial & error, in my case it turned out to be an old Logitech driver I had running for a RumblePad 2 controller. If it was active, it seemed to interrupt polling of the JS or something in a way that caused significant lag in DCS. When I uninstalled the Logitech software, the problem went away. Not sure if this is the same issue that is at work here but it may be worth checking just in case. Good luck!

Clever to pull the info from the keyboard\default.lua. However, I tried doing this with the 2.5 beta and it didn't work. Frederf (or anyone else) can you confirm this still works with 2.5 beta? Would really like to the get remaining keybinds on my HOTAS. Fixes seem to be few and far between these days. Tnx!

Yes, I've noticed the same thing. The lines between the repeating tiled textures become very obvious in this light too which is unfortunate. You can see them clearly in the screenshot you provided. I hope they get to polish details like this in the future after they deal with some of the more critical issues on their plate. Sent from my BTV-W09 using Tapatalk

That's a shame. I'd like a set of 20's too. Was going to inquire but guess I don't have to now. Sent from my BTV-W09 using Tapatalk

Any comment on when this bug will be addressed? It's been a long time since the original post and is happening in 2.5 too.

I've updated DCS 1.5.8 stable to 2.5 beta and all is well. However, I have a question about the registry. Under the HKEY_CURRENT_USER\Software\Eagle Dynamics\DCS World registry key there are values for: Language: EN Path: C:\DCS Version: 1.5 While Language & Path are self explanatory (and correct), the version still shows 1.5 even after updating (with dcs_updater @openbeta). Shouldn't it show "2.5" or "2.5 beta"? [*]Is this something the updater failed to update? [*]With autoupdate.cfg in the DCS root perhaps the registry entry isn't needed/used anymore? [*]Should this be set to 2.5 or some other value? I ask because I intend to use the DCS_updater to convert the 2.5 beta to release when it becomes available and want to make sure I don't end up d/l files unnecessarily. Thanks for any info on this. Cheers.

Our group is having the same issues but I have some observations to share that may help: I'm hosting (non-dedicated) 4 players are trying to connect. The 2 (of 4) players that CAN connect both have DCS on a SSD. The 2 that can't connect are always disconnected (usually at 4 mins) with a timout error. They are loading from HD. If the mission is VERY simple (in our case 5 planes and NOTHING else in Nevada) sometimes the last 2 can connect. I'm wondering if the problem is related to loading times? The guys with the SSD are perhaps loading within the timeout limit while the others are not? It seems reducing the complexity of the mission does help. Perhaps because there is less to load and the timeout limit isn't reached as frequently? Anyway, just thought I'd pass on these observations in hopes they may help. My general machine specs are in the sig. Win10 x64.

Thanks for this. Great work! Sent from my BTV-W09 using Tapatalk

Outside looks beautiful with these settings. But in-cockpit looks too dark and high contrast. Any plans to tweak this further? Sent from my SM-G930W8 using Tapatalk

Really helpful! Thank you! I'll second the suggestion to make it a Google Spreadsheet. Easier to always reference the latest version. Cheers.