Eldur

This is where it really depends on ED's core for atmospheric and thermal modeling. Probably the most important and eagerly awaited core changes as the sky and weather modeling is highly important for any decent sim, as well as its effect on various sensor suites. Wasn't aware the MiG-23 has/had IRST... make me want it even more. Just always wanted LNS/HB to make it... If something like the IRIS-T can have an internal database to compare it's picture to, a system like the PIRATE can have that even more. Basically, when the thing actually knows what it sees, it literally can triangulate the range with a little CPU power. The method worked well enough already in WWII, heck, even back in WWI without CPUs at all, submarine warfare heavily relied on that. If a brain can do that, it should be a stroll in the park for a modern computer system. And it'd be completely passive... 0:36 is reason enough to have that System IMHO... and as we've talked Raz already, it's a shame they decided not to model that on the Harrier...

I've read that the EF has some Motorola 68020s for the FCS. Those were in the Amiga 1200 almost 30 years ago... And I remember the NASA trying to acquire some old 8086s for the Space Shuttles in the last few years they still were operated. So yes, it's quite common to rely on things that have been there for a while. I wouldn't go that far Not as fat as a certain Amy though

Literally this. They really moved three steps forward with Flaming Cliffs back in the day, and have even been improving from that point on. The old SFM were kinda bland and dull, but the new Su-25 FM had me blown away and it set the standard it still holds today. I'll celebrate again when the SFMs of the AI get kicked out of the core. These improvements are what DCS really needs and there are quite some vital things like the weather that certainly need such a buff. If ED keeps making such jumps, the future will hopefully be bright.

You might want to use this tool as well: https://schinagl.priv.at/nt/hardlinkshellext/hardlinkshellext.html Go for the junction there.

Just noticed this: When he turns into the sun and is being blinded by it, there's some weird lighting happening to the datalink panel in the upper left. Haven't seen that in the other, already locked lighting issues thread, so here it is. Happens on my end as well.

Just flew the Hornet again yesterday. Those instruments are now almost as hard to read as the Viper's. Totally impossible to use in the Rift without zoom... how could that have been overlooked and even pushed into Stable? Can't capture that on screenshots since they always downscale to 1070p and those look as they've always been, also much less blurry and hazy outside the cockpit. On those I can see terrain landmarks where there's just a thick soup in the actual HMD image. Guess that correlates to the general brokenness of VR in the latest builds... but that has been covered here already: https://forums.eagle.ru/showthread.php?t=279072 https://forums.eagle.ru/showthread.php?t=276066 https://forums.eagle.ru/showthread.php?t=277817

This definately needs some overhaul... especially since by the radar logic in DCS, the earth would be flat...

I've had this for quite some time now and I thought it was kinda related to the abysmal performance of 256. I've got the roll SAS switch mapped to my TMWH throttle unit, but using a Target script that sets most of the buttons to "pulse" so they actually can be mapped as keystrokes without the special 2/3-way edits of the luas. Whenever I flick that switch, it unrealiably does one of those: - ~15% doesn't switch at all - ~5% switches it as required - ~80% switches twice in a row quickly (on/off), so literally no actual effect In other words, the thing is totally useless. I remember it being without issues a fair while ago though. What's up with that? BTW I've seen other switched in some modules do the same, like the RWR PWR switch on the Hornet for example, which had been fixed IIRC (still using a keyboard press though)... I guess that's somehow related to switches with solenoids to them.

It's just doing what has to be done. Chasing the Hairdryer of Doom to kill it with fire :megalol:

I could never deal with that. Anything else than a linear curve setting for TIR was just weird. Mine's set at 4 IIRC (and 8 for that other sim where the tracking is just half as sensitive with the same settings). That way, I'd check six when pointing the nose directly at the left or right screen border. I used the pausing mainly for entering things at zoomed-in view (30° FOV), for usual ops it was stable enough without. That's an important aspect and many don't think about it. I've got the tracker sitting on my monitor, but it's shifted to the left by approx. 15cm / 6" so it'd stare directly at the TrackClip Pro instead of my nose. Definately helps with the dead angles.

What I had done was to completely remove the Pause key mapping from every module (made it something like RShift+Pause instead), and map TrackIR pause to that key. Wasn't comfortable enough though so I ran an Autohotkey script as well, that basically has this in it: With that, holding down the context key (the one in between the RCtrl and RWin) pauses TrackIR, releasing it will make it track again. You could change it to fit to your likings. Bold is the key that's being pressed for momentary pause and italic is the key that's mapped in TIR software for pausing. Might also work on HOTAS with that, never tested as I always could reach that key easily anyway, change the "$AppsKey::" line accordingly: That was taken from PeterP's unchain rudder from trim script for the Ka-50 before that was an option in DCS. Just added the $ to make the function exclusive, overriding the mapping you might have in DCS.

