Art-J

Yup, other folks have reported the same Biggin problem in bugs section of this map.

Got it. Strange things happen still. While trying to load your mission for the first time, the game displayed the message that TF-51D module was required as if I didn't have it installed (yet I do). It loaded eventually, but waypoints and radio tabs were still missing, and so were all external aircraft textures for that matter (you chose "bare metal" scheme, didn't you?). What's more puzzling is - when I replaced the plane with payware Mustang, tabs didn't reappear either. Doing slow repair and cleanup procedure now, will see how the game responds later.

That's even more strange. I'll try again later, with all of my mods disabled (although none of the ones I use should affect TF-51, at least not in theory). Attach your mission please, I'll take a look at it if mine ends up being borked. EDIT: Mods turned off, apart from custom skins in Saved Games. No change - can place TF on the map as my plane, but radio and waypoints tabs remain missing.

1. and 2. are probably either caused by this particular carrier mod, or carriers in general. I've just checked ground ops and couldn't replicate any of these issues, rearming all loadout options available and zooming in and out at various prop RPMs. About 3 - well, can't have DLSS or DLAA in PC games without any ghosting. Maybe ED will tweak the game to make it less noticeable, but it will always be there.

Finally had time to do some more flying in latest OB today. Mirrors? Not bad, actually. Screens below. At the same time, I've noticed in cockpit view that pixellation seems to be more motion-induced, rather than angle-induced. It's shows up for me while pitching fast or rolling, but later, when I stabilize the plane at constant pitch and bank angle, it mostly disappears and the image is OK again.

This thread belongs rather to TF-51 section of the forum, but while we're at it there indeed seems to be somthing iffy going on with TF radios in the latest OB version of the game. When attempting to replicate the issue reported above I've noticed that waypoint and radio tabs are completely missing in the editor for TF, while they're there for standard Mustang. Screenshots and the mission file below. @Flappie, can you replicate on your PC? MG.miz

^ Mixed armament was only used on night-fighter variant of -5 so I doubt we will get that one (and neither we should).

No longer required after today's update 1.48111.

Thanks, but I don't have F-16 either, or any modern aircraft for that matter . I forgot, however, that If I've got the got the map I can open the mission file and replace the player's aircraft, and so I did. Screenshots below. As long horizon is level I'm getting some kind-of pixellation of the furthest cloud layers, but nothing as bad as you at close-to-medium distances. Adding any angle to the horizon does make things much worse, though, just like on your screens. We have a bit different gfx settings, but the problem is still there. That's the first time I'v noticed it in 2.9 so I think it might be inherent issue with some of the cloud presets, but I only flew with 2 or 3 of them, so can't say which are good and which are bad.

^ I don't own F-15E so can't check on my PC. What date, time and cloud preset does this mission use so I can try to replicate?

This post kind of belongs in AI bugs section of the forum. AI warbirds in DCS still tend to do weird things after receiving combat damage and that doesn't apply only to A-8. For example, while watching your first track on my PC, that wingman of yours flew half way back to base while being on fire, with a dead pilot, and then it made a perfect approach and touchdown on invisible landing gear. Bouncing tailwheel did follow, but I'd say it's the least troubling observation in this scenario . Screenshot below. Thanks for reporting, though.

@pavelpilot Which cloud prese is it in your 2.9 screens? Or even better - can you attach that mission and your gfx settings? I can't replicate that problem on my 2.9, but I've tried only some of the presets.

I can't check OB installer, as I already have this version on my PC, but Stable installer asks you about destination folder after epilepsy warning screen. Should look like the one below. Are you not getting it with OB? Actually, I recall it's not the first time I see the same issue being posted by someone.

Clearly a missing textures problem. If module reinstall didn't help (which is puzzling, but so be it), I'd also suggest running a file integrity check of the whole DCS itself.

After initial release and testing of MT with mixed results I settled for ST before 2.9 because of bit less stuttery experience. But I do need MT to enable some of new gfx functions, and ST is going to be dropped sooner rather than later anyway so switched to MT for good. In 2.9 it seems to be "good enough" for me.

Ah, so, you've got pilot body option switched on and fly in VR? Got it, I don't use either. As Rob pointed, Sabre has two pre-programmed "head positions" corresponding to seat height adjustment for takeoff/landing and for cruise flight. Both can be enabled or only one of them, depending on special options settings. I guess 3D model of pilot's body was built only with high position in mind resulting in problem you describe. Not much can be done about it I'm afraid, Sabre is a very old module now and no changes to its graphics are being done anymore by ED.

