virgo47

In the meantime, I discovered a problem with another object on the Kola map - and the reason why I mention it is that it seems to depend also on the plane type, which is really strange. I tried the Dover castle with some other planes and it was quite difficult to reliably replicate the results. The suspicion is that it may be CPU bound because of intense collision detection, but it's just a hunch.

I wasn't around when Caucasus 2.0 dropped, but from what I've heard it was originally more detailed but not performant enough, and some buildings were removed - those are all the blurry patches on the map surface that look like low-res satellite image. Perhaps they could at least add some of those buildings back? It would make the map look better. Even in some training mission, "a water tower on your left" (or something similar) is mentioned, and there in nothing there. Those patches look really ugly.

Today I wanted to push myself a bit with a high-performance plane I'm not that familiar with. Sure, there is 5 m/s wind from 270, but still, I'm quite satisfied with my first landing without running over the runway (barely):

I haven't checked MSAA, however, it'd be funny, because I have a feeling that DLSS now ghosts much more. And the radar scan line in F/A-18C is not anti-aliased, it looks more like unaliased+ghosted (but this may be the effect of May 21 upgrade that mentions DLSS, I haven't played F/A-18C for a while). But it's not just this in particular, F2/F3 views also show more ghosting. It's difficult for a common user to track and compare these changes in this kind of technologies - and it may even be impossible if it somehow differs from GPU to GPU.

Ah, Steam, that's it. It's not available in DCS Shop (and I tested logged-out of the shop as well), that confused me.

I was one of those lucky ones who considered one or another module here and there and always postponed, only to be rewarded with the pack of 3. That's true. At the same time, the other modules were offered for a very good discount individually. They probably didn't feel the need to add three more duo-packs. So yeah, the laggards kinda won, but there were options. BTW: Why mention it now? I can't find the pack in the shop anymore.

I found the fix! I normally use MOUSE_BTN3 (middle mouse button) for clickable cockpit toggle (single press), but for whatever reason, it was double assigned also for Camera transpose mode (press and hold). This is the original binding, I'm not sure how it got applied, but after I removed it, the clickable cockpit toggle started to work with a single press as expected. Of course, you still need the Quaggle or something similar for it because it's not provided for the mouse by default (which is a trivial fix for the devs, but often ignored, not just by Mag3). For whatever reason, zoom axis with mouse wheel started to work after this fix as well, I have no idea why. But I'm a happy animal again. Still, Mag3 guys, consider adding at least some useful bindings options for the mouse - without actual bindings, just that the cells in Controls work and are not disabled. Thanks.

Great news! Will there be a separate lock and unlock binding for the latch? Was that the original intention?

Yeah, I don't really mind... and still, I Might Be Wrong (such a great song BTW), but there was nothing clearly describing this in the changlog, so I rather ask. I adapted already to the new version. Thanks for weighing in.

"has begun"

I don't know why I started my tests on Pagan in this map. It really is extremely short, and I didn't understand why some sources mentioned a longer runway, but the one from game more or less matches today's satellite image. So a volcano is to be blamed! Great OP. I'll welcome a few more meters/feet for this strip, it's really on the edge for any warbird.

Ah, good to know about the previous report. I was confused a bit, so I didn't even know what is and what is not the problem. I can't be sure 100%, but I have very systematic binding configs, I track them with Git and also make colourful spreadsheet for them. I didn't see any binding for that lock/unlock in my controls. I'm definitely sure I have to deal with the lever lock in some planes, but again, I'm not sure which they were (probably MiG-15 out the top of my head). But I didn't use this binding before. It works fine after I bound it, so if it's intended to work like this, it's OK. Of course, separate lock/unlock bindings would be nice as well. Maybe it would be nice to have hard-core Gear Up binding where one has to explicitly control the lock and one which would do it automatically. But I'm fine with the hard-core option only as well. (EDIT: I guess this is not necessary, when there is Landing Gear Lever, toggle, which does more or less the same.) I may be wrong (often I am), but I suspect it wasn't needed a few updates ago when I last flew Yak-52. I see a different landing gear bug reported from March, so maybe something was changed around it after all.

I'm not an everyday flyer with Yak-52, but today (after the yesterday's patch), I tried Yak-52 again and couldn't retract my gear. The reason is, that the gear lever is locked. I know I have some bindings for this in other modules, but I don't seem to have any for this one (checked all my configs for it), because it likely worked auto-unlocking until now... I guess? (Unsure.) Then I started to investigate the bindings for the latch and found this (search for latch): Was there a change related to this? Probably in 2.9.15.9408? That's the latest Release notes with anything about Yak-52: DCS: Yak-52 by Eagle Dynamics Fixed. Wrong brakes behavior via axes Fixed. Bindings for Landing Gear EXTEND and RETRACT not working Fixed. Binding for the Emergency Gear Valve backwards Fixed. Rudder by notch input did not move the rudder, causing a crash instead. Fixed. Elevator Trim Keybindings not working Fixed. Incorrect behavior of AI after takeoff and during landing. But nothing quite fits the description. It seems like the Landing Gear fixes broke something. If it was mentioned as realisme improvement, then it's not described properly. How should it work?

I haven't flown CE2 for some time (but I have not long ago), so I can't be sure about the version when this broke... but there is nothing about Christen Eagle in the release notes since the fuel/radio display patch (much welcome!). But now the mouse bindings don't do the right thing. I'm using Quaggles Command Injector with the following settings: {down = 3256, cockpit_device_id = 0, value_down = 0, name = _('Pilot torch light on-off'), category = {_('Lights'), _('Custom')}}, {down = iCommandViewAngleDefault, name = _('Zoom normal'), category = {_('View'), _('Custom')}}, {pressed = iCommandViewCenter, name = _('View Center'), category = {_('View'), _('Custom')}}, {down = iCommandCockpitClickModeOnOff, name = _('Clickable Mouse Cockpit Mode - ON/OFF'), category = {_('General'), _('Custom')}}, ...because your module does not allow binding these things to the mouse for no apparent reason. In the middle of writing this report, I suspected that maybe Quaggle got broken by the latest DCS upgrade (happens occasionally), but I have similar overrides for AJS37 and it works there. So something seems to be broken with the commands themselves in CE2: Zoom axis (mouse wheel) doesn't work (that one is not even handled by Quaggle) Single click to clickable cockpit doesn't work (the fallback default double click does) Zoom normal and View Center seems to work fine though.

I also suspect something like collision detection, and that would make sense to be different for a different plane. But on my part, it's just a guess.