Nothing thereof on the list. And neither word on the thick fog in VR or sorry I dare to say this, the performance. At least we didn't have to wait another 5 weeks for this one again I just hope DCS becomes playable again in VR before the release of the Supercarrier still... oh wait! Caution: The following content is being served with a grain of salt. Just take it like that I see you're literally pulling off a Google (or lately Microsoft) here - if an option that's only being reached by pro users and not directly visible within the GUI causes support tickets, just remove it altogether, won't hurt anyone Actually that won't solve any Layer 8 problems though Was using junctions anyway when I needed that (before that option existed though) TL;DR: Thanks for the unexpected update. Let's see what's in it that is not documented and be happy about that

Just noticed:

Even the Ka-50 is suited for that though, and it's a good training since the thing does have a HUD, similar to the Mi-24, but more advanced. But the Russians apparently don't like TVVs. I've gotten best results myself by trimming the thing for a certain speed (around 200 IAS), enabling FD and then flying the thing with lots of pedal input and collective as well. Trying to get the pitch attitude by collective seems to be smoother and with that you'd be generally rather flying towards your aimpoint as well. Keep the pipper centered on that pitch ladder tape with the pedals, this literally translates to flying the ball. Now in the Mi-8 this is a lot harder because of the basic collimator sight. That's definately something to keep in mind with the Mi-8 as well. Vibrates a lot when slow and the pitch axis is less smooth compared to flying at speeds. I remember from another sim that the AH-64 has that for the rocket pods. The Ka-50 OTOH just has this for the Vikhrs. This discussion: Bill Kerman: Hold my SRB!

Those sliders could be useful for VR since at least the Oculus devices don't allow for any adjustment at all which is a shame. Nothing applies to them and the driver / windows settings are bound to a certain screen as always. But NOT instead of gamma. Leave that be! General rule that's often being defied by the major companies nowadays applies here: More options is always better! Man I do miss my good old ATI Tray Tool, that had the key mappings. Best tool ever. nVidia and the 3rd party tools do literally suck here. But TBH I hate it when I accidently change sliders with the mouse wheel and don't even notice it when scrolling in the few programs where that is implemented. Such a pain in the plot! Needs to be tied to a focus on the slider, so when you click it first, it gets activated, and as soon as you click somewhere else, it won't move anymore. Just like the cursor keys.

Our CPU/GPUs are by FAR more powerful than what's inside a 25yo "teapot" (Litening II is 1995 tech), should be piece of cake even for a PIII. OTOH DCS still can't save a single compressed jpeg image (screenshot) to an SSD without a noticable stutter, but that's most probably a software issue related to the libraries that do the image compression which technically still is stuck somewhere in the 90s even in professional software today, simply because noone actually cares. I see this in literally every game... bad thing about DCS here is that the PrintScreen key is hardcoded regardless of what we map it to in the settings. Raised a bug report on this ages ago, never got acknowledged though. Just for the lols as it's a completely different topic, the Eurofighter's FCS runs on Motorola 68020s, those were in Amiga 1200 and Mac II in the second half of the 80s...

Just hack their govts and leak their private chats. More effective than any weapon nowadays In DCS one JSOW is being misused constantly instead of cracking up bunkers and the other is a nice set of fireworks, but literally doesn't deal any damage at all which is why the first is done.

I just saw one for 1500€ on Amazon a few days ago:megalol: I could slap myself I didn't take a screenshot of that. Was gone just the day after I saw it...

If you're running Oculus, you can open up that one: C:\Program Files\Oculus\Support\oculus-diagnostics\OculusMirror.exe --Size 1024 1024 --LeftEyeOnly --FovTanAngleMultiplier 1.3 1.3 Works for me if I maximize the window then. https://developer.oculus.com/documentation/native/pc/dg-compositor-mirror/ Won't stay in foreground though (there are probably tools that make it do that), but works for streaming.

I was just about to say up the GPU as well and crank the CPU clock up. Your 6700 literally has the same IPC (instructions per cycle) as the 9900k and even the 10x00 models which are just about to be released. Since DCS doesn't use any of the other cores at all (let alone HT which often is recommended to be switched off even), there's literally no benefit from a new CPU except for it running at a higher rate. I don't use any tools at all, just increased the multi within my BIOS/UEFI for my 3570k. Didn't change the voltage though. Now the question is why do you get those spikes? Hard to tell, could be the board or PSU most probably...

There's literally a flight sim "lite" in GE... have you tried using that?

I wasn't even aware of the initially planned 2020 date, so I don't see any problems if it's being pushed back a bit.

The Tomcat is slow, compared to the 111. And I don't even talk DCS, where it is literally on par with the MiG-21...

I'm a simple stallion. I see, I buy.

Two Reverbs Probably spent all the monies on the hardware and now can't afford the modules anymore In my case, it's the other way round... might be worse The fun thing is the sale was supposed to be still going on ATM as per the newsletter that announced it... That's how I understood it and felt a little sorry for you that it just was over...