Dudikoff

I'll play with the trim settings and compare how it influences the deflection, but if I had that much of deflection as your pictures show, I probably wouldn't be writing any of this. I was landing so the speed was relatively low and still when I checked from the side view, it would barely budge a bit over it's nominal position (which matches the hull extension for the stabilators) while I'm pushing the stick hard forward. At some points during the landing, it was basically impossible to bring the nose down at all. I'll try to get a screenshot next time I encounter this problem to compare. It appeared exactly the same as the deflection I had at higher speeds, but at lower speeds it felt a bit more responsive.

And the Su-25/27/33 that we also have in the game are not Soviet planes? Nonsense.

I'm no expert, but I don't see a direct explanation on why the plane gives only a few degrees of negative pitch deflection on the horizontal stabilators. There's this line: IAS and altitude dependant gear ratio from the stick to stabilator;, but I've experienced the same limits at different speed and altitudes.

Well, it's moving perhaps 1-2 degrees, certainly not 15 as it should, if I understood correctly.

Oh, so it should go into the user files, rather than the main game folder? My mistake then, but I didn't see any installation instructions. Edit: Yeah, it works now. I can see some items on the left of the MiG in the first training mission. Sorry for the false alarm.

Hmm, I downloaded the VPC mod from your link, but can't seem to get it to run (installed with OvGME). I see the following error in the log file: 2018-10-14 13:25:07.470 INFO Scripting: plugin: SKIPPED 'VPC Object by voc & virpil.com': not authorized Not sure if it's related to this error some lines above it: 2018-10-14 13:25:05.965 ERROR SECURITYCONTROL: Failed to parse manifest: mods/tech/main/dcs_manifest.x86_64 as there's no manifest file in that folder, but it is the folder where the VPC mod copies its files.

There are some TCS shots on the TID in this video and though the video is of poor quality, the screen does seem quite capable as you said. Then I guess the main problem would be converting the digital bus output from the LTS pod into the analogue video signal compatible with the TID screen. The question is whether this was done in 1995 or they used the PTID screens straight up?

Was there any conclusion on the very limited negative-g pitch level available? The horizontal control surfaces seem to have only a slightest deflection possible in that direction. I find that and the throttle behavior (with that huge dead-zone) rather frustrating.

The IRST scan zone in the Su-27/33 is also adjustable vertically, while the one in the MiG-29 is fixed.

Well, yes and no. When the LTS pod was introduced operationally, it was used with the PTID display, but HB are simulating some supposed test variant where the LTS pod picture was shown on the TID screen (the bowl). These tests were done in 1995. I say supposed, because I don't remember seeing any unambiguous proof that the TID display was used there or even being capable of this.

Garbage, I guess. Where it belonged to in the first place apparently.

Since MCG Pro and TM Warthog grips differ in the number of available buttons, hats, etc. I doubt changing the profile only would be enough.

Only on the F-14D. https://forums.eagle.ru/showthread.php?t=175840

I've checked my Hornet user added keyboard assignments (so I can map e.g. MFD OSB buttons to my MFD's in Target) and they're defined in lua diff files in the user section and it seems they're still there and visible in the game.

Speaking of missions, does this line from the weekend news post mean that a new campaign will be added? "Includes instant action, single missions, and a campaign."

You don't have it if you didn't buy or force install the module.

I've checked the provided quickstart.lua yesterday, but it didn't contain the files that were shared so I had to add them manually.

Well, there are some Cold Start/Free Flight A/G/S instant missions that come as part of the MiG-29 module and there are some combat instant missions provided by NineLine in the OP (which I presume were accidentally left out from the module). If either are copied to the FC3 Missions/Quickstart folder, the quickstart.lua file in the same folder also needs to be updated to include them and then they will show up. I guess they'll sort this up in the next update, at least for the MiG-29.

Well, you could write some key points, I'm sure no-one would mind. IMHO, the carrier has a limited range, limited stores and aircraft complement and without the catapult, it can't launch its aircraft with full payload, nor can it provide tanker and proper AWACS support (unless you want to consider those Kh-31's which never entered service as such). It's advanced radar system (which I guess was meant to offset the AWACS limitation) also doesn't work IIRC. Well, they call them cruisers, but not necessarily because they truly consider them as such. The actual reasons could be of ideological (being offensive weapons) and also of practical nature (being forbidden to cross the Turkish straits otherwise which is kind of a problem when the shipyard capable of making them was there in the Black Sea). Sure, they added a sonar suite to them and a small complement of powerful anti-ship missiles, but those missiles only take valuable hangar space, while the limited number makes them more like a self-defense weapon against NATO ships, rather than an offensive weapon. I guess they had to install them not because they needed cruisers, but because their air complements lacked both range and anti-ship missile capabilities, which kind of defeats the purpose of having a proper aircraft carrier in the first place. That's why I mentioned that it's relatively realistic primary mission was to provide air cover (and of course the anti-submarine cover against NATO HK subs as you said which I didn't mention as we were discussing Su-33's) to their ballistic subs in the Barents Sea, certainly not duking it out with a US carrier group (I guess Backfires were in charge of keeping those away from the Barents Sea). Well, you can spin that differently - if it was a priority to have something, they wouldn't have put it in the serial production without one. And Pastel would presumably require a different display (e.g. an MFD?), which the Su-33 doesn't have. There could be other reasons like extra weight for a perhaps unnecessary or even somewhat outdated system at the time (mid 80's). Also, the original Su-27 SPO-15 installation couldn't have been simply reused because they had to mount the canards there. And I guess installing such things in new locations requires a lot of testing and adjustments to avoid interference, etc. which costs time and money, hence why I assumed it might not have been a priority. The parallel with the F-14 was that both services kind of had to fight the budgets so they often had to make do with what they had. E.g. the TF-30 engines were supposed to be interim, but they got stuck with them for almost 20 years. Same with the RWR upgrades (a capable RWR suite only became necessary when the Bombcat role became a thing and they would have to fly over land strike missions) and later weapon upgrades (e.g. had to scrap the AMRAAM integration to use the funds for LANTIRN, Harpoon and HARM missiles weren't integrated, though they were tested successfully, etc.). Of course it's not really fair to compare them as US Navy had a defined role and much more funds at its disposal, but I presumed that there could be some doctrinal similarities with their interceptors over sea not having the RWR suite as a priority.

Great, thanks.

Most of the people are probably on Open Beta. The update which supports the MiG-29 is "DCS 2.5.3.22652 Open Beta" as written in the official update post, so it's not supported by the stable branch yet.

The standalone modules and FC3 quickstart missions are a complete mess. It took me a better part of two hours to force install all the standalone modules and browse through the mission folders and copy all the missing quickstart missions and add them to the lua file. The mission files don't have consistent naming, some modules don't have missions for all the maps, some files use the Persian Gulf naming, some Straight of Hormuz, etc. It would be nice if ED could sort this mess out when they are fixing the missing MiG-29 quickstart missions.

Speaking of speed, I was playing one of the quickstart missions (I think the MiG-29S Intercept) and suddenly the velocity meter died and had a red flag over it. Are there some random failures in these missions or there is it possible to damage the pitot tube somehow or perhaps it can freeze in certain conditions? Just not sure what happened there.

Yeah, an add-on carrier DLC, OK. But, carrier ground support vehicles should come with said carriers.

It's a thread about MiG-29 quickstart (instant) missions, so, no, these are not the missions we are looking for.