m4ti140

Hi, not sure if this is 2.5 related, so I won't mark it as such, but the winds reported in the briefings seem to be reversed. Haven't got to mission 3 yet but in the first two all winds are westerly and the active runway at Kobuleti is 25, even though the wind reports are easterly and the flightplan is set up as if the 07 was active.

For me the problem is more serious, since the second flight flies into ME every single time I try to fly this mission. Is there any way to just skip it?

I've seen people report as much as 23GB of memory used. Why is 8GB listed as minimum and 16GB as recommended if people with 32GB are already running short on memory? Is this intended, or are there still unplugged memory leaks in 2.5?

I'm out (Matroshka), you can jump in my place Kraut.

Matroshka Poland unaffiliated MiG-21 EDIT: Cross me out.

The antenna elevation knob is that cylindrical thing aft of radar stick. It's not animated though (neither is the radar stick itself), so I don't think it'll be of much help :(

I meant as an axis, like you did with lights.

Hi, would it be possible to add an antenna altitude axis this way?

One thing I noticed is that all ships in the task group will slow down to the max speed of the slowest vessel in the group, so you might want to remove any supply ships from the group. Also I can confirm that the AI seems to leave the ramp at 130-135 kph from the front stations regardless of the conditions.

I'm pretty sure GNS-430 supports GLONASS

F-86, mission 4 - as soon as I roll out of the hangar the ATC screams at me to hold position. There's a truck in front of the Yak on the taxiway and using "Abort takeoff" option doesn't make it move. EDIT: The truck clears eventually but the Yak still holds short of the runway perpetualy, even after I abort takeoff.

Since when does the Fishbed need ground power to start?

I don't think setting the Three Kings (ctrl-shift-esc is a shortcut for task manager on most systems) as a default hotkey for the overlay is a good idea

Hi, I wanted to use my mouse in conjunction with the X52 throttle thumbstick/ministick/nipple/mouse stick/watchmacallit as slew sensor (when out of clickable cockpit mode) but after assigning mouse_x/y axes to those inputs and testing in game I noticed that they do not work at all (even thoigh they seem to be working fine in other modules, like F-15C). I have to use keys/assign slew to a hat switch to slew instead. And it's not an issue with my hotas since the mouse proper gives the same results. Is this a known issue? I've seen a couple threads complaining about the slew sensor in Warthog (and therefore the regular "HOTAS slew axis") behaving strange but nobody mentioned the mouse slew axes being completely dead and utterly expired.

OMG it finally worked... I disconnected from the Internet booted up into safe mode as you suggested, nuked X52pro in device manager, removed the registry entries you mentioned (and a couple more - previously I only cleansed the HKEY_CURRENT_USER folder), removed Saitek programs, booted into normal mode, unplugged my joystick. Then I cleansed the registry again and manually deleted any file from my PC still related to Saitek (particularly in AppData and ProgramData folders for all users - I discovered a couple new config files that were not removed during uninstall in process) save for my profiles and the driver downloads (not the unpacked drivers). Then I unzipped the driver exes into downloads and ran the msi files for drivers and software from there, with administrator privileges. And boom, it finally worked. My bet is that it was either broken registry entries or one of the config files kept between reinstalls. I haven't reinstalled the Windows updates I removed back then yet, so it might still break. I will first make the profiles for all modules I own just in case :P. Thanks anyway, your post should be stickied somewere

What it says on the tin: I assigned the throttle ministick on my X52pro to TDC Slew (mouse) in order to use it as a slew sensor. It works correctly with the mavericks, but when bombing in CCRP mode the target designator only reacts to the horizontal axis. The slew keys are fine, the regular TDC slew axes are fine too, it's just the TDC slew (mouse) that is broken and only in CCRP mode.

ありがとうございます

