Dudikoff

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.

Yeah, can't believe everybody fell for it when the actual release is tomorrow. Move along folks, nothing to downl.. err, see here. ;)

If you have DCS Open Beta installed, you can run the update now. If you don't, ED said that a separate DCS Open Beta installer will be released one day after.

It's downloading now :) (roughly 14 GB)

Yay, I presumed it will be coming today once I've seen the changelog posted, but it's nice to see an official confirmation.

Good question as I was just wondering myself if symbolic links would work with e.g. maps; i.e. with the future stable and open beta 2.5 releases, all the maps would have two copies even though I presume they won't differ between these two installations.

And I'd love to buy another Cougar stick base for the FSSB mod.

Yeah, I saw some screenshots and it looked pretty nice (didn't know it also has the bootloader options and all that as it requires a VKB joystick for it to load up and I only have pedals for the time being), hence why I mentioned that it might be a step in the right direction. I would still prefer if it was a part of download packages from a website where you'd select your device and it will give you the latest software for it (which would contain e.g. the zbootloader application). Likewise, I've noticed my TinyBox for the Mk.III's was still stuck on that same 2016 firmware as it's the only option on the ftp server. And, since my pedals didn't work with the new Windows 10 installation for some reason (got haywire outputs on X, Y and Z axis somehow) and the VkbDevCfg was complaining about the old firmware present, I decided to try and update it. After some google search, I've managed to dig the location where the latest BETA firmware options were available (some shared cloud folders) from some random forum topic. Out of those three firmware options there, one would fail to upload to the TinyBox for some reason, so I ended uploading the latest marked with 'B' which I presume is 'Beta'. The pedals gave zero output with that one so I shuffled between several versions back and forth trying to get a single axis to work properly, then played with various checkboxes on the Axis list, all to no avail. Finally, I've read that after installing the MCG grip on the base, it should be followed by uploading the default settings for it, so I tried that with my pedals and it worked, even with the latest beta firmware (actually finding the default option that everyone talks about in the VkbDevCfg was another story altogether). Hope I don't forget the basics again in like a year or so when I need to update something again. BTW, when is the MCG-TM scheduled for release? Were there any updates on those?

I'm curious if there are any plans to rework the VKB software distribution? I mean, I only have the simple VKB T-Rudder pedals at the moment and it can be a drag to deal with the current software as is. Some of the gripes: - the required software is not available as a package, but as a bunch of separate mini-applications with cryptic names - the required software is downloaded from the FTP(!!) server which has to be manually traversed in search of the required application, while the latest beta stuff is shared on some cloud storage - one needs to manually check the dates or version numbers to get the latest version, but there's no way of knowing for sure which version of the applications mutually support each other or the firmware version - the procedures are not unified and are spread across several applications (e.g. to upload a firmware, one needs to run VkbDevCfg, navigate through its many illogical tabs to find the bootloader button, then run a separate app to install the firmware, then back to VkbDevCfg to find a default button on a different tab, then back to a different tab to upload the default settings to the device via a Set button) - the VkbDevConfig is like an engineering test app and allows too many options that the user doesn't actually need (e.g. just for the t-rudder there's so many lines with various sensors and checkboxes and what not; I doubt 99% of the users really need any of this stuff) So, IMHO, VKB needs to make self-installing software packages (containing compatible application versions) which would also have a user-friendly all-encompassing app which would then perform user desired procedures (e.g. firmware update, calibration, axis and button test, technical support reports) in a user-friendly way by guiding him through the process and by running all the required substeps through various sub applications hidden from the user. Sorry for the rant and I presume that this was proposed already, but I had a problem yesterday updating the firmware on my rudders as I changed the computer so they didn't really work on the new Win 10 installation by default. Some of the latest beta firmware options wouldn't upload, some would show no response from the pedals while some would show the same crazy outputs from three axis even though the pedals have only one physical axis. If you don't deal with these things for e.g. six months or a year, it's easy to forget these non-intuitive procedures and then you're back to getting stuck if a problem occurs because the required procedures to find the latest apps and firmware and actually upload them are overtly complicated for the end user and the lack of some proper sticky threads on the support forums explaining the basic procedures doesn't help much (though there is a sticky requiring the user to obtain and navigate through different apps on its own and go through a bunch of diagnostic steps and screen grabs just to report a valid support request which actually prevented me from asking for help and forced me to further dig through threads on various forums in search for a solution). In the end, uploading the new default settings to the device compatible with the latest firmware solved it in the end, but this information had to be sourced by random search through some MCG support threads and just locating the ever-referenced default button (where the icon was hiding it more than making it more noticeable IMHO) was a needless pain. I can see it becoming ever so more complicated if I had the full VB set (stick and throttle) and had to play with the axis settings and button configurations, though the screenshots of this Wizzo app do look like a step towards more user friendly design.

Yes, that's what has been said. It's the same way the Open Alpha was released IIRC.

I don't see a problem here. You'll just download the new 2.5.0 Open Beta installer once it's released. Any older files to be reused will be copied from the 2.2.0 Open Alpha installation only, anyway.

That's actually a pretty sensible idea, especially given the large download the 2.5 will be. Besides, didn't ED say that they'll start releasing updates on Wednesday to give them time to patch up critical bugs before the weekend? BTW, please make it Wednesday, the 24th, not the 31st ;)

Yeah, good luck with that ;)

Ouch, was it already that long in development? Time really flies..

TBH, I was expecting an even higher price given all the new features and systems. My only disappointment is that it will be released at the end of Spring. It seems somewhat early to start the pre-purchase period now if the module is 4-5 months away from the release.

The point of G-Sync is to eliminate stuttering when the framerate drops below the refresh rate of the screen. What you're talking about is handled by either Adaptive V-Sync (which will enable V-Sync when the FPS hits the monitor refresh rate) or Fast Sync (somewhat different implementation to avoid the V-Sync induced lag, but requires a somewhat higher FPS rate to work properly IIRC).