Yeti42

Hi all, One of the challenges I have and I'm sure many people will echo in DCS is placing objects correctly in the mission editor. Yes, you can now see the objects correctly sized in the mission editor but that doesn't help that much when you need to take into account the topology of the terrain. Altitude and satellite view help but it would be really useful to be able to move objects around to edit them in a fully 3d rendered scene. The number of times I've had to start the game to view how an object such as a radar is sitting and then edit it again in the mission editor, pretty much every time really..

The one type of question I see asked most in these forums is "When will <insert functionality here> be implemented? It would be good to have official roadmaps for modules that give at least an idea of when something will be implemented, if at all. I suspect this would negate the need for a lot of questions and wasted time in discussions. I work in the software industry so do realize how much of a challenge having a roadmap can be, priorities change but it's always useful to have a target for something and a way of prioritizing dev workload. Roadmaps shouldn't be static documents and can change over time, it would give the community a better idea of what to expect and when (give or take 2 weeks... ) - Discuss

It could be related but I suspect it has something to do with the WP switch logic used in the code, you may also notice that you cannot manually switch back to the correct waypoint after the incorrectly sequenced one has been loaded in the PVI-800, all other waypoints can be selected.

OK, I've narrowed this issue down. It only occurs when there are 2 non sequenced waypoints close together, the PVI 800 gets confused and switched to the wrong waypoint. Trackfile attached KA-50_III_CAU_IA_route_close_wp2.miz.trk dcs.log

It's not correct as is, it's all over the place, you basically cannot fly in route mode past waypoint 3. EVEN when no giro drift and need for alignment is set in the mission editor.

+1, this is an easy fix, please pay it some attention.

Good job Polychop, flight model is a huge improvement! I'm finding the trim a bit tricky though...

You'd think they'd (ED)scale their infrastructure properly and be able to cope with peak periods, especially if these kinds of outages mean you can't really play. Very poor show.

I love the Jaaaag, I worked on it in the 80's and early 90's. The problem we have here is that the balance of detailed aircraft is heavily slewed to the west, we really need some 80's and 90's Soviet era aircraft like the Mig 29 or the SU 27, I'd much rather devs concentrate on that. The Jag was underpowered, had a limited weapons load and was basically a trainer which had been pimped to fill a gap... Just saying

Correct, If you don't get charged VAT it's just HMRC being incompetent or the shipper being illegal....

Wow, big update, the old flight model was rather "wooden". This update will obviously change things, may even tempt me back to give it another go

Rather than a brand new map, I'd rather see some way of linking the Persian Gulf with Syria

I loved the reapers for a while, they've lost me now though with all the Could... and How... stuff, totally unrealistic. It seems to create more hits though, unfortunately to be expected when monetarization is involved.... can't blame him.

After 10 - 60 minutes the rudder becomes unresponsive, pedals in cockpit do not move, rudder does not move. Rudder hardware is Thrustmaster TPR rudder. Track file too big to attach, log attached. dcs.log

Other aircraft modules have this kind of INU shortcut, I can't see why the KA-50 can't also have one. I'm all for realism but this is a simulator after all, please let us just fly the thing without having to worry about INU drift.

I really don't understand why anybody would say no to DLSS... DLSS is available on all RTX nvidia cards which have become the norm nowadays obviously excluding AMD. The performance uplift can be substantial as demonstrated by MSFS 2020's latest release. It's the biggest increase in performance I've seen in any game without having to drop thousands on a new graphics card.

20+ years of IT experience has taught me that the Friday release ban relates to not wanting a production outage or major issue over the weekend and not having people available to fix it... That isn't the case with DCS, people can always roll back, it's a beta, get it out there when you think you're done, waiting over the weekend isn't going to achieve anything...

I'd much rather have a tested good quality release later than a buggy release earlier... said everyone... always

Thanks, that explains it, the HUD is indicating CAS

I noticed while doing a nav exercise that ATC hold doesn't hold speed over a long period of time, the speed gradually decreases, by the end of a 30 minute leg I've lost 5 knots. This is a bit of a pain for TOT calculations and navigation. Is this a bug or is it intended? I can't see how it could be anything but a bug. Method: 1. Set ATC at 420 kts 2. Engage BALT and CPL AP modes 3. Jet holds 420 4. Change pitch in order to force increase or decrease in speed > return to level flight (ATC remains engaged, not flashing) Expected result: ATC alters throttle to resume 420 Kts Actual result: ATC fails to target 420 kts, throttle does not move, ATC remains at the lowest speed reached during the pitch maneuver ATC_test.miz.zip

From Reddit, Field changed to target elevation, it's the same thing... basically you need to "Do math" " If you know the target elevation, add the elevation MSL/1000 to the QFE value, to give you the proper elevation setting for your altimeter. Thus, at Nellis, if ATC told you 27.88 QFE.... take the target elevation of 1869, divide by 1000, and add it to the QFE. Giving you 27.88 + 1.87 = 29.75" Hg.Then take your current altimeter reading and subtract your known target elevation to get AGL. EDIT: No one in civilian aviation uses QFE anymore, the problem is at elevation levels above 2000' you often can't set you altimeter to what would be the QFE. it's all QNH which is sea level pressure accounting for regional pressure differences. I think some military's still use QFE when they can.

Same thing happens to me, even when I use the F1 view to start autostart and then switch to F2 or any other external view.

Hi all, Has anyone created a video tutorial explicitly addressing Storing a Point from CPG LOS (TADS or HMD)? The manual has a flow for this but ether I'm an idiot or something is amiss, this is a whole lot more complex than doing essentially the same thing in the A10C and probably one of the most used functionalities for Ad Hoc targeting.

Someone on a Facebook group asked if it was possible to land an F18 on a small strip on Pagan Island, as they tried and failed. Had to try and here are the results LOL

I do exactly the same