Eldur

Hope he didn't go into Veeeee Orre too much and got cracked across the head with a baseball bat 30 or 40 times a minute by a [REDACTED] psychopath hiding in the back of his plane.

Great idea to have such a chart, but with those colors against a white blackground with very little contrast, it's practically illegible.

14 hours to go on my end... Sounds great, looking forward to your feedback on it

I can imagine the Raduga sight is rendered like an MFD, so it's bound to the cockpit display setting and restrictions. I mean it also has to work in VR somehow and probably will do just alike with TIR as well. The full screen scope then is just a convenience thing for pancake pilots Well, I guess that's not the two weeks™ kind of soon there

The last time I was this early, the Hind still had the YakB turret only

Agreed. It's literally that one plane worth getting even if it's not on sale. BTW had a giggle at that saloon thing as well, but I totally understood what was meant. I like it when such bloopers happen, it even seemed like a well placed joke there. It's perfectly fine to not be perfect at things

Now you got me interested. Does that thing actually work already with DCS? I remember reading it wouldn't just a few years ago. I'd like to replace my trusty MS SW FFB2 at some point, but there's literally no alternatives (the G940 I tried, also ages ago already, was crap) and with that price tag the Brunner better be good. I mean, I'd expect it to make use of the FFB commands that DCS shells out... if it does, I'd have something (next to a new rig tho) to save up for and my TMWH stick might actually end up not collecting dust anymore...

