Vakarian

It does, I've used it ~5 minutes ago. Drag and select, ensure you press Ctrl+C, but give it time it you selected a lot of stuff. Tip, if the timer in the top left corner is not moving, it's still processing the copy command. Once it starts moving again you can open a new mission and paste the stuff there.

It's the "same" thing. One is where they hook into the simulator and "make" their own data to display, the other is where the data is already build and they "stream" it to the display. No where does it say it's capable of an actual video output, that's completely different thing. The "data" that's made is just a font collection(s) that they then display in the correct position on the display, it's not displaying a video.

How sure are you of this? Nowhere in the published data does it say that.

Referencing an object that doesn't exist. It is odd that this wasn't tested, after running an update it breaks. Also, if you attempt to start the app afterwards you get into a loop there app breaks, only way to kill it is via the Task manager.

A really rookie mistake Oh well, hopefully they will rollout a fix quickly, this is literally a few minutes fix

DCS: Christen Eagle II by Magnitude 3 Fixed floating radio and fuel gauge displays Fixed propeller blur effect Can't wait to get home and try this out

You are making it sound like this isn't the case already... Chinook, Apache, F-4, all have ludicrously high texture requirement that basically require people with 16GB VRAM cards to lower the textures a notch to be able to play. So what's the point of creating those super high-res textures if what, few percent of people will actually see them?

Well, it's "the same thing" except pilot and gunner definitions are extracted to a local function.

You've completely missed the point of the statement...

Check special settings, if the trim is in "Central position" mode, when you press trim interrupt the controls stay frozen until you return the physical controller in the central position. Explore other options, Fade In/Out is a popular one

Unfortunately, for me this doesn't create hype, it makes me more and more reluctant to open this thread as multiple times I clicked with interest to see something new and there's just a (albeit nice) picture. Nothing in particular against the dude, but I just got tired of the pictures so this was a way to "clean" the thread from my point of view. That whole page was nothing but pictures. If there would be another thread just for the pics, I wouldn't mind it at all.null

Yes please. Every time I open this thread hoping for someone sharing interesting details on either IRL bird or DCS news, and its just a picture, day after day...

Nope, that happens when you have Easy Comms enabled, then you don't need to tune the radios, you just select the thing and it automagically talks to that station

Oh yeah, that would be really nice. On the other hand, it would be good to be able to select a toggle whether we want to copy things relative or absolute. Sometimes when making multiple flight plans that should have same waypoints, copy/pasting introduces the same offset to all of the waypoints. It's not the end of the world to fix, but it is a slight annoyance. That way it would cover both cases.

Oh yeah, this has been happening for a long time. IIRC it was even fixed for a brief period then it got broken again

Still hoping this gets added to the DCS core one day. With the amount of work done in the background it surely looks like Veco is here to stay for a while

I would guess this is partly also related to what causes the master caution to yell at you when you've expended all AG ordnance, but the wingtanks are still on and you are in CAT III. IIRC centerline fuel tank is still CAT I

It's the inherent problem of the technology. IIRC using some other presets for the DLAA might help with this.

Yeah, not too happy about that, but it could also be poor wording. If the textures are higher res, but normals aren't, that should be fine. Also, it doesn't mention what was the base for the 400% increase figure. But in any case, ED should be really careful not to overdo the textures. It's all fine and dandy to look at the birds while on the ground, but for the 99% of the time, we are in the air, pretty far away. Even when in the dogfights, we are moving by so fast that even 256x256 textures would be good enough for the purpose Please, be reasonable when choosing the texture sizes, there's only so much VRAM GPU manufacturers put on them and it's doesn't bode well if the game requires 1500+ euro cards to be able to enjoy that work.

You know about that meme, "find the difference between these two pictures?" This is in no way different than the current early access model apart from the name and that what you're suggesting would "release" even more barebones modules.

This is an observation that I would like to be checked with someone who has a bit more knowledge on how the APKWS should fly. Main "issue" is that when the rocket is launched, its flight profile makes it fly so it reaches the target from beneath. This is really noticeable when the targets are near co-altitude or higher. If you monitor the launches, you will see that the rocket first flies a ballistic trajectory until it sees the laser. At that moment it's on a pitch down trajectory so it undershoots the target for the most of the flight time and then when nearing the target it pitches up to hit it. The same thing is observed if the laser is on before launch or sometime after the launch. I've made two sessions, one where I was 500ft AGL (set 1) and on the other I was at 1500ft AGL (set 2) in a OH-58D. Targets were placed on the hillside so I can get most of the elevation change with the as little distance change possible. In set 1 all shots were fired with the laser on from the launch, in set 2 rocket was fired first and then the laser was turned on ~3 seconds into the flight. Posted are tacview, track files and the screenshots describing the issue. Here are some of the examples shot from the set 2 ---- There is one really distinct case which highlights the issue (set2Positive550ftDiff). Rocket first comes of the rail and it's climbing. Once it picks up the laser it dives down and then after some time begins to climb to hit the target. That case is the one that tells me that something might be off in the APKWS guidance. If someone can give more info on is this correct or not, I would highly appreciate it. It "seems" to me that somethings aren't quite right, but I'm just a regular dude, closest I've been to a real thing was at an airshows in the crowds If this is how it's supposed to fly, then that's how it is. Tacview-20241222-215108-DCS-APKWSTest-1500ftAGL.zip.acmi Tacview-20241222-205225-DCS-APKWSTest-500ftAGL.zip.acmi apkwsTrajectories.trk apkwsTrajectoriesFartherAway.trk

It's not Retribution/Liberation/Mist/Moose... whatever related. We had a mission in my group the day the Fog patch landed. Mission was made after the patch dropped and had literally this: Dynamic spawns on Wujah and Beirut airfields, 1x SA-8 at Rayak airfield, uncontrolled AI MiG-21s, Su-24s, Mi-8s, few active infantry dudes and 3 static buildings from now in DCS core. No mods, pure 100% vanilla DCS. Some of us still experienced flickering.

Nope. As soon as you introduce delta, the entire flightplan changes. EHSI and the HUD will continue to show nav data to the now offset points because they just show the info how much away is the current point. The system doesn't know that your intention isn't to navigate to the offset points. If you had for example Steerpoint 7 on the threshold of the airfield, before you have done some TGP work and found some targets (it's irrelevant how) and you didn't CZ, when you start flying back to the airfield you will notice that the steerpoint is no longer at the threshold, but the system is guiding you to the offset position of the Steerpoint 7. That is precisely why after every engagement you have where you targeted something (moved the SPI away from the steerpoint/markpoint...), CZ and then try find another target.

Linking for context

I've seen this not only in the Viper but also in Kiowa and in the Apache. On a hunch, it could be the DCS VoIP related thing but I don't have any conclusive evidence to show, only that I've experienced it in multiple modules.