Rongor

I use a different approach without fiddling around with the CDU by using the TAD. Precondition: You have to have something hooked in the TAD to enable cursor data display in the lower display area. I assume the TAD being SOI. After receiving bullseye data, use OSB 18 to switch to BULLS/CURSOR to receive a bullseye coordinates readout for the cursor position (if not set already). Then steer the cursor to the called out coordinates. After that I press TMS right short which creates a markpoint at that position. Now I simply do another TMS up short, which now hooks that new markpoint (as the cursor will still rest on that location). Now you can press OSB17 and create a waypoint on that markpoint location. Done! If you turn the dial on the CDU to markpoint, you can also omit that OSB17 step entirely and simply use the markpoint as steerpoint. That would reduce workload after setting TAD as SOI to navigating the cursor to the bullseye coordinates and a single TMS up right. I absolutely agree these workflows are very much personal taste, but I find my way to be quicker for me. Also it keeps me able to do it both ways. I can easily tell bullseye coordinates of other found targets I "stored" on my TAD, which wouldn't be possible by that CDU usage at the same amount of steps.

Since about two years their announcements sound like EDGE and stuff is waiting right behind the corner so newsletters like this one - so appealing they might be - don't impress me anymore. Finally release something, THEN I can be happy (maybe)...

So you did 2 different downloads. One download had corrupted files, the other didn't. So this is in any way evidence for a technically weird statement? The "harm" done is the confusion you spread by claiming any connection between your successful second download and your use of two different downloaders. Your simple judgement to bear the second downloader "better" than the first one is in no way justified by this. Downloaders aren't responsible for corrupted data streaming aboard your computer.

These are two different statements. Corruption of files is not the fault of your download tool. Its job is to download stuff, not to verify its integrity. Files may be corrupted, but your downloader didn't lie when tellling you it completed the download.

This is impossible. If you downloaded from ED and ran the installer, there is now way your installation was incorporated by Steam. The title "DCS World" may only appear in Steam if you started to install it using Steam at least one time in the past. By the way I have it also in my Steam library, although I didn't install it using Steam. That is because I added it to my Steam library as a non-steam-game. This doesn't mean I installed it there, it is a link only I start from the Steam GUI, to keep my Steam friends aware I started DCS.

If you have it in your steam library and don't want to have it installed there, simply right click onto the library line saying "DCS World", select "Delete local content" and exit steam. Then go ahead with installing your DCS World files you downloaded from ED.

I would try this "repair" option you have in your start menu

I think it is pretty obvious ED is already working at their limits of capacity so we don't really face a lack of ideas but a lack of capability on ED's side. Therefore your thoughts are nice but useless at this point. To answer your topic line, best they can do would be to finally finish their EDGE project, to eventually enable increased modability features and attract additional 3rd party developers.

To be a bit more precise, those front wheels which get steered are not really controlled by the rudder but by the pedals, which on the other hand also affect the rudders.

Guys, he solved it in post #4 ;)

as mentioned above and you can also send text messages.

Without explaining exactly what you did, it is hard to determine what the problem could be. Did you use external power? Did you move the fuel lever in the described way?

I wonder if the OP meanwhile misses his wife or if he managed to maintain that excitement...

Because you did read bs. Where did your read it? In the news? Simply look at your computer! Your DCS isn't linked to steam as long as you downloaded it at ED and did not install DCS World from Steam. Please don't be so vague when saying you "come to add in some aircraft I am finding I can't". Explain your situation exactly and people may help.

I am not sure what you mean with EWR alert. I suspect you speak of the EWR emissions appearing on the RWR. - Issuing some communications frequency will not prevent the EWR appearing on your RWR. - EWR do appear on RWR regardless of being friendly or foe - Currently it is impossible to get a (ground based) EWR working for any blue side unit, you will have to keep an AWACS airborne to guide blue side units towards contacts. EWR only works for red side forces. This bug isn't affected by the aircraft you chose. Also: You can't keep out FC3 aircraft out of "different" frequencies. They are desgined to receive everything which is transmitted by their own side forces, regardless the frequency.

This is no bug. You have to reload those 3 guns first, this is indicated by the red gun ready lights. If these are illuminated, and you flipped up the safety switch on your stick, guns will fire. Btw, this is very well documented on page 20 in the quickstart manual...

Georgia, blue side, has EWR. Currently not of any use, since blue side units refuse to communicate with EWR sites. There is no way to configure EWR sites in the ME to make them work. Setting appropriate frequencies and callsigns doesn't help. Pretty annoying. Blue side is forced to have an AWACS airborne right now, to get a picture.

Even if the Hawk site launched a missile, the track radar unit never turns to illuminate the target. The SAM functionality isn't affected, so this is a apparently a missing model animation only.

Can we agree that as long as the mission editor gives us free choice to intermix countries into those two opposing sides and as long as technically the radio of the aircraft and the set frequency of an EWR site are compatible, this should work regardless of anything else... It is bs and annyoing that blue side is forced to have an AWACS airborne instead of using a Georgian EWR (for example)...

1 - page 142 2 - page 292 - and your additional question: page 339 3 - page 407 defaults are saved in LUA files... 3 - \DCSWorld\Mods\aircraft\A-10C\Cockpit\Scripts\AN_ALE40V\device\AN_ALE40V_params.lua 2 - \DCSWorld\Mods\aircraft\A-10C\Cockpit\Scripts\TGP\TGP.lua 1 - in some file in these folders, \DCSWorld\Mods\aircraft\A-10C\Cockpit\Scripts (leaving some of the egg search for you)

1, 2, yes 3, yes

Helmet sounds should also get onto the comms output. Not possible, I know...

All things considered, I always perceived the Ka-50 to be something experimental, a model which never really got introduced in large numbers. A completely real simulation would see more Ka-52. I wouldn't have a problem with giving up ABRIS, but of course it makes no sense to withdraw a feature. I think ED's development of the Black Shark has ceased anyway. I don't think they will ever touch it again.

I want to have these on the Mi-8 too then!

There currently is no fix for issue #2.