It is where ponies are literally jailed. So nothing for me. I prefer Open Clear Skies... and Open Beta Innit? I mean they never called the FC3 thing Su-27S officially even though (or I didn't see it) that's the one we've always had... anyway, we've had that highlighting of existing FC3 modules as single things in newsletters more than once in the past. That article could be better, it doesn't even mention a Su-27S, just the T-10S prototype. The German one says it's basically the same as the Su-27P (where the P usually is omitted) which was the initial interceptor/fighter variant, but with added capabilities for unguided bombs and rockets, entering service in 1985. I think the main source of that article is Andy Gröning: Su-27. Motorbuch, Stuttgart 2017, ISBN 978-3-613-03951-3.

Send me the monitor capable of that, or better or a Reverb G2 for free and I certainly will BTW when using my Quest instead of CV1, my frames literally cut in halves, but GPU load in GPU-Z roughly stays the same... Well, I had everything at the bare minimum/off and cranked individual setting up from there to see what makes a difference. I basically ended up leaving Civ Traffic at either low or off, and, of course, not having mirrors (that's "just" a 40-50% cut for almost nothing actually useful on 512 cockpit display size). The real features I have to "disable" are AI units, any kind of even remotely heavy scripts in the miz and especially multiplayer. My experience roughly is resembled by this video. Wouldn't exactly call that "stable" either, but I guess they won't release a new product Early Access into a version (read: 2.7) that isn't even on Stable yet. And TBH it could be worse. It will keep improving after all and there's a reason most of us stay on OB anyway, so we wouldn't really care about another Stable release anyway. It's more like "oh, you guys finally have catched up once again, well cya!"

You clearly forgot the Apache preorder opening there And maybe they'll finally drop the "eagerly awaited module" which, as per BN, has never been teased before (so it can't be the Apache as there have been screenshots of a blk 49 way back in 2007 already)

Where's that info from? I was kinda expecting a flying/hover/navigation video as well.

You didn't get what I wanted to say there. I totally would want to have the GPU load maxed, but my CPU's single core performance is totally insufficient to make that happen. Which is why I can crank the graphics settings to whatever I like without impacting fps at all as the GPU never hits its limits even remotely.

Worst thing about the Elite controller is that it doesn't have a gyro sensor. MS had that back in 1998 with the Sidewinder Freestyle Pro. Flying things with that worked very well and actually was quite fun. But I mainly used it for space sims like Freespace or XWA. But having a controller for DCS is better than nothing. And when you'd get a stick or HOTAS later, you still have something that you can map things to. Slewing TDCs with the analogue sticks isn't too bad actually, just not a true HOTAS setup.

TBH I haven't seen any on my 3rd gen stone age rig. And I even cranked the clouds up to Ultra without any performance difference. Didn't check my GPU load though... but I couldn't care less as long as it's well even below 50%... but I only had one flight so far with the latest ver.

Legend has it the Viper is viping

This is exactly what made me raise the question since every info I can find on the 408 is that it has 23500-23800lbf of thrust, but the chart basically has it limited to 21000lbf just like you said. Something's clearly weird here.

Wait - my CV1 and Quest do basically have that thanks to their Pentile Matrix...

You're absolutely right here. It's basically a countdown to take the engine out of the airframe for maintenance. And one thing many sims "like" to do is instantly start damaging the engine or at least reducing its performance as soon as you're past the clock at a given power rating. So basically if the manual says 5 minutes is allowed at a given setting, you'll damage the engine for sure if you run that for just one second longer. And that's certainly not realistic at all. It's a guideline (or restriction) to keep the engine in shape for a while, but exceeding it (if not excessively) should not inflict damage at all, but you'd get some nice words from your mechanics after a sortie, and probably your boss as well... As for the relearning, a lot is done now by switching water injection to TO. At a certain point it kicks in and lowers the JPT significantly so it's possible to output more thrust even within the 640° safe margin. I guess it's actually worth now keeping the water for that instead of trying to lighten the thing up. I usually didn't use the injection at all if it was not needed (basically with total weight somewhere below 20-21k lb) prior to the change.

Is there a chart somewhere that shows the actual thrust at different rpms? Would be easier to understand things with that. I'm aware though of the thrust not being linear with rpms. But it's hard to imagine 109% being 23800lbf while 105% would just be somewhere around 16500lbf. But I might be wrong with the assumption of 23800lbf being max. dry thrust. Which is why I'd like to see a power chart. Nevertheless... ... I now think you got me. I was following the parallel lines at the bottom section down to the scale, beginning on the 15°C line. Guess that was wrong and might have been the error RAZBAM had in there as well before the change, because... ... I was using the 408 chart, but prolonged the rpm scale to the left outside of the drawn area. And with what probably was my error, following the parallel (diagonal) lines down to the scale from the 15°C line on, I ended up at roughly 92-93%. By just going straight down, I indeed see the ~105% there. So basically, it must be a total coincidence that the error I assumed Herby made brought about the same error in there as the one I made at the other end Supposedly I have to relearn things now... I always kept the thing below 640°C JPT because it instantly starts to deteriorate power with more than that after just a few seconds. Well, RAZBAM probably should revisit their engine stress damage modeling. It's basically raising the JPT depending on how far you're over the max continous temp which is 645°C. With that, the limit comes down which results in a loss of thrust basically. There's an "Engine Life Count" chart right after the limits table they probably should realize in the module and determine possible damage based on that. Also, I couldn't make out any difference with the LIDS and/or having dumped all the water. I guess that should be noticable.

The M2000 is just over 2.5GB on my system. When I briefly tried 2.7 it downloaded an additional 36GB of data on top of what was already installed, but your mileage will vary depending on how much content you have installed. Personally, I would not recommend 2.7 beta in VR. The new clouds have too many issues and it ends up looking crap. Wait for the full release version instead. If you can somehow free up enough space for 2.7 (and do the update which needs more while it's installing), you should do it anyway. Even with the issues the clouds are way better than before and it's still possible to fly without, although some might consider that a heresy now BTW you could offload some contents like a few maps to another drive by moving them (from DCS World\Mods\terrains) to another place and create a junction that points to that other place with this tool: https://schinagl.priv.at/nt/hardlinkshellext/hardlinkshellext.html With that the system and DCS still see the files on the SSD within the folder structure while they actually are on another drive, being able to access them (r/w) just as if they were still on the SSD. You could even move complete games to somewhere else with that, just leaving the junction pointing to them and everything keeps working. I've done that a lot in the past when my SSD space was too limited, always having an HDD with offloaded games in the rig as well.

I use Acronis as well for backup images and cloning, but I've also done it with "dd if=src of=dst" on some systems with an Ubuntu Live image already, but that took way much longer. Didn't know there were actual multiport docks that are able to clone though. Great advice, I might end up getting myself one of those as it's great to be able to clone a drive without having the rig tasked with doing so (with all the "please don't crash", "I won't play anything while it's transfering just to make sure" shenaningans) for a long period of time. As for DCS, if you'd simply add another drive, you can just copy/move it over completely, correct the shortcut links on your desktop or whereever you have them and you're done. Luckily, DCS doesn't grow roots into the Windows registry...

Having noticed the change just recently, and having checked that chart myself as well, I think I found the error both you and RAZBAM made. Just think about it for a minute. The 408 puts out 23800 lbf of thrust, probably at 109% fan RPM ("maximum thrust", which is dry) and 710°C JPT which is limited to a usage of 15 minutes. (Fig 4-2, pg 4-5). TBH I don't know if that's maybe the maximum dry or wet thrust for the short lift settings. Anyway, there's also the LIDS and the fences, adding effectively around 1k lbf to the hover thrust helping the lift-off and hovering at low altitudes near the ground (I think that isn't modelled as I haven't benn able to tell a difference with LIDS on or off, except for visually the front fence coming down or not). Now just imagine that 23800 lbf pushing a 16500lb jet up. TWR is 1.44 at this point. No one can tell me you need ~ 105% fan RPM to be able to lift off. Because of that, I tried to understand how you got to that 104-106% value which would be needed for hovering (not lift-off which has ground effect and the LIDS lowering the required thrust!). I quickly found out what made the difference: You picked your TO weight at the far left of the table and then immediately followed the roughly parallel diagonal lines until you hit that 29.92 ISA line, then went right to meet the datum line (no fan RPM correction), then down to the 15°C ISA line, following the diagonal parallel lines down to the fan RPM scale. And yes, this is roughly the RPM needed to lift-off now on a standard DCS day -5°C (to match ISA, standard DCS is 20°C). The thing is: You missed out on one thing: Right at the beginning you have to set your starting point with both the weight and the air pressure / altitude and then go to the 29.92 line diagonally accordingly. By starting out on the far left like you did, you assume ISA conditions, but trying to take off from 6000 ft pressure altitude. Now if you correct that error and start out directly on the 29.92 line at 16500 lb, you'll roughly end up at a required fan RPM of around 92-93% - which pretty much is what was needed for that weight before RAZBAM changed all of this. So basically, they had it just about right before 2.7.0.5659. It was possible (with wet TO power) to lift-off considerably decently with weights of up to ~ 22000 lb and it was easily possible to do so with 3000 or less lb of fuel with a clean airframe, without even exceeding 103% / 640°C JPT. That's basically impossible now even with just 1% of fuel (and set to unlimited), which is slightly less than 15000 lb TO weight. That can't be right. BTW I'd love to show this visually directly on the chart, but 1.16... if needed I might try to draw a rough sketch of it to make it easier to understand. Just as a side note, the other changes made to the thrust seem reasonable though, as I was able to get to ~ M .089 at 31k (numbers I could find are 0.91 max, so it's within a margin of 0,02 - but I couldn't find the actual altitude for max speed) and around 0.87 on the deck (numbers I could find say 0.85, again within a margin of 0.02). Before the change I could get the thing a bit faster, but mostly get a lot more of acceleration out of the engine, but also with a lot more FF which was unbelievably high at that point and now seams more reasonable again.

Exciting update! I'm wondering about the BLG-66 though which hasn't been updated yet and it still acts just like an ordinary CBU. I'd appreciate that being addressed as well

I use the VR controllers since the mouse cursor often hides outside the peripheral vision and I hate having to find that thing again before being able to use it. With the controllers, I just point at things and flip the switch, done. But I have to say, I like the way that other civil sim does it with the mouse, which basically leaves it at the same position within the cockpit, not locked to the HMD. An option for that probably would be great for those who don't use controllers.

They work perfectly. I'm quite near-sighted with IOLs and got those prescription lenses for my CV1 and Q1. They just have to have the proper prescription values. Basically you need the same as for glasses that are for seeing far.