Dudikoff

Good question.

On the contrary, I would say subscription is the worst option as you pay for something regardless whether you use it or not and there are no guarantees that you will actually get more content that way. If necessary, I'd rather pay for large base game upgrades as they become available (kind of like Steel Beasts charges) or for various asset packs (like for DCS WWII), but I will not pay a monthly subscription fee to be able to play the game. There's a reason why all the MMO games abandoned this model (people weren't willing to pay for it anymore).

Yeah, you're right. I've edited my post after checking it and before I saw your answer. The front page is showing $799, but the price is actually $899.

Good question. Thought it was re-opened as the main page says $799, but adding it to the cart, it's $899. Maybe they're waiting for an actual review to be posted (and not just unboxing videos)?

Given that you're saving for the 2070 Super, you could have saved 40-50 EUR by going with Ryzen 3600 and another 70-90 by going with 16 GB of RAM. I can't say for MP, but for SP, the 32 GB of RAM won't make any difference. Not saying you've made a mistake, just that you could have gotten the 2070 Super a bit sooner and added more RAM much later on.

That looks pretty neat, thanks for sharing. I'll have to try it out once I get back to Ka-50 (I guess when they update the cockpit).

Sorry, I wasn't criticizing, just stating my impressions from the stream to point out that this approach certainly has its advantages. Nothing wrong with not reading a manual; it might take longer, but at least you learn something.

Hmm, good point, haven't thought of that as I so wanted it to be used for something else in other modules. Nice attention to detail. I see from the manual that the adjustment I mentioned was for some middle detent or something. It also mentions not to adjust it with too many turns at a time to avoid damage, so better left alone I guess.

The OP mentions Phoenix missiles, so unless he was recreating scenes from Final Countdown, I'd presume it's for all.

Yeah, I saw that in the video, but then I don't understand why it also has an axis sensor if it can't be re-purposed? The image above shows some other adjustment which might be connected to this (i.e. "THRUST LEVER NEUTRAL XXXX TENSION" OFF / ON)? Not sure if Jabbers perhaps was too eager to show of the system as soon as possible or perhaps he didn't really prepare for it intentionally (e.g. to provide a realistic unboxing demonstration of the issues a customer might encounter while assembling the system), but whatever the reason it definitely ended up being useful for everyone.

Pardon my ignorance, but seeing the big discrepancy makes me wonder if there's really a need to have a separate HB AIM-7M anyway if ED basically has one already? Especially since it's a PD missile, so e.g. HB doesn't need its own model so it can support specifics of CW guidance as well (like e.g. the F variant needs to I guess). I'd assume that the differences between the AIM-7MH and AIM-7M are pretty minor and could be easily adjusted via some missile parameters if necessary. It could be tied to those Speed Gate switch options, but I'm not sure if that's functional in the game anyway?

From what I've seen in the video (and I only saw parts of it), it's visible in the Windows Device screen so it could be mapped to anything in theory. The real question is if it can be decoupled from controlling the friction control (in the software/drivers?) so you can use it as an axis, while you can set the throttle friction to some fixed value. Or is it perhaps setting the friction mechanically when being moved around (i.e. the friction lever is physically adjusting the friction of the throttle lever)?

I was adding RIO controls option to my Target profile and was surprised to find that the station select switches cannot be mapped as they're not provided in the controls!? Also, I don't see VSL OFF position? It's already annoying enough that no module assigns default keyboard mappings for all the controls, but to have missing controls six months from release is somewhat surprising. Also, it's quite standard for rotary encoders to have an option to turn them forward and back between their initial and final position. That would be very helpful, rather than having to map a key for each position and then write special Target functions to navigate through them using forward and back controls. Finally, I guess the two position switches should also have a toggle variant to swap between the two positions. For the three or more position switches, it would be nice to have two controls which push them up or down through their positions (kind of like encoders). The if else options provided in the controls are only helpful for real three position switches where the command is pressed and held. Are these binding suggestions taken into consideration at all? I see the first post has collected quite a set of suggestions.

I see, but again, to be fair, it took them six months of relatively silent work on these features so they can announce what they've been working on and what might get released in the following months (hope things work out as they planned them out, but that remains to be seen). I'm sure one could write a similar complaint to HB on the Viggen updates as the Tomcat has gotten the priority. Meanwhile, ED released another module during the same period which obviously delayed further Hornet updates. Not an ideal situation from a Hornet owner's perspective, but I'm sure they had their reasons (like e.g. paying the bills or simply bringing the most wanted module to the masses as early as possible). The point is, with limited resources to go around, they have to make some choices which means that some module owners will always have to wait for their turn. Patience and realistic expectations are the key here, I guess.

HB? That's a strange choice of an example as IIRC they were more or less silent since the release regarding the remaining major features till few days ago. Plus, the Tomcat was delayed quite a few times as it was initially announced to be released in 2017 (granted, it came with most of the features covered, but it also doesn't have an A2G radar and guided weapons which have to be made from scratch here). Not trying to disrespect HB here, just wanted to point out that I don't quite agree with the given argumentation. As regards to exact roadmap with planned dates, they've probably been burned before over the course of all these modules to know better than to give any dates they're not sure about.

