Gliptal

Yep. If I were one and got offered a deal of sorts, I would really think twice after this.

Yes sorry, edited my previous post to better showcase my point of view on the matter.

There's no precedent. ED told Starway that his mod was going to be sold in their store as a sanctioned DLC, and made official announcements about the whole deal as well. They then backed out when DRM issues arised, leaving Starway with an year's worth of work for basically nothing. If ED had said nothing, this would be a mod just like any other. But seen how Starway more or less worked on something on ED's behalf (at least as far as we know), they should still pay him. Especially considering the whole thing failed because of a shortcoming from their end, and not Starway's. This is how things work with freelancer contracts in my country anyways.

Nice work.

Nice work!

It's probably an issue with the mission editor that seems to have surfaced in the latest Open Beta. We'll have to wait for a fix from ED.

Testing is underway, although we're encountering some issues with the AI and the current beta release braking some editor settings.

Actually, correct trimming procedure is to add trim while releasing pressure on the stick, not release and then trim. You shouldn't be flying with the trim.

The A-10C is quite easy to fly and trim. You could keep an orbit just with trim, although there really is no need to do so given the AP modes.

Are you on Open Beta by any chances?

I really feel there's something wrong here. I understand the concept of PIO, but there's way too much lag behind the rudder on the ground, and I also think there's something amiss with the tires' friction (which would explain why hitting the brakes on landing kicks you on one side of the runway).

Are there plans to add the tactical campaign as well? I just noticed the new campaign description has it removed from the list.

I know, but nonetheless with it off the plane starts swerving. With it on, it's much more stable.

Landing is the same. As soon as I hit the brakes, it swerves right, with no possibility whatosever of correcting it, even with full rudder. Quite an annoying bug I must say. Regarding takeoff, I found keeping the NWS on helps tremendously.

Yep, a new .cfg did the trick.

I tried, the updater wouldn't work.

I'd rather not. My connection is quite slow. Any official support available? LevelPulse, any chance you could send me your autoupdate.cfg file? Mine seems to be corrupted, and it may be what is holding the updater back. EDIT: I was right, the problem was a corrupted autoupdate.cfg file. I was sent one, modified a couple of the properties to match my installation, and ran a repair. I had to download a couple of DLCs, but it's still better than downloading the whole thing again.

Can't. DCSW now starts, but it won't let me log in (I click on the arrow but nothing happens) and it hangs at 12% when loading the module manager. DCS Updater is still broken.

I just now updated to 1.5.3.53108@openbeta using DCS_updater. The game autolaunched fine, but subsequent launches crash immediately. Logs\dcs.log is as follow: === Log opened UTC 2016-05-22 09:52:46 00000.000 INFO VFS: Using 'Saved Games': "C:\Users\affa\Saved Games" 00000.002 INFO DCS: DCS/1.5.3.53108 (x86_64; Windows/6.2.9200) 00000.002 INFO DCS: CPU cores: 4, System RAM: 8191 MB 00000.011 INFO EDCORE: (dDispatcher)enterToState_:0 00000.026 INFO Dispatcher: 2016/5/22 11:52 V1508170900 00000.058 INFO INPUT: Device created Keyboard 00000.060 INFO INPUT: Device created Saitek X52 Flight Control System {3012D900-4049-11e5-8001-444553540000} 00000.061 INFO INPUT: Joystick created[saitek X52 Flight Control System {3012D900-4049-11e5-8001-444553540000}], ForceFeedBack: no 00000.065 INFO INPUT: Device created Logitech RumblePad 2 USB {440AE2E0-92DD-11e5-8001-444553540000} 00000.066 INFO INPUT: Joystick created[Logitech RumblePad 2 USB {440AE2E0-92DD-11e5-8001-444553540000}], ForceFeedBack: no 00000.078 INFO INPUT: Device created Joystick - HOTAS Warthog {B261BDA0-6C58-11e5-8001-444553540000} 00000.078 INFO INPUT: Joystick created[Joystick - HOTAS Warthog {B261BDA0-6C58-11e5-8001-444553540000}], ForceFeedBack: no 00000.096 INFO INPUT: Device created Throttle - HOTAS Warthog {B2640790-6C58-11e5-8002-444553540000} 00000.097 INFO INPUT: Joystick created[Throttle - HOTAS Warthog {B2640790-6C58-11e5-8002-444553540000}], ForceFeedBack: no 00000.114 INFO INPUT: Device created Controller (Xbox 360 Wireless Receiver for Windows) {0F3BEBC0-3A2E-11e5-8008-444553540000} 00000.114 INFO INPUT: Joystick created[Controller (Xbox 360 Wireless Receiver for Windows) {0F3BEBC0-3A2E-11e5-8008-444553540000}], ForceFeedBack: no 00000.331 INFO SOUND: loaded 1084 sdefs from "sounds\sdef" 00000.400 INFO SOUND: Using driver: xaudio29 00000.436 INFO SOUND: XAudio2: channel layout: Headphones/Stereo 00000.436 INFO SOUND: Using SSE FTZ/DAZ mode. 00000.745 ALERT DCS: Error running Scripts/Database/db_main.lua: [string "./Mods/aircraft/M-2000C/entry.lua"]:70: attempt to index global 'M2KFM' (a nil value) I understand it's a M-2000C module problem, so tried to repair using DCS_updater. Whatever command I give though, the updater crashes with the following log: --- Log file: C:\Program Files (x86)\Games\Other\DCS World\autoupdate_log.txt === Log opened UTC 2016-05-22 09:53:52 INFO : DCS_Updater/2.6.16.58 (Windows NT 6.2.9200; Win64; en-GB) INFO : cmdline: "C:\Program Files (x86)\Games\Other\DCS World\bin\DCS_updater.exe" --apply repair STATUS: Initializing... INFO : basedir: C:\Program Files (x86)\Games\Other\DCS World\ ERROR: Can't parse config: JSON error: parse error: premature EOF (right here) ------^ INFO : Config contents: --- BEGIN --- INFO : Config contents: --- END --- ERROR: JSON error: parse error: premature EOF (right here) ------^ === Log closed.I already dowloaded a new copy of DCS_updater.exe from the official website. I'd rather not have to download all of DCS again.

You'll have to wait for Sabre for a definite answer, but as far as I know they have plans of adding it to the store as well.

Those are part of the old distribution method, that used compressed packages and a third part key system for activation. For a few months now the campaign is only available as official DLC on EDs store, with the old files still there only for legacy purposes.

Apparently that's how it is in the real aircraft.

4 minutes for a complete alignment. LGBs guidance kits use a bang-bang guidance method for mechanical and software semplicity. Problem is, it really uses up energy.

My advice is to first of all learn the startup procedure, since it will get you acquainted with the cockpit amd most of the systems.

CDU systems wise, AAR for flying. The concepts of SPI and SOI are often misunderstood as well, so make sure you get those right from the start.