Dudikoff

Yeah, but unless I'm mistaken, these could be patched up rather than re-downloaded every time they're modified. E.g. you generate diff files between the new and previous version and download only the diff files (if the local files are validated to match the required version, of course).

The patch is pretty huge so I presume when some terrain files are fixed, all the modified files are being re-downloaded? It seems rather inefficient, especially when there'll be more maps. Any chance of modifying the update procedure so that files are actually patched (and with generated diff files being downloaded instead) rather than being fully re-downloaded all over again?

F-5E has rather weak engines and thus acceleration, while the Su-24 was designed for supersonic low level air defense penetration so that's not surprising. It would go over Mach 2 at altitude if they kept the variable ramps.

Or its impending release which would arguably be a better way to mark the Red Army anniversary than some measly sale (at least from a perspective of someone who already owns the modules included ;) ).

Yeah, sorry, completely forgot about that; I was squarely looking at it from the A2G perspective.

I presume that the OP was saying that the throttle handle is not staying in place, but is physically inching slowly forward due to its weight (something I can attest to with the X65, but its grip is metal so its rather heavy).

I think this was already discussed and there wouldn't be any point to it. https://forums.eagle.ru/showpost.php?p=2866855&postcount=2

I'd have to agree here. Using R-73's probably requires only a slight update to the WCS and the APU-73 launch rails, while it would make the MiG-21bis more flexible in modern scenarios.

Looking forward to seeing the new look. Are there any updates of the SST software planned perhaps? Like, adding some new functionality, like e.g. a Tempo option or an option to iterate through a set of assigned commands with each button press? It's a shame that X65 is discontinued, though.

I think they lacked the digital bus so they weren't completely on the same level. But, either way, that was the upgraded F-14A with LTS support added (so, 1996+) and HB specifically stated that the F-14A they're doing will be a mid 80's standard, IIRC.

As an SST user, it sounds like you haven't cleared the default assignments which block the SST profile from working (the same goes for TM Target IIRC). Go to the controls setup screen for the particular plane, select any field in the Saitek X56 column and select 'clear category' option to remove all the X56 button assignments and then give it another go.

In general, I don't think so. I mean, all you can do is divide the axis into bands for triggering some key combination depending on the position. So, if a module had some radio select rotary control and a single PTT button, it would work, but if not, in general, you'd need some scripting support and the SST doesn't provide any of that, unfortunately. At the very least, I wish they included the tempo option in the SST (for long presses) and the ability to toggle through a defined set of commands with each press.

That depends on the timeframe, but I mean, if they're making the LTS-pod capable B, at the very minimum there's the pod itself to be made, the new display (?), the LTS control box with the controller stick, various A2G weapons that need to be supported, etc. Not sure how correct this list is: "The F-14B is either a remanufactured F-14A or new production aircraft, both equipped with F110-GE-400 engines, which replaced the TF30-P-414A engines. The F110-GE-400 is a new design which emphasizes reliability, maintainability, and operability. The new high technology engine improves capability and maneuverability without throttle restrictions or engine trimming. Sixty-seven F-14B Aircraft are being modified to extend the service life of the airframes and improve the offensive and defensive posture of the platform. This includes the F110-GE-400 engine, Fatigue Engine Monitoring System, AN/ALR-67 Countermeasure Warning and Control System, Gun Gas Purge Door Engineering Change Proposal (ECP), Direct Lift Control/Approach Power Compensator ECP, AN/AWG-15F ECP, and Engine Door Tension Fittings ECP. In addition, the AN/ASN-92 Carrier Aircraft Inertial Navigation System (CAINS) I will be replaced with the Embedded GPS Inertial (EGI) Navigation System. The F-14B Upgrade includes a MIL-STD-1553B Digital Multiplex Data Bus (DMDB), Programmable Multi-Display Indicator Group (PMDIG), PTID, the AN/AWG-15H Fire Control System, AN/ALR-67D(V)2 Radar Warning Receiver, EGI, and Mission Data Loader. Other survivability improvements were developed under the F-14 Airframe Change Number 828, Multi-Mission Capability Upgrade. The modified F-14B Aircraft is referred to as the F-14B Upgrade; modifications will be completed in FY01."

It's somewhat surprising that the F-14B gets released first, given the extra work with the LTS pod and integration of A2G weapons. It would seem easier to release the F-14A first and then release the A2G stuff later, kinda like they're doing with the Hornet. I'm not complaining, though ;)

Yeah, I'll second that, a shame it's OOP as it was their best stick and the force-sensing worked pretty well for me (love the instant centering when you release the stick compared with e.g. a TM Cougar with the NXT gimbal). I did also use the Saitek X-36 USB when it came out ages ago and that one was pretty good for the time and the price. X52 Pro was a decent stick, IMHO; my main gripe was that they cheaped out on the potentiometers (they were spiking) and the pointing stick (which was off center by default); both needed generous deadzones added to be usable. Haven't tried the X56/X65 which were like cheaper versions of the X65f design which I already bought used so it made no sense to get them.

Well, it sounds like the default in-game axis assignments are not matching the TUSBA R1 ones. So, you have to manually reassign the axis in the game controller options for each plane (just modify it once and export the controller mapping for the TUSBA device and then import it for other planes).

You mean the registry entry or the default installation location (e.g. Program Files\Eagle Dynamics\DCS World 2 Open Alpha)?

Thanks. So, you have no framerate issues with using DS together with MSAA 4x at 4K?

Same here (with deferred shading off). Did somebody try to delete the shader cache in Saved Games folder that was mentioned in another thread? I can only try that later in the evening. Also, VSync doesn't seem to work for me in 2.5 (it did in 2.2) - the FPS goes over 60 on my 60 Hz screen. I did delete the options.lua file, but now I'm considering to remove the entire user folder for the OB. Looks pretty good. Which AA settings are you using with the DS on?

Might be that AI routines would need to be adjusted somehow to track trees now, so this is a (temporary?) workaround.

I don't see why not. I've deleted mine and the 2.2 one already manually.

You're comparing it with 1.5.8 OpenBeta or 2.2 OpenAlpha? If the former, it's not really comparable since the graphics engine and the terrain data is completely different in 2.2/2.5 so it will naturally increase the RAM usage compared to the obsolete 1.5.8.

Yeah, I had the same issue as I migrated to a new laptop so the drive name changed and I didn't add the necessary registry entries before running the updater. I did cancel the update and added them, but the installer still didn't seem to have been able to find the other installations. Can somebody please post a screenshot of how their registry data entry for their DCS World 2 Open Alpha installation looks like? Path, Version and those other params? Since I moved to a new computer, I had NONE of those entries and I've seen some examples with underscores instead of spaces so I'm not sure of the correct format. Redownloading the whole of Nevada terrain was a big no-no for my current Internet speed so I tried to copy the files manually. Basically, once you start and cancel the download of the new terrain, there should be a _downloads folder (inside DCS World OpenBeta folder) and inside it there should be a mods folder containing download folders for aircraft, campaigns and terrains (basically the same structure as the mods folder in the main game folder). Basically, you can just copy the Nevada folder directly from the OpenAlpha mods/terrain/ folder and also the relevant aircraft and campaign folders that you're missing. Then restart the updater and it will check for already downloaded files by scanning through these folders. This will greatly reduce the required download size (e.g. I still have to download around 2.7 GB, but that's better than 37+ GB it was asking for before the manual copying of the aircraft and terrain files).

Hmm, I just remembered that I moved to a new computer and that I probably don't have the needed registry entries. I need to sort this out before adding Nevada I guess.

Good point, converting the installation to an open beta branch should work.