Edit: Never mind, was reading the old web manual.

Hmm, in my account it's A-10C, BS2, FC3, Nevada and MiG-21. Mi-8 and Gazelle are 'keyless'. Kind of surprising that some ED modules are still using Starforce.

Looking at that, RAM change is 6 points, but it's not cumulative. In any case, I don't think activations are used anymore. They've moved away from StarForce to some other system where the serial numbers are linked to your DCS user account. Not absolutely sure if all the modules have been migrated by now, but I'd expect so.

I have to note that while it might have the same HAL effect sensor measuring the axis positions, the gimbal itself, while itself not a high quality one on the Warthog, presumably has a much better handling. E.g. I have the older T16000 stick (the non HOTAS edition) that I use for old space sims and I find it too stiff to control precisely around the center area making slight aim adjustments needlessly hard as I keep overcompensating. I kind of remember that the X52 Pro felt much easier around the center (though it's gimbal design was bad) though it was a long time ago and I gave it away so can't try it out again.

Laptops are not as cost effective or as powerful or as quiet as desktops, but if you need portability, they can do fine depending on the configuration and your needs. E.g. I'm playing DCS on a laptop with a 1080 card on a 4K external monitor and it does pretty well.

Sure, go with 5. 3600 is a best buy, I guess.

2080 is not really an upgrade on the 1080Ti performance wise, except that it has RTX and DLSS support (both features probably useless for DCS) and 2080 Super is only slightly faster than 2080. 2080Ti would be noticeably faster, but it's way too expensive for what you get, IMHO. So, it really depends on what deals you can find. A used 1080Ti/2080/2080 Super still under warranty would be a best buy, I guess.

Is it? Without trying it out in the sim, I'd expect Mil marks the max dry thrust position and anything above that is afterburner, while Max shows the maximum afterburner (and thus throttle movement) position.

Yeah, that's true, especially since Intel switched to hexa core i7's as pretty much standard in laptops. They still offer the i5 quad core, but it can be usually found only in the lowest configurations. I'm sure that one would fare noticeably better regarding temperature and noise in not too thin laptops compared to hexa core i7. For example, a thin and light Gigabyte Aero 15 used to have a quad core i7 7700HQ and a 1060 GPU and on one review site the average noise while gaming was in the low 40's (like 42 dBA IIRC which is a pretty good value). Later came an upgrade to hexa core i7 8750h (with the same GPU) and the average noise while gaming jumped to 50dBA (or a bit more) which is rather loud. AMD surprisingly (even if those mobile CPU's are the older gen on 12nm) heats much less currently (even in quad core ULV CPU's where AMD 3500u or 3700u CPU's keep much higher clocks under load than Intel 8-series ULV CPU's, while having much lower temps). The Intel CPU's have an advantage in single-core performance, though, especially since these are not the latest AMD tech, but it shouldn't make a big difference (though it would be more noticeable than with a stronger GPU, I think). Edit: Found a comparison here for FX505 with Intel i5 and AMD 3750h: https://laptopmedia.com/review/asus-tuf-fx505-review-fresh-but-still-not-fully-polished/ Apparently, even the quad i5 config reaches high temperatures at around 90 degrees even when clocks drop down to around 3.0, while AMD drops down to higher 3.4 clock with the temps somewhat under 70 degrees. Not sure how high the CPU load is in DCS with a mid range GPU card, but I guess it might be higher than with a higher range GPU and with lower details if the FPS is not limited so these higher temperatures with Intel might be a problem (at least regarding noise) on this model.

Thanks for the effort, seems like a pretty nice product, especially since aftermarket detents can be added. https://forums.eagle.ru/showthread.php?t=249484 The demonstration of different backlight colors for different modes was quite effective. I suppose that subsequently, each momentary toggle switch can change its own color to indicate the last pushed setting (i.e. up or down)?