ED always keeps a few older DCS versions on their servers for a while (2-3 months?) before deleting them, so yes, I'm pretty sure you can still convert last stable to the last 2.8.xx build of OB. It should still be available allright. I'm not at my PC at the moment so can't check what powershell (or cmd window) command you need to type, but it will be very similar to the one BigNewy wrote above, just with specific version number added. There's a sticky thread in tutorials section of the forum which explains how to use dcs_updater commands to switch between various DCS versions. Try to find it and follow instructions. Also, If you plan to do such version switching / converting more often, I'd recommend installing Skatezilla's GUI updater utility, which does the same thing via more convenient gfx interface rather than manual typing. Very nice and useful tool.

Ancient mods from DCS 1.2-1.5.xx era are pretty much guaranteed not to work in current versions. Unless Hawkeye60 worked on this one later, don't bother. You can always PM him and ask, however.

Well, yes, the real thing had two detents, kind of. One in form of an outboard push of the lever to engage ignition and pumps, the other was actual idle detent. You can see both animated during startup procedure. It's one of these cases where our standardized joysticks and throttles with single detents just can't match the actual plane setup, unfortunately.

Same here. Folks who want to have everything mapped on HOTAS and love using fancy input macros do use TARGET and good for them. For all the others, stock DCS customization options are plenty. Individual axis tuning was a must when I was using standard length Warthog years ago. I use extension nowadays but still add a bit of curvature here and there in more pitch-sensitive planes like Spit, Thunderbolt, Mossie.

What's installed in Saved Games stays in Saved Games. The game loads shapes and textures from there.

I noticed the same thing when I wanted to recreate nice lighting conditions from Channel P-47 cold start mission in my custom mission on Normandy map. After setting up the same date and hour, what I got was much lower sun position on Normandy (screens below). Just couldn't figure out if Normandy sunset was too early or Channel sunset was too late, but you've put more effort in investigating it. Thanks!

It is Caucasus then. It's the oldest and thus the least detailed map in DCS (albeit the most framerate friendly for the same reason). There are custom mods available to make it prettier. For example Barthek's mod or CGTC mod offer general terrain textures overhaul (which one of them is nicer depends 100% on subjective preferences), while Taz1004 trees mod offers much improved trees. All of them can be found in this section of the forum. Keep in mind, if you're into multiplayer (which I believe is the case if you're coming from WT), you won't be able to use them anyway as they will break file integrity check used by major servers. That appplies to most of the custom mods really. As for comparison with YT vids - the guys who make them just know how to set the mission up for best visuals on the vid - after all that's what their goal as moviemakers is. For example, as in real life, everything looks somewhat flat and oversaturated in DCS when sun is directly above, but adjust mission time to morning or evening ("golden hours"), then add some clouds and the scenery starts to look like million dollars. It's pretty much the same as in every other flight sim, race sim, first person shooter etc. About the sea - add some hefty wind in the editor and there you'll get your choppy surface with whitecaps and all. Throw in some rain for a good measure to get wet flightdeck surface effects. While we're at it, I'd hazard a guess vid makers also mostly use payware Supercarrier module, which I believe features more detail, lights and general eyecandy compared to free Forrestal unit. Latest payware maps also offer better detail than good ole free Caucasus, but that's a given. Free Marianas map is recent and quite good-lookin' though (even for work-in-progress product). As for other naval units or AI planes - DCS, being a 10+ yrs old game, is just a mixed bag here. Some units are old and poorly detailed, some others are new and greatly detailed. All the rest is somewhere inbetween. There are bunch of cool community AI unit mods available as well, but again, they're not really usuable in multiplayer. To sum it up, mission time and weather conditions affect the looks the most. I don't bother with Reshade, when I'm in the mood for scenic hollywood'ish flight I just set the mission up accordingly.

Yes, the method described will convert whatever existing stable version you have into the latest open beta available today.

I recall It's been like this since 2014 when I started DCS'ing. So probably since module release too. Clearly a low priority issue then and not really noticeable unless you're a movie maker. Still, if the old girl got some animation improvements (propeller, muzzle fashes) in recent years, maybe wheels could be tweaked a bit as well?