OK, since this thread has been bumped anyway and I have a very similar issue with my X52pro now, I thought I'll post here: 3 days ago the Profile Editor just stopped working for me. I was setting up a profile for F-86F and I messed up when setting up bands for the throttle slider (I wanted to assign all 3 positions of airbrake switch to it without using advanced commands while also keeping it as an axis in a different mode - as a result I ended up with a perpetual "bbbbbbbb" input that wouldn't stop even after unplugging the stick :D) and I ended up hard resetting the PC (Windows 10 Pro x64, Creators update not installed yet). When it booted back up, the profile editor wouldn't start anymore: I can select existing profiles in the profiler and they work correctly but the profile editor doesn't even launch. At all. No matter if I start it from the profiler menu, from start, by directly accessing the exe (I even tried running it from the command line and slapping some bullshit parameters on to it hoping Saitek left any diagnostic stuff there). Nothing. I tired removing the software, drivers, even registry entries (not only those mentioned in this thread but everything related to Saitek) and installing everything from scratch (solving an issue with BSODs that I had due to originally installing the drivers while plugged into USB 3.0 in process), I added Profile Editor to exceptions in Windows Defender.... I even tried uninstalling recent windows updates (can't restore because Win 10 restore is broken and I lost my restore points). I even went through the bullshit copypasta I received from Saitek/Logi support that was not related to the issue I described and solved nothing. Nothing worked. Whatever I do I come to the same result: everything else works properly but the profile editor won't budge. It doesn't just crash right after launching, it does not launch at all, it never even shows up in processes in any form (nor does whatever it is supposed to launch). I can only edit profiles by manually editing the .pr0 files in notepad, which kinda sucks considering I have just bought the A-10C

This. Also the cold start mission gets stuck at one point (it doesn't tell you to turn the starter on or highlight it, there's just perpetual 'press space to continue'). It also misses the battery switch. Besides, both of these missions (but cold start in particular) need voiceover.

Does this apply to Steam version?

It is, a guy in another thread has interviewed a retired Fishbed driver who confirmed the inertia coupling at r dot higher than 90 deg/s

I think a cool idea for a campaign would be to fly as an Abkhazian pilot in a fictional, Clancy style 2010-2011 scenario. I actually started doing some missions myself but my mission builder and scripting knowledge is limited. The idea is that you are a retired Soviet PVO pilot of Abkhazian descent, who owns a civilian MiG-21bis that he flies at airshows across Europe and Russia (the first mission would literally be an airshow in Krasnodar). One day you get contacted by a Russian FSB agent who tells you that they discovered that the Georgian government is preparing a surprise attack to regain control over the separatist republics with a secret NATO support (blah blah blah, something that would be a standard DCS campaign plot if it was, say, an Su-27 or Su-25T campaign) and they offer you to make your bird combat ready again and secretly ship you to Gudauta to fly for the forming Abkhazian Air Force. You then fly a series of introductory missions where there is no open conflict between any of the sides involved and you would need to find nonviolent resolution whenever confronted with Georgian/NATO aircraft. Once the war goes hot, you would be put into situations where you have to push your aircraft to the edge of its abilities and/or use it in situations it was not designed for (like Kh-66 attacks (field modification), intercepting a huge number of enemy aircraft alone forcing you to resort to guns and R-60 or flying missions at the edge of Fishbed's range). The plot would involve some political intrigue with Russia and NATO engaging in a proxy war through Abkhazia and Georgia respectively and alliances changing as the story progresses and the real motivations of each side are uncovered. For example, one scenario I had in mind (and started working on with limited success) would require you to fly a pair of Fishbeds at low altitude through a narrow corridor along the Georgian border to perform BARCAP over South Ossetia, while the Ossetian forces airlift cargo from Tskhinvali to a hidden base in the north. Crossing the border into Georgia or flying too far into the Russian territory would result in either VVS or French Air Force (not sure where I pulled the French from, guess I just wanted this scenario to involve a confrontation with M2000C in particular) intercepting your flight and forcing you to turn back, firing at you if you don't comply. Due to fuel limitations you would only carry a pair of R-60Ms for your armament. Once you get close to the SO territory the Mi-8s would launch from Tskhinvali, and shortly after a pair of M2000C would take off from Tbilisi to investigate. You would have a limited GCI support meaning that if you don't find them with your radar, you get a very short warning before it is to late to react. Your job would be to force them to turn back before they reach the hidden base/Mi-8 flights without resorting to violence (the French would have ROE not to engage unless fired upon, which at the least would force both aircraft into a merge instead of Fishbeds being blasted away with Supers). Ideally, the campaign would branch there depending on whether you manage to turn them back without violence, they reach and overfly the area of rebel activity or violence breaks out and either you or the French flight suffers losses - but there is only so much you can do with the campaign system in DCS.

Did you manage to fix it Wolverine? I have an exact same problem with a similar rig (960M and twice the ram)

GCI stands for Ground Controlled Interception, any form of interception supported by a ground controller with ground based radar information is GCI. Look it up on Wikipedia. What you're talking about is probably LAZUR and it wasn't automatic either.

This looks like glass being polarized, but that makes sense only for the HUD, not the whole canopy